While the JACE has the ability to route MS/TP traffic over one of its serial ports, handling the overhead of the BACnet MS/TP token passing protocol burdens the JACE's CPU. This results in increased CPU usage that could be used for other functions and calls for the potential need to change to a higher-powered JACE.
The JACE CPU usage can be decreased by offloading the MS/TP token passing to external BACnet MS/TP to BACnet/IP routers. This is especially important if you require the JACE to be connected to multiple MS/TP networks. Both our BASrouter and BASrouterLX provide the solution. The units offer stand-alone routing between BACnet networks such as BACnet/IP, BACnet Ethernet, and BACnet MS/TP - allowing the system integrator to mix BACnet network technologies within a single BACnet internetwork. Learn more about our BASrouters.
Although the JACE has the ability to communicate Modbus RTU over one of its serial ports, Modbus points cannot be discovered like BACnet points requiring manual configuration of each Modbus register. By using external Modbus RTU to BACnet gateways, with pre-defined Modbus device profiles, configuration of Modbus registers is just as quick as configuring BACnet points allowing to greatly reduce the time to configure Modbus devices in the field.
Our BASgatewayLX provides a 10/100 Mbps Modbus TCP or BACnet/IP Ethernet port and an opto-isolated Modbus EIA-485 serial port for Modbus RTU or Modbus ASCII devices. Up to 30 Modbus serial devices (represented by up to 1000 polled points) can share the single Modbus port on the BASgatewayLX. The virtual routing feature in the BASgatewayLX allows each connected Modbus device to appear as an individual BACnet compliant device which can save configuration time if using multiple identical Modbus devices. Learn more about the BASgatewayLX.