How it Works
Perle
Loading...
IOAN DS1
User Manual
214 pgs1.85 Mb0

Perle IOAN DS1, IOLAN TS2 User Manual

Download
Page 1
IOLAN DS Family
DS1/TS2 User’s Guide
Version 1.8
Part #5500162-18
November 2006
Page 2
Copyright Statement This document must not be reproduced in any way whatsoever, either printed or electronically, without the consent of: Perle Systems Limited,
60 Renfrew Drive Markham, ON Canada L3R 0E1
Perle reserves the right to make changes without further notice, to any products to improve reliability, function, or design.
Perle, the Perle logo, and IOLAN are trademarks of Perle Systems Limited. Microsoft, Windows 98, Windows NT, Windows 2000, Windows Server 2003, Windows XP, and Internet Explorer are
trademarks of Microsoft Corporation. Netscape is a trademark of Netscape Communications Corporation. Mozilla Firefox is a trademark of the Mozilla Foundation. Solaris is a registered trademark of Sun Microsystems, Inc. in the USA and other countries. Perle Systems Limited, 2004-2006.
FCC Note The IOLAN Device Server has been found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions in this Guide, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his/her own expense.
EN 55022: 1998, Class A, Note
WARNING This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.
Caution: The IOLAN Device Server is approved for commercial use only.
Page 3
Table of Content s
Preface ...............................................................................19
About This Book ........................................................................ 19
Intended Audience..................................................................... 19
Documentation........................................................................... 19
Typeface Conventions............................................................... 20
Online Help................................................................................. 20
Contacting Technical Support.................................................. 21
Making a Technical Support Query ......................................................21
Who To Contact................................................................................. 21
Have Your Product Information Ready .............................................. 21
Making a support query via the Perle web page................................ 21
Repair Procedure....................................................................................22
Feedback on this Manual....................................................................... 22
Chapter 1 Introduction......................................................23
About the IOLAN Device Server ............................................... 23
IOLAN Device Server Models.................................................... 23
Device Server Features............................................................. 24
Hardware................................................................................................. 24
Software .................................................................................................. 24
Security ...................................................................................................25
Supported Products/Versions.................................................. 25
Web Browsers.........................................................................................25
IOLAN Device Server User’s Guide, Version 1.8 3
Page 4
Table of Contents
Typical Applications Summary .................................................25
Managing the Device Server..................................................................25
Managing/Accessing devices attached to the Device Server.............25
Network Security.....................................................................................26
Chapter 2 Installation........................................................27
Introduction.................................................................................27
IOLAN Device Server Components...........................................27
What’s Included ......................................................................................27
What You Need to Supply......................................................................27
Available Accessories............................................................................27
Getting to Know Your Device Server........................................28
DS1...........................................................................................................28
TS2 ...........................................................................................................28
LED Guide................................................................................................29
Console Mode vs. Serial Mode..............................................................29
Powering Up the Device Server ................................................29
Power Supply Requirements.................................................................29
Serial Only Models ............................................................................. 29
I/O Models.......................................................................................... 30
Serial Only Models..................................................................................30
I/O Models................................................................................................30
Setting Jumpers .........................................................................31
1-Port Device Server...............................................................................31
Device Server DB25 Male/Female..................................................... 31
Device Server RJ45............................................................................ 31
Device Server DB9............................................................................. 32
2-Port Device Server...............................................................................32
Digital I/O Module....................................................................................33
Analog Input Module ..............................................................................34
4 IOLAN Device Server User’s Guide, Version 1.8
Page 5
Table of Contents
Wiring I/O Diagrams................................................................... 34
Digital I/O.................................................................................................34
Digital Input Wet Contact ................................................................... 34
Digital Input Dry Contact.................................................................... 35
Digital Output Sink ............................................................................. 35
Digital Output Source......................................................................... 35
Analog Input............................................................................................36
Current............................................................................................... 36
Voltage............................................................................................... 36
Temperature Input..................................................................................36
Thermocouple.................................................................................... 36
RTD 2-Wire........................................................................................ 37
RTD 3-Wire........................................................................................ 37
RTD 4-Wire........................................................................................ 37
Relay Output........................................................................................... 37
Normally Open Contact...................................................................... 37
Normally Closed Contact ................................................................... 38
Setting an Initial IP Address ..................................................... 38
Using DeviceManager............................................................................39
Using a Direct Connection.....................................................................40
Using DHCP/BOOTP...............................................................................40
Using ARP-Ping......................................................................................41
IPv6 Network. .......................................................................................... 41
Pinouts........................................................................................ 42
DB25 Male ............................................................................................... 42
DB25 Female........................................................................................... 43
RJ45......................................................................................................... 44
DB9 Male (Serial Only)...........................................................................44
DB9 Male I/O............................................................................................45
EIA-232 Cabling Diagrams ........................................................ 46
Terminal DB25 Connector .....................................................................46
DB25 Male ......................................................................................... 46
DB25 Female..................................................................................... 46
RJ45................................................................................................... 47
DB9 Male ........................................................................................... 47
Modem DB25 Connector........................................................................48
DB25 Male ......................................................................................... 48
RJ45................................................................................................... 48
DB9 Male ........................................................................................... 49
5
Page 6
Table of Contents
Chapter 3 Configuration Methods ...................................51
Introduction.................................................................................51
DeviceManager ...........................................................................51
WebManager ...............................................................................52
Using the WebManager..........................................................................52
CLI................................................................................................52
Menu ............................................................................................52
Accessing the Menu...............................................................................52
Menu Conventions..................................................................................53
DHCP/BOOTP..............................................................................53
SNMP ...........................................................................................54
Chapter 4 Configuring the Device Server .......................55
Introduction.................................................................................55
Configuring the Device Server..................................................55
General Device Server Configuration...................................................55
Device Server Services ..........................................................................55
TruePort...................................................................................................56
Hardware Configuration.........................................................................56
Ethernet Connection........................................................................... 56
Serial Connection............................................................................... 56
Other................................................................................................... 56
Modbus Configuration ...............................................................57
Overview..................................................................................................57
Configuring a Master Gateway........................................................... 57
Configuring a Slave Gateway............................................................. 57
Modbus Gateway Settings.....................................................................58
Modbus Master Gateway.................................................................... 58
Modbus Slave Gateway...................................................................... 58
Modbus Line Settings.............................................................................59
Modbus Master Settings..................................................................... 59
Modbus Slave Settings....................................................................... 59
Example Scenario...................................................................................60
6 IOLAN Device Server User’s Guide, Version 1.8
Page 7
Table of Contents
Machine To Machine Connections........................................... 62
Users Connecting to Serial Devices ........................................ 62
Users Connecting to the LAN................................................... 62
Connecting To the Device Server.........................................................63
Connecting Through the Device Server...............................................63
Setting Up Lines......................................................................... 63
DSLogin...................................................................................................63
Direct/Silent/Reverse Connections.......................................................64
Virtual Modems.......................................................................................64
BIDIR........................................................................................................ 64
TruePort...................................................................................................64
Signal I/O................................................................................................. 64
UDP..........................................................................................................65
Serial Tunnel Settings............................................................................66
Setting Up Users........................................................................ 66
User Accounts........................................................................................66
User Levels ............................................................................................. 67
Sessions..................................................................................................67
Users From LAN to Device Server to Serial Device............................ 67
Easy Port Access Menu..................................................................... 67
Reverse Sessions and Multisessions................................................. 68
Configuring Network Options................................................... 69
Hosts........................................................................................................69
Gateways.................................................................................................69
Syslog......................................................................................................69
SNMP....................................................................................................... 69
Configuring Time ....................................................................... 69
Language support...................................................................... 69
Loading a Supplied Language ..............................................................70
Translation Guidance............................................................................. 70
Software Upgrades and Language Files.............................................. 71
7
Page 8
Table of Contents
Downloading Terminal Definitions ...........................................71
Creating Terminal Definition Files.........................................................71
TFTP Configuration....................................................................73
Resetting Configuration Parameters........................................73
Lost Admin Password................................................................73
DHCP/BOOTP..............................................................................73
DHCP/BOOTP Parameters .....................................................................74
Creating Custom Applications..................................................74
I/O Model Features .....................................................................74
Failsafe Timer..........................................................................................74
Alarms......................................................................................................75
UDP ..........................................................................................................75
UDP Unicast Format........................................................................... 75
UDP Unicast Example........................................................................ 76
I/O Modbus Slave....................................................................................76
Modbus Serial Application Connected to the Serial Port.................... 76
Modbus Serial Application Connected to the Network ....................... 77
Modbus TCP Application.................................................................... 77
Modbus I/O Access.................................................................................77
Function Codes .................................................................................. 77
A4/T4 Registers.................................................................................. 78
A4D2/A4R2 Registers ........................................................................ 78
D4/D2R2 Registers............................................................................. 79
Serial Signals...................................................................................... 79
TruePort...................................................................................................80
TruePort/Modbus Combination........................................................... 80
API Over TruePort Only...................................................................... 80
Digital Channels......................................................................................81
Digital Input......................................................................................... 81
Digital Output...................................................................................... 82
Temperature Channels...........................................................................83
Analog Channels.....................................................................................84
Relay Channels.......................................................................................85
Serial Signals ..........................................................................................85
8 IOLAN Device Server User’s Guide, Version 1.8
Page 9
Table of Contents
Calibrating Analog Input........................................................................86
Calibrating Voltage............................................................................. 86
Calibrating Current............................................................................. 86
Calibrating Temperature Input..............................................................86
Calibrating Thermocouple.................................................................. 86
Calibrating RTD.................................................................................. 86
Chapter 5 Using the DeviceManager...............................87
Introduction................................................................................ 87
Starting a New Session............................................................. 87
Managing a Device Server.....................................................................88
Populating the Device Server List...................................................... 88
Assigning a Temporary IP Address to a New Device Server............. 89
Adding/Deleting Static Device Servers .............................................. 89
Creating a New Device Server Configuration...................................... 90
Opening an Existing Configuration File...............................................90
Connecting to a Device Server................................................. 90
Managing a Device Server ........................................................ 91
DeviceManager Work Flow....................................................................91
Creating/Editing Configuration Files.................................................... 91
Working With the Device Server Configuration.................................. 91
Working With a Local Configuration File............................................ 91
Configuring the Server.............................................................. 92
Configuring the Main Server Window................................................... 92
Server................................................................................................. 92
Services ............................................................................................. 92
Configuring Advanced Server Settings................................................ 93
Configuring TruePort Baud...................................................................94
Configuring the Hardware .....................................................................94
Custom App............................................................................................94
9
Page 10
Table of Contents
Configuring Lines.......................................................................95
Advanced Line Settings.........................................................................97
Service Settings......................................................................................99
DSLogin.............................................................................................. 99
Raw Settings .................................................................................... 100
Telnet Settings.................................................................................. 100
BIDIR Settings.................................................................................. 101
UDP Settings.................................................................................... 102
VModem Settings............................................................................. 103
Server Tunnel Settings..................................................................... 103
Client Tunnel Settings ...................................................................... 104
Modbus Slave Settings..................................................................... 104
Modbus Master Settings................................................................... 105
Remote IP Slave Mappings.............................................................. 106
Custom App Settings........................................................................ 107
TruePort Settings.............................................................................. 108
Packet Forwarding................................................................................109
Configuring Modems............................................................................111
Configuring I/O .........................................................................112
Global Settings......................................................................................112
Temperature Settings....................................................................... 112
Failsafe Timer Settings..................................................................... 112
Modbus Settings............................................................................... 113
TruePort Settings.............................................................................. 113
UDP Settings.................................................................................... 113
Channels................................................................................................115
Digital Output.................................................................................... 115
Digital Input....................................................................................... 116
Relay ................................................................................................ 118
Analog .............................................................................................. 119
Basic Alarm Settings ........................................................................ 120
Advanced Alarm Settings................................................................. 121
Temperature..................................................................................... 122
Configuring Users ....................................................................122
Configuring Line Access......................................................................124
Configuring Sessions...........................................................................124
Configuring the Default User...............................................................125
10 IOLAN Device Server User’s Guide, Version 1.8
Page 11
Table of Contents
Configuring the Network......................................................... 125
Configuring Hosts................................................................................125
Configuring SNMP................................................................................126
Configuring TFTP.................................................................................127
Configuring Gateways ......................................................................... 127
Configuring Syslog ..............................................................................128
Configuring Administration Tasks......................................... 129
Configuring Bootup Files ....................................................................129
Configuring the MOTD File..................................................................129
I/O Status/Control .................................................................... 130
Statistics................................................................................... 130
Tools ......................................................................................... 131
Saving a Configuration To File............................................................131
Getting a Configuration File................................................................131
Configuring Multiple Device Servers..................................................131
Downloading Device Server Firmware............................................... 132
Setting the Device Server’s Date and Time........................................ 133
Rebooting the Device Server...............................................................133
Resetting the Device Server to Factory Defaults .............................. 133
Resetting a Line....................................................................................133
Custom Files.........................................................................................134
Saving Crashes to a Dump File ....................................................... 134
Downloading Terminal Definitions.................................................... 134
Downloading a Language File.......................................................... 134
Downloading a Custom App File...................................................... 134
I/O Channels..........................................................................................134
Calibrating Analog Channels............................................................ 134
Resetting Calibration Data............................................................... 135
Setting DeviceManager Options .........................................................136
11
Page 12
Table of Contents
Chapter 6 Command Line Interface...............................137
Introduction...............................................................................137
CLI Conventions.......................................................................137
Command Syntax..................................................................................137
Command Shortcuts.............................................................................138
Command Options................................................................................138
Server Commands....................................................................139
Server Commands................................................................................139
Set Custom-App............................................................................... 139
Set Server......................................................................................... 139
Set Service....................................................................................... 141
Show Custom-App............................................................................ 141
Show Modbus................................................................................... 141
Show Server..................................................................................... 141
Hardware Commands...........................................................................142
Set Ethernet...................................................................................... 142
Show Hardware................................................................................ 142
Modbus Commands..............................................................................142
Set Modbus Gateway....................................................................... 142
Show Modbus................................................................................... 143
TruePort Baud Commands ..................................................................144
Set TruePort Remap-Baud............................................................... 144
Show TruePort.................................................................................. 144
User Commands.......................................................................144
Logged Into the Device Server Commands........................................144
Admin ............................................................................................... 144
Help.................................................................................................. 144
Kill Line............................................................................................. 144
Kill Session....................................................................................... 144
Logout............................................................................................... 145
Menu................................................................................................. 145
Ping .................................................................................................. 145
Resume............................................................................................ 145
Screen.............................................................................................. 145
Set Termtype.................................................................................... 146
Set User............................................................................................ 146
Set User Session.............................................................................. 147
Show Line Users .............................................................................. 147
Syslog Console................................................................................. 147
Show Sessions................................................................................. 147
12 IOLAN Device Server User’s Guide, Version 1.8
Page 13
Table of Contents
Show Termtype................................................................................ 147
Start.................................................................................................. 148
Telnet............................................................................................... 148
Version............................................................................................. 149
Configuring Users................................................................................149
Add User.......................................................................................... 149
Delete User...................................................................................... 149
Set Default User............................................................................... 150
Set User........................................................................................... 152
Set User Session ............................................................................. 154
Show Default User........................................................................... 154
Show User........................................................................................ 154
Line Commands....................................................................... 155
Line Commands....................................................................................155
Set Line............................................................................................ 155
Set Line Interface............................................................................. 158
Set Line Service............................................................................... 159
Set Modem....................................................................................... 161
Set Termtype.................................................................................... 161
Show Line ........................................................................................ 161
Line Service Commands......................................................................162
Set Custom-App............................................................................... 162
Set Telnet-Client .............................................................................. 162
Set UDP........................................................................................... 163
Set Vmodem .................................................................................... 163
Set Modbus-Slave Line.................................................................... 164
Set Modbus-Master Line.................................................................. 165
Show Custom-App........................................................................... 165
Show Interface................................................................................. 166
Show Modbus .................................................................................. 166
Show Telnet-Client........................................................................... 166
Show UDP........................................................................................ 166
Show Vmodem................................................................................. 166
Modem Commands .............................................................................. 166
Add Modem...................................................................................... 166
Delete Modem.................................................................................. 166
Show Modems ................................................................................. 166
Packet Forwarding Commands...........................................................167
Set Packet-Forwarding Line............................................................. 167
Show Packet-Forwarding Line......................................................... 169
13
Page 14
Table of Contents
Network Commands.................................................................169
SNMP Commands.................................................................................169
Add Community................................................................................ 169
Add Trap........................................................................................... 169
Delete Community............................................................................ 170
Delete Trap....................................................................................... 170
Set SNMP......................................................................................... 170
Show SNMP..................................................................................... 170
TFTP Commands ..................................................................................171
Set Server TFTP............................................................................... 171
Hosts Commands .................................................................................171
Add Host........................................................................................... 171
Delete Host....................................................................................... 171
Set Host............................................................................................ 171
Show Hosts ...................................................................................... 171
Gateway Commands.............................................................................172
Add Gateway.................................................................................... 172
Delete Gateway................................................................................ 172
Set Gateway..................................................................................... 173
Show Gateways................................................................................ 173
Logging Commands.............................................................................174
Set Syslog ........................................................................................ 174
Show Syslog..................................................................................... 174
Time Commands.......................................................................174
Set Time........................................................................................... 174
Show Time........................................................................................ 174
Time/Date Setting Commands.............................................................175
Set Date............................................................................................ 175
Set Time........................................................................................... 175
Show Date........................................................................................ 175
Show Time........................................................................................ 175
Administration Commands......................................................175
Bootup Commands...............................................................................175
Reboot.............................................................................................. 175
Reset................................................................................................ 175
Reset Factory................................................................................... 175
Save ................................................................................................. 175
Set Bootup........................................................................................ 176
Show ARP........................................................................................ 176
Show Bootup.................................................................................... 176
14 IOLAN Device Server User’s Guide, Version 1.8
Page 15
Table of Contents
TFTP File Transfer Commands ...........................................................176
Netload............................................................................................. 176
Netsave............................................................................................ 177
MOTD Commands ................................................................................177
Set MOTD........................................................................................ 177
Show MOTD..................................................................................... 178
Statistic Commands ................................................................ 178
Configuration Statistics.......................................................................178
Show Netstat.................................................................................... 178
Show Modbus Statistics................................................................... 178
Show Netstat Statistics .................................................................... 178
Show Routes.................................................................................... 178
Run-Time Statistics..............................................................................179
Delete Arp........................................................................................ 179
Show Arp.......................................................................................... 179
Show Serial...................................................................................... 179
Uptime.............................................................................................. 179
I/O Commands.......................................................................... 179
Global I/O Commands..........................................................................179
Set IO UDP ...................................................................................... 179
Set IO Failsafe ................................................................................. 180
Set IO Modbus................................................................................. 180
Set IO Temperature-Scale............................................................... 180
Set Line..................................................................................................181
Set Line Service............................................................................... 181
Set IOChannel.......................................................................................181
Set IOChannel Mode........................................................................ 181
Set IOChannel Digital I/O................................................................. 181
Set IOChannel Digital Input.............................................................. 182
Set IOChannel Digital Input (Serial Pins)......................................... 183
Set IOChannel Digital Output........................................................... 184
Set IOChannel Digital Output (Serial Pins)...................................... 185
Set IOChannel Relay ....................................................................... 186
Set IOChannel Analog (True Analog) .............................................. 187
Set IOChannel Analog (Temperature) ............................................. 189
Kill IOChannel.................................................................................. 191
Show IO ........................................................................................... 191
Show IOChannel.............................................................................. 191
15
Page 16
Table of Contents
I/O Channel Control Commands..........................................................192
Digital Output.................................................................................... 192
Digital Input....................................................................................... 192
Relay ................................................................................................ 192
Analog Input ..................................................................................... 192
Calibrating Analog Input (Analog/Temperature)................................193
Calibrate Analog............................................................................... 193
Reset Calibration.............................................................................. 193
Appendix A Troubleshooting.........................................195
Introduction...............................................................................195
Hardware Problems..................................................................195
Communication Issues ............................................................195
DeviceManager Problems........................................................196
Host Problems ..........................................................................196
Login Problems ........................................................................196
Problems with Terminals.........................................................197
Unknown IP Address................................................................197
DHCP/BOOTP Problems ..........................................................198
Language Problems .................................................................198
Long Reboot Cycle...................................................................198
I/O Digital or Relay....................................................................198
16 IOLAN Device Server User’s Guide, Version 1.8
Page 17
Table of Contents
Appendix B Utilities ........................................................199
Introduction.............................................................................. 199
TruePort.................................................................................... 199
API I/O Access Over TruePort ................................................ 200
API Request Format............................................................................. 200
API Response Format..........................................................................200
Error Codes...................................................................................... 201
Appendix C Accessories................................................203
Introduction.............................................................................. 203
Starter Kit (Adapters/Cable).................................................... 203
RJ45F to DB25M DTE Crossover Adapter.......................................... 204
RJ45F to DB25M DCE Modem Adapter ..............................................205
RJ45F to DB25F DTE Crossover Adapter .......................................... 206
RJ45F to DB9M DTE Crossover Adapter............................................ 207
RJ45F to DB9F DTE Crossover Adapter ............................................ 208
Sun/Cisco RJ45M Connector Cable for Rack Mount Models........... 208
Glossary...........................................................................209
Index.................................................................................211
17
Page 18
Table of Contents
18 IOLAN Device Server User’s Guide, Version 1.8
Page 19
Preface
About This Book
This guide provides the information you need to:
z configure the Device Server z incorporate the Device Server into your production environment
Intended Audience
This guide is for administrators who will be configuring the Device Server. Some prerequisite knowledge is needed to understand the concepts and examples in this guide:
z If you are using an external authentication application(s), working knowledge of the
authentication application(s).
z Knowledge of TFTP, the transfer protocol the Device Server uses.
Documentation
The following documentation is included on the Device Server installation CD:
z IOLAN DS1/SDS1 Device Server Quick Start Guide z IOLAN Device Server User’s Guide z TruePort User Guide z TruePort Installation and Configuration Guide for Windows NT z Online Help in the DeviceManager (automatically installed with the DeviceManager application) z Link to knowledge base
IOLAN Device Server User’s Guide, Version 1.3 19
Page 20
Typeface Conventions
Typeface Conventions
Most text is presented in the typeface used in this paragraph. Other typefaces are used to help you identify certain types of information. The other typefaces are:
Typeface Example Usage
At the C: prompt, type:
add host
Set the value to TRUE. The typeface used for TRUE is also used when referring to
subscribe project subject
run yourcode.exec
File, Save This typeface and comma indicates a path you should
IOLAN DS Family User’s Guide This typeface indicates a book or document title. See Chapter 1, Introduction on page 23
for more information.
Online Help
Online help is provided in the DeviceManager. You can click on the What’s This button ( or ) and then click on a field to get field-level help. Or, you can press the F1 key to get window-level help. You can also get the User’s Guide online by selecting
This typeface is used for code examples and system-generated output. It can represent a line you type in, or a piece of your code, or an example of output.
an actual value or identifier that you should use or that is used in a code example.
The italicized portion of these examples shows the typeface used for variables that are placeholders for values you specify. This is found in regular text and in code examples as shown. Instead of entering you enter your own value, such as for
yourcode, enter the name of your program.
follow through the menus. In this example, you select
Save from the File menu.
This indicates a cross-reference to another chapter or section that you can click on to jump to that section.
Help, Help Topics.
stock_trader, and
project,
20 IOLAN Device Server User’s Guide, Version 1.3
Page 21
Contacting Technical Support
Making a Technical Support Query
Who To Contact
Contacting Technical Support
Note:
If you bought your product from a registered Perle supplier, you must contact their Technical Support department; they are qualified to deal with your problem.
Perle offers free technical support to Perle Authorised Distributors and Registered Perle Resellers.
Have Your Product Information Ready
When you make a technical support enquiry please have the following information ready:
Item Write Details Here
Product Name Problem Description
Your Name Company Name and
Address
Country Phone Number Fax Number Email Address
Making a support query via the Perle web page
If you have an internet connection, please send details of your problem to Technical Support using the email links provided on the Perle web site in the
Click here to access our website at the following URL: http://www.perle.com
Support area.
21
Page 22
Contacting Technical Support
Repair Procedure
Before sending a Device Server for repair, you must contact your Perle supplier. If, however, you bought your product directly from Perle you can contact directly.
Customers who are in Europe, Africa or Middle East can submit repair details via a website form. This form is on the Perle website,
Click here to access our web site at the following URL: http://www.perle.com/support_services/rma_form.asp
Feedback on this Manual
If you have any comments or suggestions for im proving this manual please email Perle using the following address;
Email: [email protected]
Please include the title, part number and date of the manual (you can find these on the title page at the front of this manual).
www.perle.com, in the Support area.
22 IOLAN Device Server User’s Guide, Version 1.3
Page 23
Introduction Chapter 1
1
About the IOLAN Device Server
The Device Server is an ethernet communications/terminal server that allows serial devices to be connected directly to LANs. The Device Server can connect to a wide range of devices including:
z T erminals for multi-user UNIX systems z Data acquisition equipment (manufacturing, laboratory, scanners, etc.) z Retail point-of-sale equipment (bar coding, registers, etc.) z PCs using terminal emulation z Modems for remote access and Internet access z ISDN adapters for branch remote access and Internet access z All types of serial printers
The performance and flexibility of the Device Server allows you to use a wide range of high speed devices in complex application environments. The Device Server will work in any server environment running TCP/UDP/IP.
IOLAN Device Server Models
The IOLAN Device Server comes in several different models to meet your production environment needs:
z DS—Offered as a 1-port unit, this model provides basic Device Server functionality. This model
can be ordered with RJ45, DB9 male, DB25 female, or DB25 male connection options. There is also a line of DS models that support Analog Input, Temperature Input, Relay Output, and/or Digital I/O.
z TS—The model does everything the DS model does plus has two RJ45 serial ports (supports
EIA-232 only). This model does not support the power out/power in pins or I/O.
z SDS—This model does everything the DS model does plus additional features such as external
authentication, SSH, SSL, port buffering, email alerts, RIP, DNS/WINS, plus much more. This model has an EIA-232/422/485 switchable interface. Rack mount models have a dedicated Console port and support gigabit Ethernet. The 1-port model can be ordered with RJ45, DB9 male, DB25 female, or DB25 male connection options. Some SDS models support Power Over Ethernet or have an internal modem. There is also a line of SDS models that support Analog Input, Temperature Input, Relay Output, and/or Digital I/O; all models in this line are extended temperature models, meaning that they can operate in higher temperature environments.
z STS—This model does everything the DS model does plus additional features such as external
authentication, SSH, SSL, port buffering, email alerts, RIP, DNS/WINS, plus much more. This model has an EIA-232 interface. Rack mount models have a dedicated Console port and support gigabit Ethernet. Some models support dual input DC power.
IOLAN Device Server User’s Guide, Version 1.8 23
Page 24
Device Server Features
z SCS—This model does everything the DS model does plus additional features such as external
authentication, SSH, SSL, port buffering, email alerts, RIP, DNS/WINS, plus much more. This model has an EIA-232 interface. Rack mount models have a dedicated Console port. This model comes equipped with PCI interface (supports the Perle PCI modem card), gigabit support, dual Ethernet, and can have dual AC power.
Device Server Features
The Device Server is a communications server with 1 port for making serial network connections. It attaches to your TCP/IP network and allows serial devices such as modems, terminals, or printers to access the LAN. It also allows LAN attached devices to access serial devices attached to the Device Server.
Hardware
The Device Server hardware features include:
z Auto sensing 10/100 RJ45 Ethernet interface. z Universal, software-selectable EIA-232/422/485 interface. z Full modem control using DTR, DSR, CTS, RTS and DCD. z Tx and Rx activity indicators. z External AC power supply or power over serial. z LEDs for diagnostic testing. z Self-test on power-up. z Reset switch.
Software
The Device Server software features include:
z Multiple ways to configure the Device Server:
– Easy Config Wizard, an easy configuration wizard that allows you to complete basic Device
Server configuration
– DeviceManager, a fully functional Windows 98/NT/2000/ME/Server 2003/XP
configuration/management tool
– WebManager, a web browser option for configuring/managing the Device Server – Menu, a window-oriented menu interface for configuration and user access – CLI, a Command Line Interface option for configuration/management and user access – SNMP, allowing remote configuration via SNMP as well as statistics gatherin g – DHCP/BOOTP, a method of automatically updating the Device Server
z IPv6 support. z Support for TCP/IP and UDP protocols telnet. z Vi rtual modem emulation. z ‘Fixed tty’ support for several operating systems (TruePort). z DHCP/BOOTP for automated network-based setup. z Dynamic statistics displays and line status reporting for fast problem diagnosis. z Multi session support on a single terminal. z Interoperability with IP routing through gateway tables.
24 IOLAN Device Server User’s Guide, Version 1.8
Page 25
Security
The Device Server security features include:
z Supervisory and port (line) password. z Port locking. z Per user access level assignment. z Logging via Syslog. z Idle port timers, which close a connection that has not been active for a specified period of time. z Ability to individually disable daemons/services that won’t be used by the Device Server.
Supported Products/Versions
Web Browsers
The WebM anager has been tested on Windows and Linux with the following web browsers:
z Netscape—7.x z Internet Explorer—6.x z Mozilla Firefox—1.x
Supported Products/Versions
Typical Applications Summary
Managing the Device Server
The Device Server can be managed and configured by administrators through various methods, allowing them full configuration capabilities and easy access to management statistics and tools. Administrators can access the Device Server using the following methods:
z Connection through ethernet using the DeviceManager, a Windows-based configuration
application.
z Connection through ethernet using WebManager , via a web browser. z Direct connection to the serial port using a Serial Terminal or Terminal Emulation Software. z From the network through the ethernet interface using reverse Telnet (Port 23). z Through an SNMP agent, using the Device Server MIB.
Managing/Accessing devices attached to the Device Server
The Device Server can be configured to allow users or administrators to view or manage specific devices on the Device Server’s serial port across the Ethernet interface using two different methods.
z Direct Connect—users can directly connect to the device on the serial port by Telnet (Line
Service
serial device’s assigned TCP port number.
z Easy Port Access—users can connect to the Device Server using the configured Device Server’s
IP address by reverse Telnet (port number 23), and are provided with a device menu displaying the name of the device that the user has access to. This feature eliminates the need for administrators and users to recall the specific port number associated with a certain device connected to the Device Server. The user can simply connect to a specific device based upon the name of the device and then return to the device menu without disconnecting its initial reverse Telnet connection.
must be set to Rev Telnet) using the Device Server’s configured IP address and the
25
Page 26
Typical Applications Summary
Network Security
The Device Server provides a comprehensive suite of security features to allow an organization to implement robust security planning to prevent unauthorized access. These include trusted host filtering and the ability to disable individual services.
26 IOLAN Device Server User’s Guide, Version 1.8
Page 27
Inst allation Chapter 2
2
Introduction
This chapter tells you what is packaged with your IOLAN Device Server, how to power up the Device Server to make sure it works correctly, and how to assign the Device Server an IP address through the LAN.
IOLAN Device Server Components
What’s Included
When you open your IOLAN Device Server package, you should have the following components:
z The Device Server z External power supply (except I/O models)
Note:
z Quick Start Guide (for I/O models, a soft copy exists on the CD-ROM) z Warranty Card z A CD-ROM containing documentation, firmware, DeviceManager, etc. z Administration cable (consisting of an RJ45-->DB9F adapter and a 3’ RJ45 cable) for models
that have an RJ45 connector
If the Device Server was bought in bulk, you must supply the power supply.
What You Need to Supply
Before you can begin, you need to have the following:
z A serial cable z An Ethernet 10/100BASE-T cable if you are connecting the Device Server to the network
Available Accessories
The following accessory is available for purchase for the Device Server:
z DIN Rail Mounting Kit (35mm)
Contact your distributor for details.
IOLAN Device Server User’s Guide, Version 1.8 27
Page 28
Getting to Know Your Device Server
Getting to Know Your Device Server
DS1
This section describes the components found on the Device Server.
TS2
Console/Serial
Mode Switch
Power Supply
Power
LAN Connection
LAN Activity
Serial Activity
Serial Connection
This section describes the components found on the TS2 Device Server model.
Console/Serial
Mode Switch
Power Supply
Reset to Factory
Defaults
Ethernet
Interface
Reset to Factory
Defaults
Ethernet
Interface
Power
LAN Connection
LAN Activity
Serial Activity
Serial Connection
28 IOLAN Device Server User’s Guide, Version 1.8
Page 29
LED Guide
The Device Server LEDs display the following information:
z Power/Ready—(Green/Red/Yellow) Shows red at power up. If this LED remains red, indicates
that there is a critical error (return to factory). Flashes green to indicate that the Device Server is booting. Flashes green/yellow when the firmware is being updated. Stays solid green to indicate that the Device Server is ready.
z Link/10/100
– Green—10 Mbits – Yellow—100 Mbits – Off—no LAN connection
z Activity—Flashes Green for transmit (TX) or receive (RX) LAN data z Tx—Flashes with transmit serial activity z Rx—Flashes with receive serial activity
Console Mode vs. Serial Mode
You will notice a little switch at the back of the Device Server for switching the Device Server to either Console or Serial mode.
Powering Up the Device Server
When the switch is down (ON), the Device Server is in Console mode; when the switch is up, the Device Server is in Serial mode. Console mode is used when you have a direct connection between a serial device (like a terminal or a PC) and the Device Server, accessed by the Admin user to configure/manage the Device Server. You can connect directly to the Device Server in Serial mode, but the Device Server will not display all the messages/information you will get in Console mode. Console mode automatically sets the
No, Bits to 8, Stop Bits to 1, and Parity to None, in addition to displaying extra system messages.
Your Device Server will not work in a production environment in Consol e mode. Serial mode is used when the Device Server acts as a communications server, or anytime you are not
connecting directly to the Device Server to configure it.
Serial Interface to EIA-232, Speed to 9600, Flow Control to
Powering Up the Device Server
Power Supply Requirements
Serial Only Models
If you are providing a power supply for a desktop Device Server model, your power supply mu st meet the following requirements:
z Output between 9-30V DC. z The cable attached to the power supply should be about 20AWG, lengt h 6 feet approximately.
The barrel dimensions of the cable-plug are OD=5.5, ID=2.1, and length= 9.5mm, with a straight barrel, and positive polarity on the inside and negative polarity on the outside.
z Power can also be provided by pin 12 for DB25M/F and pin 1 RJ45 serial models.
29
Page 30
Powering Up the Device Server
I/O Models
If you are providing a power supply for a desktop Device Server I/O model, your power supply must meet the following requirements:
z Output between 9-30V DC and a minimum of 600mA current.
Note:
Serial Only Models
Before you attach the Device Server to your network or try to configure it, we suggest that you power it up to verify that it works properly. To power up the Device Server, perform the following steps:
1. Plug the external power supply into the Device Server and then into the electrical outlet.
2. If the Device Server is working correctly, you should see: a. The Power/Ready LED starts out red. b. The Power/Ready LED flashes green while the Device Server boots up. c. The Power/R e ady LED stays solid green, indicating that it is ready to configure/use.
You are now ready to begin communicating wi th you r IOLAN Device Server. The last step of the installation process is to set an IP address for the Device Server; this is necessary before it can be configured and put into production.
Before you start to configure the Device Server, you should set the Device Server jumpers if you want to terminate the line.
I/O Models
Before you attach the Device Server to your network or try to configure it, we suggest that you power it up to verify that it works properly. To power up the Device Server, perform the following steps:
1. Unplug the power plugable terminal block from the Device Server.
2. Loosen the screws and then insert your positive (+) wire into the left terminal and screw it down.
Insert the negative (-) wire into the right terminal and screw it down.
3. Plug the power terminal block back into the Device Server.
4. Plug the power supply into the electrical outlet.
5. If the Device Server is working correctly, you should see the LEDs cycle for several seconds and
then remain a solid green, indicating that it is ready to configure/use.
You are now ready to connect your I/O peri pheral s to the Devi ce Server and then begin communicating with your IOLAN Device Server. The last step of the installation process is to set an IP address for the Device Server; this is necessary before it can be configured and put into production.
Before you start to configure the Device Server, you should set the Device Server jumpers for Digital I/O (see channels.
Digital I/O Module on page 33) or Analog Input (Analog Input Module on page 34)
The maximum load for the Relay channel is 1A @ 30VDC or 0.5A @ 120VAC.
30 IOLAN Device Server User’s Guide, Version 1.8
Page 31
Setting Jumpers
The Device Server contains jumpers that you might need to set before you configure it and put it into production. You can set the power out pin (no t on the DB9 model) to a fixed 5V DC output or to the external adapter output; this can range from 9-30V DC (if an external adapter is shipped with the Device Server, it has a 12V DC output). By default, the power out pin is set to no power. You can set the Device Server line termination to (not applicable for I/O models).
1-Port Device Server
Device Server DB25 Male/Female
To change the settings, do the following:
1. Unplug the Device Server from the electrical outlet and disconnect everything from the box.
2. Open the case by unscrewing the two side screws, one on each side, and lifting off the top of the
case. You should see the followin g:
Setting Jumpers
on or off (this is off by default) if you are using EIA-422/485
Screw
Serial Connection
J9
J1
Dip Switch
Screw
Power
Reset
RJ45
3. To turn line termination on, locate and jumper both J1 and J9.
4. Close the Device Server case by replacing the case lid and the two screws. You can now power it
on with the new settings.
Device Server RJ45
To change the settings, do the following:
1. Unplug the Device Server from the electrical outlet and disconnect everything from the box.
2. Open the case by unscrewing the two side screws, one on each side, and lifting off the top of the
case. You should see the followin g:
Screw
Power
RJ45 Serial
Dip Switch
Reset
J9
J1
3. To turn line termination on, locate and jumper both J1 and J9.
4. Close the Device Server case by replacing the case lid and the two screws. You can now power it
on with the new settings.
RJ45
Screw
31
Page 32
Setting Jumpers
Device Server DB9
To change the settings, do the following:
1. Unplug the Device Server from the electrical outlet and disconnect everything from the box.
2. Open the case by unscrewing the two side screws, one on each side, and lifting off the top of the
case. You should see the followin g:
Screw
Power
DB9 Serial
J9
Dip Switch
Reset
J11
3. To turn line termination on, locate and jumper both J11 and J9.
4. Close the Device Server case by replacing the case lid and the two screws. You can now power it
on with the new settings.
2-Port Device Server
To change the settings, do the following:
1. Unplug the Device Server from the electrical outlet and disconnect everything from the box.
2. Open the case by unscrewing the two side screws, one on each side, and lifting off the top of the
case. You should see the followin g:
RJ45
1
J7 J9
Pin1
RJ45
2
RJ45
Screw
Screw
Power
J8 J11
DIP Switch
Reset
RJ45
Screw
3. To turn line termination on for Line 1, locate and jumper both J7 and J8 (as shown in the
diagram). To turn line termination
4. Close the Device Server case by replacing the case lid and the two screws. You can now power it
on with the new settings.
32 IOLAN Device Server User’s Guide, Version 1.8
on for Line 2, locate and jumper both J11 and J9.
Page 33
Digital I/O Module
Device Servers that have Digital I/O have an input/output jumper that mu st be set for each channel and must match the software configuration for each channel. Depending on the model, the placement of the Digital I/O board can change, so the diagram below shows how to set jumper for any Digital board.To change the settings, do the following:
1. Detach the Device Server from the electrical power source and disconnect everything from the
box.
2. Open the case by unscrewing the five side screws, two on each side plus the grounding screw,
and lifting off the top of the case. You should see the following configurat ion for the Digital I/O board:
Channel 2/4
J5
Pin1
Pin1
Setting Jumpers
J3
Channel 1/3
I/O
Note:
Jumper pins 1 and 2 for Input. Jumper pins 2 and 3 for Output.
3. To configure either Channel 1 or Channel 3 (depending on how many Digital channels your I/O
supports and following the mylar channel definitions) for Input, jumper J3 pin 1 and 2 (as shown); this is the default setting. To configure either Channel 2 or Channel 4 (depending on how many Digital channels your I/O supports and following the mylar channel definition s) for Output, jumper J5 pin 2 and 3 (as shown).
4. Close the Device Server case by replacing the case lid and the five screws. You can now power it
on with the new settings.
33
Page 34
Wiring I/O Diagrams
Analog Input Module
Device Servers that have Analog input have a voltage/current jumper that must be set for each channel and must match the software configuration for each channel. To change the settings, do the following:
1. Detach the Device Server from the electrical power source and disconnect everything from the
box.
2. Open the case by unscrewing the five side screws, two on each side plus the grounding screw,
and lifting off the top of the case. You should see the following configurat ion for the Analog input board:
Channel 1
JP1 JP2
Channel 2
I/O
3. To configure Channel 1 for Voltage, no jumper should be set (as shown); this is the default
setting. To configure Channel 2 for Current, jumper both J2 pins (as shown).
4. Close the Device Server case by replacing the case lid and the five screws. You can now power it
on with the new settings.
Wiring I/ O Diagrams
This section describes how to wire the various Device Server I/O models.
Digital I/O
Make sure the Digital I/O jumpers support the software setting; see Digital I/O Module on page 33 for jumper settings.
Digital Input Wet Contact
If you are using a wet contact for your Digital input, for channel D1 connect one wire to D1 and the other wire to GND. The power source is supplied by the GND (ground) connector.
D1
Channel 3
JP3
D2
GND
I/O
COM
Channel 4
JP4
VCC
34 IOLAN Device Server User’s Guide, Version 1.8
Power Source
Page 35
Wiring I/O Diagrams
Digital Input Dry Contact
If you are using a dry contact for your Digital input, for channel D1 connect one wire to D1 and the other wire to COM. The power source is supplied by the COM (common) connector.
D1
D2
GND
COM
VCC
Power
Source
Digital Output Sink
For a Digital output sink (ground) configuration for channel D1, follow the diagram below.
D1
D2
GND
COM
VCC
­Battery
+
-
+
Device
Digital Output Source
For a Digital output source (voltage) configuration for channel D1, follow the diagram belo w.
D1
D2
GND
COM
VCC
+
Battery
+
Device
-
-
35
Page 36
Wiring I/O Diagrams
Analog Input
Make sure the Analog jumpers support the software setting; see Analog Input Module on page 34 for jumper settings.
Current
To connect channel A1 with a 2-wire shielded cable, connect the positive wire to A1+, the negative wire to A1-, and optionally the shield to GND.
If you have the positive/negative wires reversed, the output will always read 0 (zero).
Voltage
To connect to Channel A1 with a 2-wire shielded cable, connect the positive wire to A1+, the negative wire to A1-, and optionally the shield to GND.
A1+
A1-
A2+
A2-
-
+
A3+
A3-
A4+
A4-
GND
shield
If you have the positive/negative wires reversed, the polarity of the voltage will be reversed.
Temperature Input
If you are using RTD sensors, a short detected status will be displayed if the wires are connected improperly. RTD or thermocouple sensors will display an open detection status when the circuit is broken.
Thermocouple
To connect to Channel A1 with a 2-wire cable, connect the positive wire to A1+ and the negative wire to A1-; you will not be using the A1s connection.
A1+
A1-
A2+
A2-
-
+
A1+
A1-
A1s
A2+
A2-
A2s
A3+
A3-
A4+
A4-
GND
shield
A3+
A3-
A3s
A4+
A4s
A4-
+
36 IOLAN Device Server User’s Guide, Version 1.8
-
Page 37
Wiring I/O Diagrams
RTD 2-Wire
In a 2-wire RTD configuration, connect the excite wire to A1-, the return wire to A1+, an d jump er th e sense wire from A1s with a insulated wire going to A1+.
A3+
A3-
return
A1+
A1-
excite
A1s
sense
A2+
A2-
A2s
A3s
A4+
A4s
A4-
RTD 3-Wire
In a 3-wire RTD configuration, connect the return wire to A1+, the excite wire to A1-, and the sense wire to A1s.
A3+
A3-
A3s
A1+
A1-
A1s
A2+
A2s
A2-
A4+
A4s
A4-
RTD 4-Wire
In a 4-wire RTD configuration, connect the return wire to A1+, the excite wire to A1-, the sense wire to A1s, and leave the fourth wire disconnected.
Relay Output
Normally Open Contact
To connect Relay channel R1 for a circuit that is normally inactive, connect one wire to the COM (common) connector and one wire to the NO (normally open) connector.
return
return
sense
excite
A1+
A1-
A1s
A2+
sense
excite
COMNCNONOCOM
A2-
NC
A3+
A3-
A3s
A2s
A4+
A4-
A4s
R1
R2
37
Page 38
Setting an Initial IP Address
Normally Closed Contact
To connect relay channel R1 for a circuit that is normally active, connect one wire to the COM (common) connector and one wire to the NC (normally closed) connector.
COMNCNONOCOM
R1
NC
R2
Setting an Initial IP Address
This section describes the different methods you can use to set the Device Server IP address. Following is a list of methods for setting the Device Server IP address and a short explanation of
when you would want to use that method:
z Easy Config Wizard—The Easy Config Wizard is automatically launched from the CD ROM
included with your Device Server. Y o u can use the Easy Config Wizard to set the Device Server’s IP address and configure the line(s).
z DeviceManager—Use this method when you can connect the Device Server to the network and
access the Device Server from a Windows application that can be used for Device Server configuration and management.
z Direct Connection—Use this method when you can connect the Device Server directly to a
dumb terminal, essentially logging directly into the Device Server. Using this method, you will need to configure and/or manage the Device Server using either the Menu or CLI.
z DHCP/BOOTP—Use this method when you have a BOOTP or DHCP server running and you
can connect the Device Server to your network. The Device Server will automatically obtain an IP address from a local network DHCP/BOOTP server when this service is enabled (it is disabled by default).
z ARP-Ping—Use this method when you can connect the Device Server to the network and want
to assign a temporary IP address to the Device Server by specifying an ARP entry and then pinging it.
z IPv6 Network—When the Device Server is connected to an IPv6 network, its local link address
should automatically be recognized by the network.
®
PC. The DeviceManager is a Windows-based
Note:
Regardless of which method you use, the Device Server must reside within the same network as the host you are accessing it from.
Once an IP address has been assigned to the Device Server, in most cases, you can continue to use the same method to configure and/or manage the Device Server. See
on page 51 for more information on the different methods you can use to manage/configure the
Device Server.
38 IOLAN Device Server User’s Guide, Version 1.8
Chapter 3, Configuration Methods
Page 39
Using DeviceManager
To use the DeviceManager, you must first install it on a Windows 98/2000/NT/ME/Server 2003/XP operating system (Windows NT requires Service Pack 4 or later) that resides in the same network as the Device Server. The DeviceManager installation wizard can be found on the CD-ROM included in the Device Server package.
1. Connect the Device Server to the LAN and plug it in; it will automatically boot up.
2. From the CD-ROM that was included in the Device Server packaging, select the DeviceManager
link.
3. Click on the link under Location and click Open to automatically start the DeviceManager
installation.
4. Install the DeviceManager by following the installation wizard. On the last window, check the
Yes, I want to launch DeviceManager now. box and click the Finish button.
5. On the Manage Device Server tab, click the Search Local Network button.
6. Any Device Server that does not have an IP address will be displayed as Not Configured, with
the
Model and MAC Address to identify the Device Server. Highlight the Device Server that you
want to assign an IP address to and click the
Setting an Initial IP Address
Assign IP button.
Note:
If your Device Server is displayed with an IP address at this point, you are running a DHCP/BOOTP server on your network and the Device Server has obtained an IP address already. If you want to permanently assign an IP address, continue following the directions, if the DHCP/BOOTP assigned IP address is sufficient, you are now ready to configure the Device Server.
7. Type in the IP address that you want to assign to this Device Server and click the Assign IP
button.
Note:
This is just a temporary IP address that you can use to open a session to the Device Server for configuration.
8. You are now ready to configure the Device Server. Double-click the Device Server you just
assigned the temporary IP address to, to open a configuration session. Type factory default Admin user password) in the Login window and click
superuser (the
OK.
9. Expand the Server Configuration folder and select Server. You can choose to enter a permanent
IP address in the
Note:
If your network runs a DHCP server and you don’t want the Device Server to obtain its
IP Address from the DHCP server (or if you’re not sure if there is a DHCP server and
you want to assign a permanent
Internet Address field and the Subnet/Prefix Bits field of the Server window.
IP Address), disable the DHCP/BOOTP Service in this
window.
10. Click the Apply button when you’re done with the Server window. To permanently assign the IP
address, you need to download the new configuration file and then reboot the Device Server.
11. Download the configuration file to the Device Server by selecting Tools, Download
Configuration to Unit
.
12. Reboot the Device Server by selecting Tools, Reboot Server.
For more information on configuring the Device Server using DeviceManager, see Chapter 5, Using
the DeviceManager on page 87.
39
Page 40
Setting an Initial IP Address
Using a Direct Connection
You can connect to the Device Server using a PC with a terminal emulation package, such as HyperTerminal or a terminal.
1. Connect the Device Server to your PC or dumb terminal. Make sure the dip switch is in Console
mode (this sets the Device Server serial port to EIA-232). When connecting a terminal or PC directly (without modems), the EIA-232 signals need to be crossed over (‘null modem’ cable). See
EIA-232 Cabling Diagrams on page 46 for cabling diagrams.
2. Using a PC emulation application, such as HyperTerminal, or from a dumb terminal, set the Port
settings to 9600 Baud, 8 Data bits, No Parity, 1 Stop Bits, and No Hardware Flow control to connect to the Device Server.
3. When prompted, type admin for the User and superuser for the Password. You should now
see the
DS1# prompt.
4. You are now logged into the Device Server and can set the IP address by typing from the
command line using the Command Line Interface (CLI):
set server internet <ipv4address>
Where ipv4address is the IP Address being assigned to the Device Server.
5. T ype the following command:
save
6. If you are going to use another configuration method, such as WebManager or DeviceManager,
unplug the Device Server. Change the Device Server dip switch to Off Serial (dip switch in the up position) and connect it to your serial device. Plug the Device Server back in, automatically rebooting the Device Server in the process.
7. If you want to complete the configuration using a direct connection, see Chapter 3,
Configuration Methods on page 51 and/or Chapter 6, Command Line Interface on page 137.
After you complete configuring the Device Server, unplug the Device Server. Change the Device Server dip switch to Off Serial (dip switch in the up position) and connect it to your serial device. Plug the Device Server back in, automatically rebooting the Device Server in the process.
Using DHCP/BOOTP
If you are using BOOTP, you need to add an entry for the Device Server that associates the MAC address (found on the back of the Device Server) and the IP address that you want to assign to the Device Server. After you have made the MAC address/IP address association for BOOTP, use the following directions for BOOTP or DHCP.
You can connect to the Device Server using a PC with a terminal emulation package, such as HyperTerminal or a terminal.
1. Connect the Device Server to your PC or dumb terminal. Make sure the DIP switch is in Console
mode. When connecting a terminal or PC directly (without modems), the EIA-232 signals need to be crossed over (‘null modem’ cable). See diagrams.
2. Using a PC emulation application, such as HyperTerminal, or from a dumb terminal, set the Port
settings to 9600 Baud, 8 Data bits, No Parity, 1 Stop Bits, and No Hardware Flow control to connect to the Device Server.
3. When prompted, type admin for the User and superuser for the Password. You should now
see the a prompt that displays the model type and port number; for example,
4. You are now logged into the Device Server and can set the IP address by typing from the
command line using the Command Line Interface (CLI). Type the following command:
set server service dhcp/bootp o n
EIA-232 Cabling Diagrams on page 46 for cabling
DS1#.
40 IOLAN Device Server User’s Guide, Version 1.8
Page 41
5. T ype the following command:
6. The the following command:
7. When the Device Server reboots, it will automatically poll for an IP address from the
DHCP/BOOTP server. If you have a Device Server with dual Ethernet, each Ethernet connection will automatically be assigned an IP address, you can access the Device Server through either IP address.
If for some reason it cannot obtain an IP address from your DHCP/BOOTP server, you will have to either connect to the Device Server on the console port and reboot it or push the Reset to Factory button to access the Device Server.
You are now ready to configure the Device Server. See Chapter 3, Configuration Methods on page
51 for information on the different Device Server configuration methods.
Using ARP-Ping
You can use the ARP-Ping (Address Resolution Protocol) method to temporarily assign an IP address and connect to your Device Server to assign a permanent IP address. To use ARP-Ping to temporarily assign an IP address:
1. From a local UNIX/Linux host, type the following:
arp -s a.b.c.d aa:bb:cc:dd:ee:ff
Setting an Initial IP Address
save
reboot
2. Whether you use UNIX or Windows®, you are now ready to ping to the Device Server. Here is a
You are now ready to configure the Device Server. See Chapter 3, Configuration Methods on page
51 for information on the different Device Server configuration methods.
IPv6 Network
The Device Server has a factory default link local IPv6 address that takes the following format: Device Server MAC Address: 00-80-D4-AB-CD-EF Link Local Address: fe80::0280:D4ff:feAB:CDEF The Device Server will also listen for IPv6 router advertisements to learn a global address. You do
not need to configure an IPv4 address for a Device Server residing in an IPv6 network. You are now ready to configure the Device Server. See Chapter 3, Configuration Methods on page
51 for information on the different Device Server configuration methods.
On a Windows® 98 or newer system, type the following:
arp -s a.b.c.d aa-bb-cc-dd-ee-ff
(where a.b.c.d is the IPv4 address you want to temporarily assign to the Device Server, and
aa:bb:cc:dd:ee:ff is the Ethernet (MAC) address of Device Server, found on the back of the
unit.
UNIX example of the sequence to use:
arp -s 192.168.209.8 00:80:d4:00:33:4e ping 192.168.209.8
41
Page 42
Pinouts
Pinouts
DB25 Male
This section defines the pinouts for the DB25 male connection used on the 1-port Device Server.
Pin 1
Pin 14
The following table provides pinout information:
EIA-232
Pinout
1 Shield Shield Shield Shield 2 (out) TxD 3 (in) RxD 4 (out) RTS 5 (in) CTS 6 (in) DSR
EIA-422
Pin 13
Pin 25
EIA-485 Full Duplex
EIA-485 Half Duplex
7 GND GND GND GND 8 (in) DCD 12 Power in Power in Power in Power in 13 CTS­14 TxD+ TxD+ DATA+ 15 TxD- TxD- DATA­18 RTS+ 19 RTS­20 (out) DTR 21 RxD+ RxD+ 22 RxD- RxD­25 CTS+
The power in pin, pin 12, can be 9-30V DC.
42 IOLAN Device Server User’s Guide, Version 1.8
Page 43
DB25 Female
This section defines the pinouts for the DB25 female connection used on the 1-port Device Server.
Pinouts
Pin 13
Pin 25
The following table provides pinout information:
EIA-232
Pinout
1 Shield Shield Shield Shield 2 (out) RxD 3 (in) TxD 4 (out) CTS 5 (in) RTS 6 (in) DTR
EIA-422
Pin 1
Pin 14
EIA-485 Full Duplex
EIA-485 Half Duplex
7 GND GND GND GND 8 (in) DCD 12 Power in Power in Power in Power in 13 RTS­14 RxD+ RxD+ DATA+ 15 RxD- RxD- DATA­18 CTS+ 19 CTS­20 (out) DSR 21 TxD+ TxD+ 22 TxD- TxD­25 RTS+
The power in pin, pin 12, can be 9-30V DC.
43
Page 44
Pinouts
RJ45
This section defines the pinouts for the RJ45 connection used on the DS and TS Device Server. The TS Device Server does not support power in, so use the 8-pin mappings for this model. These pinouts do not apply to I/O models.
Pin 1
The following table provides pinout information:
Pinout 10-pin
Pinout 8-pin
1 Power In Power In Power In Power In 2 (in) 1 DCD 3 (out) 2 RTS TxD+ TxD TxD+/RxD+ 4 (in) 3 DSR 5 (out) 4 TxD TxD- TxD- TxD-/RxD­6 (in) 5 RxD RxD+ RxD+ 7 6 GND GND GND GND 8 (in) 7 CTS RxD- RxD-
The power in pin, Pin 1, can be 9-30V DC.
DB9 Male (Serial Only)
This section defines the pinouts for the DB9 male connection used on the 1-port Device Server that is serial only (not I/O).
Pin 10
EIA-232
EIA-422
EIA-485 Full Duplex
EIA-485 Half Duplex
The following table provides pinout information:
Pinout 9-pin
EIA-232
1 (in) DCD 2 (in) RxD RxD+ RxD+ 3 (out) TxD TxD+ TxD+ 4 (out) DTR 5 GND GND GND 6 (in) DSR RxD- RxD­7 RTS 8 (in) CTS 9 TxD- TxD-
44 IOLAN Device Server User’s Guide, Version 1.8
EIA-422/485 Full Duplex
EIA-485 Half Duplex
Page 45
DB9 Male I/O
Pinouts
This section defines the pinouts for the DB9 male connection used on the 1-port Device Server I/O models.
The following table provides pinout information:
Pinout 9-pin
EIA-232
EIA-422/485 Full Duplex
EIA-485 Half Duplex
1(in) DCD 2 (in) RxD RxD+ 3 (out) TxD TxD- TxD-/RxD­4 (out) DTR 5 GND GND GND 6 (in) DSR RxD­7 RTS TxD+ TxD+/RxD+ 8 (in) CTS 9
45
Page 46
EIA-232 Cabling Diagrams
EIA-232 Cabling Diagrams
This section shows how to create EIA-232 cables that are compatible with the Device Server.
Terminal DB25 Connector
The following diagrams show how the null modem cable should be configured when connecting to a terminal DB25.
DB25 Male
IOLAN DS1
DB25 (DTE)
2 (TxD) 3 (RxD)
3 (RxD) 2 (TxD)
4 (RTS) 5 (CTS) 5 (CTS) 4 (RTS)
6 (DSR) 20 (DTR)
7 (GND) 7 (GND)
20 (DTR) 6 (DSR)
DB25 Female
IOLAN DS1
DB25 (DCE)
3 (TxD) 3 (RxD)
2 (RxD) 2 (TxD)
5 (RTS) 5 (CTS)
Terminal DB25
(DTE)
Terminal DB25
(DTE)
4 (CTS) 4 (RTS)
20 (DSR) 20 (DTR)
7 (GND) 7 (GND)
6 (DTR) 6 (DSR)
46 IOLAN Device Server User’s Guide, Version 1.8
Page 47
RJ45
Terminal DB25
IOLAN RJ45
10-pin 8-pin
4 (DSR) 3 20 (DTR) 3 (RTS) 2 5 (CTS)
5 (TxD) 4 3 (RxD) 6 (RxD) 5 2 (TxD) 7 (GND) 6 7 (GND) 8 (CTS) 7 4 (RTS) 9 (DTR) 8 6 (DSR)
DB9 Male
EIA-232 Cabling Diagrams
(DTE)
IOLAN DS1
DB9 Male
3 (TxD) 3 (Rx D )
2 (RxD) 2 (TxD)
7 (RTS) 5 (CTS) 8 (CTS) 4 (RTS)
6 (DSR) 20 (DTR)
5 (GND) 7 (GND)
4 (DTR) 6 (DSR)
Terminal DB25
(DTE)
47
Page 48
EIA-232 Cabling Diagrams
Modem DB25 Connector
The following diagrams show how a standard straight through cable should be configured when connecting to a DB25 modem.
DB25 Male
IOLAN DS1
DB25 (DTE)
2 (TxD) 2 (RxD)
3 (RxD) 3 (TxD)
4 (RTS) 4 (CTS) 5 (CTS) 5 (RTS)
6 (DSR) 6 (DSR) 7 (GND) 7 (GND) 8 (DCD) 8 (DCD)
20 (DTR) 20 (DTR)
RJ45
IOLAN RJ45
10-pin 8-pin
2 (DCD) 1 8 (DCD)
Modem DB25
(DCE)
Modem DB25
(DCE)
3 (RTS) 2 4 (CTS) 4 (DSR) 3 6 (DSR) 5 (TxD) 4 2 (RxD) 6 (RxD) 5 3 (TxD) 7 (GND) 6 7 (GND) 8 (CTS) 7 5 (RTS) 9 (DTR) 8 20 (DTR)
48 IOLAN Device Server User’s Guide, Version 1.8
Page 49
DB9 Male
EIA-232 Cabling Diagrams
IOLAN DS1
DB9 Male
1 (DCD) 8 (DCD)
2 (RxD) 3 (TxD)
3 (TxD) 2 (Rx D )
4 (DTR) 20 (DTR)
5 (GND) 7 (GND)
6 (DSR) 6 (DSR)
7 (RTS) 4 (CTS) 8 (CTS) 5 (RTS)
Modem DB25
(DCE)
49
Page 50
EIA-232 Cabling Diagrams
50 IOLAN Device Server User’s Guide, Version 1.8
Page 51
Configuration Methods Chapter 3
3
Introduction
This chapter provides information about the different methods you can use to configure the Device Server. Before you can configure the Device Server, you must assign an IP address to the Device Server. You can assign an IP address to the Device Server using one of the following methods:
z Using the DeviceManager as described in Using DeviceManager on page 39. z Using ARP-Ping as described in Using ARP-Ping on page 41. z Using a direct connection to the Admin port as described in Using a Direct Connection on page
40.
DeviceManager
The DeviceManager is a fully functional Windows 98/NT/2000/ME/Server 2003/XP Device Server configuration/management tool. You must install the DeviceManager from the CD-ROM included with the Device Server. Through the DeviceManager, you can:
z assign an IP address to new Device Servers. z perform firmware updates. z create configuration files, which can be immediately downloaded to the Device Server. z save configuration files locally in the DeviceManager’s native binary format or to a text file. The
text configuration file can be edited with a text editor.
z open a session to a Device Server and import a (saved) configuration file. z view statistics for a Device Server. z download custom files, such as new terminal definitions and a custom language file. z download a configuration file to multiple Device Servers.
You can use the DeviceManager as a stand-alone application to create configuration files that can be saved locally or you can use the DeviceManager to open a session to a Device Server to actively manage and configure it.
See Chapter 5, Using the DeviceManager on page 87 for information on configuring/managing the Device Server with DeviceManager.
IOLAN Device Server User’s Guide, Version 1.8 51
Page 52
WebManager
WebManager
The WebManager is a web-browser based method of configuring/ma nagi ng a Device Server. To access a Device Server through the WebManager, open up your web browser and type in the IP
address of the Device Server that you want to manage/configure. A login screen will appear.ype in the Admin password.
Using the WebManager
The Server Configuration window is displayed after you first log on. The running Device Server configuration is displayed in the WebManager. You navigate through the different configuration windows by selecting the configuration window from the drop-down options in the upper-lefthand corner of the browser.
When you have completed all the changes to a configuration window, click the Submit button. After you make all your configuration changes, click the to take effect immediately, click the and then click the
Save to FLASH button, your changes will be lost the next time the Device Server reboots. After you
click the
Reboot button, you will need to reconnect and login to the Device Server.
Save to FLASH button. If you want your changes
Reboot button. Yo u can make changes to a line, Submit them,
Kill Line button to test the changes immediately; however, if you do not click the
Note:
Use the WebManager’s drop-down menus to navigate through the WebManager. Do not use the browser’s Back button.
CLI
The Command Line Interface (CLI) is a command line option for Device Server configuration/management and user access. See a full explanation of how to use the CLI.
Menu
The Menu is a window-oriented Device Server configuration and user access option. To manage the Device Server, you will also need to use the CLI, WebManager, or DeviceManager, as you cannot download or upload files to the Device Server through the Menu.
Accessing the Menu
Menu access is available to any user whose Line Service is set to DSLogin, and whose User Service is set to DSPrompt. What the user sees depends on what the User Level is set to:
z Menu—Users with User Level Menu will only see the sessions that have been set up for them.
They can start predefined sessions, kill (stop) a running session, resume a session, and logout of the Device Server.
z Restricted—Users with User Level Restricted can basically perform the same tasks as a Menu
user, except that they have the option of performing these tasks via the Menu or the CLI.
z Normal—Users with User Level Normal can do everything a Restricted user can do, plus start a
free session (connecting to any host on the network), set up their own user parameters (sessions, password, language, hotkey prefix), define their terminal, and become the Admin user (if they know the Admin password).
z Admin—Users with User Level Admi n (not the Admin user), have complete access to the
Device Server, the same as the Admin user. Through the Menu program, the Admin level user can configure the Device Server, although there are several tasks that can only be done in the CLI, such as downloading and uploading files and saving the configuration to FLASH.
Chapter 6, Command Line Interface on page 137 for
52 IOLAN Device Server User’s Guide, Version 1.8
Page 53
Menu Conventions
You select an option from the Menu by using the keyboard up and down arrows to navigate the list. When the menu item you want to access is highlighted, press the list of options or to get the configuration screen, depending on what you select. When you are done configuring parameters in a screen, press the
exit the form
you will be prompted with to return to the screen so you can press
If there are a number of predefined options available for a field, you can scroll through those items by pressing the arrows to highlight the option you want, and then press
DHCP/BOOTP
If you have a DHCP/BOOTP server and the Device Server’s Server Service DHCP/BOOTP is enabled, the Device Server can obtain its IP address and several configuration parameters from the DHCP/BOOTP server when it boots up. However, you must use another method for creating the configuration file, like the DeviceManager, WebManager, or the CLI. See
Parameters on page 74 for more information on the DHCP/BOOTP parameters that can be set for the
Device Server. When DHCP/BOOTP is enabled and there is a DHCP/BOOTP server within the network, the IP
Address obtained from DHCP/BOOTP will always override the Device Server’s configured IP Address when the Device Server is rebooted.
DHCP/BOOTP
Enter key to either get to the next
Enter key and then the Enter key again to Accept and
. If you want to discard your changes, press the Esc key to exit a screen, at which point
Changes will be lost, proceed? (y/n), type y to discard your changes or n
Enter to submit your changes.
Space Bar or you can type l (lowercase L) to get a list of options, use the up/down
Enter to select it.
DHCP/BOOTP
53
Page 54
SNMP
SNMP
Before you can configure/manage the Device Server using SNMP, you need to set the Device Server IP address and configure a read-write user for SNMP version 3 or a community for SNMP version 1 or 2. You can use DeviceManager, CLI, or the Menu to set the IP address and user/community (don’t forget to reboot the Device Server before connecting with the SNMP manager to make your changes take effect).
Once the IP address and user/community have been set, load the file from the Device Server CD-ROM into your SNMP manager.
Connect to the Device Server through your SNMP manager using its IP address to configure/manage the Device Server. Expand the folders. Below is an example of the configurable parameters under the
PERLE-IOLAN-DS1-MIB folder to see the Device Server’s parameter
ServicesInfo folder.
The first variable in each folder is the Status variable, for example, serviceStatus. When you perform a
z 1—Indicates that the container folder is active with no changes. z 2—Indicates that the container folder is active with change(s).
GET on this variable, one of the following values will be returned:
Once you have completed setting the variables in a folder, you will want to submit your changes to the Device Server. To do this, set the
Status variable to 6.
z 4—Indicates that the changes in the container folder are to be submitted to the Device Server. z 6—Indicates that the changes in the container folder are to be discarded.
Status variable to 4. If you want to discard the changes, set the
If you want to save all the changes that have been submitted to the Device Server, you need to expand the the configuration changes take effect,
adminInfo container folder and SET the adminFunction to 1 to write to FLASH. To make
SET the adminFunction to 3 to reboot the Device Server.
54 IOLAN Device Server User’s Guide, Version 1.8
Page 55
Configuring the Device
4
Server Chapter 4
Introduction
This chapter provides general information about configuring the Device Server for your production environment. Although this chapter is not specific to any configuration method, there should be enough information that you can apply the information to any of the configuration methods.
When you are configuring the Device Server, remember that none of your configuration changes will be permanent until you submit/apply your changes, save to FLASH, and reboot the Device Server.
Configuring the Device Server
General Device Server Configuration
At this point, you should already have assigned the Device Server an IP address. Therefore, you have your choice of how to configure the Device Server; using the DeviceManager, WebManager, Menu, CLI, or SNMP.
Device Server Services
In order to be as flexible and accessible as the Device Server is, it can run several predefined daemon and client applications. The Device Server can run the following daemon applications:
z TelnetD z SPCD (the TruePort daemon) z DeviceManagerD z HTTPD z SNMPD z ModbusD
If you disable any of the daemons, it can affect how the Device Server can be used or accessed. For example, if you disable HTTPD, you will not be able to access the Device Server with the WebM anager. If you disable DeviceManagerD, the DeviceManager will not be able to connect to the Device Server. If you do not want to allow users to Telnet to the Device Server, you can disable TelnetD; therefore, disabling daemons can also be used as an added security method for accessing the Device Server.
The following client applications can run on the Device Server:
z Syslog z DHCP/BOOTP
If you do not have a DHCP/BOOTP server in your network, we recommend that you disable the DHCP/BOOTP service to speed up Device Server reboots (otherwise, the Device Server waits for a DHCP/BOOTP packet until it times out on a reboot).
By default, all daemon and client applications (excet DHCP/BOOTP) are enabled and running on th e Device Server.
IOLAN Device Server User’s Guide, Version 1.8 55
Page 56
Configuring the Device Server
TruePort
The TruePort utility acts as a com port redirector that allows applications to talk to serial devices across a network as though the serial devices were directly attached to the server. For Device Server I/O models, you can also monitor and control I/O through the TruePort client. Yo u can map the baud rate of the host COM port to a higher baud rate for the serial line that connects the serial device and the Device Server. You must be running the TruePort daemon on the host that is accessing the serial device for this to work. See
Hardware Configuration
Configure the ethernet interface that is connecting the Device Server to the LAN and the serial cable that is connecting the Device Server to the serial device.
Ethernet Connection
You need to know the ethernet interface speed and duplex as follows, unless you are using the Auto detect option:
z 10 Mbps half or full duplex z 100 Mbps half or full duplex
TruePort on page 199 for more information about the TruePort utility .
Serial Connection
You also need to know the serial interface specifications as follows (TS2 support EIA-232 only):
z EIA-232 and its speed z EIA-422 and its speed z EIA-485 and
– its speed – half duplex with/without echo suppression or full duplex – TX driver control is automatic or RTS
Other
The most important thing to keep in mind when configuring the hardware parameters is to make sure that they are consistent with the serial device you have connected to the port. So, if you are connecting to a modem that sends out a DSR signal, you probably want to turn the option on. Following is a list of just some of the other hardware configuration options:
z Data Bits—5 to 8 z Stop Bits—1, 1.5, 2 z Monitor DSR—on, off z Monitor DCD—on, off z Parity—None, Odd, Even, Space, Mark z Flow—Software, Hardware, or None
Monitor DSR
56 IOLAN Device Server User’s Guide, Version 1.8
Page 57
Modbus Configuration
This sections provides a brief overview of the steps required to configure a Device Server for your Modbus environment. You can read the
Settings on page 59 sections for more specific information about the Modbus settings.
Overview
Configuring a Master Gateway
To configure a Master Gateway (Modbus Master resides on the serial side of the Device Server), do the following:
1. Verify that the default Modbus Gateway settings (the settings to the Slave Gateway do not apply
here) in the Server section work in your environment; if they don’t configure as required.
2. Set the Line Service parameter to Modbus Master for the Line connected to the Modbus serial
Master.
3. In the Modbus Master settings, map the Modbus TCP Slave’s IP addresses and their UIDs that
the Modbus serial Master will attempt to communicate with.
Configuring a Slave Gateway
To configure a Slave Gateway (Modbus Master resides on the TCP/Ethernet network), do the following:
1. Verify that all the default Modbus Gateway settings in the Server section work in you r
environment; if they don’t configure as required.
2. Set the Line Service parameter to Modbus Slave for the Line connected to the Modbus serial
Slaves.
3. In the Modbus Slave settings, specify the Modbus Slave UIDs that the Modbus TCP Master will
attempt to communicate with.
Modbus Configuration
Modbus Gateway Settings on page 58 and Modbus Line
57
Page 58
Modbus Configuration
Modbus Gateway Settings
The scenarios in this section are used to illustrate how the Modbus Gateway settings are incorporated into a Modbus device environment. Depending on how your Modbus Master or Slave devices are distributed, the Device Server can act as both a Slave and Master Gateway(s) on a multiport Device Server or as either a Slave or Master Gateway on a single port Device Server.
Modbus Master Gateway
The Device Server acts as a Master Gateway when the Modbus Master resides on the serial side of the Device Server. Each Modbus Master can communicate to UIDs 1-247.
Modbus Slave
Serial
EIA-232
Modbus Master
Modbus Slave
TCP
Modbus Slave
Master Gateway
Network
EIA-422/485
Device Server
Modbus Master
Modbus Slave Gateway
The Device Server acts as a Slave Gateway when the Modbus Master resides on the TCP/Ethernet network and the Modbus Slaves reside on the serial side of the Device Server. Note that there is only one Slave Gateway for the Device Server. You can define only one Slave Gateway for the Device Server, although multiple lines/ports can participate as part of that gateway (depending on how you configure the
Modbus Master
Line Service settings).
TCP
Network
Slave Gateway
Serial
EIA-232
EIA-422/485
Modbus Slave
Modbus Master
58 IOLAN Device Server User’s Guide, Version 1.8
Device Server
Modbus Slave
Modbus Slave
Modbus Slave
Page 59
Modbus Line Settings
Modbus Master Settings
When you have Modbus Masters on the serial side of the Device Server, configure the Line as a Modbus Master. If you also have a Modbus serial Slave on the same serial network as the serial Modbus Master that communicates with that serial Master, do not define its UID in the Remote Slave IP Mappings settings, or the Modbus serial Slave may not function properly. You must configure the Modbus TCP Slaves (we term these as Remote Slave IP Mappings) on the TCP/Ethernet side so the Device Server can properly route messages to the appropriate UIDs configured for those remote Modbus TCP Slaves.
Modbus Slave
TCP
Network
Master Gateway
Device Server
Serial
EIA-422/485
Modbus Configuration
EIA-232
Modbus Master
Modbus Slave
Modbus Slave
Do not include in Device Server configuration
Modbus Master
Modbus Slave Settings
When you have Modbus Slaves on the serial side of the Device Server, configure the Line as a Modbus Slave. There is only one Slave Gateway in the Device Server, so all Modbus serial Slaves must be configured uniquely for that one Slave Gateway; all Modbus serial Slaves must have unique UIDs, even if they reside on different serial ports, because they all must be configured to communicate through the one Slave Gateway.
Modbus Master
TCP
Modbus Master
Slave Gateway
Network
Device Server
Modbus Slave
Serial
EIA-232
EIA-422/485
Modbus Slave
Modbus Slave
Modbus Slave
59
Page 60
Modbus Configuration
Example Scenario
The following example describes the settings that you would configure to set up a Modbus environment on a multiport Device Server, where the Modbus Master resides on a serial port/line connected to the Device Server. This scenario assumes two things, that the Modbus daemon) is enabled and that the default The Modbus Master communicates with Modbus Slaves that reside on the TCP/Ethernet network and on another serial port defined as part of the Slave Gateway in the Device Server, and with a Modbus serial Slave (UID 10) that is on the same serial line as the Modbus Master itself. The Device Server will act as a Master Gateway for the Modbus serial Master and allow it to communicate to the remote Modbus TCP Slaves. By configuring the Device Server’s own IP address as a remote Modbus Slave and having the Slave Gateway configured, the Modbus serial Master can communicate with Modbus serial Slaves on another serial port/line on the Device Server (UIDs 6-8).
Modbus Slave IP: 10.10.10.12 UID: 23
Modbus Slave IP: 10.10.10.11 UID: 22
TCP
Master Gateway/Port 2 Slave Gateway/Port 1
Network
Device Server IP: 10.10.10.10
Service ModbusD (the
Modbus Gateway settings have not been changed.
UID: 6
UID: 7
UID: 8
Modbus Slaves
Port 1
Port 2
EIA-422/485
UID: 10
Modbus Slave
Modbus Master
Do not include in Device Server configuration
When the Modbus Master is communicating with the TCP/Ethernet Modbus Slaves, the Line/port that the Modbus Master is attached to must be configured with a By configuring the Remote Slave IP settings as:
60 IOLAN Device Server User’s Guide, Version 1.8
Line Service of Modbus Master.
Page 61
Modbus Configuration
The Device Server will send a request and expect a response from a Modbus Slave with an IP Address of 10.10.10.11 on Port 502 with UID 22 and from Modbus Slave with and IP Address of
10.10.10.12 on Port 502 with UID 23 (remember when
Range Mode is set to Host, the Device
Server increments the last octet of the IP address for each UID specified in the range). Also note that the Modbus Slave (UID 10) that is on the same line as the Modbus Master should not
be configured anywhere in the Device Server’s Master Gateway table for that serial port, or a Modbus Exception may be sent (if this option is enabled) because the Device Server will attempt to connect and send to a non-existent remote Modbus TCP Slave and a response timeout can occur.
To communicate with the Modbus Slaves on the serial side of the Device Server, the Device Server must also be configured to be a Slave Gateway. The Modbus Slaves on a serial port attached to the Device Server must be connected to a Line/port that is configured for the
Slave
. To communicate with the Modbus Slaves on the serial port configured as part of a Slave
Line Service of Modbus
Gateway, the Remote Slave IP settings are configured as:
The Device Server also acts as a Slave Modbus Gateway, receiving all the messages for IP address
10.10.10.10 and routing them to Modbus Slave devices with UIDs 6,7, and 8. You must also configure the Line Service as Modbus Slave for the Modbus serial slaves as:
The Modbus serial Master will attempt to communicate through the Modbus Master Gateway to Modbus serial Slaves with UIDs 6, 7, and 8. In order to accomplish this, the communication is routed through the Device Server’s Modbus Slave Gateway from the Device Server’s Modbus Master Gateway, to the serial Slaves.
61
Page 62
Machine To Machine Con nections
Machine To Machine Connections
If you are using the Device Server to connect two hosts, allowing data to flow freely between them, you just need to configure the serial device is a security Card Reader that needs to transmit and receive information to/from a host on the network that maintains the Card Reader’s application every time an employee uses an access card to attempt to gain entry to the company.
Server and the Line (no User required). In the following example, the
perle
Card
Reader
After configuring the Server parameters (Server Name, IP Address, Ethernet and Serial interfaces, etc.), the the Card Reader and its associated application on the Security host (though the Device Server), by specifying the Security host name (which must already be configured in the Device Server’s Host Table) and TCP/IP port number. Therefore, the Card Reader can make a request to the Security host card reader application for employee verification, also logging access time, employee name, etc., and the Security host application can send back a code that does or does not unlock the door.
Line Service is set to Sil Raw , which creates an automatic, continuous connection between
Device Server
Network
Users Connecting to Serial Devices
For a user to connect to the serial device connected to the Device Server from the LAN, the Line
Service
the Easy Port Access Menu, depending on the Users who are Level Admin or Normal will access the serial device directly; the user must connect to
the Device Server’s IP address and port number (the login with a user name and password; if this is successful, the user is automatically connected to the serial device.
Users who are Level Restricted or Menu can access the serial device through the Easy Port Access Menu, which displays the line number and name and a logout option; the user just needs to connect to the Device Server’s IP address. The user will be asked to login with a user name and password; if this is successful, the Easy Port Access Menu is displayed.
must be set to Rev Telnet. The user will either access the serial device directly or go through
User Level setting.
DS Port parameter). The user will be asked to
Security
Users Connecting to the LAN
For a user to connect to the LAN through the Device Server from a serial device, the Line Service can be set to any
User accounts should be created when:
z authentication is being done locally by the Device Server. z you want to create predefined sessions for a user to limit that user’s access to the network.
62 IOLAN Device Server User’s Guide, Version 1.8
Direct or Silent setting, plus Bidir or DSLogin.
Page 63
Connecting To the Device Server
When a user connects to the Device Server, that user is authenticated and is usually set up with predefined sessions or given the opportunity to configure a any protocol (must have a user must have a
Line and User Service of DSLogin and DSPrompt, respectively. So, user Dennis is
authenticated by the Device Server and then chooses to configure a using the Telnet protocol (Dennis could have attempted to access any host on the network).
Level of at least Normal to configure a Free Session). In this example, the
Setting Up Lines
Free Session to access any host using
Free Session to the HR_Server
Dumb Terminal
Dennis
User: Dennis
perle
Device Server
Connecting Through the Device Server
When a user connects through the Device Server, that user is authenticated and is usually set up with a
User Service that, once authentication is completed successfully, passes the user onto the specified
host. Therefore, the the user will use to access the host; in this example, the
Service Dir Telnet
Dennis will always have to log into the same server with this configuration.
Dumb Terminal
Dennis
Line Service is set to DSLogin and the User Service is set to whatever protocol
is selected, the IP address of the HR_Server is specified as the target Host IP. User
perle
Device Server
Network
Free Session: Telnet
User Service is set to Dir Telnet. When User
Network
HR_Server
HR_Server
Setting Up Lines
Line and port is often used interchangeably. They are almost the same, that is, each line has an associated port number (Line 1 is port 10001 by default).
How you set up a line is really determined by the device that is connected to the line. This section goes over some of the common ways a line is used and things that you will want to keep in mind when configuring the line.
DSLogin
When you configure the Line for DSLogin, users connecting to the Device Server will have to go through some form of authentication, either local or remote authentication. Regardless of whether a user has been configured in the User table (local authentication) or is inheriting the Default User’s attributes (remote or Guest authentication), when a that connection (
Telnet) will inherit the connection settings defined for DSLogin.
User Service is selected (other than DSprompt),
63
Page 64
Setting Up Lines
Direct/Silent/Reverse Connections
Direct connections bypass the Device Server, enabling the user to log straight into a specific host. A direct connection is recommended where a user logging in to the Device Server is not required. It is also recommended where multiple sessions are not a requirement. Direct connections require user interaction: the message session to the host is not initiated until displayed. The message is redisplayed on logout.
Silent connections are the same as direct connections except that they are permanently established. The host login prompt is displayed on the screen. Logging out redisplays this prompt. Silent connections, unlike direct connections, however, make permanent use of pseudo tty resources and therefore consume host resources even when not in use.
Reverse connections enable a host on the network to establish a connection through the Devi ce Server port to a serial device.
Press return to continue is displayed on the user’s screen and the
Virtual Modems
Vmodem is a feature of the Device Server that provides “modem like” communication between two
Device Servers on a network or between a Device Server and a host. This feature behaves like two modems connected across a telephone line. Typically, you use the multiple devices communicating with a central site. With just a single IOLAN Device Server at each end of the network, you don’t need to use multiple modems, avoiding the associated costs of calls and connections.
The data is sent in raw format from the virtual modem and can be received by another Device
Server
configuring the host and port number of the receiver; if the receiving side is also a set the
Vmodem to initiate bidirectional data flow) and the Device Server port that the data is coming in
on (this should match the port number on the sending connection by typing
+++ATH. The ip_address can be in IPv4 or IPv6 formats and is the IP address of the receiver. For
example, punctuation.
or a host. This data can be sent automatically using the Monitor DSR option and then
Line Service to Rev Raw or Vmodem (Rev Raw if the Device Server is only receiving,
ATD<ip_address>,<port_number> and end the connection by typing
ATD123.34.23.43,10001 or you can use ATD12334234310001, without any
Enter is pressed, after which the host login prompt is
Vmodem feature when you have
Device Server,
Device Server). Or, you can manually start a
BIDIR
When you configure BIDIR, you are creating a bidirectional raw connection, meaning that the connection can be initiated from either the ethernet or serial side.
TruePort
When you configure a line for TruePort, the Device Server provides a complete COM port interface between the attached serial device and the network. You can also set the which allows either the client or the Device Server to initiate communication. See
199 and the TruePort documentation for your operating system more information.
Signal I/O
When you configure a line for Signal I/O, you are using the DSR, DCD, CTS, DTR, and RTS serial pins for I/O channel digital input (DSR, DCD, and CTS) or digital output (DTR and RTS). Only after
Signal I/O is specified for the Line Service can you configure the serial pins for I/O.
64 IOLAN Device Server User’s Guide, Version 1.8
Client Initiated option,
TruePort on page
Page 65
UDP
Setting Up Lines
When you configure UDP, you are setting up a range of IP addresses and a port number that you will use to send UDP data to or receive UDP data from. For example:
The UDP configuration window, taken from the DeviceManager, is configured to:
z UDP Entry 1
All hosts that have an IP address that falls within the range of 172.16.1.1 to 172.16.1.25 and listen to only receive UDP data from the hosts in that range with a source
z UDP Entry 2
Port 33001 will receive UDP data from the serial device. The serial device will
Port of 33001.
All UDP data received from hosts that have an IP address that falls within the range of
172.16.1.20 to 172.16.1.50 and Port 33010 will be sent to the serial device. The Device
Server will not send any data received on its serial port.
z UDP Entry 3
All hosts that have an IP Address that falls within the range of 172.16.1.75 to 172.16.1.80 and who listen to
Port 33009 will receive UDP data from the serial device. No UDP data will be
sent to the serial device.
z UDP Entry 4
This entry is disabled since Direction is set to None.
If Direction is set to In or Both, and Port is set to 0 (zero), the Device Server will learn a host IP Address and Port number based on the first UDP packet it receives and will then only send and/or accept UDP data from that host.
65
Page 66
Setting Up Users
Serial Tunnel Settings
The purpose of the serial Line Service Client/Server Tunnel is to allow two Device Servers that are connected back-to-back over Ethernet to virtually link two serial ports, based on RFC 2217. The serial device that initiates the connection is the although once the serial communication tunnel has been successfully established, the tunnel will stay connected and communication can go both ways.
Client Tunnel and the recipient is the Server Tunnel,
Serial
Server Tunnel
Device Server
The Server Tunnel will also support Telnet Com Port Control protocol as detailed in RFC 2217.
Serial
Server Tunnel
Device Server
The port signals will also follow the signals on the other port. If one port receives DSR then it will raise DTR on the other serial port. If one port receives CTS then it will raise RTS on the other port.
Setting Up Users
You can create up to four users, in addition to the Admin user (who cann ot be deleted). A user can even represent a device, like a barcode or a card swipe device, that you want to be
authenticated.
User Accounts
When a serial device (like a dumb terminal or a barcode reader) is trying to access a host through the Device Server, you will need to configure user accounts when users:
z are authenticated by the Device Server and then connect to a host. z want a single or multiple session(s) on a host; here they initially login to the Device Server
before starting that session. The Device Server is used to configure and start the session.
When a host is accessing a serial device (like a modem or a server), you will need to configure user accounts where users:
z are using a reverse telnet connection to manage a UNIX server or a router.
perle
Network
perle
Device Server
perle
Network
Serial
Client Tunnel
Running
2217 Application
66 IOLAN Device Server User’s Guide, Version 1.8
Page 67
User Levels
Setting Up Users
There are four User Levels: Admin, Normal, Restricted, and Menu. Setting up users is only necessary when the users are actually connecting to the Device Server. Oftentimes, the Device Server is used as a gateway to a network and the user never actually logs into the Device Server itself. Users who do log into the Device Server ( will have to navigate by either the Menu or CLI (except for users with
Line Service set to DSLogin and User Service set to DSPrompt)
Menu privileges, who can only
use the Menu).
z Admin—Users with Admin privileges have full administrative access to the IOLAN Device
Server. This is not the same as the Admin user, but has equal authority (the Admin user is a permanent, factory-set user on the IOLAN Device Server).
z Normal—Users with Normal privileges have access to the Sessions menu and associated CLI
only . They can start sessions, define and predefine sessions, and can change their own user environment.
z Restricted—Users with Restricted privileges have access to a restricted Sessions menu and
associated CLI; they can only open sessions predefined for them by the Admin user, but not alter their own environment or sessions. Predefined sessions can also be configured to start automatically at login.
z Menu—Users with Menu privileges have access to predefined session. All other functionality is
unavailable.
When the Admin user logs into the Device Server, the prompt ends with a #, whereas all other users’ prompts ends with a
$ or £, depending on the character set.
Sessions
Sessions are defined for users who are coming in through a serial device going to a host on the LAN. Users who have successfully logged into the Device Server (User Service set to DSprompt) can start
up to four login sessions on LAN hosts. These users start sessions through the Menu option
Sessions.
Multiple sessions can be run simultaneously on the same host or on different hosts. Users can switch between different sessions and also between sessions and the Device Server using hotkey commands.
Users with Admin or Normal privileges can define new sessions and connect through them, even configure them to start automatically on login to the Device Server. only start sessions predefined for them by the Admin user.
You can configure the User access rights to the port, such as Read/Write (RW) or Read Input (RI).
Users From LAN to Device Server to Serial Device
Easy Port Access Menu
The Easy Port Access Menu is displayed when a Restricted or Menu level user logs into the box from the Ethernet side ( Easy Port Access Menu displays the line number, line name, line protocol (either
rev-ssh), and a logout option. You can only access a line if it has the same connection protocol as
the one you used to log into the Device Server. So, if you used SSH to log into the Device Server and the
Line Service is set for Rev Telnet, you will not be able to access the serial device connected to
that line.
Line Service set to Rev Telnet or Rev SSH) to access a serial device. The
Restricted and Menu users can
rev-tel or
67
Page 68
Setting Up Users
Reverse Sessions and Multisessions
(2 Port+ only) The interaction between reverse sessions and multisessions is somewhat complex, so the definition of each parameter is provided to give you a context for their interaction.
Reverse Session—The definition of a Reverse Session is a TCP connection to a TCP port (defined in the Line configuration as the or
Reverse Raw. Other LAN to Device Server connections, such as the connection to the well-known
Telnet or SSH ports (the management TCP ports of 23 for Telnet and 22 for SSH), do not count as reverse sessions.
Reverse Session Limit—This server parameter is the maximum number of Reverse Sessions (as defined above) that can be active on the Device Server at any given moment. This value is completely independent of the Line maximum of 20, that only says that the total number of reverse sessions cannot exceed 20; it says nothing about total number of reverse sessions per line, total number of active line, etc.
The minimum value is 1. The maximum value is determined as follows:
1. Add up all the serial ports, internal modems, and PCI slots in the Device Server. This number
equals the maximum number of lines available on the Device Server.
2. If the maximum number of lines is less than 4 exclusive (that is, 1, 2, or 3), then multiply that
number by 4 to obtain the maximum Server maximum number of lines by 2 to obtain the maximum Server
Multisessions—The Line Multisessions limit is the number of additional reverse sessio ns (beyond the first reverse session) allowed on the line. Therefore, if this number is set to 5, the total number of reverse sessions allowed on the line is 5+1 or 6.
The default and minimum value is 0, which means that reverse Multisessions is disabled and you only get the 1 default reverse session; therefore, the maximum value is the maximum
Reverse Session Limit
Reverse Session Security—If this Line parameter is enabled, the user must login when making a
Reverse Telnet connection to a configured DS Port (the TCP port associated with the line that is
configured for a reverse connection). If the line is configured for redundant, because a login is always required when SSH is specified.
So, in order to make multiple reverse connections to a line, the line must be configured to log users in so the user’s Line Access Rights can be obtained from the User profile (regardless of whether that profile comes from a defined User, the Default User’s settings, or is passed to the Device Server from TACACS+ or RADIUS). This means that one of the following conditions have been met:
z The line is configured for Reverse Telnet and Reverse Session Security is enabled. z The line is configured for Reverse SSH.
If users are connecting to the Device Server by the management TCP port (or well-known port of 23 for Telnet and 22 for SSH), they always have to login to the Device Server and depending on their access level can get:
admin—standard CLI/Menu with admin privileges normal—standard CLI/Menu with normal privileges restricted—Easy Port Configuration Menu menu—Easy Port Configuration Menu
If users are connecting to the Device Server by the IP address and configured DS Port (for example, the line has a configured
telnet 101.170.12.15 88 command), a line set up for Reverse Telnet would require a login if Reverse Session Security is enabled, otherwise, the User settings would dictate what the user sees.
For
Reverse SSH, the user always has to login to the Device Server.
DS Port) on a line that is configured for Reverse Teln et, Reverse SSH,
Multisessions number. If the Reverse Session Limit is set to a
Reverse Session Limit, otherwise, multiply the
Reverse Session Limit.
Server
-1.
Reverse SSH, this option is
DS Port of 88, so the user would connect with the
68 IOLAN Device Server User’s Guide, Version 1.8
Page 69
Configuring Network Options
Hosts
This is probably one of the first Device Server options you want to configure, since so many other configuration options require a preconfigured host. You can use any host name you want, since the host name is used only by the Device Server. You can configure up to 20 hosts using IPv4 or IPv6 internet addresses.
Gateways
Gateways are hosts that connect Local Area Networks (LANs) together. If you want to access a host that isn’t on your local network, you will be connected via a gateway. Gateways route data via other gateways until the destination local network is reached. There are three types of gateways:
z Default—A gateway that provides general access beyond your local network. z Host—A gateway reserved for accessing a specific host external to your local network. z Network—A gateway reserved for accessing a specific network external to your local network.
You can specify up to twenty gateways.
Configuring Network Options
Syslog
The system log is sent to the specified host. You can configure a primary and secondary host for the syslog information and specify the level for which you want syslog information sent.
SNMP
If you are using SNMP to manage/configure the Device Server, or to view statistics or traps, you must set up a User in SNMP version 3 or a Community in SNMP version 1,2 to allow your SNMP manager to connect to the Device Server; this can be done in the DeviceManager, WebManager, CLI, or Menu. You must then load the perle-ds1.MIB (found on the CD-ROM packaged with the Device Server) file into your SNMP manager before you connect to the Device Server.
Configuring Time
The Device Server has an internal clock that can be set, but it will be reset during a reboot or a power outage.
Language support
T wo language files, in addition to English, are supplied on the supplemental CD, French and German. You can use any of these language files to create a translation into a language of your choice. You can download the language file (whether the language is supplied or translated) into the Device Server and select the WebManager field labels display in your language.
You can view Menu, CLI, or WebManager in one other language only (as well as English). If you download another language file, this new language will replace the first language you downloaded.
You can revert to English at any time; the English language is stored permanently in the Device Server and is not overwritten by your new language. Each user logged into the Device Server can operate in either English or the downloaded language.
Language option of Customlang (custom language), making the Menu, CLI, and
69
Page 70
Language support
Loading a Supplied Language
This section describes how to download a language file using the CLI, since it is the least intuitive method. French and German language files are provided on the supplemental CD.
T o load one of the supplied languages into the Device Server, so the Menu, CLI and WebManag er fields appear in another language, do the following:
1. Open the supplemental CD and identify the language file, either Iolan_ds_French.txt or
Iolan_ds_German.txt, or supply one of your own translated files.
2. Copy the language file to a host machine on the network; place it in the main file system or on
the main hard drive.
3. Either use the TFTP defaults in the Device Server or, configure as necessary, TFTP in the Device
Server.
4. In the CLI of the Device Server, enter the host IP address and file name; for example,
netload customlang 172.16.4.1 / temp/Iolan_ds_ French.txt
Do not enter a drive letter! Also, the path and/or file name must begin with the forward slash (/) character.
The Device Server will download the language file via TFTP.
5. To set an individual user to the new language, go to the Users menu and, in the Language field
select
Customlang. In the CLI (only) you can set individual users or all users to the new
language; see the
6. The user will see the change of language when he/she logs out (Main Menu, Sessions Menu,
Logout) and logs back into the Device Server. If, as Admin user, you change your language
setting to
Customlang, you will see the text menus display in the new language when you save
and exit the
set user * command.
Change User form.
Note:
If you download a new software version, you can continue to use your language unchanged; however, we recommend translating the new strings, which will be added to the end of the language file. A
On successful download, the Customlang in the Device Server will be overwritten by the new language.
Translation Guidance
To help you with your translation, of supplied ASCII text language files we offer the following guidance:
z The Device Server will support languages other than English (and the supplied German and
French languages). The English language file, each line at the beginning of the line. If a translated line goes over that character length, it will be displayed truncated in the Menu, CLI, or WebManager.
z Translate line for line, do not omit lines if you do not know the translation; leave the original
untranslated text in place. Also, you must maintain the same sequential order of lines. It is a good practice to translate the file using a text editor that displays line numbers, so you can periodically verify that the line sequence has not changed from the original file (by comparing it to the original file).
z Keep all translations in quotes, otherwise the line will not display properly. z Each line must end with a carriage return. z If a line contains only numbers, for example 38400, leave that line in place, unchanged (unless
you are using a different alphabet).
Reset to Factory Defaults will reload the Customlang as English.
english.txt, displays the character length of
70 IOLAN Device Server User’s Guide, Version 1.8
Page 71
Software Upgrades and Language Files
If you receive a software upgrade for the Device Server, the language files supplied on the supplemental diskette/CD might also have been updated. We will endeavour to provide a list of those changes in another text file on the same supplemental CD.
Downloading Terminal Definitions
Note:
If you are already using one of the supplied languages, French or German, you probably want to update the language file in the Device Server. Until you update the Device Server with the new language file, new text strings will appear in English.
If you are already using a language translated from an earlier version, you probably want to amend your translation. When a language file is updated, we will try to maintain the following convention:
1. New text strings will be added to the bottom of the file (not inserted into the body of the existing
2. Existing text strings, if altered, will be altered in sequence; that is, in their current position in the
3. The existing sequence of lines will be unchanged.
4. Until you have the changes translated, new text strings will appear in the Menu, CLI, or
The upgrade of your software (firmware) will not change the display of the language in the Menu, CLI, or WebManager.
file).
file.
WebManager in English.
Downloading Terminal Definitions
All terminal types can be used on the Device Server. Some terminal types which are not already defined in the Device Server, however, are unable to use Full Screen mode (menus) and may not be able to page through sessions properly. When installed, the Device Server has several defined terminal types—Dumb, WYSE60, VT100, ANSI, TVI925, IBM3151, VT320, and HP700.
If you are not using, or cannot emulate, any of these terminal types, you can add up to three additional terminal definitions to the Device Server. The terminal definitions can be downloaded from a TCP/IP host.
To download terminal definitions, follow these steps:
1. Decide which TCP/IP host you are going to use. It must be a machine with TFTP enabled.
2. Configure TFTP in the Device Server as necessary.
3. Download the new terminal definition to the Device Server as Term1, Term2, or Term3.
4. In the Line configuration, select the Terminal Type Termx that you custom defined.
Creating Terminal Definition Files
To create new terminal definition files, you need to copy and edit the information from the terminfo database.
1. On a UNIX host, change directory to /usr/lib/terminfo/x (where x is the first letter of the
required terminal type). For a Wyse60, for example, you would enter the command
cd /usr/lib/terminfo/w.
2. The termcap files are compiled, so use the command infocmp termfile to read the required
file (for example:
3. Check the file for the attribute xmc#n (where n is greater than or equal to 1). This attribute wil l
corrupt menu and form displays making the terminal type unsuitable for using Menu mode.
4. If the terminal definition is suitable, change to a directory of your choice.
infocmp wy60).
71
Page 72
Downloading Terminal Definiti ons
5. Rename and copy the file to the directory specified at step 4. using the command
infocmp termfile > termn where n is greater than or equal to 1; (for example, infocmp wy50 > term1). Make sure the file has global read and execute permission for its
entire path.
6. Edit the file to include the following capabilities in this format:
term= acsc= bold= civis= clear= cnorm= cup= rev= rmacs= rmso= smacs= smso= page= circ=
For example:
term=AT386 | at386| 386AT |386at |at/386 console acsc=jYk?lZm@qDtCu4x3 bold=\E[1m civis= clear=\E[2J\E[H cnorm= cup=\E[%i%p1%02d;%p2%02dH rev=\E4A rmacs=\E[10m rmso=\E[m smacs=\E[12m smso=\E[7m page= circ=n
Note:
As you can see from the example, capabilities which are not defined in the terminfo file must still be included (albeit with no value). Each entry has an 80 character limit.
On some versions of UNIX, some of the capabilities are appended with a millisecond delay (of the form $<n>). These are ignored by the Device Server and can be left out.
The ‘acsc’ capability, if defined, contains a list of character pairs. These pairs map the characters used by the terminal for graphics characters to those of the standard (VT100) character set.
Include only the following character pairs: jx, kx, lx, mx, qx, tx, ux and xx (where x must be substituted by the character used by the terminal). These are the
box-drawing characters used to display the forms and menus of Menu mode. They must be entered in this order.
The last two capabilities will not be found in the terminfo file. In the page field you must enter the escape sequence used by the terminal to change screens. The whether the terminal can use to
y or n. These capabilities can be found in the documentation supplied with the terminal.
previous page and next page control sequences. It must be set
circ field defines
72 IOLAN Device Server User’s Guide, Version 1.8
Page 73
TFTP Configuration
TFTP can be configured for two unique transfer operations:
1. Between the DeviceManager and a Device Server. This configuration is accessed by selecting
Tools, Options from the DeviceManager’s tool bar. You can specify the number of times the DeviceManager’s TFTP server retries a file transfer to a Device Server, how long the TFTP process will wait (timeout) before retrying to transfer a file, and the UPD port that will be used for the file transfer between the DeviceManager and the Device Server. (DeviceManager only.)
2. Between the Device Server and a host. This configuration is accessed by selecting Network,
TFTP in the DeviceManager, by typing Configuration, TFTP from the Menu, by selecting ServerInfo, tftpRetry and tftpTimeOut in the SNMP MIB, or by selecting Network, TFTP in the WebManager. You can configure the number of times the Device Server’s TFTP client retries a file transfer to a host and how long the TFTP process will wait (timeout) before retrying to transfer a file.
You must have a TFTP server running on any host that you are uploading or downloading files to/from. If you are using the DeviceManager and transferring a local file to a Device Server, you still need to have a TFTP server running on your PC. When you specify the file path, the path must be relative to the default path set in your TFTP server software (do not use drive letters in the file path).
TFTP Configuration
set server tftp in the CLI, by selecting Network
Resetting Configuration Parameters
You can reset the Device Server to its factory settings through any of the following methods:
z You can push in the recessed button at the back of the Device Server hardware for more than
three seconds (pushing it in and then quickly releasing will just reboot the Device Server)
z DeviceManager, select Tools, Reset to Factory Defaults z CLI, at the command line type, reset factory z WebManager, click the Factory Defaults button z Menu, select Network Configuration, Reset to Factory Defaults z SNMP, in the adminInfo folder, Set the adminFunction variable to 2
Lost Admin Password
If the Admin user password is lost, there are only two possible ways to recover it:
z reset the Device Server to the factory defaults z have another user that has admin level rights, if one is already configured, reset the Admin
password
DHCP/BOOTP
You can use DHCP/BOOTP to perform the following actions on a single or multipl e Dev ice Servers on bootup:
z auto-configure with minimal information; for example, only an IP address z auto-configure with basic setup information (IP address, subnet/prefix bits, etc.) z download a new version of firmware z download a full configuration file
DHCP/BOOTP is particularly useful for multiple installations: you can do all the Device Server’s configuration in one DHCP/BOOTP file, rather than configure each Device Server manually . Another advantage of DHCP/BOOTP is that you can connect a Device Server to the network, turn on its power and let autoconfiguration take place. All the configuration is carried out for you during the DHCP/BOOTP process.
73
Page 74
Creating Custom Applications
DHCP/BOOTP Parameters
The following parameters can be set in the DHCP/BOOTP bootp file:
z SW_FILE—The full path, pre-fixed by hostname/IP address (IPv4 or IPv6), and file name of the
firmware update.
z CONFIG_FILE—The full path, pre-fixed by hostname/IP address (IPv4 or IPv6), and file name
of the configuration file. Note: these parameters include clear text user passwords.
z GUI_ACCESS—Access to the Device Server from the HTTP WebManager. Values are on or
off.
z SECURITY—Restricts Device Server access to devices listed in the Device Server’s host table.
Values are
z TFTP_RETRY—The number of TFTP attempts before aborting. This is a numeric value, for
example, 5.
z TFTP_TMOUT—The time, in seconds, before retrying a TFTP download/upload. This is a
numeric value, for example, 3.
z CUSTOM_LANG—The full path, pre-fixed by a hostname/IP address (IPv4 or IPv6), and file
name of a translated language file. For example,
192.101.34.211 /accounting/Iolan_ds_german.txt.
z EXTRA_TERM1—(EXTRA_TERM2, EXTRA_TERM3) The full path, pre-fixed by a
hostname/IP address (IPv4 or IPv6), and file name of a termcap file for a specific terminal type.
yes or no.
Creating Custom Applications
You can create custom applications for the Device Server by using the Perle SDK. See the SDK Programmer’s Guide (the SDK and guide are found on the Perle website at
www.perle.com/downloads/index.shtml) for information about the functions that are
supported. You must download the program and any ancillary files to the Device Server and set the
Line Service to Custom App to run a custom application. You must also specify the program
executable in the
Program Command Line parameter.
I/O Model Features
There is a line of I/O Device Servers that can control/monitor the following types of I/O:
z Analog (Input) z Digital Input/Output z Relay z Temperature
Some of the models are I/O combinations and some of the models support one I/O type.
Failsafe Timer
The Failsafe Timer is enabled on a global basis and provides a trigger mechanism that can be configured for each channel when no I/O traffic/management has occurred for the specified amount of time. A Failsafe Action can be configured for each Digital Output channel, each Serial Signal Output channel (DTR and RTS), and each Relay channel to either Activate or Deactivate the output.
74 IOLAN Device Server User’s Guide, Version 1.8
Page 75
Alarms
UDP
I/O Model Features
Analog and Temperature input models support an Alarm mechanism in which you can specify up to five severity levels of alarm triggers and clear levels; the alarm triggers/clear levels can activate in either increasing or decreasing severity levels.
The Digital input supports an Alarm mechanism based on a trigger of either active input or inactive input and can be cleared either manually or automatically (when the trigger condition goes inactive or active, respectively).
Each time an alarm is triggered or cleared, you can specify any combination of the following to be initiated:
z An SNMP trap z A message to syslog
The I/O UDP broadcast feature periodically broadcasts the I/O channel status in a UDP message. You can configure up to four sets of IP address entries (each entry consisting of a start and end IP
address range) to broadcast I/O status data. The data depends on the I/O model (Analog, Digital, Serial Signals) and contains information for all channels.
UDP Unicast Format
In order to interpret the UDP unicast data, you must use the following tables to decipher the appropriate data. If your model does not support a data format (for example, digital data) or you do not have any channels configured for a data format, it will be included in UDP broadcast package, with a Total Length of 0 (zero) and no data following.
Version Total Length Analog Data Digital Data Serial Signal Data
Each section, with the exceptions of the Version and Total Length sections, is comprised of its own subset of bytes.
Analog Data
Each Analog channel is comprised of the following data fields (big Endian format):
Total
Length
2 Bytes 1 Byte
The following section describes the values in the Analog Data field:
z curRawValue—The current raw value received from the Analog to Digital converter. z minRawValue—The minimum value received from the Analog to Digital converter until it is
z maxRawValue—The maximum value received from the Analog to Digital converter until it is
z curEngValue—The current convert ed value (voltage/current for Analog or Celsius/Fahrenheit
z minEngValue—The minimum converted value (vo ltage/current for Analog or
z maxEngValue—The maximum converted value (voltage/current for Analog or
*Data Exists
(in bits)
curRawValue
2 Bytes
minRawValue
2 Bytes
maxRawValue
2 Bytes
cleared.
cleared.
for Temperature).
Celsius/Fahrenheit for Temperature) until it is cleared.
Celsius/Fahrenheit for Temperature) until it is cleared.
Data
curEngValue
4 Bytes
minEngValue
4 Bytes
maxEngValue
4 Bytes
75
Page 76
I/O Model Features
Digital/Relay Data
The digital data is in bit format, 1 meaning On and 0 (zero) meaning Off. Each channel has its own bit, in least significant bit order.
Length *Data
Data (1 Byte, one bit for each channel)
Exists
2 Bytes 1 Byte
(in bits)
Channel4 Channel3 Channel 2 Channel 1
Serial Signal Data
The serial data is in bit format, 1 meaning On and 0 (zero) meaning Off. Each channel has its own bit, in the following order.
Length *Data
Data (1 Byte for each port, one bit for each signal)
Exists
2 Bytes 1 Byte
(in bits)
RTS DTR CTS DCD DSR
*Data Exits Field
The Data Exists field is 1 byte in least significant bit order, for each channel. If data exists for a channel, the bit will be 1, if no data exists for a channel (it is not configured), the bit will be 0 (zero).
Data Exists(1 Byte, one bit for each channel)
Channel4 Channel3 Channel 2 Channel 1
UDP Unicast Example
For an example of the I/O UDP unicast, see the sample program, ioudpbcast.c, found on your CD-ROM.
I/O Modbus Slave
If you have a Modbus serial or TCP application, it can access I/O connected to the Device Server when the I/O Global Modbus Slave is enabled. You mu st supply a unique UID for the Device Server, as it will act as a Modbus Slave.
There are three ways your Modbus Application can connect to the Device Server to access I/O.
Modbus Serial Application Connected to the Serial Port
Your Modbus serial application can be connected right to the Device Server serial port to access I/O.
PC running a
Modbus Serial
Application
Serial
UID: 15
perle
Device Server
Power
I/O Digital Output
76 IOLAN Device Server User’s Guide, Version 1.8
Page 77
I/O Model Features
Modbus Serial Application Connected to the Network
If you want to access the I/O from a LAN connection, you can install TruePort on the PC running the Modbus serial application as described in the network.
TruePort on page 80 and connect to the Device Server over
PC running a
Modbus Serial
Application
Modbus TCP Application
If you have a Modbus RTU or Modbus ASCII program, you can access the I/O by connecting to the Device Server over the network.
PC running a Modbus RTU
or ASCII
Application
Modbus I/O Access
The section defines the function codes and registers you will need to access the I/O through Modbus TCP, Modbus serial, or Modbus serial/TruePort.
Network
Network
UID: 15
perle
Device Server
UID: 15
perle
Device Server
Power
I/O Digital Output
Power
I/O Digital Output
Function Codes
The following function codes are supported by the Device Server:
z 01 read coils z 03 read multiple holding registers z 04 read input registers z 05 write coil z 06 write single register z 08 diagnostics (echo the request) z 15 force multiple coils z 16 write multiple registers
There are four Modbus data models:
Discrete Input Not used Coils Digital Input (DI), Alarm state for DI, Digital Output (DO) Input Registers (IR) Analog Input (AI), Alarm state for AI Holding Registers Status (R), Control value (R/W or W)
77
Page 78
I/O Model Features
A4/T4 Registers
The following registers are supported by the Device Server A4 and T4 input models:
Data Model A1/T1 A2/T2 A3/T3 A4/T4 R/W
Holding Registers:
MB_REG_HR_AI_CLEAR_ALARM_LATCH 2049 2050 2051 2052 W MB_REG_HR_AI_CLEAR_MAX 2113 2114 2115 2116 W MB_REG_HR_AI_CLEAR_MIX 2177 2178 2179 2180 W
Input Registers:
MB_REG_IR_CURR_ENG MB_REG_IR_MIN_ENG MB_REG_IR_MAX_ENG MB_REG_IR_CURR_RAW MB_REG_IR_MIN_RAW MB_REG_IR_MAX_RAW MB_REG_IR_ALARM_LEVEL
2080 2112 2144 2176 2082 2114 2146 2178 2084 2116 2148 2180 2086 2118 2150 2182 2087 2119 2151 2183 2088 2120 2152 2184 2089 2121 2153 2185
R R R R R R R
A4D2/A4R2 Registers
The following coils and registers are supported by the Device Server A4D2 and A4R2 I/O models:
Data Model A1 A2 A3 A4 D1/R1 D2/R2 R/W
Coils:
MB_REG_DI_SENSOR ----- ----- ----- ----- 6149 6150 R MB_REG_DI_SENSOR_ALARM_STATE ----- ----- ----- ----- 6213 6214 R/W
*
MB_REG_DO_SENSOR ----- ----- ----- ----- 6661 6662 R/W
Holding Registers:
MB_REG_HR_DI_SENSOR_LATCH ----- ----- ----- ----- 6149 6150 R/W MB_REG_HR_DO_SENSOR_PULSE_ISW ----- ----- ----- ----- 6213 6214 R/W MB_REG_HR_DO_SENSOR_PULSE_ASW ----- ----- ----- ----- 6277 6278 R/W MB_REG_HR_DO_SENSOR_PULSE_COUNT ----- ----- ----- ----- 6341 6342 R/W MB_REG_HR_AI_CLEAR_ALARM_LATCH 2049 2050 2051 2052 ----- ----- W MB_REG_HR_AI_CLEAR_MAX 2113 2114 2115 2116 ----- ----- W MB_REG_HR_AI_CLEAR_MIX 2177 2178 2179 2180 ----- ----- W
Input Registers:
MB_REG_IR_CURR_ENG MB_REG_IR_MIN_ENG MB_REG_IR_MAX_ENG MB_REG_IR_CURR_RAW
78 IOLAN Device Server User’s Guide, Version 1.8
2080 2112 2144 2176 ----- ----­2082 2114 2146 2178 ----- ----­2084 2116 2148 2180 ----- ----­2086 2118 2150 2182 ----- -----
R R R R
Page 79
I/O Model Features
Data Model A1 A2 A3 A4 D1/R1 D2 /R2 R/W
MB_REG_IR_MIN_RAW MB_REG_IR_MAX_RAW MB_REG_IR_ALARM_LEVEL
2087 2119 2151 2183 ----- ----­2088 2120 2152 2184 ----- ----­2089 2121 2153 2185 ----- -----
*For DI alarm state read will get state, write will clear alarm.
D4/D2R2 Registers
The following coils and registers are supported by the Device Server D4 and D2R2 I/O models:
Data Model D1 D2 D3/R1 D4/R2 R/W
Coils:
MB_REG_DI_SENSOR 6145 6146 6147 6148 R MB_REG_DI_SENSOR_ALARM_STATE 6209 6210 6211 6212 R/W
*
MB_REG_DO_SENSOR 6657 6658 6659 6660 R/W
Holding Registers:
MB_REG_HR_DI_SENSOR_LA TCH 6145 6146 6147 6148 R/W MB_REG_HR_DO_SENSOR_PULSE_ISW 6209 6210 6211 6212 R/W MB_REG_HR_DO_SENSOR_PULSE_ASW 6273 6274 6275 6276 R/W MB_REG_HR_DO_SENSOR_PULSE_COUNT 6337 6338 6339 6340 R/W
R R R
*For DI alarm state read will get state, write will clear alarm.
Serial Signals
The following coils and registers are supported by the Device Server I/O models:
Data Model Pin R/W
Coils:
MB_REG_DI_DSR 4225 R MB_REG_DI_DSR_ALARM_STATE 4289 R/W MB_REG_DI_DCD 4353 R MB_REG_DI_DCD_ALARM_STATE 4417 R/W MB_REG_DI_CTS 4481 R MB_REG_DI_CTS_ALARM_STATE 4545 R/W MB_REG_DO_DTR 4673 R/W MB_REG_DO_RTS 4737 R/W
Holding Registers:
MB_REG_HR_DI_DSR_LATCH 4097 R/W MB_REG_HR_DI_DCD_LATCH 4609 R/W MB_REG_HR_DI_CTS_LATCH 5121 R/W
79
Page 80
I/O Model Features
TruePort
You can see a sample API I/O over TruePort program called ioapiotp.c on the CD-ROM.
TruePort/Modbus Combination
If you have a Modbus serial application running on a PC that is connected to a network, you can use TruePort as a virtual serial connection to communicate with the Device Server over the network to access I/O data. You also have the option of enabling SSL as a security option to encrypt the data that is communicated between the Device Server and the host machine (SSL/TLS must be configured in the Server settings and on the TruePort host).
UID: 15
Network
perle
Power
PC running a
Modbus Serial
Application/
TruePort
Device Server
I/O Digital Output
The host running TruePort must be in Modbus/ASCII or Modbus/RTU mode.
API Over TruePort Only
If you have a custom application that talks to a serial port, you can use TruePort as a virtual serial port to communicate with the Device Server over the network to access I/O data using the Perle API. You also have the option of enabling SSL as a security option to encrypt the data that is communicated between the Device Server and the host machine (SSL/TLS must be configured in the Server settings and on the TruePort host). See information on the API.)
API I/O Access Over TruePort on page 200 for more
Network
PC running
Custom
Application (API)/
TruePort
The host running TruePort must be in I/O API mode.
80 IOLAN Device Server User’s Guide, Version 1.8
perle
Device Server
Power
I/O Digital Output
Page 81
Digital Channels
You can configure the Digital I/O channels for either input or output, making the Device Server flexible in your production environment. Jumpers must be set to correspond with the software settin g of either Input or Output; see
Digital Input
The Digital input channels allow you to configure the following options:
z You can choose to remember the last state change, or latch, that occurred. Your options are to
latch (remember) when the state changes from inactive to active or active to inactive.
z You can choose to invert the signal, which is usef ul if your sensor is wired in such a way that
closed is actually inactive, whereas closed is normally considered active.
z You can also configure an alarm trigger and clear mode based on whether the Digital input is
active or inactive, sending an email, syslog message, and/or SNMP trap when the alarm is triggered or cleared.
In an industrial freezer warehouse example, a D4 is used to monitor the open door sensor, so that every time a freezer door is opened, an alarm is triggered and a syslog message is sent to syslog, where the monitoring application notes the time.
I/O Model Features
Digital I/O Module on page 33 for jumper settings.
Monitoring
Application
Network
D4
perle
Device Server
Input
Input
Digital I/O
Industrial Freezers
81
Page 82
I/O Model Features
Digital Output
The Digital output channels support three types of Digital output: sink (voltage), source (ground), and sink and source (apply voltage or ground). For the output type, you can configure the following options:
z You can choose to manually activate/deactivate the Digital output. z You can choose to manually activate/deactivate the Digital output and then specify that the
Digital output will either pulse (you get to specify the active and inactive pulse times) continuously or for a specified number of pulse counts.
z You can choose to manually activate/deactivate the Digital output and then specify a delay before
the output goes from inactive to active or active to inactive.
z You can also specify a failsafe action that can either activate or inactivate the Digital output
when the failsafe timer is triggered (see
When one of the industrial freezer doors are left open for more than five minutes, the Monitoring Application (using the Perle API) starts the Digital output sink, causing the strobe light on top of the offending freezer to activate.
D4
Network
Monitoring
Device Server
Application
Failsafe Timer on page 74 for more information).
Output
Input
perle
Digital I/O
Output
Input
Industrial Freezers
82 IOLAN Device Server User’s Guide, Version 1.8
Page 83
Temperature Channels
Temperature input channels monitor RTD or thermocouple temperature sensors. You can also configure severity alarms that can send an email, a syslog message, and/or an SNMP when an alarm is triggered or cleared; See
RTD ranges are:
z Pt100 a=385 -50 to 150C z Pt100 a=392 -50 to 150C z Pt1000 a=385 -40 to 160C z Pt100 a=385 0 to 100C z Pt100 a=392 0 to 100C z NiFe604 a=518 -80 to 100C z Pt100 a=385 0 to 200C z Pt100 a=392 0 to 200C z NiFe604 a=518 0 to 100C z Pt100 a=385 0 to 400C z Pt100 a=392 0 to 400C z Pt100 a=385 -200 to 200C z Pt100 a=392 -200 to 200C
I/O Model Features
Alarms on page 75 for more information about the alarms.
Note:
IEC RTD 100 ohms.=0.00385 JIS RTD 100 ohms.=0.00392
Thermocouple ranges are:
z B 500 to 1800C z K 0 to 1370C z T -100 to 400C z E 0 to 1000C z R 500 to 1750C z J 0 to 760C z S 500 to 1750C
The the following example, a Temperature I/O Device Server is used to monitor industrial freezer as a temperature sensor, with an alarm set to send a syslog message if the temperature rises above 31
o
C.
T4
perle
Temperature I/O
Industrial
Monitoring
Application
Network
Device Server
Freezers
83
Page 84
I/O Model Features
Analog Channels
Analog input channels monitor current or voltage within a specified range and can then trigger an alarm for up to five severity levels that will send an email, SNMP trap, and/or syslog message wh en the alarm is triggered and/or cleared. See
In our industrial freezer warehouse, a Device Server A4R2 is used to monitor humidity transducers, which are in place to help prevent freezer burn. If the humidity reaches a certain percentage (monitored by an Analog channel) a syslog message is sent to the Monitoring Application. The Monitoring Application then sends a command to the Device Server via the Perle API that causes the Relay channel to activate an internal freezer dehumidifier. The relay is turned off when the Analog channel sends a clear syslog message to the Monitoring Application and the Relay channel is deactivated.
Alarms on page 75 for more information on alarms.
Monitoring Application
Network
A4D2
perle
Device Server
Analog I/O
Relay
Analog
Relay
Analog
Industrial Freezers
84 IOLAN Device Server User’s Guide, Version 1.8
Page 85
Relay Channels
Relay output channels work as a physical on/off switch, and are used to drive higher voltage devices with a lower controlling voltage.
You can configure the following Relay outp ut channel options:
z You can choose to manually activate/deactivate the Relay output. z You can choose to manually activate/deactivate the Relay output and then specify that the Relay
output will either pulse (you get to specify the active and inactive pulse times) continuously or for a specified number of pulse counts.
z You can choose to manually activate/deactivate the Relay output and then specify a delay before
the output goes from inactive to active or active to inactive.
z You can also specify a failsafe action that can either active or inactivate the Relay output when
the failsafe timer is triggered (see
In our industrial freezer warehouse, a Device Server A4R2 is used to monitor humidity transducers, which are used to help prevent freezer burn. If the humidity reaches a certain percentage (monitored by an Analog channel) a syslog message is sent to the Monitoring Application, causing the Relay channel to activate an internal freezer dehumidifier. The Relay channel is deactivated when the Analog channel sends a clear syslog message to the Monitoring Application and the Relay channel is deactivated.
I/O Model Features
Failsafe Timer o n page 74 for more information).
Serial Signals
When the Line Service is set to Signal I/O, you will be able to configure the serial signal I/O pins. This allows you to enable/disabled each of the serial pins in the serial port that can be used as Digital inputs and outputs. The serial signal Digital I/O channels can be set for Digital output (RTS and DTR) and/or Digital input (DSR, DCD, and CTS).
Monitoring
Application
Network
A4D2
perle
Device Server
Relay I/O
Relay
Analog
Relay
Analog
Industrial Freezers
85
Page 86
I/O Model Features
Calibrating Analog Input
To calibrate an Analog input channel, read the section that applies to the type of input you are calibrating. Note that calibration will be done for the active channel configuration; for example, if Channel A1 is set to voltage, you cannot calibrate it for current. The voltage range configured for this channel will also dictate what is being calibrated. For example, if this channel is configured for a range of +/-10V, calibrating this channel will calibrate all channels which are configured for +/-10V. During the calibration process, you will be asked to apply the minimum and maximum configured range value to the channel; for example, to calibrate for voltage +/- 10V, you will be prompted to first apply -10V and then +10V to the channel.
Also, you cannot actively calibrate disabled channels (although, for Voltage, if you enable the channel and then set it for a range that has already been calibrated for another channel, it will also be calibrated).
Calibrating Voltage
When calibrating the Device Server Analog input for voltage, you will need a calibration meter that is better than .1% volts precision. When you calibrate one channel, all voltage channels are automatically calibrated for that range; if another channel is set for a different range, you will need to calibrate that channel separately, but all channels that use that range are also automatically calibrated.
Calibrating Current
When calibrating the Device Server Analog input for current, you will need a calibration meter that is better than .1% current precision. Each channel needs to be calibrated individually.
Calibrating Temperature Input
To calibrate an Analog (Temperature) input channel, read the section that applies to the type of input you are calibrating. Note that calibration will be done for the active channel configuration; for example, if Channel A1 is set to thermocouple, you cannot calibrate it for RTD. During the calibration process, you will be asked to apply the minimum and maximum range value to the channel in either mV or Ohms; for example, to calibrate for thermocouple J 0 to 760C, you will be prompted to first apply -80mV and then +80mV to the channel.
Also, you cannot actively calibrate disabled channels (although if you enable the channel and then set it for the type of thermocouple or RTD that has already been calibrated on another channel, it will also be calibrated).
Calibrating Thermocouple
When calibrating the Device Server Analog input for thermocouple, you will need a calibration meter that is better than .15% accuracy. When you calibrate one channel, all thermocouple channels are automatically calibrated for that range; if another channel is set for a different range, you will need to calibrate that channel separately, but all channels that use that range are automatically calibrated.
Calibrating RTD
When calibrating the Device Server Analog input for RTD, you will need a resistor that is better than .05% Ohms accuracy. When you calibrate one channel, all RTD channels are automatically calibrated for that range; if another channel is set for a different range, you will need to calibrate that channel separately, but all channels that use that range are automatically calibrated.
86 IOLAN Device Server User’s Guide, Version 1.8
Page 87
Using the
5
DeviceManager Chapter 5
Introduction
This chapter provides information about configuring/managing the Device Server using the DeviceManager. It is assumed that the DeviceManager has already been installed; if you still need to install the DeviceManager, see
Using DeviceManager on page 39.
Starting a New Session
When you start the DeviceManager application, the New Session window is displayed.
You can choose:
z Manage Device Server—Connect to a Device Server to manage/view it. z New Configuration—Create a new Device Server configuration. z Open Configuration—Open an existing configuration file.
IOLAN Device Server User’s Guide, Version 1.8 87
Page 88
Starting a New Session
Managing a Device Server
You can connect to Device Servers or assign a temporary IP address to a new Device Server. Whenever you connect to a Device Server through the DeviceManager, you connect as the Admin user and must supply the password for the Admin user.
If you want to connect to a Device Server to manage/configure it, or assign a temporary IP address to a Device Server, select to create a new or edit an existing configuration file, select
Configuration or Open Configuration radio button.
File, New Session and the Manage Device Server radio button. If you want
File, New Session and the New
Populating the Device Server List
The first time you start the DeviceManager, the Manage Device Server window will be empty . To add Device Servers to the
z Click the Search Local Network button. This searches the local network segment and
automatically displays any Device Servers it finds. Any Device Servers found by this method will be displayed in Servers that were displayed as
Network
z Click the Static Server List button to add Device Servers to the Device Server List permanently.
button again.
This also allows you to add Device Servers that are not found on the local network segment with the
Search Local Network button. To connect to a Device Server that is not in the Device Server
List and resides outside the local network, see
89.
For more information about managing a Device Server, see Managing a Device Server on page 91.
Device Server List, you can do either of the following:
Type column as Dynamic. Once you close the DeviceManager, any Device
Dynamic will not be there until you click the Search Local
Adding/Deleting Static Device Servers on page
88 IOLAN Device Server User’s Guide, Version 1.8
Page 89
Starting a New Session
Assigning a Temporary IP Address to a New Device Server
If your network does not use DHCP/BOOTP, you can temporarily assign an IP address to a Device Server that is connected to your local network segment, for the purpose of connecting to it and downloading a configuration file (containing a permanent IP address). To temporaril y assign an IP address to a Device Server, do the following:
1. Click the Search Local Network button. The Device Server will be displayed in the IP Address
column as
2. Select the new Device Server and click the Assign IP button. The following window is
displayed:
3. Type a valid temporary IP address into the address field and click the Assign IP button.
4. Double-click the Device Server in the Device Server List. If this is the first time you are
accessing the Device Server, type in the factory default Admin password,
OK. The DeviceManager will display a window indicating that it is trying to authenticate and
connect you on the Device Server.
5. If the authentication and connection are successful, the Server Info window is displayed. You are
now ready to configure the Device Server. If authentication was unsuccessful, try to connect to the Device Server again; you probably mistyped the password for the Admin user.
For more information about managing a Device Server, see Managing a Device Server on page 91.
Not Configured.
superuser, and click
Adding/Deleting Static Device Servers
To permanently add or delete a Device Server to/from the Device Server List, select the Static
Server List
To permanently add a Device Server to the Device Server List, type in the IP address of the Device Server and click the Server
button. The following window is displayed:
Add Server button. To permanently delete a Device Server from the Device
List, select the Device Server’s IP address and click the Delete Server button.
89
Page 90
Connecting to a Device Server
Creating a New Device Server Configuration
If you selected the New Configuration radio button, the New Configuration window is displayed.
Select the Device Server model for which you want to create a new configuration file.
Opening an Existing Configuration File
If you selected the Open Configuration radio button, a browse window is opened so you can select the configuration file you want to edit. Device Server configuration files can be in the Device Server-native binary format ( Either configuration version can be imported into the DeviceManager.
.dme) or as a text file (.txt), which can be edited with a text editor.
Connecting to a Device Server
To connect to a Device Server, double-click on the Device Server in the Device Server List. You will be prompted for the Admin Password.
If the authentication and connection are successful, the Device Server’s Server Info window is displayed.
If you cannot connect to a Device Server, you can highlight the Device Server and click the Ping button to verify that the DeviceManager can communicate with the Device Server’s IP Address. If the ping times out, then you might need to set up a Gateway in your Device Server or verify that your network is communicating correctly .
90 IOLAN Device Server User’s Guide, Version 1.8
Page 91
Managing a Device Server
Once you are connected to a Device Server, you can edit its configuration, download a new configuration, save the configuration to file, perform administrative tasks, and view statistics abo ut the Device Server and its network environment.
DeviceManager Work Flow
When you connect to a Device Server, the Device Server’s configuration is automatically uploaded to the Device Server. Before you make any changes to the configuration, you probably want to save the configuration locally, to make a backup file of the configuration. Use the navigation panel to select the feature that you want to edit. After you make all your changes to a configuration window, you must click the configuration edits, select effect at this point, select
Creating/Editing Configuration Files
You can create and edit Device Server configuration files. When you open a new configuration file, the configuration file contains the Device Server’s factory default settings.
Apply button to submit those changes. When you have completed all of your
Tools, Download Configuration to Unit. If you want your changes to take
Tools, Reboot Server.
Managing a Device Server
Working With the Device Server Configuration
When you connect to a Device Server, the configuration that is saved to FLASH is automatically uploaded to the DeviceManager. It is suggested that you save the working configuration to a file as a backup precaution by selecting the configuration and download it back to the Device Server by selecting
Configuration to Unit
Device Server by selecting Device Server, you can reconnect to the Device Server after it has been rebooted.
. The downloaded configuration does not take effect until you reboot the
Tools, Save Configuration to Fil e . You can then make any edits to
Tools, Download
Tools, Reboot Server. If you want to continue managing/configuring the
Working With a Local Configuration File
You can also connect to a Device Server and open a saved configuration file by selecting Tools, Get
Configuration
the Device Server by selecting configuration does not take effect until you reboot the Device Server by selecting
Server
. If you want to continue managing/configuring the Device Server, you can reconnect to the
Device Server after it has been rebooted.
, Import from File. This configuration can then be edited or just downloaded right to
Tools, Download Configuration to Unit. The downloaded
Tools, Reboot
91
Page 92
Configuring the Server
Configuring the Server
The following sections describe how to configure the Device Server’s server parameters.
Configuring the Main Server Window
When you select Server Configuration, Server from the navigation panel, the following Server window is displayed.
Enter values in the Device Server parameters that you need for your production environment.
Server
Server Name Domain Name
Internet Address
Mask
You must supply a name for the Device Server. Unique name for your domain, your location in the global network. Like
Hostname, it is a symbolic, rather than a numerical, identifier. See IPv6 Network on page 41 for information on how to determine your IPv6
address. The Device Server’s unique IPv4 network IP address. If you are using the
Device Server in an IPv6 network, this field can be left blank. The network subnet mask. For example, 255.255.0.0.
Services
Services are either daemon or client processes that run on the Device Server. You can disable any of the services for security reasons. If you disable the DeviceManagerD service, you will not be able to use DeviceManager to connect to a Device Server.
TelnetD SPCD DeviceManagerD
Telnet daemon process in the Device Server on port 23. SPC (Trueport) daemon process in the Device Server on port 688. DeviceManager daemon process in the Device Server. If you disable this
service, you will not be able to connect to the Device Server with the DeviceManager application. DeviceManagerD listens on port 33812 and sends on port 33813.
HTTPD SNMPD ModbusD
92 IOLAN Device Server User’s Guide, Version 1.8
HTTP daemon process in the Device Server on port 80. SNMP daemon process in the Device Server on port 161. Modbus daemon process in the Device Server on port 502.
Page 93
Configuring the Server
Syslog DHCP/BOOTP
Syslog client process in the Device Server. DHCP/BOOTP client process in the Device Server. By default, this is
disabled/off. If this is enabled, the server IP address parameter is disabled.
Configuring Advanced Server Settings
In the Server window, the following window is displayed when you click the Advanced button.
Configure the appropriate parameters:
OEM Login
Password Limit
When set, and a custom language file is in use, the login prompt will use the string defined in the language file as the login prompt instead of the default prompt,
login:.
The number of attempts a user is allowed to enter a password for a port. If this limit is exceeded, the port is disabled for 5 minutes. A user with Admin level rights can restart the port, bypassing the timeout, by issuing a kill on the disabled port. The default value is
3.
Bypass Password
Single Telnet
Flush On Close
Banner
When set, authorised users who do not have a password set, with the exception of the Admin user, WILL NOT be prompted for a password at login with
Authentication
.
Local
Sets all reverse connections (raw and telnet) to a one connection at a time mode. Server-side applications will get a (socket) connection refused until:
z All data from previous connections on that serial port has drained z There are no other connections z Up to a 1 second interconnection poll timer has expired
This also enables a per-connection keepalive TCP keepalive feature. After approximately 3 minutes of network connection idle time, the connection will send a gratuitous ACK to the network peer, thus either ensuring the connection stays active OR causing a dropped connection condition to be recognised by the reverse service (all connections).
Applications using Single Telnet need to be aware that there can be some considerable delay between a network disconnection and the port being available for the next connection attempt; this is to allow any data sent on prior connections to be transmitted out of the serial port. Application network retry logic needs to accommodate this feature. The default value is
Off.
When enabled, deletes any pending data when a port is closed; as opposed to maintaining the port to send pending data. The default value is
Off.
This parameter concerns the banner information (product name/software version). This banner information is presented to a user with a login prompt. For security reasons, you can turn off the display of this information. The default is
Off.
93
Page 94
Configuring the Server
Prompt With Name
Displays the Server Name field value instead of default product name. When enabled, the prompt, WebManager login screen, and the heading of the Menu. The default value is
Configuring TruePort Baud
The TruePort Baud configuration window allows you to map the baud rate coming out of the serial host to another baud rate that will run between the Device Server and the serial device. See
Appendix B, Utilities on page 199 for more information about TruePort.
Configuring the Hardware
You need to configure the ethernet interface that you are using to connect the Device Server to the LAN.
Select the appropriate option:
Ethernet Speed and Duplex
Define the ethernet connection speed at one of the following:
z auto—automatically detects the ethernet interface speed and duplex z 10 Mbps Half Duplex
z 10 Mbps Full Duplex z 100 Mbps Half Duplex z 100 Mbps Full Duplex
Server Name is displayed in the Device Server login prompt, CLI
Off.
Custom App
You can create a custom application that can run on the Device Server using the Perle SDK.
Configure the following parameter:
Program Command Line
The name of the SDK program executable that has been already been downloaded to the Device Server, plus any parameters you want to pass to the program. Maximum of 80 characters. Use the
shell CLI command as
described in the SDK Programmer’s Guide to manage the files that you have downloaded to the Device Server. For example, using sample outraw program, you would type:
outraw -s 0 192.168.2.1:10001 Acct:10001
if you were starting the application on the Server (notice the
-s 0 parameter
specifies Line 1).
94 IOLAN Device Server User’s Guide, Version 1.8
Page 95
Configuring Lines
When you configure the Device Server Line, you are specifying how the port will be used and accessed. You can always make changes to
Tools, Kill Line to test your changes. However, you still must select Tools, Download Configuration to Unit
Configuring Lines
Line parameters, click the Apply button, and then select
and Tools, Reboot Server to make your changes permanent and take effect.
Configure the appropriate parameters:
Line Name Service
Provide a name for the line so it can be easily identified. Defines the Line Service, which determines how the line will be used.
See Service Settings on page 99 for more information about configuring each
Line Service.
DS Port Terminal Type
Serial Interface
The Device Server port number. Specifies the type of terminal connected to the line:
z Dumb z WYSE60 z VT100 z ANSI z TVI925 z IBM3151TE z VT320 (specifically supporting VT320-7) z HP700 (specifically supporting HP700/44) z Term1, Term2, Term3 (user defined terminals)
Specifies the type of line that is being used with the Device Server. Select either EIA-232, EIA-422, or EIA-485 (TS2 supports only EIA-232).
Speed
Specifies the baud rate of the line; keep in mind that speed is affected by the length of the cable. You can also specify a custom baud rate; valid values are 50-230400.
Bits Parity
Specifies the number of bits in a byte. The default is 8. Specifies if you are using Even, Odd, or No parity on the line. If you want to
force a parity type, you can specify Mark for 1or Space for 0.
95
Page 96
Configuring Lines
Stop Bits Flow Control
Single Character Interrupt
Duplex
TX Driver Control
Echo Suppression
Monitor DSR
Specifies the number of stop bits that follow a byte. Defines whether the data flow is handled by the software (Soft), hardware
(
Hard), Both, or None.
When enabled, causes the Device Server to process every character as it comes in, as opposed to buffering the characters before processing; this provides better latency at the expense of efficiency.
Specify whether the line is Full Duplex (communication both ways at the same time) or
Half Duplex (communication in one direction at a time).
Used with a EIA-485 serial interface, if your application supports RTS (Request T o Send), select this option. Otherwise, select
Auto. Default is Auto.
This parameter applies only to EIA-485 Half Duplex mode. All characters will be echoed to the user and transmitted across the serial ports. Some EIA-485 applications require local echo to be enabled in order to monitor the loopback data to determine that line contention has occurred. If your application cannot handle loopback data, echo suppression should be suppression
Off.
On. The default is echo
Specifies whether the RS-232 signal DSR (data set ready) should be monitored. This is used with modems or any device that sends a DSR signal. When it is monitored and the Device Server detects a DSR signal, the line service is started. Default is
Off. If both Monitor DCD and Monitor DSR are enabled,
both signals must be detected before the line service is started.
Monitor DCD
Specifies whether the RS-232 signal DCD (Data Carrier Detect) should be monitored. This is used with modems or any other device that sends a DCD signal. When it is monitored and the Device Server detects a DCD signal, the line service is started. Default is
Off. If both Monitor DCD and Monitor DSR
are enabled, both signals must be detected before the line service is started.
96 IOLAN Device Server User’s Guide, Version 1.8
Page 97
Advanced Line Settings
You can configure these advanced settings for a line.
Configure the appropriate parameters:
Configuring Lines
Pages
User
Reverse Session Security
Dial
Dial Timeout
Dial Retry
Modem Phone Initial Mode
For DSLogin line service, this is the number of video pages the terminal supports. Valid values are 1-7. The default is
5 pages.
For DSLogin line service, makes this a line that is dedicated to the specified user. Only this user will be able to log in on this line and they won’t need to enter their login name - just their password.
Enables/disables login/password authentication, locally or externally, on reverse Telnet connections. The default is
Off.
Determines how a modem will work on the line. If your user is remote and will be dialing in via modem or ISDN TA, set this parameter to Server is being used as a router, set this parameter to either
In; if the Device In, Out, or Both,
depending on which end of the link your Device Server is situated and how you want to initiate the communication.
The number of seconds the Device Server will wait to establish a connection to a remote modem. The default value is 45 seconds.
The number of times the Device Server will attempt to establish a connection with a remote modem. The default value is
2.
The name of the predefined modem that is used on this line. The phone number to use when Dial is set to Out. Specifies the initial interface a user navigates when logging into the line; either
the
Menu or a prompt for the CLI. The default is CLI.
97
Page 98
Configuring Lines
Break
Flowin
Flowout
Reset Keep Alive
Specifies how a break is interpreted:
z None—The Device Server ignores the break key completely and it is not
passed through to the host. This is the default setting.
z Local—The Device Server deals with the break locally. If the user is in a
session, the break key has the same effect as a hot key.
z Remote—When the break key is pressed, the Device Server translates this
into a telnet break signal which it sends to the host machine.
z Brkintr—On some systems such as SunOS, XENIX, and AIX, a break
received from the peripheral is not passed to the client properly. If the client wishes to make the break act like an interrupt key (for example, when the stty options
-ignbrk and brkintr are set).
Determines if input flow control is to be used. Default is On. This is active only when
Line Flow Control is set to Soft, Hard, or Both.
Determines if output flow control is to be used. Default is On. This is active only when
Line Flow Control is set to Soft, Hard, or Both.
Resets the terminal type connected to the line when a user logs out. Enables a per-connection TCP keepalive feature; after approximately 3 minutes
of network connection idle time, the connection will send a gratuitous ACK to the network peer, either ensuring the connection stays active OR causing a dropped connection condition to be recognised by the reverse raw service.
Applications using this feature need to be aware that there might be some considerable delay between a network disconnection and the port being available for the next connection attempt; this is to allow any data sent on prior connections to be transmitted out of the serial port buffer. Application network retry logic needs to accommodate this feature.
MOTD Lock
Idle Timer
Session Timer
Enables/disables the message of the day on the line. When enabled, the user can lock his terminal with a password using the Hotkey
Prefix (default Ctrl-a) ^a l (lowercase L). The Device Server prompts the user
for a password and a confirmation. Enter a time period, in seconds, for which the Idle Timer will run. Use this
timer to close a connection because of inactivity. When the
Idle Timer expires,
the Device Server will end the connection. The maximum value is 4294967 seconds (about 49 days). The default value of
0 (zero) means the Idle Timer
will not expire, so the connection is permanently open. Enter a time, in seconds, for which the Session Timer will run. Use this timer
to forcibly close the session (connection). When the
Session Timer expires,
the Device Server will end the connection. The default value is 0 seconds so the port will never timeout. The maximum value is 4294967 seconds (about 49 days).
98 IOLAN Device Server User’s Guide, Version 1.8
Page 99
Configuring Lines
Hotkey Prefix
Service Settings
Line Services determine how line is defined. As a rule, when you are accessing a serial device
through the Device Server, coming from the ethernet side, you want to set the
Reverse Raw or Reverse Telnet.
DSLogin
When the Line Service is set to DSLogin, any user accessing the Device Server will have to log into the Device Server. What happens after the user successfully logs into the Device Server is based on how the user is configured. For example, if after a successful login, the user is set to telnet to a specific host, you will want to set the Telnet parameters that will be used by the user for the telnet session (any parameters that are also available in the user’s configuration are overridden by the user’s definitions).
The prefix that a user types to lock a line or redraw the Menu. The default value is
hex 01, which corresponds to Ctrl-a (^a) (hex value 02 would be
Ctrl-b (^b), etc.):
z ^a l—(Lowercase L) Locks the line until the user unlocks it. The user is
prompted for a password (any password, excluding spaces) and locks the line. Next, the user must retype the password to unlock the line.
z ^r—When you switch from a session back to the Menu, the screen may not
be redrawn correctly. If this happens, use this command to redraw it properly.
You can use the parameter is
Hotkey Prefix key to lock a line only when the Line Lock
On.
Line Service to
See Telnet Settings on page 100 for information on the Telnet Settings parameters.
[
99
Page 100
Configuring Lines
Raw Settings
When the Line Service is set to Direct or Silent Raw, data is sent through the connection in its original format. This raw TCP/IP connection is initiated from the Device Server to the configured host.
Configure the following parameters:
Host Name Port
The name of the target host. The port number the target host is listening on for incoming connections.
Telnet Settings
When the Line Service is set to Direct or Silent Telnet, data is sent through the connection in a telnet session. This telnet session is initiated from the Device Server to the configured host.
Configure the following parameters:
Terminal Type Host Name
Type of terminal attached to this line; for example, ANSI or WYSE60. The name of the target host.
Port Local Echo
The port number the target host is listening on for incoming connections. Toggles between local echo of entered characters and suppressing local echo.
Local echo is used for normal processing, while suppressing the echo is convenient for entering text that should not be displayed on the screen, such as passwords. This parameter can only be used when
Off.
Line Mode
When On, keyboard input is not sent to the remote host until Enter is pressed, otherwise input is sent every time a key is pressed. Default is
Map CR to CRLF
Maps carriage returns (CR) to carriage return line feed (CRLF). The default value is
100 IOLAN Device Server User’s Guide, Version 1.8
Line Mode is On. Default is
Off.
Off.
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use