R91001 user manual in PDF format.

Product Manual for Sealevel Model 7404e in PDF Format

COM Express modules integrate the core CPU and memory functionality in an embedded computer board. The system buses, video, Ethernet, USB and other I/O capabilities are mapped to one or two high-density connectors on the bottom of the module. The COM Express module is paired with a carrier board that brings out the connectors required for the application.

The PICMG COM Express module specification revision 2.0 defines seven different Types, depending on required features: Type 1 – Type 6 and Type 10. Type 2 is currently the most common pin out.

• Type 1: single 220 pin connector, 6 PCI Express lanes, 4 SATA, Ethernet
• Type 2: dual 220 pin connectors, 22 PCI Express lanes, PEG, PCI, IDE, 4 SATA, Ethernet
• Type 3: dual 220 pin connectors, 22 PCI Express lanes, PEG, PCI, 4 SATA, Ethernet
• Type 4: dual 220 pin connectors, 32 PCI Express lanes, PEG, IDE, 4 SATA, 3 Ethernet
• Type 5: dual 220 pin connectors, 32 PCI Express lanes, PEG, 4 SATA, 3 Ethernet
• Type 6: dual 220 pin connectors, 24 PCI Express lanes, PEG, DDI, 4 SATA, Ethernet, 2 Serial, USB 3.0
• Type 10: single 220 pin connector, 4 PCI Express lanes, 2 SATA, Ethernet, LVDS, DDI, 2 Serial

Sealevel has the experience to add additional serial, Ethernet, USB and other functionality via PCI Express lanes. Sealevel can help you select the appropriate COM Express module for your requirements and design a COM Express carrier board to the exact specifications for your application.

Yes, COM express modules feature soldered processors, soldered memory and other surface mount components for shock and vibration resistance. COM Express modules securely mount to carrier boards at all four corners. High-density connectors provide a single mounting point between COM Express modules and carrier boards.

The system can be designed to be completely cable-less – requiring no cables between the COM Express module, carrier board and other system interfaces. This makes a COM Express system highly suitable to rugged and high vibration applications.

Additionally, conformal and vibration coating, silicon potting and resin encapsulation can be used to maximize shock and vibration resistance.

Sealevel can help you select the appropriate COM Express module for your requirements while designing a COM Express carrier board ruggedized to the exact shock and vibration specifications for your application.

While the PICMG COM Express module specification revision 2.0 describes the physical size of COM Express modules, there is no standard specification for carrier board sizes. 

Sealevel can develop a COM Express carrier board designed to perfectly fit the application. A carrier board can be virtually any size, shape and even span multiple boards, if necessary. The carrier board can be tailored to the exact electrical and mechanical requirements of your application. Call for details.

The PICMG COM Express module specification revision 2.0 describes three sizes of COM Express modules: Basic, Compact and Extended.

Basic modules are the most common size and measure 125mm x 95mm. To meet the demands for smaller form factors, Compact modules are small, measuring only 95mm x 95mm, similar in size to PC/104 modules. Extended modules typically offer advanced features and measure 155mm x 110mm. 

Driven by the demand for even smaller sizes, the Ultra form factor measuring only 55mm x84mm is under consideration. Depending on the required features, custom sizes are also available from COM Express vendors.

Additionally, there are six different Types that define various pin outs. See the COM Express Types FAQ for additional information.

Using these steps, a user can create a 'silent install' for any Sealevel software driver for Microsoft Windows operating systems. All steps are run in a command prompt (Start -> Run -> CMD [Enter]):

1) Create a directory on the c: drive called ‘silent’ using this command:

MD c:\silent

2) Copy the Sealevel software driver for your adapter to the directory ‘c:\silent\’. 

3) In this example, we are using the SeaCOM driver from the software CD. Run the installation from the command prompt using the ‘/r’ parameter:

CD \silent
SeaCOM_Installer.exe /r

4) The installation proceeds with the user supplying the appropriate responses to the dialog windows. Once the installation completes, the file c:\windows\setup.iss is generated, which contains the user-supplied answers for a silent installation.

5) Copy the file c:\windows\setup.iss to c:\silent\.

COPY c:\windows\setup.iss c:\silent\

6) Run the installation again to uninstall the SeaCOM software that you installed in step 3. This is necessary to test the silent installation on your system.

SeaCOM_Installer.exe

7) To test the silent install or perform a silent install on the target system, make sure the Sealevel software executable (exe) and the setup.iss files are in the same directory. Run the installation from the command prompt using the following parameters:

SeaCOM_Installer.exe /s /f1"c:\silent\setup.iss"

Note: The ‘/s’ parameter tells the installation to run in silent mode and the ‘/f1’ parameter indicates the path to the setup.iss file. Relative paths are unreliable so the full path should be used. The silent installation will not work if the ‘/f1’ parameter is omitted.

8) The silent installation will proceed without any interaction from the user.

Note: Sealevel does not distribute a silent installation package for two reasons: (1) the license agreement must be accepted by the customer; and (2) the questions answered during the recorded installation are based on the warning levels set on the user's systems.

Most Sealevel serial adapters use the serial drivers built into the Linux kernel. For USB and UART-based serial adapters, the Linux drivers may need additional information in order to provide access to the Sealevel serial device. For SeaLINK Ethernet serial servers, Sealevel offers a dedicated Linux driver.

• To configure UART-based serial adapters, please read How to configure UART-based serial adapters in Linux.
• To configure USB serial adapters, please read How to configure USB serial adapters in Linux.
• For Ethernet serial servers, please download the Sealevel SeaLINK software driver for Linux.

Linux supports the direct use of 16CXXX UART-based devices with drivers included in the kernel sources. Some Sealevel asynchronous serial devices do not currently have their vendor/product IDs included in this driver. It is necessary to either manually identify the UARTs to the driver or modify the driver by adding the vendor/product IDs.

Option 1: Using the Setserial Command Line Utility.

NOTES

• This procedure is the ONLY method of accessing a PC/104 or ISA device by using standard device drivers.
• Since the <IO_ADDRESS> and <IRQ_NUMBER> are static in the case of PC/104 and ISA, a distribution's start-up scripts can easily be modified to enable driver attachment. This assumes that no new plug-and-play serial devices will be added later on as they will be overwritten until the start-up scripts are modified.
• A recent change in the way the serial driver attaches to <MINOR> numbers may prevent more than 4 serial ports to be attached to the driver at any time. This issue can be remedied by changing the CONFIG_SERIAL_8250_NR_UARTS configuration variable and recompiling the kernel module, which means if this is a PCI device, it may be prudent to enable Plug-and-Play capability.

The setserial program is an open source utility to aide in the configuration of the 8250 async serial port driver. It is included with most Linux distributions or available through that distribution’s package management system (check distribution documentation). Alternatively, the source code can be found at the setserial project website.

Once the setserial utility is available, it is necessary to determine the IO addresses and IRQ line for each of the devices UARTs. If this is an ISA or PC/104 device, these options are configured manually with jumpers on the board. If this is a PCI, PCI Express, or PC/104+ device, these are assigned through a combination of BIOS and OS. To determine what IO address and IRQ line has been assigned, use the lspci command as demonstrated. The d switch filters results to any devices with IDs VENDOR:PRODUCT. By leaving the PRODUCT ID blank, ALL Sealevel devices attached to the PCI bus will be displayed. The vvv option tells the command to be as verbose as possible giving us all the information we will need.

$ lspci -d 135e: -vvv

00:0f.0 Serial controller: Sealevel Systems Inc Unknown device 7203 (rev 01) (prog-if 02 16550])
Subsystem: Sealevel Systems Inc Unknown device 7203
Flags: medium devsel, IRQ 11
Memory at ee000000 (32-bit, non-prefetchable) [size=128]
I/O ports at b000 [size=128]
I/O ports at a800 [size=8]
I/O ports at a400 [size=8]

00:11.0 Serial controller: Sealevel Systems Inc Unknown device 7803 (rev 01) (prog-if 02 16550])
Subsystem: Sealevel Systems Inc Unknown device 7803
Flags: medium devsel, IRQ 10
Memory at ed800000 (32-bit, non-prefetchable) [size=128]
I/O ports at a000 [size=128]
I/O ports at 9800 [size=64]

The <IRQ_NUMBER> can easily be extracted from the output of the lspci command. Next to each device is listed the assigned IRQ. This is one of the two pieces of information we need.

The next piece of information can be extracted from the PCI Regions listed in the lspci output. Each PCI device is different, and a certain amount of thinking must be done to determine which region(s) are mapped to the devices UARTs.

• Most Sealevel devices with 4 or less ports use individual PCI regions to map each UART's 8 IO registers. Look for IO regions that have sizes of 8. There should be X number of size 8 regions (where X is the number of UARTS on the device).
• Many newer devices and 16 port devices use one large PCI region to map all of the devices UARTs IO registers. Look for IO regions that have sizes that are 8 times the number of UARTs.
• This information is usually contained within the device manual. If you are unable to determine the correct IO space, please contact Sealevel's Technical Support for assistance.

Once you know which region(s) correspond to which UARTs, you are interested in the <IO_ADDRESS>. This is a 4-digit hexadecimal number.

Now that all the necessary information has been gathered, it is time to use the setserial utility to attach a device to the 8250 driver. Each UART must be assigned, one at a time, using setserial.

# setserial /dev/ttyS# port <IO_ADDRESS> irq <IRQ_NUMBER> baud_base X

* The baud_base parameter is very, very important. Without a value > 0, the setserial command will fail. The proper baud_base is dependent on the particular piece of hardware being used. The product manual should be consulted to identifiy the proper baud_base.

The /dev/ttyS# (where # is an integer) must correspond to an existing device file. If there aren't enough device files, they can be created with the following command. The <MAJOR> is determined by the 8250 driver, and the <MINOR> is the next incremental integer. ($ ls -al /dev/ttyS#-1 to see what they should be)

# mknod /dev/ttyS# c <MAJOR> <MINOR>

Option 2:  Modify 8250 Driver to Include Sealevel Product/Vendor IDs.

NOTES

• This method requires kernel sources (NOT HEADERS). These can usually be obtained through the distribution's package management system. Alternatively, the vanilla kernel sources can be downloaded from kernel.org. Recompiling the Linux kernel goes beyond the scope of this document, and may be different depending on the distribution used. Consult the distribution's documentation concerning module building.
• This method could also be necessary if more than 4 8250 serial ports must be used at the same time. This requires modifying the kernel's configuration to support more ports.
• For instructions on adding a specific product configuration, contact Sealevel technical support.

Navigate to the directory containing kernel sources (usually /usr/src/linux).

First, verify that the desired device is not already supported by the 8250 driver. Open the header file pci_ids.h located in the include/linux subdirectory.  Find the keyword "SEALEVEL". There will be a list of definitions assigning macro names like "PCI_DEVICE_ID_SEALEVEL_*" to hexadecimal Sealevel product IDs. Scan through the list looking for your device's product number. If it is listed, then that device is already supported by the 8250 driver. If it is not listed, make a new entry with a unique macro name and the corresponding product ID.

.../include/linux/pci_ids.h
#define PCI_DEVICE_ID_SEALEVEL_COMM8   0x7801     //existing entry
#define PCI_DEVICE_ID_SEALEVEL_UCOMM8  0x7804     //new entry

Next, add the device to the 8250's device detection code. Edit the 8250_pci.c file located in the drivers/serial/ subdirectory. Again, find the keyword "SEALEVEL". There will be an array of pci_device structs. Scroll to the last entry with a SEALEVEL vendor macro. Make a new entry using the product ID that was created in the previous step. The last element of this entry will be a descriptor to a specific board configuration, which is hardware dependent.

.../drivers/serial/8250_pci.c
{PCI_VENDOR_ID_SEALEVEL, PCI_DEVICE_ID_SEALEVEL_COMM8, PCI_ANY_ID, PCI_ANY_ID, 0, 0, pbn_b2_8_115200 },
{PCI_VENDOR_ID_SEALEVEL, PCI_DEVICE_ID_SEALEVEL_UCOMM8, PCI_ANY_ID, PCI_ANY_ID, 0, 0, pbn_b2_8_115200 },

Next, verify that a reasonable number of 8250 serial ports can be allocated by the device driver. Edit the .config file located in the root of the kernel source directory. Search for the keyword "CONFIG_SERIAL_8250". Verify that appropriate values are used for each variable.

.../.config
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=48

Now recompile the driver module, remove the old module and insert the new one.

The serial USB driver in Linux contains many product IDs for Sealevel devices. However, the newest devices may not be currently included in the driver. This guide consists of example USB device installation instructions using either driver load time parameters or modification of the device driver to natively support the device. There are often subtle differences in Linux distributions. Any distribution specific conflicts should be resolved by consulting the distribution's documentation. 

Option 1: Serial USB Installation Instructions (No Recompile Necessary)

Notes:

• Commands preceded by '$' can be issued by user-level privileges.
• Commands preceded by '#' require root-level privileges.
• This method will ONLY work with single and dual port devices. Any device with more than two ports requires a driver modification and recompile (see Option 2 below).

1) Plug in the Sealevel USB device(s).

2) Open a terminal window and attain root privileges. This varies by distribution, but the most common method is to use the su command as demonstrated below.

$ su -
Password:
#

3) Ensure that the device has been detected by the USB subsystem. This can be accomplished by using the lsusb command as demonstrated below. The -s 0c52 parameter returns only information about Sealevel devices attached to the system's USB subsystem. For this example, we will attach the device driver to the e402 Sealevel hardware, which is the USB to RS-485 bridge used in Sealevel SeaI/O U-series data acquisition modules.

# lsusb -s 0c52
Bus 002 Device 011: ID 0c52:e402 Sealevel Systems, Inc.
Bus 002 Device 010: ID 0c52:2101 Sealevel Systems, Inc. 

4) The kernel driver module for all FTDI based USB serial devices is sometimes configured for automatic load at boot time. Depending on distribution, it may be necessary to unload the driver if it is already loaded. This can be achieved by issuing the following command. This command can be issued without detriment when the driver is not loaded.

# modprobe -r ftdi_sio

5) The FTDI serial USB driver in Linux contains many product IDs for Sealevel devices. However, the newest devices may not be currently included in the driver. The driver allows a single vendor and product pair to be passed at module load time. Using these parameters, it is unnecessary to recompile the driver. To inform the FTDI driver of the Sealevel device's identification information, issue the following command.

# modprobe ftdi_sio vendor=0x0C52 product=0xE402

6) The driver should now have identified the Sealevel device and is ready for communications. It may now be necessary to create the character special file used to interface with the device. Most modern distributions include a method of automatically creating these files in the /dev file system when they are identified by a device driver. The character special files typically use the ttyUSB# nomenclature. Verify their creation by issuing the following command.

# ls -al /dev/ttyUSB*
crw-rw----1 root uucp 188, 0 2008-05-08 10:59 /dev/ttyUSB0
crw-rw----1 root uucp 188, 1 2008-05-08 10:59 /dev/ttyUSB1

7) If the character special files have not been created automatically, or more than one appears, it is necessary to identify the driver major and device minor numbers. The driver major can be determined by searching the devices file in the /proc file system as demonstrated in the following command. The major number is highlighted in yellow below.

# cat /proc/devices | grep -i "ttyUSB"
188 ttyUSB

The device minor number can also be determined by searching a file located in the /proc file system. The tty directory contains information about all of the currently loaded tty drivers. Executing the next command will display a list of all USB serial ports detected by any USB serial drivers currently loaded. If multiple USB serial ports are detected by the system, identify which corresponds to the Sealevel device by checking the vendor and product IDs.

# cat /proc/tty/driver/usbserial
usbserinfo:1.0 driver:2.0
0: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52 product:2101 num_ports:1
port:1 path:usb-0000:00:1d.1-1.2
1: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52 product:e402 num_ports:1
port:1 path:usb-0000:00:1d.1-1.4

8) If the character special file for the Sealevel device was not present in step 6, it may be created by executing the following command. It may also be beneficial to you to create any extra special files corresponding to other USB serial devices that are not currently present. Be sure to replace the major and minor numbers listed below with those listed by the commands demonstrated in step 7 as they may vary from system to system.

# mknod /dev/ttyUSB0 c 188 0
# mknod /dev/ttyUSB1 c 188 1

9) User applications may now interactive with Sealevel device through the character special file with major and minor numbers corresponding to those determined in step 7. To check the major and minor numbers that are associated with the character special files in /dev file system, use the ls command as demonstrated. The major/minor pair is highlighted in yellow for each file.

# ls -al /dev/ttyUSB*
crw-rw----1 root uucp 188, 0 2008-05-08 10:59 /dev/ttyUSB0
crw-rw----1 root uucp 188, 1 2008-05-08 10:59 /dev/ttyUSB1

10) Ensure that all users account which must access the Sealevel device may do so. There are many ways to configure the file permissions to accomplish this goal, depending on the system and requirements. Distribution documentation on the chmod and chown commands should be consulted. To simply allow full access to any USB serial device, use the following command.

# chmod 777 /dev/ttyUSB*

The Sealevel device can now be accessed through the character special file corresponding to the major/minor pair of the device. In the examples shown here, the file would be /dev/ttyUSB1.

Option 2: Serial USB Installation Instructions (Hardcoded Driver Support)

Notes:

• Commands preceded by '$' can be issued by user-level privileges.
• Commands preceded by '#' require root-level privileges.
• This is the ONLY way a device with more than 2 ports will work in Linux.
• This method requires full Kernel source (see your distribution documentation for specific instructions to acquire and configure)

1) Open the ftdi_sio.h file for editing located in your kernel source directory.
(<source>/drivers/usb/serial/ftdi_sio.h)

2) Search for SEALEVEL_VID. This will bring you to a list of #define's for Sealevel USB serial devices.

3) Add new entries for each Sealevel listing discovered with the lspci command as described in Step 3 of the previous section.

...
#define SEALEVEL_2803_8_PID 0x2883 // SeaLINK+8 2803
#define SEALEVEL_E402_PID   0xE402 // << adding new E402 product ID
...

4) Close and save the changes to the header file.

5) Next open the ftdi_sio.c file for editing. It is located in the same directory as the header file.

6) Search for SEALEVEL_VID. This will bring you to an array of vendor/product id structures.

7) Add new entries for each new #define added in Step 3.

...
{ USB_DEVICE(SEALEVEL_VID, SEALEVEL_2803_8_PID) },
{ USB_DEVICE(SEALEVEL_VID, SEALEVEL_E402_PID) }, // << adding new E402 ID
...

8) Now recompile kernel driver modules. Consult your specific distribution documentation.

# cd <source>
# make modules && make modules_install

9) Now reload the ftdi_sio kernel module.

# modprobe -r ftdi_sio
# modprobe ftdi_sio

10) Continue from Step 6 of Option 1 above.

The 2107 is designed for two-wire (half duplex) RS-485 applications and provides reduced wiring costs and protection against EMI and other induced line noise.

To integrate the 2107 with your RS-485 network, start by installing the 2107 per the instructions in the user manual. Since termination and biasing are always present on the 2107, it can be placed at either end of your RS-485 network. Detach the included removable terminal block adapter (TB34) from the 2107. Wire the terminal block on the TB34 as noted in the table.

Connect the TB34 to the 2107's DB9M connector and secure the thumbscrews. Your 2107 is now ready to communicate with other RS-485 devices at data rates up to 921.6K bps.

We assume that you want to use a standard (CAT5/6 EIA/TIA-568B) Ethernet patch cable to connect to the RJ45 pass-through connector on the side of the SeaI/O module, due to their low cost, wide availability and various lengths.

If you are connecting a SeaI/O module to another RS-485 device, plug one end of the patch cable into the RJ45 pass-through connector on the side of the SeaI/O module. Cut off the RJ45 connector on the other end of the cable and connect the following wires to your RS-485 device:

• Blue is RS-485 Data + (Data B)
• White/Blue is RS-485 Data - (Data A)
• Both Brown and White/Brown are Common (Signal Ground)

Note: If you are connecting two SeaI/O modules together, you can simply connect them together using a standard Ethernet patch cable. Do not use an Ethernet crossover cable, else you will short the power and ground wires.

We recommend using a SeaI/O-570 module, which has eight 16-bit A/D inputs that are capable of measuring floating, or non-referenced, analog signals.

For instructions and schematics for interfacing a SeaI/O-570 module to floating analog signals, read the Floating Signal Source Wiring Guide section of the Interfacing Analog Signals to SeaI/O-570 Modules resource article.

A floating signal source is a signal that is not connected in any fashion to the building ground system but rather has an isolated ground reference point. 

Examples of floating signal sources are outputs of transformers, thermistors, battery-powered devices and optically-isolated outputs.

Product Manual for Sealevel Model 8012e in PDF Format

Article by Liz Segrist (Appeared in November 7, 2011 issue of GSA Business)

Sealevel Systems Inc. of Liberty recently expanded to support its new contracts with the U.S. Department of Defense and a defense company – the largest contracts in the company’s 25-year history.

Download the pdf and read the full article below.

COM Express is the most commonly used Computer on Module implementation. Although there are three different sizes and other technical variations, the Basic size (125 x 95mm) and Type 2 pin out configuration are the most widely used and will work for most applications.

The Type 2 COM Express pin out provides a number of high speed buses to the carrier board including PCI Express, PCI, VGA, SCDO, IDE, SATA, Ethernet, USB, LPC and more. These signals are used in Sealevel carrier board designs to create optimized, custom solutions that provide the application-specific I/O, connector layouts and mechanical configurations for target applications.

The signal buses and capacity on Basic sized Type 2 modules include:

Bus Signals	Capacity & Usage
PCI Express	Up to 22 lanes for PCI Express devices. Can provide additional I/O expansion via FPGA and Sealevel IP.
PEG / SDVO	PCI Express Graphics supporting up to 16 lanes dedicated to video; or Serial Display Video Out via a dedicated I2C channel. Can provide HDMI, DVI and DisplayPort interfaces.
PCI	A single 32-bit port 33/66MHz interface for PCI devices.
SATA	Up to four SATA channels that support 150 – 300Mb transfer.
IDE	A single Parallel ATA100 (PATA) interface for mass storage devices.
LAN	A single 10/100/1000 Base-T Gigabit Ethernet port. Carrier board can include additional LAN ports via PCI Express.
USB	Up to 8 USB 2.0 ports. Can provide additional USB ports on carrier board via USB hub chips.
LPC	Low Pin Count Bus for legacy I/O expansion. Ideal for adding serial, parallel, floppy, keyboard and mouse via Super I/O controller.
AC'97 / HDA	Audio Codec 1997 specification; or High Definition Audio for 16-bit stereo audio output.
Speaker Out	A single PC-AT speaker signal for system beeps and chirps.
VGA	A single analog video output via dedicated DDC. Resolution dependent upon embedded graphics capability of COM Express module. Can provide additional VGA interfaces on carrier board via PCI Express.
LVDS	Low Voltage Differential Signaling with dual-channel interface for very high bandwidth displays.
TV Out	For NTSC/PAL standard video output. Supports Component, S-Video, or Composite video interfaces.
I2C	Inter-Integrated Circuit. A single dedicated I2C channel for low speed system communications.
SMBus	Generic processor interface via I2C for System Management Bus.
GPIO	8-bits of General Purpose I/O for software configurable interfaces.
ExpressCard	Two ExpressCard interfaces for mobile computing and hot-swappable peripheral cards.
Watchdog	A single watchdog timer for system reset logic and recovery.

COM stands for “Computer on Module”. A COM Express module is a small, integrated computer board that contains the CPU, memory, video, Ethernet and USB functionality in a rugged, embedded form factor. The COM Express module is mounted to a custom carrier board that integrates application-specific I/O and the necessary connectors for interfacing real-world devices.

COM Express modules are available from many suppliers in a variety of processor choices, with low power, low heat and extended temperature capabilities. A Sealevel custom carrier board and software drivers can deliver the perfect mix of serial, digital, analog and other application specific I/O. Click to learn more about Sealevel COM Express carrier board designs and solutions.

The DIN-rail mount Interface Converters (Item# 1104, 1105) QuickStart Guide in PDF format.

Article by Earle Foster
(Reprinted from Military Embedded Systems, October 2011)

Military system designers often struggle with finding COTS technologies that can meet critical application requirements. Custom designs almost always offer the best opportunity to create an optimized design, but time to market and design costs can be prohibitive. A hybrid architecture using a Computer on Module (COM) for the core processing functionality with a custom carrier board for application specific I/O can offer the best of both worlds. This approach eliminates the time and risk associated with a custom processor design while the less complex carrier board provides the advantages of a purpose-built design.

A COM Express module and custom carrier board provide the advantages of custom solutions with the convenience of COTS. Read more about design flexibility, reliability improvements and design control advantages of a COM Express carrier board design. Download the PDF file below.

The COM Express Custom Solutions datasheet in PDF format.

TTL I/O devices are commonly used to control solid-state relay modules that interface a variety of input and output devices.  An important consideration in these applications is to make sure that the solid-state outputs are properly configured before being energized. 

Solid-state relays operate using negative logic, where the off state (logic 0) is 5V. Sealevel TTL devices adhere to the Opto22 standard for solid-state relays and are designed to power up in the off state by having 5V present on all I/O pins at start-up. This prevents unintended activation of connected negative logic devices.

Sealevel TTL I/O adapters follow a specific start-up sequence to provide safe operation by guaranteeing a single transition from no state to either 0V (logic 1) or 5V (logic 0).

• As soon as power is applied to the TTL adapter, the I/O pins are pulled to 5V through a 10K Ohm resistor. At this point all I/O pins are inputs and power up in a known state.
• Next, the device driver or firmware applies the preset values from the device configuration to all pins. All TTL I/O pins are still configured as inputs and the preset values have no affect on input pins. Therefore, this step does not change the state of any I/O pins. 
• Finally, the device driver or firmware switches ports that are configured as outputs to an output state. Since the presets were applied before this step, only output pins that are preset to negative logic 1 (0V) change their value. All outputs that are preset to negative logic 0 remain at 5V and do not change state.

All I/O pins remain in this state until the user’s application takes control of the adapter.

"When a circuit requires logic 1 to operate, engineers may refer to this condition as positive logic. Thus, the more positive voltage causes the action to take place. On the other hand, if a circuit requires a logic 0 to cause action, this type circuit is referred to as negative logic.

There is nothing negative or positive about these various circuits. The notation simply provides a shorthand that tells engineers and users whether a logic 1 or a logic 0 causes an action." The Digital I/O Handbook, Chapter 1 Logic Principles, Tom O'Hanlan and Jon Titus

Sealevel digital I/O adapters that use the SeaIO driver support configuring them for positive or negative logic. The relay outputs are configured for positive logic by default, meaning that the relays are in the open or reset position and logic 1 must be written to close or set the relays. If the relays are configured for negative logic (through Windows Device Manager), then logic 0 would be written to close or set the relays.

Optically isolated inputs are also configured for positive logic by default, meaning that the inputs report logic 1 when a voltage is applied across the contacts. If the inputs are configured for negative logic (through Windows Device Manager), then logic 0 would be reported when a voltage is applied across the contacts.

The SeaI/O data acquisition modules use the SeaMAX driver and support positive logic.

Microsoft Windows maintains the configuration (enumeration) information for every USB device that has ever been connected, unless you explicitly uninstalled the device before unplugging it. When a USB device is not physically connected to the computer, Windows does not normally display the device in Windows Device Manager. These USB devices are called “non-present” or “phantom” devices.

Windows Device Manager can be used to uninstall or change the properties of non-present USB devices after a session-specific variable has been set. This variable can be set in a command window in Windows 2000 and later. These commands must be “Run as administrator” in Windows 7, Vista or later.

• set DevMgr_show_NonPresent_Devices=1
• devmgmt.msc

These commands set the variable and open Windows Device Manager. In the Device Manager window, click the View menu and set the 'Show hidden devices' option.

Non-present devices appear with a ghosted icon. Right-click on the non-present device and select 'Uninstall' in the fly-out menu.

Non-connected analog inputs should always be connected to the analog ground or common reference terminal. This eliminates phantom readings on all unused analog inputs.

When an unused analog input is not connected to a reference voltage source, the high-impedance circuitry can react to local electrical noise causing the input to see phantom data. Connecting all unused analog inputs to the analog ground or common reference terminal will eliminate this problem.

Sealevel SeaLINK Ethernet serial servers support a 2-byte format to marshal 9-bit serial data between the host computer and the serial server. The least significant bit of the first byte is the 9^th bit of the serial frame and the second byte is the first 8 data bits of the serial frame. SeaLINK Ethernet serial servers also support 9-bit serial tunneling.

SeaLINK Ethernet serial servers use RFC-2217, the Telnet COM port control protocol, to transmit modem control signals in serial tunneling mode. Since SeaLINK Ethernet serial servers are DTE devices, they follow standard null-modem conventions to tunnel output modem control signals. This is done in two parts as explained below.

Setting the output modem control signals on the remote serial server

The remote SeaLINK serial server sets output modem control signals on the output serial port when it receives the matching RFC-2217 command:

• Set DTR ON
• Set DTR OFF
• Set CTS ON
• Set CTS OFF

Receiving input modem control signals on the local serial server

When input modem control signals are set on the input serial port, the local SeaLINK Ethernet serial server will send the RFC-2217 commands to set DTR or CTS as follows:

• When a SeaLINK device sees either the DSR or DCD input is ON, it sends the RFC-2217 command to set DTR ON.
• When a SeaLINK device sees both the DSR and DCD inputs are OFF, it sends the RFC-2217 command to set DTR OFF.
• When a SeaLINK device sees the CTS input is ON, it sends the RFC-2217 command to set RTS ON.
• When a SeaLINK device sees the CTS input is OFF, it sends the RFC-2217 command to set RTS OFF.

Sealevel's SeaIO Classic V3 software drivers and utilities make installation and operation easy using 32-bit versions of Microsoft Windows operating systems.

SeaIO software is supported in:
Windows 7 32-bit
Windows Vista 32-bit
Windows XP 32-bit
Windows 2000
Windows ME
Windows 98, 98SE

*Note: SeaIO Classic V3 supports USB, PC/104 and ISA products. For 64/32-bit driver support for PCI and PCI Express products, use SeaIO Classic V4.

Product Manual for Sealevel Model 7804e in PDF Format

Product Manual for Sealevel Model 2107 in PDF Format.

Sealevel synchronous serial adapters support the three most common non-encoded clocking modes:

1. The Sealevel serial adapter provides the clock using the baud rate generator (BRG) that will be used by the other serial device for transmitting and receiving.
2. The other device provides an external clock that the Sealevel serial adapter will use for transmitting and receiving.
3. The Sealevel serial adapter provides the clock (using the BRG) for the transmitted data and the other device provides an external clock for its transmitted data. The benefit of this mode is the transmit and receive data rates do not have to match.

Sealevel synchronous serial adapters are capable of a constant output stream if the application program can provide a constant stream of serial data. If you are using either blocking (normal) I/O or overlapped I/O with only one write active at a time, then the adapter will run out of data to send when the application is processing the next write. The most efficient solution is to have multiple overlapped writes that are active simultaneously.

Product Manual for Sealevel eI/O Ethernet Digital I/O Modules in PDF Format.

The extra data is non-serial Telnet command messages such as COM port settings and modem control signals. SeaLINK devices communicate using the RFC-2217 Telnet Com Port Control protocol so they also send control sequences and certain bytes in a Telnet compliant manner.

Every Telnet control sequence begins with the "Interrupt As Command" (IAC) byte, which has the decimal value 255. Serial data is sent with the IAC value (decimal 255) repeated as a two-byte (escaped) sequence. The receiving device interprets that two-byte sequence as a single (unescaped) serial data byte with decimal value 255 instead of a Telnet control sequence.

For proper enumeration of Sealevel multiport serial adapters, the following components must be included in the Microsoft Windows XP Embedded OS image build:

"Class Installer - Multifunction adapters [Version 5.1.2600.2180, R2890]"
"Class Installer - Multi-port serial adapters [Version 5.1.2600.2180, R2890]"

Ensure that mf.sys is included in the Windows/Systems32/Driver directory. Also make sure that the current SeaCOM serial driver is installed prior to installing the serial adapter hardware.

Microsoft Windows requires these drivers and components to be installed so that Sealevel multiport serial devices will install properly and enumerate.

Manchester clock encoding (also known as split phase or bi-phase level encoding) always produces a transition at the center of the bit cell.

Sealevel synchronous serial adapters with the Zilog Z85230 chipset family can receive Manchester encoded data, but cannot transmit it.

Sealevel synchronous serial adapters with the Zilog Z16C32 chipset can both receive and transmit Manchester encoded data.

To optimize a SeaLINK Ethernet serial server for lower latency, disable Nagle’s algorithm on both the SeaLINK device and virtual COM port driver. SeaLINK devices and drivers use Nagle’s algorithm, also referred to as “nagling”, to increase serial data throughput while reducing network traffic.

By default, SeaLINK Ethernet serial servers use Nagle's algorithm to reduce network traffic and increase serial data throughput, with the side effect of increasing latency. Both SeaLINK devices and the virtual COM port driver have settings to disable Nagle's algorithm, also referred to as "nagling". To reduce latency, disable Nagle's algorithm in both the SeaLINK device and driver.

Sealevel USB serial adapters are supported by the SeaCOM driver, which includes a latency timer with a default setting of 16 msec. Decreasing this value reduces the amount of time a USB device buffers data before completing a write to the host computer, which increases the CPU overhead of the driver. A full USB device buffer is sent immediately without waiting for the timer to expire. Decreasing the latency timer can improve performance related issues and should reduce the overall latency of read cycles.

To access the latency timer, navigate to Windows Device Manager; expand the ‘Ports’ section and right-click on the USB to serial adapter listed. Click ‘Properties’ to open the device properties window. Click the ‘Ports Settings’ tab followed by the ‘Advanced…’ button. The ‘Latency Timer (msec)’ drop box is located in the ‘BM Options’ group on the left side of the window.

To avoid potential data loss, we do not recommend setting the latency timer below 4 msec. The latency timer does not affect the transmission of data from the host computer to the USB device.

Floating Signal Source Wiring Guide
A floating, non-referenced signal source is a signal that is not connected in any fashion to the building ground system but rather has an isolated ground reference point. Examples of floating signal sources are outputs of transformers, thermistors, and battery-powered devices. To measure these devices, the ground reference point must be set to the analog ground reference of the SeaI/O-570 as shown in the below schematic. Without this connection, the signals will float and an accurate measurement is not possible. The SeaI/O-570 is configured to measure floating, non-referenced signals by default.

Ground-Referenced Signal Sources Wiring Guide
A ground-referenced signal is a signal that is connected in some fashion to the building system ground and therefore is already connected to a common ground point with respect to the SeaI/O-570. Examples would be non-isolated outputs of instruments and devices that are connected to the same building power system as the SeaI/O-570. The difference in ground potential between two devices connected to the same building power system is typically 1mV to 100mV and can be much higher with improper power system grounding. This ground potential difference can show up as a measurement error without using the proper measurement connections. The connection scheme below is designed to eliminate this ground potential difference from the measurement. This setting can be configured and verified via Sealevel SeaMAX software.

Thermistor Inputs
On the SeaI/O-570 PCB, Switch 5 (SW5) allows each of the eight A/D channels to be individually configured for a thermistor by moving the corresponding channel selector (1-8) to the “On” position. This will apply a bias voltage of +5V through a 10K Ohm resistor. Connect the thermistor between the input and ground reference on the SeaI/O-570’s terminal block connector. This will create a voltage divider and as the resistance of the thermistor changes so will the voltage read by the application. Please reference the data sheet of the chosen thermistor to calculate the measured temperature.

This is the standalone version of the Sealevel WinSSD diagnostic utility that is included in our SeaCOM, SeaLINK, and SeaMAC software packages.

WinSSD is a full featured synchronous/asynchronous diagnostic utility for Windows. For asynchronous serial troubleshooting, WinSSD allows the user to modify the default UART parameters, perform external loopback tests, toggle modem control signals and transmit test pattern messages. Included applications allow terminal mode operations, bit error rate testing, and throughput monitoring. When used with a Sealevel synchronous serial adapter, the user has full control over electrical interface, framing method, RSET and TSET source, transmitter and receiver bitrate, oscillator frequency, CRC, preamble, clock encoding, sync character, and more.

For more information, read the SeaCOM and SeaMAC software overview pages linked below.

Overview
This condition is potentially encountered in Microsoft Windows when connecting a serial GPS device to a serial port. It is caused when the NMEA 0183 GPS serial data is misinterpreted as mouse data by the serial port enumerator (serenum.sys), resulting in erratic mouse cursor activity. The following steps will cure the "crazy mouse" syndrome with Sealevel USB to serial adapters. The instructions were tested in Windows 7 and can be adapted for Windows Vista or XP operating systems.

Unplug or Disable the Serial GPS Device


1. To gain control of the mouse, first make sure that the attached NMEA data source (e.g., GPS, AIS, Sonar) is either powered off or unplugged from the serial port on the USB serial adapter.
2. Keep the USB to serial adapter connected to the USB port.
   




Locate the USB Serial COM Port in Windows Device Manager


3. Click on the Start menu.
4. Right click on 'Computer' ('My Computer' in Windows XP).
5. In the fly-out menu, left click 'Manage', as shown.





6. In the 'Computer Management' window, left click on Device Manager.
7. In the right pane, expand the ‘Ports (COM & LPT)’ section by clicking on the triangle ('+' symbol in Windows XP), as shown.
8. Under 'Ports (COM & LPT)', double click on the USB serial device entry to bring up the Device Properties dialog box. Sealevel devices will be labeled 'SeaLINK' or 'SeaPORT'.








Disable the Serial Port Enumerator (Serenum.sys)


9. In the Device Properties window, click the 'Port Settings' tab.
10. Then click the 'Advanced' button, as shown, to open the Advanced Settings window.





11. In the Advanced Settings window, locate the Miscellaneous Options section and uncheck the box for 'Serial Enumerator', as shown. This will prevent serenum.sys from being associated with this COM port.





12. Click the OK button to confirm your changes.
13. Click the OK button to close the Device Properties window.
14. Close the Computer Management window by clicking the 'X' in the top-right corner.
    

Contact our technical support department if you continue to experience symptoms of "crazy mouse" syndrome.

Yes. Please include your account number in the 'Special Instructions' field and we will bill the freight charges to your account. The 'Special Instructions' field is found on the 'Shipping Method' screen of the checkout process.

All Sealevel TTL Digital I/O products are configured to power up in input mode by default. This ensures that no outputs are inadvertently activated.

The R5200 industrial computer supports boot up after a power failure scenario. The default setting is ‘OFF’.

To enable this feature, access the BIOS settings by pressing the DEL button from the start-up splash screen.

Once in the BIOS, navigate to ‘Integrated Peripherals’ – ‘SuperIO Device’ – ‘Power On after PWR-Fail’. Select the ‘ON’ option and then press F10 to save the changes and exit the BIOS settings. The R5200 will now reboot automatically after a power failure.

Talos framework and R9 development software for the Sealevel R9 family of embedded RISC computers.

SeaPAC R9-8.4 user manual in PDF format.

You are describing the "crazy mouse" syndrome, a common condition when Microsoft Windows receives NMEA 0183 data from a serial GPS device. The condition occurs when the GPS data is misinterpreted as mouse data by the Windows serial enumerator and will cause unwanted mouse cursor activity. It is most commonly encountered when connecting a serial GPS device to any USB to serial adapter. It is easily remedied in Windows Device Manager by disabling the Windows serial enumerator for the COM port connected to the GPS.

For more information, read the How to fix "crazy mouse" syndrome with USB serial adapters article.

The Zilog 16C32-based 3514 and 5104 have 256 K of memory on the adapters that are used for buffering the input and output data. To aid in transfer efficiency, the Windows SeaMAC V4 driver conducts 32-bit transfers from the adapters’ memory to the system memory until there are less than four bytes to transfer. The remaining (1-3) bytes use 8-bit transfers.

The Z16C32 operates similar to a UART and transmits the least significant bit first. The only exception is when the card is operating in SDLC/HDLC mode with CRC enabled. The CRC is transmitted most significant bit first and all other serial data is transmitted least significant bit first.

Please refer to the SeaLINK User Manual or contact Sealevel technical support for instructions on updating the firmware on your SeaLINK Ethernet serial hardware.

The ITU document O.153 paragraph 2.1 indicates the BERT pattern can be used at data rates up to 14.4 Kbps. However, the Sealevel WinSSD utility allows the BERT pattern to be used at all available data rates and supported communication modes, including those above 14.4 Kbps.

The CRC-CCITT polynomial value used in the Zilog Z85230 is:
x¹⁶ + x¹² + x¹¹ + x¹⁰ + x⁸ + x³ + x² + x¹ + 1
The corresponding hexadecimal value is 0x1D0F.

The CRC-CCITT polynomial value used in the Zilog Z16C32 is:
x¹⁶ + x¹² + x⁵ + 1
The corresponding hexadecimal value is 0x1021.

The Cyclic Redundancy Check (CRC) is a check value used to detect transmission errors in a frame or block of data. The transmitter encodes the calculated CRC value and appends it to the data transmitted. The receiver decodes the calculated CRC value and compares it to the received data. Errors in the CRC indicate data was corrupted during transmission.

With Sealevel synchronous serial adapters, the CRC is used to detect errors in the received address, control and data fields. It is generated based on specific polynomials and a starting sequence of either zeros or ones.

Application Example:

Highly inductive loads, those that use magnetic fields such as DC motors, produce a surge of voltage (referred to as "blowback voltage") when a relay is opened, breaking power to the electrical circuit. This surge of blowback voltage is created by the collapsing of the armature coil's magnetic field. In cases with large or higher wattage motors, this can cause an overvoltage condition on the motor and could cause the relay contacts to arc and possibly fuse. To protect against this overvoltage condition, care must be taken to dissipate the energy stored in the DC motor's coil when power is removed and there is no longer a path for current to flow.

In this example, we will demonstrate why an open-collector output with a flyback diode is better suited for controlling applications that are considered highly inductive.

Application Explanation

Reed Relay Implementation

Figure 1 shows a simple circuit for controlling power to a 24V typical DC motor using a Reed relay on a Sealevel SeaI/O-440U distributed I/O module. For this example, we will use an oscilloscope to measure the voltage change when power is removed (turned off) using this circuit.

Figure 1

Figure 2 represents a graphic from an oscilloscope measurement of the voltage spike that is induced at the Reed relay terminals when the relay is opened, removing power from the DC motor. This graph shows a delta voltage (delta Y on the screen) of 127V. During testing there were approximately 200V (delta) spikes routinely observed when the Reed relay is turned from on to off, indicating that the Reed relay did not properly dissipate the highly inductive load energy from switching the DC motor's power.

Figure 2

Open Collector Output

Figure 3 shows a circuit for a controlling a 24V DC motor with Sealevel's SeaI/O-540U open-collector output module with integrated flyback diode controlling power:

Figure 3

Figure 4 shows a graphic using an oscilloscope measurement of the voltage change that is induced when power is removed from the DC motor when using an open-collector output from the SeaI/O-540 module. During the open-collector output testing, the largest observed voltage change was 30V DC at the output terminal.

Figure 4

Conclusion

When power is removed from a highly inductive DC motor, the motor's blowback voltage must be properly dissipated to avoid damage to the electrical control circuit and/or the DC motor. This example clearly verifies that our open-collector output with a flyback diode circuit works very well at controlling highly inductive load energy associated with DC motors.

Sealevel's SeaI/O-530 and SeaI/O-540 modules use open-collector outputs with integrated flyback protection diodes making them a good choice for this application. The flyback diode provides a path for current to flow and dissipate in these conditions.

If Reed relays are used for moderate inductive load applications, they may require employing circuit protection measures. Reed relays are perfectly suited for a broad range of control applications but are not typically called upon as a solution for highly inductive loads.

Equipment Specifications:

DC motor: Pittman/CPR: 500
Power supply: Bench top 24VDC
Oscilloscope: Rigol DS1052E

SeaIO-540U: (32) Open-Collector Outputs (each containing a flyback protection diode)
SeaIO-440U: (32) Form A - Reed Relay Outputs

Section 2.5 of the ITU O.151 document basically states that a pattern can be encapsulated by the framing bits of a protocol, if necessary. Therefore, the BERT pattern can be used in a synchronous mode, such as SDLC/HDLC, as well as asynchronous mode.

Open-collector outputs with circuit protection are the best choice for controlling power to devices with highly inductive loads such as DC motors, solenoids, and high-current relays.

Switching off inductive loads can induce a voltage spike capable of causing damage to relays, digital outputs, or the DC motor itself.

Both SeaI/O-530 and SeaI/O-540 modules have isolated open-collector outputs with integrated flyback diodes. The flyback diode provides a high level of circuit protection against the voltage spike damage caused by switching highly inductive loads.

Product Manual for Sealevel Model Relio R5200 in PDF Format.

In Windows Device Manager, Sealevel synchronous serial adapters will install under the ‘SeaMAC Device’ category. The device names for Sealevel synchronous serial adapters, with part numbers in parenthesis, are shown as they appear in Device Manager.

PCI Synchronous Serial Adapters
‘4 Port Synchronous-Capable Serial Adapter (5402)’
‘High Speed Multi Protocol Serial PCI Adapter (5104)’
‘Synchronous-Capable Serial Adapter (5103)’
‘Synchronous-Capable Serial Adapter (5102)’

PCMCIA Synchronous Serial Adapter
‘Synchronous-Capable Serial Adapter (3612)’

PC/104+ Synchronous Adapters
‘High-Speed Multi-Protocol Serial PC/104 Adapter (3514)’

PC/104 & ISA Synchronous Adapters*
‘Synchronous-Capable Serial Adapter (ACB 1 Port)’

* Note that (ACB 1 Port) is the name displayed in Device Manager for all legacy Sealevel synchronous serial adapters.

An example showing a 5102 and 5104 installed is shown in the image below.

Overview

A new customer, who makes communication equipment for the public safety sector, had relied on a competing Ethernet to RS-232 serial server for a number of years. The product’s installation and configuration process was not simple as promised in the competitor’s advertisements, and the process often involved multiple, time-consuming attempts. Known issues with the driver, a lack of support from the product manufacturer, and a major upgrade looming led the company to look for other options. After reviewing all available options, the company selected the Sealevel Ethernet serial server as the best option.

See how Sealevel engineers hit a home run with the Sealevel Ethernet-to-RS-232 serial server. Download the rest of the "Customer Spotlight – Ethernet to RS-232 Custom Solutions: Public Safety Communications" article (PDF), below. Sealevel also offers a variety of standard SeaLINK Ethernet serial server solutions.

Customer Spotlight - RF Base Station Interface

Sealevel synchronous serial adapters enumerate as SeaMAC devices in Windows. Since the devices are zero-indexed, the first installed port will be ‘SeaMAC0’.

SeaMAC devices support additional features that are not typically found on asynchronous serial adapters which enumerate as COM ports. Many banking, military, aerospace and other synchronous applications communicate using common synchronous serial protocols and do not expect a COM port. The SeaMAC V4 API provides a user-friendly interface for developing these optimized applications. By enumerating as devices, SeaMAC synchronous adapters operate at maximum efficiency.

Applications that require 9-bit protocols are rare so the chips that support them are more expensive than standard 8-bit UARTs.

Most 8-bit UARTs can simulate 9-bit protocols by setting the parity bit to mark or space. This was an easy solution on the 16C450 UART and other 8-bit UARTs without FIFO buffers. Modern 8-bit UARTs like the 16C550 and 16C850 have FIFO buffers that make 9-bit support more complicated to implement.

The 16C950 UART and 16C954 quad-port UART solve this issue by including 9-bit data buffers in hardware. Most Sealevel asynchronous serial adapters can be upgraded with 16C950 or 16C954 UARTs for a nominal charge. Call for details.

Note: USB serial adapters use a different communications chipset and cannot support 9-bit data framing.

Any Sealevel asynchronous serial adapter that includes a 16C950 UART or 16C954 quad-port UART natively supports 9-bit framing in hardware. USB serial adapters use a different chipset and are not capable of 9-bit data framing. Other Sealevel serial adapters can be upgraded with a 16C950 or 16C954 UART for a nominal charge. Call for details.

2-wire RS-485 connects the transmitter and receiver to the same data channel. Many applications are not designed to receive the same data they are transmitting and expect the serial port to be set to ‘No Echo’. Therefore, when the serial port is transmitting data, the receiver is disabled. For this reason an external loopback adapter will not work with 2-wire RS-485.

To successfully perform a loop back test with 2-wire RS-485, the easiest method is to connect two adjacent serial ports together and use the BERT function in WinSSD. Set the first port to transmit and, the second port to receive and verify the data sent is the data received. Next, set the first port to receive and the second port to transmit to complete the loopback test.

On single port serial adapters configured for 2-wire RS-485, enable ‘Echo’ to allow the receiver to listen during transmission. This allows you to perform an internal loopback test. No external loopback adapter is required.

Note: Some single-port 2-wire RS-485 adapters do not support ‘Echo’. These must be configured for RS-422 or 4-wire RS-485 in order to perform a loopback test.

Yes. In the past Sealevel installed the OEM version of Microsoft Windows XP Professional. Now when you order Windows XP, Sealevel will install Windows XP Professional for Embedded Systems, including the latest service pack updates, on our industrial computers.

Not to be confused with Windows XP Embedded, Windows XP Professional for Embedded Systems and the OEM version of Windows XP Professional are identical from a technical and operational standpoint. Drivers and applications are installed exactly the same on both operating systems. Windows updates operate the same on both versions, too.

The key differences between the two operating systems are the way Microsoft licenses the products. Due to the licensing changes announced by Microsoft back in 2009, Windows XP Professional for Embedded Systems has the following characteristics:

• Longer product life-cycle – Windows XP Professional for Embedded systems is available until at least 2016. The OEM version of Windows XP Professional went end of life in 2009.
• You receive a license only – The license and certificate of authenticity is in the form of a decal applied to the computer chassis.
• No media is included - A CD or hard-copy manual is not included with the system. However, online help is available and you have the ability to create a recovery CD (requires an internal or external recordable CD/DVD drive).

Order Windows XP from Sealevel and know that you will receive the best support in the industry. You can also order Windows Embedded, Windows CE, Linux and other operating systems. Call us for details.

Non-polarized means that the input trigger condition measures the voltage magnitude across the input, or alternatively the current magnitude through the input, regardless of the actual direction of the voltage polarity or current direction. This distinguishes these optically isolated inputs from polarized inputs because the optical isolator uses a back-to-back arrangement of light emitting diodes. Inexpensive optical isolators will only trigger when the voltage across the input has a specific polarity or the current through the input is in a specific direction.

All Sealevel I/O products with isolated inputs use non-polarized optical isolators for trouble-free field wiring and improved reliability.

Manual for the Sealevel Talos API Framework in PDF Format. This manual includes the Talos API documentation for Windows CE 6.0 supporting the R9 family of embedded RISC computers.

Manual for Sealevel SeaMAX API in PDF Format. This manual includes the SeaMAX API documentation with support for SeaI/O, eI/O, SeaDAC and SeaDAC Lite modules.

The ACC-188 USB synchronous serial radio adapter (Item# 9065) and free software from DISA enables tactical radios with the capability to transmit and receive IP data such as email, text messages, GPS maps, images, coordinates, and other communications. The system is nonproprietary and MIL-STD-188-184 compliant, allowing for interoperability with various radios without multiple connections or additional equipment.

Learn how warfighters can benefit greatly from having fully interoperable radio IP-based data communications at the theater level in our "USB to Synchronous Cable Enables IP Data Communications for Tactical Radios" White Paper. Download the PDF file below.

Article by Earle Foster
(Reprinted from Defense Tech Briefs, February 2010)

The ACC-188 USB synchronous serial radio adapter (Item# 9065) and free software from DISA enables tactical radios with the capability to transmit and receive IP data such as email, text messages, GPS maps, images, coordinates, and other communications. The system is nonproprietary and MIL-STD-188-184 compliant, allowing for interoperability with various radios without multiple connections or additional equipment.

Learn how warfighters can benefit greatly from having fully interoperable radio IP-based data communications at the theater level in our "USB to Synchronous Cable Enables IP Data Communications for Tactical Radios" White Paper. Download the PDF file below.

Sealevel SeaI/O devices offer flexible I/O expansion to APC Netbotz remote environmental monitoring equipment. All APC NetBotz appliances that have a USB port support SeaI/O 450U and 462U modules to expand the amount of digital I/O. SeaI/O 450U modules provide 16 Form C relay outputs useful for locking doors, turning lights on or off, and other relay controlled actions. SeaI/O 462U modules provide 96 channels of TTL digital I/O useful for monitoring a large number of dry contact sensors. APC has developed a useful application note (download link below) with more information on using SeaI/O modules with your APC NetBotz appliance.

On February 16, 2010, Kontron customers received an End of Life (EOL) notification (PDF link at bottom of article) regarding the elimination of serial and I/O devices from their product listing. For more than 20 years, Sealevel has manufactured these products for Kontron. Sealevel will continue to offer these serial and I/O devices following Kontron’s Last Time Buy on August 31, 2010.

Below you will find a reference table showing the Kontron product and corresponding Sealevel product. The Sealevel products listed on this page are the same products you purchased from Kontron. From sales to technical support, our team will ensure that you purchase the correct product for your application.

For Sales Support Contact:
Charlie McKenzie
Channel Sales
charlie.mckenzie@sealevel.com
+1 864-843-4343

For Technical Support Contact:
support@sealevel.com
+1 864-843-4343

Kontron to Sealevel Part Number Cross Reference

Serial I/O - Asynchronous
Kontron Part#	Description	Sealevel Part#
USB
USB-ULTRA485	USB to 1 Port RS-422/485	2102
USB-COM232I	USB to 1 Port RS-232 (Isolated)	2103
USB-ULTRA485I	USB to 1 Port RS-422/485 (Isolated)	2104
USBCOMM232/2	USB to 2 Port RS-232	2201
USB-UC422/2	USB to 2 Port RS-422/485	2202
USB-UC232/2	USB to 2 Port RS-232/422/485	2203
USB-COMM232/4	USB to 4 Port RS-232	2401
USB-UC422/4	USB to 4 Port RS-422/485	2402
USB-UC232/4	USB to 4 Port RS-232/422/485	2403
USB-COMM232/8	USB to 8 Port RS-232	2801
USB-UC422/8	USB to 8 Port RS-422/485	2802
USB-UC232/8	USB to 8 Port RS-232/422/485	2803
PCI
ULTRA485	PCI to 1 Port RS-422/485	7105
COMM232PCI/2-55	PCI to 2 Port RS-232	7202
COMM232PCI/2-85	PCI to 2 Port RS-232 (16C850 UARTs)	7202-SE
UC232PCI/2-851	PCI to 2 Port RS-232/422/485	7203
UC422PCI/4-55	PCI to 4 Port RS-422/485	7402
UC422PCI/4-85	PCI to 4 Port RS-422/485 (16C850 UARTs)	7402-SE
UC232PCI/4-85	PCI to 4 Port RS-232/422/485	7404
Low Profile PCI
COMM+850	Low Profile PCI to 1 Port RS-232	7104
UPCI-COMM4/EX-555-LP	Low Profile PCI to 4 Port RS-232 (DB25)	7406
UPCI-COMM4/EX-559-LP	Low Profile PCI to 4 Port RS-232 (DB9)	7406-DB9
CompactPCI
CPCI-UC232/2	cPCI 2 Port RS-232/422/485	7901
CP6-3UADAPTER	cPCI 3U to 6U Adapter	7902
CPCI-UC232/2I	cPCI 2 Port Isolated RS-232/422/485	7903
CPCI-UC232/4	cPCI 4 Port RS-232/422/485	7904
CPCI-WINCOMM8	cPCI 8 Port RS-232 (DB25)	7905
CPCI-WINCOMM8-DB9	cPCI 8 Port RS-232 (DB9)	7905-DB9 (Call)
PC/104
SP104/232	PC/104 1 PORT RS-232	3551
ISA
ULTRA-485	ISA 1 Port RS-422/485	3055
SPRT2B/AT	ISA 2 Port RS-232/422/485	3087
DUAL232/AT	ISA 2 Port RS-232	3088
ULTRA-485/2ISO	ISA 2 Port Isolated RS-422/485	3189
WINCOMM8/C	ISA 8 Port RS-232 (DB25)	3420
HS-RS232/DP-85	ISA 2 Port High Speed RS-232 (16C850 UART)	3188-SE (Call)
Serial I/O - Synchronous
Kontron Part#	Description	Sealevel Part#
PCI-ACB	PCI 1 Port RS-232/422/485/449/V.35 (Z85230)	5102
PC-ACB-MP	PCMCIA 1 Port RS-232/422/485/530/530A/V.35 (Z85233)	3612
ACB-104/B	PC/104 1 Port RS-232/422/485/449/V.35 (Z85230)	3512
Digital I/O
Kontron Part#	Description	Sealevel Part#
USB
USB-DIO16	USB 8 Isolated Input /8 Reed Relay Output	8209
USB-16REL	USB 16 Reed Relay Output	8208
USB16ISO	USB 16 Isolated Inputs	8207
USB-DIO8	USB 8 Isolated Input/8 Form C Output	8206
USB-DIO96	USB 96 Channel Digital I/O	8205
USB-DIO48	USB 48 Channel Digital I/O	8203
PCI
PCI-16REL	PCI 16 Relay Output Digital I/O Card	8003
PCI-DIO32	PCI 16 Isolated Inputs / 16 Reed Relay Outputs	8004
PCI-DIO32-24-S	PCI 16 Isolated Inputs / 16 Reed Relay Outputs (For 24V with 2.2k resistors)	8004-2000 (Call)
PCI-16ISO	PCI 16 Isolated Inputs	8006
PCI-32REL	PCI 32 Reed Relay Outputs (Standard Male/Male Cable)	8007
PCI-32REL-B	PCI 32 Reed Relay Outputs (With CA-173 A Side/B Side Cable)	8007-A01 (Call)
ISA
DIO-32B	ISA 16 Isolated Inputs / 16 Reed Relay Outputs	3093
DIO-32B-24V	ISA 16 Isolated Inputs / 16 Reed Relay Outputs (For 24V)	3093-104 (Call)
16ISO	ISA 16 Isolated Inputs	3094
16ISO Special Order	ISA 16 Isolated Inputs (With 761-3-R2.2K)	3094-104 (Call)
16REL	ISA 16 Reed Relay Outputs	3095
DIO-16	ISA 8 Isolated Inputs / 8 Reed Relay Outputs	3096
32REL-B	ISA 32 Switched Relay Outputs	3098
Custom Counter/Timer Boards
Kontron Part#	Description	Sealevel Part#
PCI/DCC5-P10433-01A	PCI 16-bit 5-Channel Counter/Timer Board (PCIDCC5-P)	9004 (Call)
PCI/DCC10-P10433-02A	PCI 16-bit 10-Channel Counter/Timer Board (PCIDCC10-P)	9005 (Call)
PCI/DCC20-P10433-03A	PCI 16-bit 20-Channel Counter/Timer Board (PCIDCC20-P)	9006 (Call)

The USB Digital I/O QuickStart Guide in PDF format.

For guidance covering the initial steps of compiling and running individual example projects using Microsoft Visual Studio, please refer to the SeaMAX API Documentation.

To access the documentation from the Start Menu, click All Programs and locate the Sealevel Systems folder. In the SeaMAX subfolder, click on Documentation, and then click on the SeaMAX API Documentation link, which will open in your default browser.

Click on "Example Code & Instructions" under the Getting Started heading. Be sure to also read the "Integrating SeaMAX into Your Project" for a complete list of integration steps.

The SeaMAX Software package automatically installs several application samples with source code in the Example Projects subfolder.

To access the samples from the Start Menu, click All Programs and locate the Sealevel Systems folder. In the SeaMAX subfolder, click on Documentation, and then click on the Example Projects Folder shortcut. Select your development platform from the available choices. Sample applications are supplied for Microsoft .Net C#, native C++, and Microsoft Visual Basic 6.

The sample applications are designed to let you walk through the same integration steps that are required to integrate SeaMAX with your own project.

A Quadrature counter, also known as a Quadrature decoder, shaft decoder, or rotary decoder, is a type of digital input that uses a two-bit Gray code input to increase or decrease a value. The Quadrature counter works in combination with an optical or mechanical encoder, also known as a rotary or shaft encoder, to monitor the exact position, speed, and direction of a DC motor shaft.

The Quadrature counter works by reading the angular position of a shaft and converting it to high resolution digital data. This data is used for synchronizing moving parts for reliable, trouble-free operation. Optical encoders are commonly found in motors installed in industrial control applications, precision robotics, drive shafts, and rotating radar platforms.

Sealevel includes Quadrature counters in certain models of our R9 family of embedded RISC computers.

This Quick Start Guide is excerpted from the SBC-R9 hardware manual. For a complete overview of the hardware, including technical descriptions, connector diagrams, pin outs and debugging information, please refer to the product manual. If you want to get started right away, you may jump to the section Quick Start section below.

Before You Get Started

What's Included
The SBC-R9 is shipped with the following items. If any of these items are missing or damaged, please contact Sealevel for replacement.

• SBC-R9 ARM9 Embedded RISC Single Board Computer
• SD Card with CE runtime image, Talos .NET Framework, application samples, and documentation
• CD with Setup files and documentation
• Microsoft® Windows® CE 6.0 Core license

QuickStart Kit
The SBC-R9 QuickStart Kit (Item# SBC-R9-KT) is available, which includes the most common accessories. For applications with specialized hardware requirements, developers can use the SBC-R9 as a platform for application development while Sealevel designs a customized target system specific to the user’s application requirements.

The SBC-R9-KT includes the following items:

• SBC-R9 ARM9 Embedded RISC Single Board Computer
• SD Card with CE runtime image, Talos .NET Framework, application samples, and documentation
• CD with setup files and documentation
• Microsoft Windows CE 6.0 Core License
• TR134 – 100-240VAC to 12VDC @ 2.5A, wall mount power supply
• CA179 – USB Type A to USB Type B, device cable
• CA429 – R9 serial debug cable
• CA246 – CAT5 patch cable, 6' length
• CA273 – 40-pin IDC ribbon cable to (4) DB9M connectors

SBC-R9 Quick Start

Remove the contents from the box.

Insert the accompanying CD into your PC and run the installation program. This will install Talos Framework binaries, documentation, and examples on your PC. (See Figure 1)

Figure 1. Installation Wizard

After installation, the package can be found in Windows by clicking Start > All Programs > Sealevel Systems > R9 Development.

Verify that the accompanying SDCARD (located on the bottom card slot B (J11) of the SBC-R9) is correctly inserted. The contents of the SDCARD will allow the SBC-R9 to run Windows CE 6.0 OS when power is applied to the board.

Warning! To avoid accidental damage, be sure to follow proper ESD procedures by grounding yourself and the board.

Apply power to the SBC-R9 by connecting the TR134 Molex connector to the SBC-R9 (P3) connector. Attach the other end of the TR134 into a 120VAC wall outlet. (See Figure 2.)

Figure 2.  Connect the TR134 Molex connector to the SBC-R9 (P3) connector

Use a standard USB device cable and connect the Type B connector to the SBC-R9. (See Figure 3.) Connect Type A connector into the host PC.

Figure 3. Connect the Type B connector to the SBC-R9

You are now ready to set up a USB communication interface between the host PC and the SBC-R9 board. Depending on which operating system you are using – Windows Vista or XP – the setup experience will vary.

Windows Device Center

If your host PC is running Windows Vista or later and you are connected to the internet, then Windows Mobile Device Center software will install automatically. If you are not connected to the internet but have obtained the Mobile Device Center software manually then running their setup will achieve the same result.

After installation, a negotiation will begin between the PC and the SBC-R9 board and the device center connection screen will appear. (See Figure 4.)

Figure 4. Device Center connected screen

Using your mouse, select "Connect without setting up your device". The idea is to explore the file system on the SBC-R9 without setting up synchronization with contacts, calendar, or e-mail. Now choose "File Management > Browse the contents of your device" from the screen. (See Figure 5.)

Figure 5. Device Center File Management

This action opens a standard Windows Explorer where the default file contents of the SBC-R9 can be read or written to. (See Figure 6.)

Figure 6. Contents of SBC-R9

Windows ActiveSync for XP

If your host PC is running Windows XP, ActiveSync is required to establish connection to the SBC-R9. ActiveSync differs from Mobile Device Center in that having an internet connection will not establish an automatic download and installation. For installation procedures, refer to Microsoft's website. After installation, a negotiation will begin between the PC and the SBC-R9 board, and the "New Partnership" dialog will appear. (See Figure 7.)

Figure 7. ActiveSync New Partnership screen

Using your mouse, select "No" and then select "Next". The ActiveSync main dialog will appear. Select the "Explore" icon. This action opens a standard Windows Explorer where the default file contents of the SBC-R9 can be read or written. (See Figure 8.)

Figure 8. ActiveSync Main Dialog screen

You are now ready to set up a complete development environment for building and debugging smart device applications and libraries. The next section guides you by example using Microsoft Visual Studio.

Programming using the .NET Compact Framework

Application Development

Introduction
With .NET Compact Framework coupled with our Talos .NET Framework, C# and VB.NET programmers can develop powerful embedded applications on the SBC-R9 such as mobile, robotics, home automation, industrial, and a broad range of other embedded applications. The low cost of licensing for Windows 6.0 CE has created an ideal environment to develop a new generation of embedded products around the SBC-R9.

Our Talos Framework allows access to the more specific I/O sections of the SBC-R9 development board such as analog and digital I/O points, CAN bus, quadrature counter inputs, and the multi-electrical interface serial ports. A complete list of the API documentation can be found either in Windows by clicking Start > All Programs > Sealevel Systems > R9 Development > Talos Documentation.html or by referencing the Sealevel website.

Writing .NET applications for the SBC-R9 is very similar to writing desktop or console applications for XP and Vista. The only difference is the amount of resources available. Because the memory footprint is smaller compared to a desktop computer, care should be taken where allocation of memory is concerned, such as huge object creations.

Requirements

• Visual Studio 2005 or 2008
• .NET Compact Framework 3.5

Getting Started
For this demonstration, we will construct a smart device console application using Visual C#. Start Visual Studio and select File > New > Project. A 'New Project' dialog will appear. Select a project type of Visual C# > Smart Device. Select 'Smart Device Project' as the Template. Make sure the combo box has .NET Framework 3.5 selected. Type the name of the project. In this case, call it AnalogIO. (See Figure 9.)

Figure 9. Visual Studio New Project dialog

Click the "OK" button. The next configuration screen allows you to select the type of project you are creating. Select "Windows CE" for the target platform, .NET Compact Framework version 3.5 and select the "Console Application" icon for the template. (See Figure 10.)

Figure 10. Visual Studio Add Smart Device dialog

Once you have selected all of the configuration options, click the "OK" button. You will now see a console application template called AnalogIO in Visual Studio. (See Figure 11.)

Figure 11. Visual Studio Main Window

We can now add the references to the Talos Framework. Right click on the "References" and select the "Add Reference…" selection. (See Figure 12.)

Figure 12. Adding References to Project

An 'Add Reference' dialog will appear. Click on the 'Browse' tab then search for the installed library path "C:\Program Files\Sealevel Systems\R9 Development\Assemblies". If you don't see a list of the R9 libraries as shown in Figure 12, then refer to the SBC-R9 QuickStart section for software installation details. While holding down the CTRL key, click on both "SLCorLib.dll" and "Talos.dll". Click the "OK" button. (See Figure 13.)

Figure 13. Core library reference

Both DLLs should appear in your "References" list. (See Figure 14.)

Figure 14. Verification of added library references

Now that the Talos Framework has been referenced, you have access to all the I/O points exposed on the SBC-R9 device.

Replace the contents of the "AnalogIO" class file created by the project wizard with the installed AnalogI/O C# example. This example can be found at "C:\Program Files\Sealevel Systems\R9 Development\Samples\C#\AnalogIO\AnalogIO\Program.cs".

From Visual Studio's menu bar, select "Build > Build AnalogIO". After the build process has completed select from the same menu bar, "Build > Deploy AnalogIO". A "Deploy AnalogIO" dialog will appear for you to choose the appropriate target. Choose "Windows CE Device" then press the 'Deploy' button. (See Figure 15.)

Figure 15. Choose Windows CE Device and Deploy

After the deployment phase a console will appear to display the current count of analog points and their associated current values.

More examples can be found from the installation directory or the supplied SDCARD under "..\R9 Development\Sample\C#" and "..\R9 Development\Sample\VB.NET".

This Quick Start Guide is excerpted from the SBC-R9 hardware manual. For a complete overview of the hardware, including technical descriptions, connector diagrams, pin outs and debugging information, please refer to the product manual.

WinSSD currently only provides support for the 511-bit pattern defined in ITU document O.153 paragraph 2.1. This test pattern is common to many BERT applications. If you need other algorithms, contact Sealevel technical support for assistance.

Sealevel recommends using the installed COM numbers if at all possible to avoid system conflicts. If you previously installed a USB or PCMCIA serial interface, it will have resources assigned by the operating system. If the device is not currently connected to your computer, these COM assignments will not be apparent and forcing new COM port assignments will create a conflict when the devices are reconnected at a later time.

One scenario where you would have to change the COM port assignments is when your legacy application only works at COM1 through COM4 and the Sealevel serial device you installed comes in at COM5 or higher. Another scenario might occur when you install a multiport serial card and the COM port numbers are not assigned consecutively and you want them to appear consecutive.

In Windows 7, Vista, XP, or 2000, you can change the COM port assignments in Device Manager. In Windows 95, 98, ME, or NT, you’ll need to use Sealevel’s Port Manager or Advanced Ports utility.

Sealevel recommends using the installed COM numbers if at all possible to avoid system conflicts. If you previously installed a USB or PCMCIA serial interface, it will still have resources that have been assigned by the operating system. If the device is not currently connected to your computer, these COM assignments will not be apparent. It is possible to force a new COM port assignment when the device is removed that will create a conflict when the device is reconnected at a later time.

One scenario where you would have to change the COM port assignments is when your legacy application only works at COM1 through COM4 and the Sealevel serial device you installed comes in at COM5 or higher. Another scenario might occur when you install a multiport serial card and the COM port numbers are not assigned consecutively and you want them to appear consecutive.

Windows 95, 98, ME, and NT did not provide a way to change COM port assignments in Device Manager. Sealevel developed the Port Manager utility (Advanced Ports in NT) to address this Windows limitation. Port Manager is automatically installed when you install the SeaCOM serial driver. In Windows NT, the SeaCOM software driver installs the Sealevel Advanced Ports utility in the Control Panel.

To change COM port assignments using Port Manager in Windows 95, 98, or ME operating systems, follow these steps:

1) Click Start -> All Programs -> SeaCOM -> Port Manager

2) In the Port Manager window, select your current Device in the table by clicking on it to highlight.

3) Change the COM port assignment by choosing an available COM number in the Port Name drop box.

4) Click on the Apply button, and then the OK button to confirm changes.

5) Verify your changes in Device Manager under the Ports (COM & LPT) listing.

To change COM port assignments using Advanced Ports in Windows NT, follow these steps:

1) Click Start -> Control Panel
2) In the Control Panel window, double-click the Advanced Ports icon.
2) In the Advanced Ports window, select your current Device in the table by clicking on it to highlight.
3) Change the COM port assignment by choosing an available COM number in the Port Name drop box.
4) Click on the Apply button, and then the OK button to confirm changes.
5) Verify your changes in Device Manager under the Ports (COM & LPT) listing.

Contact our technical support department if you are still experiencing problems with serial COM port assignments.

Sealevel recommends using the installed COM numbers if at all possible to avoid system conflicts. If you previously installed a USB or PCMCIA serial interface, it will have resources assigned by the operating system. If the device is not currently connected to your computer, these COM assignments will not be apparent and forcing new COM port assignments will create a conflict when the devices are reconnected at a later time.

One scenario where you would have to change the COM port assignments is when your legacy application only works at COM1 through COM4 and the Sealevel serial device you installed comes in at COM5 or higher. Another scenario might occur when you install a multiport serial card and the COM port numbers are not assigned consecutively and you want them to appear consecutive.

In Windows 7, Vista, XP or 2000 operating systems, you can change the COM number assignment using Windows Device Manager.  To change the COM port assignments in Device Manager, follow these basic steps:

1) Click the Start button.

2) Right-click on My Computer.

3) In the fly-out menu, click Manage.

4) In the Computer Management Window, click on Device Manager.

5) In the right-hand pane, expand the Ports (COM & LPT) listing by clicking the "+" symbol.

6) Right-click on the COM number you want to change and select Properties from the fly-out menu.

7) In the Communications Port Properties window, click the Port Settings tab and then click the Advanced button.

8) In the Advanced Settings window, you can select the new COM port number from the drop box (be careful not to select a COM number already in use).

9) Click the OK button to confirm your changes. If Windows detects a conflict, choose another COM port number.

10) Click the OK button to close the Communications Port Properties window.

11) When Device Manager refreshes the hardware list, the COM assignment will reflect your changes. To get Device Manager to refresh the window on Windows XP, you may need to click 'Action' in the menu and then click 'Scan for hardware changes' in the sub-menu (Note: If 'Scan for hardware changes' isn't listed in the sub-menu, click on the computer name in the right pane and then repeat this step).

Contact our technical support department if you are still experiencing problems with serial COM port assignments.

Sealevel SeaI/O and SeaDAC devices are fully compatible with other Modbus compliant devices, PLCs and applications.  Many third party software applications and PLCs support interfacing digital I/O devices via the Modbus protocol. Sealevel devices with USB, RS-232, or RS-485 interfaces use the Modbus RTU protocol.  Sealevel devices with Ethernet or Wireless interfaces use the Modbus TCP protocol. Detailed information is included in the documentation installed with the Sealevel SeaMAX software.

Modbus information is available at www.modbus.org.

Depending on your application, Sealevel digital I/O products with either optically isolated inputs or TTL level signaling can be used.

Sealevel products with TTL inputs require tight coupling and will work for simple applications where there is a short distance between the input and output modules. TTL signals require voltages of 5 VDC.

Sealevel digital I/O devices with optically isolated inputs offer increased flexibly over TTL level inputs. The optically isolated inputs can interface over greater distances than possible with TTL signals. Optically isolated inputs are compatible with higher voltages (typically 5-30 VDC) and offer protection from ground loops. Each optically isolated input has an inline current limiting resistor and is non-polarized, so they can be wired without regard to the polarity.

Many third-party software packages (and PLCs) include support for the open and well-documented Modbus protocol. Sealevel SeaI/O modules use the Modbus protocol for communication and control. SeaI/O modules with USB, RS-232, or RS-485 interfaces use the Modbus RTU protocol. Ethernet and wireless SeaI/O modules use the Modbus TCP protocol. More information is included in Sealevel SeaMAX library documentation.

The Modbus protocol is documented at www.modbus.org.

R91001-SBC user manual in PDF format.

SeaIO is the classic software driver that supports our PCI Express, PCI, PC/104, ISA, and classic USB digital I/O devices. SeaMAX is the driver for our latest digital I/O data acquisition products, including SeaI/O modules, SeaDAC modules, and SeaDAC Lite modules.

Most of our bus based adapters, including PCI Express, PCI, PCMCIA, PC/104 and ISA, can be used. The adapter must have a 16C950 UART installed and support the Ring Indicator (RI) signal. The 16C950 UART is necessary to allow the SeaCOM driver to put the adapter into isochronous mode. Ring Indicator accepts the external clock signal which is required to operate in isochronous mode.

Order the serial adapter with an “-SN” suffix, which designates the 16C950 UART. Refer to the pin out diagram of the appropriate product manual for the presence of the Ring Indicator signal.

The HUB7i QuickStart Guide in PDF format.

The HUB7M QuickStart Guide in PDF format.

The HUB7P QuickStart Guide in PDF format.

The SeaI/O 463 Ribbon Cable QuickStart Guide in PDF format.

The TB34 DB9-to-5 Screw Terminal Block Adapter datasheet in PDF format.

The R5220 Relio Industrial Computer datasheet in PDF format.

The Relio R9 RISC Embedded Computing datasheet in PDF format.

The SBC-R9 RISC Embedded Computing datasheet in PDF format.

The 2009 R9 Embedded I/O Server product mailer in PDF format.

The ACC-188 (9065) Synchronous Serial Radio Adapters for Tactical Radio Communications product brochure in PDF format.

Click on the link to view the product pages for the Synchronous Serial Radio Adapters for USB and PCMCIA interfaces.

The Relio™ Embedded I/O Servers product brochure in PDF format.