BACnet Connector Troubleshooting

What is your current issue? 1. My connector is down 2. I get a “Socket Timeout” error 3. I get an “Unknown object” error 4. My point is not changing value 5. COV of current value VS history

What is your current issue? 1. My connector is down

1. My Connector is Down The down status actually states that your connector is in Idle mode. The reason why a connector is in Idle mode is because there is no watch active on it To have a watch active: there has to be a point in your database that is connected to your idle connector, and you need to view it(only when a user is looking at a point the watch gets activated) Or there has to be at least a point that is collecting history(there is always a watch active when collecting history)

What is your current issue? 2. I get a “Socket Timeout” error

1.Verify that you can ping the ip you are trying to reach ( 2.If step 1 worked, verify that your firewall allows access for the BACnet port(the default one is 47808) 3.If step 1 & 2 worked, verify that your URL is correct ( RL+correct+format ) RL+correct+format

What is your current issue? 3. I get an “Unknown object” error

At the point level At the connector level 1.Use the Debug Info Tool at the connector level to confirm the error: Manually correct the device instance number using the edit option at the connector level 1.This error will appear when the point instance number has been changed at the device level and hasn’t been updated in the FIN Stack data base. The user can check this out using the Debug tool: ointPropertySheet-PointDebugInfo ointPropertySheet-PointDebugInfo 2.Manually correct the bacnetCur/bacnetWrite tags to the proper values

What is your current issue? 4. My point is not changing value

First please make sure you follow cases 1,2&3 If all cases work fine then the point debug info needs to be checked and investigated

What is your current issue? 5. COV of current value VS history

COV of current value is set via the tunning policy at the point level( Edit+Tuning+Policy#Create-EditTuningPolicy- Addingtuningpolicytopoints) Edit+Tuning+Policy#Create-EditTuningPolicy- Addingtuningpolicytopoints COV for history collection is set in the DB builder UI ( ty+Sheet#PointPropertySheet-HasHistory ) ty+Sheet#PointPropertySheet-HasHistory