Thanks for the reply.
While attempting to activate both Modbus (Sub @ 19.2K with HUM-N-LCD) and BACnet (Main @76.8K with Tstat8’s) on the T3-Nano both became unstable. The T3-Nano operation was stable with only the Main bus configured as either Modbus or Bacnet, which is fine for my current application using one (1) BACnet MS/TP bus for multiple BACnet Devices.
My intent was to use the T3-Nano as a BACnet IP to BACnet MS/TP Router, which is currently working in early trials but the T3-Nano does not have BACnet Explorer (YABE) discovery of several typical “BACnet Router” Variables (BASrouter);
yes… Device Name: (BacnetRouter)
no… Device Instance: ()
no… Device Description: ()
no… Ethernet Network: (0 - 65534)
no… BACnet/IP UDP Port 1: (BACO / 47808)
no… BACnet/IP Network 1: (0 - 65534)
no… IP Address: (0.0.0.0 - 255.255.255.254)
no… IP Subnet: (0.0.0.0 - 255.255.255.254)
no… IP Gateway: (0.0.0.0 - 255.255.255.254)
no… MS/TP MAC: (0 - 127)
no… MS/TP Netwok: (1 - 65534)
yes… Max Masters: (1 - 127)
no… Mac info Frames: (1 - 100)
no… MS/TP Baudrate: (9.6K - 115.2K)
no… MS/TP Tolerance: (?)
MAC Address:
Using YABE most of these variables (IP and or MS/TP) are accessible from the Tstat8 and the T3-8o. These variables may be accessible from the T3-XB’s, but I had not been able to establish uninterrupted communications to my T3-BB which has been returned for replacement. Without access the “Network Variables” cannot currently be easily mapped to another front-end software e.g. Mango Automation. Are there any plans to make these variable accessible from a BACnet Explorer? Thanks.
BTW, the T3-8o works “seamlessly” using the Mango Automation Software (HTML BMS Front-end), All the TStat8 points are discovered / visible / can be mapped , but the operation of the T3-Nano has been intermittent (only connected approx. 85% of the time).