Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC830919); site kvvax4.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!hpda!fortune!amd!decwrl!decvax!mcvax!kvport!kvvax4!roald From: roald@kvvax4.UUCP (Roald Adolfsen) Newsgroups: net.lan Subject: Re: 10Mb Ether for HP-IB? Message-ID: <455@kvvax4.UUCP> Date: Wed, 29-Aug-84 11:52:52 EDT Article-I.D.: kvvax4.455 Posted: Wed Aug 29 11:52:52 1984 Date-Received: Mon, 3-Sep-84 09:11:32 EDT References: <9886@gatech.UUCP> Organization: Kongsberg Vaapenfabrikk, CTG, P.O Box 25, N-3601 Kongsberg, Norway Lines: 57 We have experience with using the Ungermann-Bass IEEE-488 (HPIB, GPIB) interface to the 10 Mbits Net/One (Ethernet). Using this IEEE-488 interface, one can choose between the Net/One (TM) Datagram Interface and the Net/One Ethernet Data Link Interface, both of them makes it possible to transmit Ethernet datagrams from an HP-IB device to any other Ethernet or Net/One device attached to the network. As far as I know, there is some limitations (you have to check them): a. The aggregate throughput of the interface is around 500 kbits/s using DMA (this interface uses DMA in the NIU (TM), and we have used a DMA-based controller to a Norsk Data ND-100 minicomputer) b. There should be only one other device except for the NIU on the HP-IB bus. This user device should be the bus 'controller'. c. Using the Net/One datagram interface, one can only talk to other Ether-devices also using the same datagram interface. This (software) interface is available for various hardware interfaces, for example 32-bits parallell interface (can be connected to DEC DR11-W interface), RS-232-C async serial interface and 8 bits parallell interface. d. Using the Net/One Ethernet Data Link Interface, one can exchange Ethernet datagrams with any Ethernet device, but one cannot talk to these accross Net/One Local- or Remote Bridges. These bridges require that you use the Net/One datagram interface. The experience with the IEEE-488 interface and the 32-bits parallell interface on Net/One Datagram interface is good (at least for software releases later than 11.0 of the Net/One OPS). Datagrams are at least transferred correctly between equal types of interfaces (we have not tried other combinations yet). Both broadcasting, multicasting and absolute addressed datagrams are handled correctly by the NIU (Network Interface Unit) - into which the Net/One IEEE-488 interface fits. BTW - The difference between the Net/One Datagram interface and the Net/One Ethernet Data Link interface is the Ethernet addresses is 6 bytes each, Net/One addresses are 10 bytes each (6 bytes + 4 bytes Network-id) In addition, the Net/One datagram interface provides a 16 bits IP-type field for each of the source and destination processes (of which some of the ranges are reserved for internal Net/One usage), while the Ethernet Data link interface provides one 8-bits type-field for each. Further, datagrams transmitted using the Net/One Datagram Interface can have a length in the range 0..600 bytes, while Ethernet datagrams can have a length in the range 46..1500 bytes (I'm talking about the user data field). Roald Adolfsen {decvax,philabs}!mcvax!kvport!kvvax4!roald A/S Kongsberg Vaapenfabrikk, Dept CTG4, PO Box 25, N-3601 Kongsberg, Norway Tel. (+473) 738556 Tlx. 71491 vaapn n -- Roald Adolfsen {decvax,philabs}!mcvax!kvport!kvvax4!roald A/S Kongsberg Vaapenfabrikk, Dept CTG4, PO Box 25, N-3601 Kongsberg, Norway Tel. (+473) 738556 Tlx. 71491 vaapn n