T3 Nano as Modbus Rtu to Modbus TCP/IP and BACnet mstp to BACnet IP

[maurice]

This forum post shows the general idea for all the above scenarios where you will use the data on board the controller for programming, floor plans, trend logging and so on.

Network Programming Overview

Here is an overview of the typical scenarios for referring to remote Bacnet and Modbus devices in the T3000 programming environment. Be sure to update FIRST your T3000 front end, and then also update the T3 controller firmware as some features are recent. [NetworkProgramming4] Two T3 controllers on the LAN For the two T3 controllers on the Ethernet lan at tabs1 and 2, we use programming lines 1 and 2 to read data from another controller. VAR1 = 2IN1 where 2 refers to any other panel ID on th…

There are a few things we need to document better which is the ‘transparent’ networking functions.

For Modbus RTU to Modbus IP gateway type applications, the T3 controllers can transparently pass traffic without any programming at all.

For Bacnet MSTP to IP traffic this can also happen transparently without any programming at all as well. You can refer to the instance number and Bacnet object of any device in the network, Bacnet will automatically handle the routing to/from IP and RS485 if applicable.

The T3 Nano has all the communications features of the larger T3-BB series controllers so any routing or gateway features mentioned in our documentation applies to the Nano just as much as the other programmable controllers.