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.
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.
Yes to all of the above. There are no practical limitations to the number of points you can route from one network to the other. All routing and protocol scenarios are supported. Most routing is transparent but some such as translating from Modbus to Bacnet or vice versa you’ll need a little program to poll and set a VAR on the controller. If you run into something we didnt cover just send us a note and we’ll get it on the todo list.