×

Did you know that your internet is out of date?

Your browser is out of date, and may not be compatible with our website.

Just click on the icons to download a compatible browser. 

Close this window

By closing this window you acknowledge that your experience on this website may be degraded. 

/content/tridium/us/en/search.html
Outage Notification: On Saturday, June 5,12:30-2:30 p.m. EDT (6:30 to 8:30 p.m. UDT), this website will undergo planned maintenance. Thank you for your patience.

Virtual Serial Port

Gives a Niagara station serial ports it does not physically have. Each virtual port looks like an ordinary COM port to Niagara, but the data travels over the network to a serial-to-Ethernet gateway that turns it back into RS-485 or RS-232 at the equipment. Serial drivers use it without modification, simply pointing at the port name. It answers three problems: a JACE short of ports, devices too far away for cable, and a Supervisor with no serial port at all.
CONTACT SELLER

Overview

It implements the standard Niagara serial port interface, so drivers address it exactly as they address COM1, whether they are ours, Tridium's, or a third party's. Tested with Modbus RTU, Siemens Apogee P1, and Johnson Controls N2, and most serial drivers work unchanged. Any gateway offering a raw TCP server works, among them Moxa NPort, Lantronix XPort, Digi Connect, Perle IOLAN, Advantech EKI, Atop SE59xx, USR-TCP232, and Schneider EGX. RS-232, RS-422, and RS-485 are all fine, since the electrical side is the gateway's job, and baud rate and parity are set there rather than in Niagara. Ports connect on demand, show their state in the navigation tree, and re-establish themselves after a network interruption without intervention. Devices can sit anywhere the network reaches, including remote sites across a VPN. Runs on a JACE, sitting under the native serial service alongside COM1, and on a Supervisor under its own service. Licensing is perpetual, bound to the Host ID.

List of FAQs

Which serial drivers work with it? Any driver written to the standard Niagara serial port interface, which is nearly all of them. It has been tested with Modbus RTU, Siemens Apogee P1, and Johnson Controls N2, and it is not limited to our own drivers. The honest caveat is timing: a driver that depends on tight turnaround, very high baud rates, or multi-master arbitration can struggle with the latency a network adds. If you are unsure about a particular driver, ask us before you buy. Do I actually need it? Only if the serial port is missing or the cable will not reach. If your JACE has a free RS-485 port and the devices are wired to it, use that port and save the money. This exists for the cases where that is not true. Can a Supervisor talk to serial devices without a JACE? Yes, and that is one of the main uses. A Windows Supervisor or virtual machine has no serial port, so a gateway plus a virtual port lets it reach RS-485 equipment directly. Note that the Supervisor's own Tridium licence needs device and point capacity for field integration, which is a Niagara licensing matter rather than something this module controls. Can I add more serial ports to a JACE? Yes, without buying expansion hardware. Virtual ports appear under the JACE's native serial service next to COM1 and COM2 and are used the same way, so a controller that has run out of physical ports can keep growing. How far away can the serial devices be? Anywhere the IP network reaches. That covers a rooftop or car park at the end of a Wi-Fi or cellular link, a remote plant room, and several sites joined over a VPN with a gateway at each one, all without long serial cable runs or a JACE at every location. Which gateways does it work with? Any serial-to-Ethernet gateway that presents a raw TCP server, including Moxa NPort, Lantronix XPort, Digi Connect, Perle IOLAN, Advantech EKI, Atop SE59xx, USR-TCP232, and Schneider EGX.

Software Version

Niagara-powered device with software N4.8+, including JACE and Supervisor.