48,1;&RPPXQLFDWLRQ3URGXFWV

48,1;&RPPXQLFDWLRQ3URGXFWV EtherQuinx Token Quinx EtherQuinx Mini EtherQuinx 19 Rack Version User s Manual Technical Reference

Table of Contents Introduction 1 Applications 1 EtherQuinx Interfaces 3 Serial Interface 3 Customer specific Versions 3 Network interface 3 Hardware Address 3 Power Supply 4 Network protocols 7 Packing Algorithm 7 Channel Identification 7 IP-address 7 TCP port number 7 Configuration 8 Network Configuration 8 IP address first-time setting 8 Serial configuration 8 Configuration Parameters 8 Basic Parameters 8 Locally Administered Hardware Address 9 IP address 9 Gateway IP address 9 Netmask 9 Telenet Config Password 9 Channel-specific parameters 9 Baudrate 9 Interface Mode 9 Flow control 10 TCP port number 10 Remote IP address 10 Remote TCP port 10 Connect Mode 11 Automatic Connection Address 11 Disconnect Mode 12 i

Force Telnet Mode 12 Buffer flushing 12 Inactivity timeout 12 Send characters 12 Telnet Terminal type 12 Exit Configuration Mode 13 Monitor mode and Firmware upload 15 Monitor commands 15 Firmware download serial 15 Distribute Firmware 16 Firmware download from host 16 Serial Line interfaces 17 Connector pinout RS-232C, Chan 1 17 Connector pinout RS-232C Chan 2 17 Connector pinout RS-422/485 18 Line interface description 18 Application examples 21 ASCII Terminal to Host for Login 21 RS-485 2-wire prolongation over network 21 Telnet Server for Device Management 21 Connection of a printer 22 LED status display 23 Yellow and green LED 23 Red LED 23 Technical data 25 CPU, memory controllers: 25 Serial interface 25 Network interface 25 Power supply 25 Power consumption: 25 LEDs 25 Case 25 Dimensions 25 Weight 25 ii

Appendix A - 19 rack mount version 27 Description 27 Front panel schematic 27 LED functions 27 Serial RJ-45 connector pinout 27 Interface selection 28 Appendix B - Token Ring specific 29 Additonal information for Token Ring Versions 29 Token Ring simulator 29 Appendix C - IP Addresses, Netmask etc 31 IP Addressing 31 Class A network 31 Class B network 31 Class C network 31 Network Address 31 Broadcast Address 31 IP Netmask 31 Private IP networks and the Internet 32 Network RFC s 32 Appendix D - Bit to HEX conversion 33 Bin/DEC/Hex table 33 Index 34 iii

Introduction The EtherQuinx is designed to connect peripherals with a serial interface to an Ethernet or Token Ring Network using the TCP/IP protocol family. Various peripherals can be interfaced, for example: Applications terminals of all kind, time/attendance and data collection devices, CNC controllers, industrial robots, data display units of all kind, instruments, printers and modems. Depending on the model used, EtherQuinx s have different network interfaces. Introduction 1

EtherQuinx connects the peripherals through a transparent TCP data channel or a telnet connection to computers or even another EtherQuinx. The Network interface speed is 10Mbit for the Ethernet models and 4 or 16Mbit for the Token-Ring version. The EtherQuinx is available with various interfaces to connect the peripherals: Introduction 1

EtherQuinx Interfaces Depending on the model, the EtherQuinx supports different types of interfaces for the connection of the peripheral device and the different network topologies: Serial Interface EtherQuinx External Ethernet and Token Ring: 1 x RS-232/RS-422 interface (channel 1), software selectable, including RS- 485 2-wire support, up to 115kBaud, SubD25 female connector 1 x RS 232 interface (channel 2), up to 115kBaud,SubD9 male connector Connector Pinouts: please check in the Appendix EtherQuinx 19 Rack Version, Ethernet 2 x RS-232/RS-422 jumper selectable, 38.4kBaud, RS-485 2-wire possible EtherQuinx Mini, Ethernet and Token Ring 1 x TTL 3-wire (RxD and TxD only) serial interface, 19.2kBaud, Customer specific Versions On request, special hardware and software can be developed to support whatever is needed by the customer. Examples are: CAN-Bus Interface, synchronous Interfaces, PPP network connection etc. Network interface All Ethernet Models support 10Mbit, all Token Ring models 4 and 16 Mbit network speed, switch or jumper selectable. Token Ring source bridge routing and the setting of an administered address is fully supported. Hardware Address Network Hardware Address The hardware address of a EtherQuinx can be calculated from the serial number and type: First three bytes are fixed, and read 00-20-4A Fourth byte is the type of the unit: beeing 01 for EtherQuinx Mini 02 for EtherQuinx External Ethernet 08 for all Token Ring models Fifth and Sixth bytes are the serial number in hex notation. Example: EtherQuinx Mini, serial #101-161: 00-20-4A-01-65-A1 EtherQuinx Interfaces 3

Depending on the model, the EtherQuinx supports different types of physical network interfaces. The following list gives model-specific information EtherQuinx External Ethernet 10BaseT (RJ-45 Connector) and AUI (SubD 15 Connector) for connection of external transceivers EtherQuinx 19 Rack Mount Version (Ethernet) 10BaseT interface (RJ-45 connector on front panel) EtherQuinx Mini, Ethernet Version 10BaseT interface (jumper strap) optional AUI port (12V power, some passive components required) EtherQuinx External Token Ring STP and UTP interfaces (SubD9 and RJ-45) Ring speed (4/16Mbit) switch selectable from outside of EtherQuinx. EtherQuinx Mini, Token Ring Version STP and UTP interfaces (jumper straps) Power Supply Depending on the model, the EtherQuinx has different power supply needs. In the EC (230VAC) and USA (110VAC), the EtherQuinx External models are shipped with an AC power adaptor. EtherQuinx External Ethernet and Token Ring Require 13-18V AC or 15-20V DC (polarity unimportant), power consumption varies with connected transceivers, phantom current etc. Typically, the ethernet version consumes around 250mA with the 10BaseT interface activated, while the Token Ring version needs about 400mA at 15V (including phantom drive). EtherQuinx Interfaces 4

EtherQuinx 19 Rack Mount Version Quinx needs +5V, 500mA and +12V and -12V about 100mA regulated. Consumption highly depends on the serial interface activated. EtherQuinx Mini, Ethernet and Token Ring both need only 5V regulated. The ethernet version drains typically less than 250mA while the Token Ring Version needs up to 800 ma. EtherQuinx Interfaces 5

Network protocols The EtherQuinx family uses the TCP/IP protocols for network communication. The supported standards are: ARP, UDP, TCP, ICMP, Telnet, TFTP and SNMP, (NTP for the Radio Clock option). For the transparent connections, TCP/IP (binary stream) connections or the Telnet protocol is used. Firmware updates can be done with the TFTP protocol. The IP protocol defines addressing, routing and handling of data blocks over the network. The TCP is the transmission control protocol, assuring that no data is lost or duplicated, and that everything sent into the connection on one side is arriving at the target exactly as it was sent. For typical datagram applications, where devices want to interact with others without maintaining a point to point connection, UDP is used (customer specific versions and Datagram mode). Packing Algorithm Channel Identification IP-address TCP port number The two available packing algorithms (which define how and when packets are sent to the network) are selectable by software on a per-channel base. The standard algorithm is optimized for the applications where the Ether- Quinx is typically used in a local environment, giving very small delays for single characters while trying to keep the packet count low. The alternate packing algorithm minimizes the packet count on the network, and is especially useful for applications in routed WAN networks. The EtherQuinx has one IP Address. The specific channel is selected by the port number, which must be unique. Every device which is connected to the TCP/IP network must have a unique IP address. This IP address is used to reference the specific device, for example to build up a connection to a serial port. See Appendix C for a complete description of IP Addressing. Every TCP connection is defined by the two peer IP addresses, source and destination port number. These port numbers are necessary to address different applications or channels on a network host. The port number can be compared to an extension on a PBX system. Example: The Telnet application (login to a host with an ASCII terminal) is commonly assigned TCP port number 23. More than one Telnet connection can be established to one host to the Telnet port; however, the other peer IP address/port number combination must be different. In the EtherQuinx, a different port number for each channel must be configured. Port 9999 (decimal) is used for remote configuration. Network protocols 7

Configuration The EtherQuinx can be configured by various methods, remote or locally. To configure locally, access to the first (or only) serial port and an ASCII terminal or terminal emulation is necessary, while configuring over the network uses a PC or other computer with a telnet client. The EtherQuinx configuration is stored in nonvolatile memory and is retained without AC power. The configuration can be changed any time. The Ether- Quinx performs a reset after the configuration has been changed and stored. Network Configuration IP address first-time setting To configure over the network, a Telnet connection to port 9999 must be established. If the IP Address of the EtherQuinx is not known or undefined, the following procedure sets a temporary IP address that the setup over the network can be done: a) set a static route to the EtherQuinx with the desired IP address. You need the serial number of the EtherQuinx to do this. It is printed on the product label and can also be calculated from the serial number (see Network Interface). Command example for win95, to be given in the Dos Box (EtherQuinx External Ethernet, Serial number 100-11 (which is 64-0B hex): arp -s 191.12.3.77 00-20-4A-02-64-0B b) open a telnet connection to port number 1. This connection will fail, but the EtherQuinx will change its IP address to the desired one in that step c) open a telnet connection to port 9999 and set all required parameters. Note: the temporary IP address is reverted after every reset of the Ether- Quinx. Be sure to enter configuration and store the parameters to make the change permanent! Serial configuration An ASCII terminal or PC with a terminal emulation is connected to the first serial port of the EtherQuinx. The terminal (or PC) is configured to 9600 Baud, no parity, 8 bit, 1 or 2 stop bits. To enter configuration mode, the power supply of the EtherQuinx must be cycled (powered off and back on). After power-up, the self-test begins. About half second later the red LED starts dashing. Now three lowercase x characters must be sent to the EtherQuinx. These characters must all be sent within about one second to start configuration mode. Note: The easiest way to enter the configuration is to hold down the x key at the terminal(emulation) and then powering the EtherQuinx. This will ensure that the x characters will arrive in time Configuration Parameters After configuration mode is entered (confirm with <CR>), the parameters can be changed, default values can be confirmed with the enter key. After finishing the parametrization, the parameters must be stored, and the Ether- Quinx does a reset. Basic Parameters To change the basic parameters, press 0. The following values can be set/changed: Configuration 8

Ethernet interface Ethernet Interface AUI (N)# This parameter is used to select the network port on the External Ethernet Model (10BaseT or AUI) Token Ring interface Locally Administered Hardware Address IP address Gateway IP address Netmask The Token Ring network interface speed is set by means of a switch, and cannot be set with software. The Token Ring locally administered hardware address can be set here. This parameter should not be used without consulting the system administrator of the Token Ring LAN. IP address : (000).(000).(000).(000) The IP address must be set to a unique value in your network. Please refer to the literature mentioned in Appendix C if you are not familiar with IP addresses. If the EtherQuinx is set to an address which is already in use, it will display an error code with the LEDs and will not connect to the network. Set Gateway IP Address (N) The router/gateway address is needed to communicate to other LAN segments. The default gateway must be set to address the router which connects these segments. This address must be within the local network. If in doubt, the network administrator should be consulted. By entering a netmask, it is possible to define how many bits from the IP address are to be taken as the network part and how many bits are to be taken as the host part (reminder: Standard class A 8/24 (net/host), class B 16/16, class C 24/8 bits). If set to 0, the standard netmask appropriate for the actual IP address is used. Appendix C covers the calculation of the right value in detail. The EtherQuinx prompts for the number of host bits, and then calculates the netmask. It is shown in standard format ( 255.255.xxx ) when the parameters are displayed. Telenet Config Password Channel-specific parameters Baudrate Interface Mode The Telnet Configuration Password can be set to disable unauthorized access to the setup menu through a telnet connection to the setup port (9999). For the Setup through the serial port, it is not necessary to enter the password. The parameters for the communications channel(s) are set by selecting the appropriate channel in the main configuration dialog (1 or 2). The Baudrate can be set within the defined limits (model dependent, most models 300 to 19200 or 115k Baud). Note: 115 kbaud is entered as 150 The line interface (I/F) mode is a bit-coded Byte with the following meaning. It is entered in hexadecimal notation. Configuration 9

Function 7 6 5 4 3 2 1 0 RS-232C 0 0 RS-422/485 0 1 RS-485 2-wire 1 1 7 Bit 1 0 8 Bit 1 1 No Parity 0 0 Even Parity 1 1 Odd Parity 0 1 1 Stopbit 0 1 2 Stopbit 1 1 Quinx Often used settings: RS-232C, 8 bit, no parity, 1 stop bit = 4C RS232,n,8,1 RS-232C, 7 bit, even parity, 1 stop bit = 78 RS232,e,7,1 RS-485 2-wire, 8 bit, no parity, 1 stop bit = 4F RS485,n,8,1 RS-422, 8 bit, odd parity, 2 stop bits = DD RS422,o,8,2 The bit combination can easily be converted to the hexadecimal notation necessary for input. See Appendix D for the conversion Tables. Flow control This parameter sets the local handshake method for stopping output. Generally, Flow control is not required if the connection is used to pass a blocked protocol with blocksizes <1k (ACK/NAK protocols and the like) - No flow control:... 00 - XON/XOFF flow control in both directions:... 01 - Hardware handshake with RTS/CTS lines:... 02 - XON/XOFF, pass characters to host:... 05 (XON/XOFF characters not filtered by box) TCP port number Remote IP address Remote TCP port This setting is the source port number in TCP connections, and is the number used to identify the channel for remote initiated connections. The port number must be unique for every channel, and different from 0 and 9999 (Range: 1-65535). In general the port numbers 0..1023 are reserved in UNIX systems for specific applications. It is advisable to use numbers in the range 1000-30000 to avoid potential conflicts (although these are unlikely). If automatic connection mode is selected, a connection is made to this IP address (and the set remote port number). In manual connection mode, the parts of the IP address which are not given are taken from this value. Remote TCP Port ( 00000) : Configuration 10

The remote TCP port number must be set to use automatic connections, and can be set to give a default for manual connect mode. This parameter defines the port number on the target host to which a connection is attempted. Note: To connect an ASCII terminal to a host using a EtherQuinx for login purposes, use the remote port number 23 (This is the Internet standard port number for Telnet services). Connect Mode This parameter defines how the EtherQuinx makes a connection and how it reacts to incoming connections over the network: Function 7 6 5 4 3 2 1 0 Connection acceptance never accept incoming 0 0 0 accept incoming with active DTR 0 1 0 only accept unconditional (if not busy) 1 1 0 Response on serial to connect nothing (quiet) 0 Character response: (C=conn., 1 D=disc., N=not available/unreachable) Active connection startup no active connection startup 0 0 0 0 start connection with any character 0 0 0 1 on serial line start connection with active-going 0 0 1 0 DTR line start connection with CR (0x0d) 0 0 1 1 only manual connection startup ( C + 0 1 0 0 address) Datagram Mode (separate Documentation!) 1 1 0 0 Please refer to Appendix D on how to convert the values to hexadecimal. Automatic Connection Address For each serial port, information for automatic establishment of a TCP connection can be programmed - these are the remote IP address and the TCP port number. If automatic connection is selected, it is necessary that all the parameters are supplied. If manual connection startup is configured (with C + address/port), only the part not supplied in the command string is used. In manual mode, at least the last byte of the address must be supplied. Example (IP address 129.1.2.3, TCP port number 1234 are configured): C121.2.4.5/1<CR> complete override - connection is started with host 121.2.4.5, port 1. Configuration 11

C5<CR> Connect to 129.1.2.5, port 1234. C28.10/12<CR> Connect to 129.1.28.10, port 12. Disconnect Mode Force Telnet Mode Buffer flushing With the disconnect mode, DTR drop can be activated or ignored to end a connection: - Disconnect with DTR drop:... 80 - Ignore DTR:... 00 With another bit in the disconnect mode, the EtherQuinx can be forced into Telnet (terminal) mode and the setup for the terminal name can be enabled: - activate Telnet mode and terminal type setup:... 40 With this parameter it is possible to control the handling of the line and network buffers with connection startup and disconnect. Also the selection between two different packing algorithms is possible. Function 7 6 5 4 3 2 1 0 clear input buffer (line to network) - with active connection establishment: 1 - with passive connection establishment: 1 - at time of disconnect 1 clear output buffer (network to line) - with active connection establishment: 1 - with passive connection establishment 1 - at time of disconnect 1 alternate packing algorithm 1 All functions can be independently selected. Please refer to Appendix D on how to convert the values to hexadecimal. The alternate packing algorithm is optimized for a minimum packet count on the network. The standard algorithm, is optimized for speed, while the alternate algorithm typically packs a data block on the serial line, which consists of up to about 500 characters, into one TCP frame. This is achieved by collecting characters in the buffer until a) buffer is full or b) a predefined character arrives in the data stream or c) a 15msec timeout occurs. Inactivity timeout Send characters Telnet Terminal type With these parameters, an inactivity time can be set. If the set time expires without an activity on the serial line, the connection is dropped. Up to two characters can be entered in hexadecimal representation in the parameters Sendchar. If a character received on the serial line matches on of these characters, it is sent together with any waiting characters immediately to the TCP connection. This is especially useful to minimize the response time for specific protocol characters on the serial line (i.e. ETX, EOT etc.). This parameter appears only if the Terminal type option is enabled by setting bit 6 in the disconnect mode. If set, the terminal name used for the Telnet terminal type exchange option can be set here. Only one name can be entered. Configuration 12

If Terminal type option is enabled, the EtherQuinx also reacts to the EOR (end of record) and binary options and can be used for applications like terminal emulation to IBM hosts (contact QUINX for details). Exit Configuration Mode To leave the configuration program and save all changes, press 9. All values will be stored in nonvolatile (E²PROM) memory, and the EtherQuinx will reset. Configuration 13

Monitor mode and Firmware upload To enter monitor mode, the same principle as setting the parameters is used (see 32 Serial configuration). Instead of entering three x, xx1 is keyed in. The EtherQuinx will respond with a special prompt. A EtherQuinx Tokenring needs a working network connection to enter monitor mode! Because Network functions are needed for some diagnostics commands, it may take up to 20 seconds until the network part of the EtherQuinx is initialized and the prompt is displayed. This is especially true if an empty Tokenring (or a ring simulator) is used. For a simple ring simulator, see Appendix B. To start the monitor mode without network functions, enter xx2 (new function with Version 2.05 and later). Monitor commands The following commands are available in the monitor mode. Many commands have an IP address as an optional parameter (x.x.x.x). If it is given, the command is applied to another EtherQuinx with that IP address. If no IP address is given, the command is executed locally. All commands must be given in capital letters, only blanks (spaces) are accepted between parameters. DL Firmware download to the EtherQuinx SF x.x.x.x Send Firmware to EtherQuinx with IP x.x.x.x VS (x.x.x.x) Query software header record (16 Byte). GC (x.x.x.x) Get configuration as HEX records SC (x.x.x.x) Set configuration from HEX records PI x.x.x.x Check with Ping if x.x.x.x is alive and reachable. QU Quit - exit diagnostics mode Command result codes: 0 OK, no error 1 no answer from remote device 2 cannot reach remote device or does not answer 8 wrong parameter(s) 9 invalid Command Firmware download serial Downloading is done in Monitor mode. Once in Monitor mode, the DL command is given. The node now waits for the firmware image in INTEL HEX format, which must be sent completely through the serial interface. When the end record is received, the EtherQuinx checks the integrity of the firmware image and then starts programming the new firmware in the Flash prom. At that time, it is absolutely necessary not to switch off the power supply! A loss of power while reprogramming the program code will result in Monitor mode and Firmware upload 15

a corrupt program image and a nonfunctional EtherQuinx. The following screen displays a typical screen while programming new firmware. After compete reprogramming, the EtherQuinx restarts. Distribute Firmware Firmware download from host To distribute the firmware of the one EtherQuinx to others, the SF command is used. After entering Monitor mode on the EtherQuinx, simply send the firmware with the SF command to the other devices. It is advisable to check the version of the other devices after reprogramming to make sure the reprogramming was a success. To download a new firmware from a computer to a EtherQuinx, it is necessary to have a TFTP client able to send a binary file. The parameters to send the firmware are: Target filename: 3Q Transfer mode: binary Note: The file to be downloaded must be the.rom (binary) image, not the hex version! File size should be 32768 or 65536 bytes. Typical screenshot: Monitor mode and Firmware upload 16

Serial Line interfaces Connector pinout RS-232C, Chan 1 This Connector is available on the EtherQuinx External Models. Configuration is DCE (modemlike), 25pin female SubD Pin Direction Function 1 Shield 2 to Ether- TxD Transmitted data Quinx 3 from Ether- RxD Received data Quinx 4 to Ether- RTS Request to send Quinx 5 from Ether- CTS Clear to send Quinx 6 from Ether- DSR Data set ready Quinx 7 Ground 8 from Ether- DCD Data carrier detect Quinx 20 to Ether- Quinx DTR Data Terminal Ready NOTE: Please make sure that the other pins are not connected, as there are other signals on the connector, and improper wiring of these pins might damage the EtherQuinx! Connector pinout RS-232C Chan 2 This Connector is available on the EtherQuinx External Models. Configuration is PC-like (9pin male SubD), but signals have different meaning due to DCE function! Serial Line interfaces 17

Pin Direction Function 1 to Ether- DTR Quinx 2 to Ether- TxD Transmitted data Quinx 3 from Ether- RxD Received data Quinx 4 from Ether- DCD Quinx 5 Ground 7 from Ether- CTS Quinx 8 to Ether- Quinx RTS Connector pinout RS-422/485 This connector is the same as the Channel 1 RS-232 connector for the External EtherQuinx Models. Pin Function 1 shield 7 Ground 14 DIN+ 15 DIN- 21 DOUT+ 22 DOUT- Note: For RS-485 2-wire functionality, 14 and 21 as well as 15 and 22 have to be connected together. Line interface description First Channel, RS-232C The following paragraph addresses mainly the Standard EtherQuinx. The serial interface of the EtherQuinx is designed to be used like a standard modem like a DCE (data communications equipment). EtherQuinx transmits data received from the network to RxD (pin 3), and sends data received on TxD (pin 2) to the network. Hardware handshake is controlled by means of the signals RTS (pin 4) and CTS (pin 5, EtherQuinx-driven). The DSR line (pin 6) is active hardwired. If a connection to/from the channel is active to a peer on the network, the DCD line (pin 8) is set active Connection establishment and disconnect can be controlled with DTR (pin 20) Secondary RS-232C Interface The secondary interface (used for channel 2) works exactly the same way as defined for channel 1. Serial Line interfaces 18

RS-422/485 Interface The RS-422/485 interface is designed for two- or four-wire applications (selectable by one bit in the Connect Mode). Only TxD and RxD signals are available. When two-wire operation mode is selected, the EtherQuinx automatically switches off the transmitter after the last data byte and suppresses the echo from the line.etherquinx RS-485 input and output must be connected together externally. Serial Line interfaces 19

Application examples ASCII Terminal to Host for Login RS-485 2-wire prolongation over network Telnet Server for Device Management To connect a DTE (Data Terminal Equipment) (PC, Terminal etc.), a standard non-crossed cable can be used for port 1. Channel one would be configured for Speed, Interface mode (typically 4C, N,8,1), Flow control (Hardware or XON/XOFF). TCP port number would be selected arbitrary (10000 is fine), Connect Mode 01 (Connect with any character, never accept network initiated connections), remote IP Address set to the host, and the remote port number to 23 (telnet service). Flush mode can be set to 80 to select the block-saving packing algorithm, and no buffers are cleared. A disconnect timeout can be set, whereas the DTR disconnect feature would be disabled (00) Two EtherQuinxes are used for this application, one at the local site and one at the remote site. Only Channel 1 can be used because Channel 2 supports only RS-232. Assumed that one device everytime initiates the dialog, the following shows a sample setting: Interface mode is set to what is necessary for this application, typically 7E1 gives 7B (including 2-wire support bit). Flow control is normally not used in these applications (set to 00) Port number can be anything, it is recommended to use the same value for both sides (i.e. 10000) Flush mode should be set to 80, to minimize packet count, unless both EtherQuinxes are connected to a local LAN and transmission delay minimization is a premium. The Send Characters can be programmed to Block trailing Characters (like <CR>) to speed up transmission. Disconnect Mode should be set to 00 The Connect mode can be configured similar on both sides, although it is advisable to declare one side to the master which activates the connection. For the master side, the remote IP address and port number MUST be set, and the connect mode typically is set to 01 (autoconnect with any character, never accept incoming connections), whereas the slave EtherQuinx connect mode is set to C0, indicating it will not build up a connection an accept on the network everytime. It is not necessary to set the remote IP address and port for the slave. If a symmetric setup is desired, both connect mode entries should be C1, and remote IP address and port have to be set on both sides. Management of Workstations, routers and other equipment through telnet sessions is accomplished by defining the EtherQuinx as a telnet server. The EtherQuinx accepts connections over the network and so connects directly to the serial port. It is neccessary to either set the port number to 23 (the telnet service standard) or to explicitly enable the telnet functionality by setting bit6 (hex 40) in the disconnect mode. Recommended settings: Connect Mode: C0 (or 40 if inactive DTR signals that device is not available) Disconnect Mode: 40 (to enable telnet server) Flush Mode: 80 Sendchars: 0A 0A (line feed) Most commonly, the interface mode will be 4C (N81, RS.232) Application examples 21

Example: PC or ASCII Terminal to EtherQuinx Connection of a printer A serial printer is normally wired like a DTE, different meaning of the printerready and flow control line sometimes need a different cabling. In the printer documentation, the necessary information can be found. Depending on the model, the flow control is done with: RTS (standard) DTR (widespread, named Busy most times) TXD This signal goes low if the printer is not able to accept more data (e.g. the printers buffer is full). It must be connected to the EtherQuinx RTS input. Software handshake If a device uses software handshake, it is not necessary to connect the RTS and CTS wires. It may be advisable to jumper the inputs to always active. Printer ready signal If a DTE (printer) has a ready - signal, giving the information that the device is ready for service (paper installed etc.), it can be used to deny the connection if not ready. In this case, this signal must be connected to EtherQuinx DTR signal, and the Connection setup should be set to accept only with active DTR. Application examples 22

LED status display Depending on the model, three LEDs with different colors display the status of the EtherQuinx. Most models also have some network diagnostic LEDs (such as Good Link (GL), Receive (RX), Transmit (TX), Collision (CL). They are labled at the front. Yellow and green LED While the yellow LED displays the status of Channel 2, the green LED displays the status of Channel 1 (the red LED will be off while in normal operation): Stable color: Dashing, 1 sec cycle Channel idle, no connection Connected over the network Red LED If the red LED is on or dashing, the green LED will give a diagnostics code. There is a fatal error, and the EtherQuinx is not working. Red LED stable on, green LED dashing: 1x: EPROM-checksum error 2x: RAM-error 3x Network controller error (Token Ring) 4x: E²PROM checksum error or bad 5x: IP address already used on network Red LED dashing, green LED dashing 4 times: The network connection is faulty. This code should only appear after power up. Even though the EtherQuinx is going into operation mode, the problem will potentially persist. LED status display 23

Technical data CPU, memory controllers: Some values are for the standard external models only! V.40 CPU, 10 MHz clock. Z85C30 SCC Serial Communications Controller. National Semiconductor DP839xx Ethernet Controller or TMS340 chipset for Token Ring Version. 128kByte RAM, 128 or 256kByte Flash PROM. 256 Byte E²PROM for parameter storage. Serial interface Network interface Power supply Power consumption: LEDs Case Dimensions Weight 25 pin D-shell female connector (DCE pinout). Speed software selectable 300 to 115k baud. Software selectable RS-232C or RS-422/485. Second channel RS-232C interface. 15 pin AUI interface (External Ethernet only) for transceiver connection to: Thick Wire Ethernet, Thinwire Ethernet fiber optics Integrated 10-BaseT port (RJ-45 connetor) Power Plug (supplied), or 15-30 Volt DC, 800mA max. max 9 Watt Three LEDs for channel status display Four LEDs for network interface status (Ethernet). Aluminum case, removable mounting brackets 180 x 155 x 40 mm approx. 500g without AC power adaptor Technical data 25

Appendix A - 19 rack mount version Description The EtherQuinx Rack Version is suitable for mounting in 19 racks. Dimensions: board size 160mm x 100mm, front 3HE, 6TE. The EtherQuinx rack version has only a twisted pair ethernet connection. A token ring version is not yet available. The two line interfaces are accessible through two RJ-45 connectors at the front panel. They are changeable from RS-232 to RS-422/485 via jumpers. Power (+5, +12, +12V) is fed through the rear connector (VG32). Front panel schematic LED functions Serial RJ-45 connector pinout The LED functions are exactly as with the standard EtherQuinx. The Status LED is the Red LED. The following figure shows the front view of the RJ-45 connector: 1 2 3 4 5 6 7 8 Appendix A - 19 rack mount version 27

Pin RS 232 RS485 1 Shield GND Shield GND 2 RTS (input) DOUT - 3 RXD (output) DIN + 4 DCD (output) DIN - 5 Signal GND DOUT + 6 TXD (input) Signal GND 7 DTR (input) - 8 CTS (output) Signal GND Interface selection The operating mode of the interfaces (RS-232 or RS-485) is selected for each channel by jumpers - this is neccessary due to the limited pins on the RJ-45 connector. RS-232: Jumper block installed near to the RJ-45 connector (default setting) RS-422/485: Jumper block installed on the opposite position (away from the front panel). Appendix A - 19 rack mount version 28

Appendix B - Token Ring specific Additonal information for Token Ring Versions The following information describes which behaviour is different for the Token Ring versions: Token Ring insertion process needs time When the EtherQuinx tries to enter the ring, exhaustive tests of the ring physical interface are done before opening the loop. These tests take a couple of seconds. After opening the ring, the EtherQuinx waits for a token from a ring master. If there is no other device in the ring, it may take up to 30 seconds until the ring insertion process is completed (and the red LED stops dashing). Token Ring simulator The following schematic defines a simple Token Ring simulator which can be used to test the EtherQuinx Network interface without a MAU. Appendix B - Token Ring specific 29

Appendix C - IP Addresses, Netmask etc IP Addressing Class A network An IP address is a 32 bit value, divided into four octets of eight bits each. The standard representation is four decimal numbers (in the range of 0..255), divided by dots. Example: 192.2.1.123 This is called decimal-dot notation. The IP address is divided in two parts: a network and a host part. To support different needs, three network classes have been defined. Depending on the network class, the last one, two or last three bytes define the host, while the remaining part defines the network. In the following text, x stands for the host part of the IP address: IP address 1.x.x.x to 127.x.x.x Only 127 different networks of this class exist. These have a very large number of potential connected devices (up to 16777216) Example: 10.0.0.1, (network 10, host 0.0.1) Class B network IP address 128.0.x.x to 191.255.xxx.xxx These networks are used for large company networks. Every network can consist of up to 65534 devices. Example: 172.1.3.2 (network 172.1.3, host.2) Class C network IP address 192.0.0.xxx to 223.255.255.xxx These network addresses are most common. Most smaller companies networks are class C networks. These networks can consist of a maximum number of, 254 hosts. Example: 192.7.1.9 (network 192.7.1, host 9) The remaining addresses 224.x.x.x - 239.x.x.x is defined as Class D and is used as a multicast address. Note: No addresses are allowed with the four highest-order bits set to 1-1-1-1. (240.x.x.x. - 254.x.x.x)These addresses, called "class E", are reserved. Network Address Broadcast Address The host address with all host bits set to "0" is used to address the network as a whole (for example in routing entries). The address with the host part bits all set to 1 is the broadcast address, meaning for every station. Network and Broadcast addresses must not be used as a host address (e.g. 192.168.0.0 identifies the entire network, 192.168.0.255 identifies the broadcast address). IP Netmask The netmask is used to divide the IP address differently from the standard defined by the classes A,B,C. Entering a netmask, it is possible to define how many bits from the IP address are to be taken as the network part and how many bits are to be taken as the host part. Appendix C - IP Addresses, Netmask etc 31

Standard IP network netmask: Network bits Host bits Netmask Class A 8 24 255.0.0.0 Class B 16 16 255.255.0.0 Class C 24 8 255.255.255.0 Quinx The number of host bits are entered; the EtherQuinx then calculates the netmask. The netmask is displayed in standard decimal-dot notation. Netmask examples Netmask Host bits 255.255.255.252 2 255.255.255.248 3 255.255.255.240 4 255.255.255.224 5 255.255.255.192 6 255.255.255.128 7 255.255.255.0 8 255.255.254.0 9 255.255.252.0 10 255.255.248.0 11.... 255.128.0.0 23 255.0.0.0 24 Private IP networks and the Internet If your network is not connected to the Internet and there are no plans to make such a connection you may use any IP address you wish. However if you are not connected to the Internet and have plans to connect to the Internet or you are connected to the Internet and want to operate your EtherQuinx s on an intranet you should use one of the sub-networks below for your network. These network numbers have been reserved for such networks. If you have any questions about IP assignment ask your Network Administrator. Class A Class B Class C 10.x.x.x 172.16.x.x 192.168.0.x Network RFC s For more information regarding IP addressing see the following documents. These can be located, for example, on the World Wide Web using one of the directories or indices- RFC 950 Internet Standard Subnetting Procedure RFC 1700 Assigned Numbers RFC 1117 Internet Numbers RFC 1597 Address Allocation for Private Internets Appendix C - IP Addresses, Netmask etc 32

Appendix D - Bit to HEX conversion Bin/DEC/Hex table Hexadecimal digits have values from 0..15, represented as 0...9, A (for 10), B (for 11)... F (for 15). The following table can serve as a conversion chart bin - dec. - hex: Decimal Binary Hexadecimal 0 0000 0 1 0001 1 2 0010 2 3 0011 3 4 0100 4 5 0101 5 6 0110 6 7 0111 7 8 1000 8 9 1001 9 10 1010 A 11 1011 B 12 1100 C 13 1101 D 14 1110 E 15 1111 F To convert a binary value in a hexadecimal representation, the upper and lower four bits are treated separately, resulting in a two-digit hexadecimal number. Appendix D - Bit to HEX conversion 33

Index 19 rack mount version 35 Appendix A 35 Appendix B 37 Appendix C 39 Applications 1 Binary to Decimal Conversion table 43 class A: 39 class B: 39 class C: 40 EtherQuinx Token Ring additional information 37 Configuration 9 Parameters see Parameters serial 10 via telnet 9 Connector pinout 23 RS-422/485 24 Conversion table 43 Decimal to Hex Conversion table 43 Error codes see LED status display Ethernet Interface see Parameters Examples Connection of DTE 27 Connection of printer 29 Firmware download from EtherQuinx to Ether- Quinx 21 from host with TFTP 21 serial 20 Hex to Decimal/ binary Conversion table 43 IP Addressing 39 IP Netmask 40 IP-address 8 LED status display 31 Line interface RS-232 24 RS-485 25 Monitor mode 19 commands 19 result codes 20 Netmask Examples 41 network interface 4 Hardware Address 4 Parameters 10 basics 10 Baudrate 12 Buffer Flushing 16 channel parameters 12 Connection startup 15 Connection Timeout 17 DTR disconnect 16 ethernet interface 11 flow control 13 gateway IP address 11 Interface Mode 13 IP address 11 netmask 12 Remote IP address 14 Remote TCP port 14 send characters 17 TCP port number 14 Telnet terminal type option 18 Token Ring administered address 11 Private IP networks and the Internet 41 remote address 15 RFC 42 TCP port 8 Technical data 33 token Ring interface 11 Index 34

1998 Quinx AG, CH-5732 Zetzwil. All rights reserved. We explicitly reserve the right to change and improve the product without notice. All trademarks mentioned or used are belonging to their respective owners. Quinx is a registered trademark. Quinx AG Hauptstrasse 115 CH-5732 Zetzwil Switzerland Phone: +41 (62) 767 00 40 Fax: +41 (62) 767 00 45 Internet: web: http://quinx.com email: salesmaster@quinx.com