BACnet IP server communication failure

[KlaudiaKl]

Hello!
I've got the issue with communicating Enterprise Server or Automation Server with BACnet IP server gateway (Modbus to BACnet IP Intesis: https://www.intesis.com/products/protocol-translator/modbus-gateways/modbus-rtu-tcp-bac-ibox-bac-mbm). I see it in the device discovery tab as an "Unconfigured Devices" (photo) and I can move the device to the system tree and see the properties, the name of device, the addres etc. but I can't see any variables and I cannot add them manually. We tested the gateway and it communicated with the room unit without problems - we added the registers, we tested read/write functions and it worked (we could change the setpoints, operation mode etc.). The only option I considered was that the gateway have the password and we can't delete it from the device. We entered that password in Workstation Building Operation (version 1.9) but the error "Reject unrecognized service" appeared. Is there other option to add the device and collect the variables from it?



Klaudia

 

[markb_ci3]

Devices that come in as "Unconfigured" usually have a problem with compliance to the BACnet standard.

Items that must be unique:

BACnet Address (applies to MSTP)

BACnet Name (workarounds to this are available)

BACnet Device Instance

That last one is a deal breaker. BACnet communications won't work if multiple devices are responding to the same ID.

There can also be problems with how the device is responding to the "WhoIs" request from the AS-P.

Insert a managed switch with a mirrored port in line with the device and do a WireShark capture to see the packets.

A "Who-Is" must be followed by an "I-am" by the device and it will provide the device details to the AS-P such as manufacturer, and the read/write properties it supports. If this communication does not happen properly, the AS-P won't know what to do with the device.

Armed with a BACnet capture, you should engage the manufacturer to see if they can help.

Good luck!

Mark

[KlaudiaKl]

Hello!
Thank you so much for your reply. We found out that it was the problem with BACnet Device Instance number and with the connection to the internal network. Now we see the device as configured in the Workstation and we can read the values of the units registers. But we got another problem now - we can read the values of the input registers but we can't write data to the outputs - we can't control the unit. When we put for example value of the setpoint of temperature we got the validation error. Maybe it is a problem that the device have the password that can't be delete? Do you got any ideas what we could do to make it work well?

Best Regards,
Klaudia