I have a Duct Mount Airlab device, DUCTAIR-CO2-TVOC. It is powered on and I’m connected to it via a BACnet USB to RS485 converter. I am unable to to discover the device using the T3000 software. Looking through the forum I see that I may need to use the EspTouch software on an Android device to configure the device’s IP and connect that way, however, I don’t believe I obtained the sensor with the WiFi option.
I was under the impression that I would be able to connect a BACnet converter and discover the device and it’s BACnet points out of the box. Am I missing something?
‘ESP Touch’ is from the early days, used to provision Wifi connections in the initial setup but not relevant these days. Windows deprecated adhoc wifi connections so it wasn’t so helpful without a lot of steps.
The best bet is to get connected up is start off with RS485, use a simple USB to RS485 converter. Hit the magnifying glass icon and T3000 should discover the device no matter the protocol or the baud rate set. The parity is not explored though, if you have adjusted it the scan will not see the device.
Once T3000 sees the device you can set it to Bacnet or modbus on any of the RS485 ports. With ethernet you dont have to specify the protocol.
Thank you for your assistance. I was able to properly scan with the USB to RS485 converter and it recognized the COM4 port and successfully scanned and located the device. That allowed me to enable BACnet communication and I scanned the device within my BMS station and found the device as well as the BACnet points. I think there was an issue with my computer recognizing the USB previously or something. We are in business.
Great. One thing to note is that the Bacnet objects may not show up if the range is st to somethign other than the default range of unused. And a final note, the discovery of Bacnet objects may have to be re-initalized after making changes in one environment to fully propogate to the other environment.