RemoteTRAK® RS485 I/O

What protocols does RemoteTRAK RS485 I/O support?

All RemoteTRAK RS485 I/O modules support Modbus ASCII, Modbus RTU, and SIXNET protocol. All you need to do is use the supplied SIXNET I/O Tool Kit configuration utility to set the module for the protocol that you need.

Back to Top

Can RemoteTRAK I/O be mixed on an RS485 network with other non-SIXNET devices?

Yes. You can install RemoteTRAK RS485 I/O on your existing RS485 network along with your other devices as long as you are using one of the supported protocols.

Back to Top

What is the Remote I/O Field Setup module and why do I need it?

This module is required to initially set the communication parameters of a RemoteTRAK RS485 I/O module. It is plugged in place of the I/O module and provides a standard RS232 port to connect to one of your PC's com ports. Then with the SIXNET I/O Tool Kit software you can load down the communication parameters for the RS485 port. This information gets stored in the RemoteTRAK's base. Then when you plug in the I/O module it will automatically self-configure from the information stored in the base. You then can communicate to the I/O module via RS485.

Back to Top

What if I need high-speed counting or RTDs but there is no RemoteTRAK I/O modules for these signals?

No problem. All EtherTRAK Ethernet I/O modules have a RS485 port in addition to their Ethernet port. This RS485 port has the same capabilities as on a RemoteTRAK I/O module. Therefore, you can connect EtherTRAK I/O modules along with RemoteTRAK I/O modules on the same RS485 network. The EtherTRAK I/O line includes modules that accept high-speed counter and RTD inputs. 

Back to Top

How many RS485 devices can I have on my network?

The standard RS485 guidelines typically allows 32 "full-load" devices. A RemoteTRAK I/O module is a full-load device. If you have devices that are considered 1/2-load or 1/4-load then you can have more devices on your RS485 network. For example, you can have 64 1/2-load devices or 128 1/4-load devices. If you need more than 32 full-load devices then check out the RemoteTRAK RS232 to RS485 converter (RM-232-485-4U) which provides you with 4 separate RS485 ports allowing up to 128 full-load stations. 

Back to Top

Why is SIXNET's "Process Quality" I/O better than typical PLC I/O?

There are numerous reasons. Please go to "Process Quality" I/O for details.

Back to Top

I just got my RemoteTRAK I/O. What should I do first?

First, install the SIXNET I/O Tool Kit software. Refer to the RemoteTRAK User Manual to power-up your RemoteTRAK module. Next, use the field setup module to configure your RemoteTRAK. Refer to the getting started help in the SIXNET I/O Tool Kit for details. Then follow the prescribed steps to configure and use your RemoteTRAK.

Back to Top

Why can't I communicate to the field setup module plugged into my RemoteTRAK base?

First, make sure that the serial number you entered into the SIXNET I/O Tool Kit software exactly matches the one on your RemoteTRAK module's base. Then make sure you are using a ST-CABLE-PF (supplied with the setup module) or an exact equivalent. Refer to the RemoteTRAK User Manual for a pin-out diagram. An off-the-shelf "null modem" cable may not work. Next check the Device menu settings in the SIXNET I/O Tool Kit. Make sure you have selected to "Use the settings for the field setup module". When you try to communicate watch the LEDs on the setup module. If you see no activity then you may have the wrong or a bad cable, or you have selected the wrong com port on your PC. If you see only the RD LED flash then it's probably your Device menu settings. Finally, try cycling power to your module and base.

Back to Top

Why can't I communicate with my RemoteTRAK from my PC using a RS485 card or RS232 to RS485 converter?

Setting up RS485 communications can sometimes be very tricky. Here are some of the things to watch out for. First, make sure the com parameters (protocol, baud rate, data bits, parity, stop bits, flow control, etc.) of the software in your PC match the settings that you loaded (via the field setup module) to your RemoteTRAK I/O modules. 

Next, refer to the RemoteTRAK User Manual and the documentation for your RS458 card/converter and make sure that the proper biasing and termination are in place. Also, it is required that the signal ground (in addition to the RS485 + and -) be connected for RemoteTRAK to communicate properly. Therefore, the so-called "2-wire" connection actually requires three wires. 

For twisted pair cable,  the shield wire is commonly used for the signal ground. Another common problem are the RS485 lead and lag times. Many RS485 PC cards and converters do not automatically handle lead and lag time delays that are required for "2-wire" RS485 communications. If this is the case then your Windows software would need to control the card/converter for the proper delays to occur. It's quite possible that your software does not do this. We highly recommended that you use SIXNET's RM-232-485-4 RS485 to RS232 converter. It eliminates most of the problems encountered when connecting a RS485 network to your PC. 

Unlike other cards/converters that have a plethora of dip switches and jumpers, the RM-232-485-4 has no user settings at all. It automatically handles the lead and lag times, and eliminates the need for biasing if connected to just SIXNET RS485 devices. 

Finally, if all else fails try swapping the + and - connections on one end of your cable. We have seen it where the + and - designations on some cards/converters are opposite to RemoteTRAKs. So instead of the normal + to + and - to - connections you may need a + to - and - to + connection.

Back to Top

Why can't I communicate to my RemoteTRAK from a master RS485 device such as a PLC?

First, make sure the com parameters (protocol, baud rate, data bits, parity, stop bits, flow control, lead time, lag time, etc.) of the RS485 port on your PLC or other master device match the settings that you loaded (via the field setup module) to your RemoteTRAK I/O modules. Next, refer to the RemoteTRAK User Manual and the documentation for your RS458 master device and make sure that the proper biasing and termination are in place. Also, it is required that the signal ground (in addition to the RS485 + and -) be connected for RemoteTRAK to communicate properly. Therefore, the so-called "2-wire" connection actually requires three wires. For twisted pair cable,  the shield wire is commonly used for the signal ground. Finally, if all else fails try swapping the + and - connections on one end of your cable. We have seen it where the + and - designations on some devices are opposite to RemoteTRAKs. So instead of the normal + to + and - to - connections you may need a + to - and - to + connection.

Back to Top

Why can't I communicate to my RemoteTRAK connected off of an EtherTRAK module or gateway?

First, make sure the RS485 port parameters (passthru protocol, baud rate, data bits, parity, stop bits, flow control, lead time, lag time, etc.) on the EtherTRAK I/O module are configured to match those of your RemoteTRAK I/O modules. Make sure you have the proper RS485 termination. Simply terminate each end of your RS485 network. See the RemoteTRAK User Manual for details. Note: No RS485 biasing is required when connecting just SIXNET RS485 devices. Also, make sure the RS485 signal ground is connected between the EtherTRAK and RemoteTRAK. If you are using a Modbus/TCP driver then make sure you have specified the correct IP address of the EtherTRAK, station number of the RemoteTRAK, port 502 (for Modbus), and the appropriate Modbus I/O addresses.

Back to Top