AI-SRVR ARCNET Server to Ethernet Client Software Manual # TD000200-0MC
Trademarks BASautomation, Contemporary Controls and CTRLink are registered trademarks of Contemporary Control Systems, Inc. BACnet is a registered trademark of the American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. Powered by Sedona Framework is a trademark of Tridium, Inc. Other product names may be trademarks or registered trademarks of their respective companies. Copyright © Copyright 2014, by Contemporary Control Systems, Inc. All rights reserved.
1 Table of Contents 1 TABLE OF CONTENTS........................................................................................... 3 2 HISTORY ................................................................................................................. 4 3 INTRODUCTION ...................................................................................................... 4 3.1 4 Product Images .................................................................................................
2 History 2/1/2005 Initial Release 7/1/2006 Expanded LED and Proxy functionality 7/1/2014 Added TCP timeouts, Hostname and expanded Server functionality 3 Introduction The AI-SRVR employs a CPU (running the Linux operating system) to perform as an ARCNET Server to an Ethernet Client. There are several models which offer different transceiver options. The AI-SRVR-1/CXB accommodates coaxial cabling at a data rate of 2.5 Mbps. The AI-SRVR-1/TB5 has an RJ-45 port for dipulse signals at a rate of 2.5 Mbps.
3.
4 Operation 4.1 General Considerations Configuration is accomplished while the AI-SRVR is connected to a suitable device, either a computer terminal or a computer running a terminal emulation program such as HyperTerminal or PuTTy. The connection is made via the AI-SRVR serial port (console port) which uses standard EIA-232 protocol. 4.1.
4.1.4 Access Options The AI-SRVR can be accessed through its Ethernet port or its console (serial) port. Initially, the unit must be configured so that its IP address is set to a value placing it on the same subnet as that in which it is being installed. The simplest way to do this is via the console port. If a null-modem cable is not available, the unit can also be configured via its Ethernet port and a Telnet session as described in Section 4.1.4.4. 4.1.4.
A Telnet session requires a login procedure as displayed in Figure 2. The default login string is “root” and it is echoed on screen. The default Password string is “ccsi2431”, but it is NOT echoed on screen. If the login is successful, a Linux bash prompt is displayed. From the bash prompt, two commands enable the user to choose the operational function. These commands are config-srvr and config-proxy. Figure 2 — Telnet Login Screen 4.1.4.
For initial configuration, the computer chosen for the procedure should temporarily have its IP address modified as shown in Figure 4 — which uses a Windows 7 example. Figure 4 — Changing the IP Address of the Computer Used for Setup The example in Figure 4 suggests an IP address for the computer of 192.168.92.69, but the final quad of the address could be any value from 1 to 255 — except for 68 which is used in the AI-SRVR’s default IP address.
4.1.4.5 Web Browser Access (Read Only) Although the AI-SRVR must be configured via either its console port (Section 4.1.4.2) or via a Telnet session (Section 4.1.4.3), statistics can be monitored by a web browser run from any Internet-capable computer. The AI-SRVR is factory-programmed with a default IP address of 192.168.92.68 and a Class C subnet mask of 255.255.255.0. Changing the IP address is strongly encouraged. A sample statistics page appears in Figure 5.
4.2 AI-SRVR Function 4.2.1 AI-SRVR Statistics Screen (Read Only) When the AI-SRVR Function is initially invoked, the default AI-SRVR Statistics screen of Figure 6 appears — presenting information in 8 data fields. Figure 6 — AI-SRVR Statistics Screen (Read Only) On the left side of the screen, 5 ETHERNET fields are reported: IP Address reports the currently assigned IP Address of the AI-SRVR. Clients lists how many Ethernet clients are connected to the AI-SRVR.
The screen of Figure 6 offers three case-insensitive options: R forces an immediate refresh of the screen. Otherwise, the screen refreshes itself automatically every 10 seconds. S opens the Setup Screen for configuration (Section 4.2.2). C resets all 4 packet counters. 4.2.2 AI-SRVR Configuration By pressing “S” from the AI-SRVR Statistics Screen, the default AI-SRVR Configuration Screen of Figure 7 appears to allow control of 16 parameters.
All fields in the centre and right columns of Figure 7 require numerical values: IP Addr is 192.168.92.68 by default. Defining a new address before placing the unit into service is highly recommended. Netmask is the subnet mask — 255.255.255.0 by default. Gateway is 192.168.92.1 by default. If your Ethernet LAN does not have a gateway, set this value to 0.0.0.0. DNS #1 is the IP address of the chosen Domain Name Server (if one is desired at all). It is 0.0.0.0 by default. DNS #2 is 0.0.0.
Then, the Hostname field should be modified if desired. Next, the BRIDGE fields should be configured. The Node ID can be any value from 1 through 255 so long as the designated value is unique within the ARCNET network to which it belongs. Speed can be set to 156kbs, 312kbs, 625kbs, 1.25Mbs, 2.5Mbs, 7.5Mbs or 10Mbs. The 7.5Mbs option is not recommended, but it is provided if a special need exists. * NOTE: The TB5 and CXB transceivers only support 2.5 Mbps. The 485X transceiver only supports 1.25 Mbps, 2.
Keepalive Probes is the number of retransmissions to be carried out before declaring that the remote end is not available. TCP Retries tells the kernel how many times to retry before killing an alive TCP connection. TCP FIN Timeout tells the kernel how long to keep sockets in the state FIN-WAIT-2, if you were the one closing the socket. This is used if the other peer fails to close its side of the connection — perhaps because the other peer crashed.
4.3 AI-PROXY Function The AI-SRVR offers a function called “AI-PROXY”. This function allows an ARCNET node in one LAN to communicate with an ARCNET node in another LAN through an Ethernet backbone link that can be either wired or wireless. A communication path between two ARCNET networks requires two AI-SRVR units, each serving in one ARCNET LAN as a proxy for a remote node in the other LAN. Each AI-SRVR-1 can act as proxy for only one node as shown in Figure 8.
The AI-SRVR-1 and the AI-SRVR-8 can be used together — for example, to add a remote ARCNET node to an eight-node ARCNET system as shown in Figure 10. Figure 10 — AI-SRVR-1 and AI-SRVR-8 Can Work Together The AI-PROXY concept requires each local proxy represent a node in the remote network by assuming the Node ID of the remote device being represented.
4.3.1 AI-PROXY Statistics Screen (Read Only) A sample AI-PROXY Statistics screen appears in Figure 11. The 3 upper ETHERNET fields and the ARCNET RX Packets and TX Packets fields serve the same function as in the AI-SRVR — as do the R, S and C commands. However, the AI-PROXY screen differs from the AI-SRVR screen in the following ways: The PROXY Status field replaces the Server Status field of the AI-SRVR. Whenever the AI-PROXY software is running, this field will report ONLINE.
4.3.2 AI-PROXY Configuration The AI-PROXY configuration screen differs from that of the AI-SRVR in that five fields have been deleted and two fields added. The default screen is that of Figure 12. The fields present in the AI-SRVR screen but missing from the AI-PROXY screen are: Node ID (Instead, the AI-PROXY uses the Node ID List field.) Receive All (Promiscuous mode is not used in the AI-PROXY.) Tx Enable (In Proxy mode, Enable.) FIFO Depth (Mailboxes are not used with AI-PROXY.
EXAMPLE: Figure 13 shows how (using sample values) the fields of an AI-SRVR-8/CXB might be configured in AI-PROXY mode. Only those fields that have had their default values changed are discussed: Boot Protocol has been set to DHCP. Hostname has been set to AISRVRa2. IP Addr DHCP server has assigned 10.0.0.22 to this proxy unit. Gateway has been set to 10.0.0.1. DNS #1 has been set to 159.50.0.1. Remote Proxy IP’s has two entries for proxy units outside the local subnet.
