-
timeSynchronizationRecipients:
Hello,
We have a distech system and have the following error in the application director;
WARNING [12:08:58 12-Jan-21 CST][bacnet] utcTimeSynchronizationRecipients: writeAsn: listElem is null or type mismatch!
Has anyone ever seen this error before. All the EC-BOS's are online and nothing seems to be out of normal.
Thanks
-
-
Looks like its just a BACnet time sync failing.
BacnetNetwork - local device - UTC time sync recipients. Someone in there isn't happy.
-
Post Likes - 1 Likes, 0 Dislikes
-
which one
Originally Posted by
orion242
Looks like its just a BACnet time sync failing.
BacnetNetwork - local device - UTC time sync recipients. Someone in there isn't happy.
Do you know if the server has log files which at least can tell me the IP address, or how to get information on the error it's creating.
Thanks
-
Might be able to crank up the logging on the Bacnet driver and get more info. Normally looking at the list and the controllers internal clocks will point out the problem pretty quick. Guessing you have a million entries in there which would be a bit more of a hassle.
-
Lost
Originally Posted by
orion242
Might be able to crank up the logging on the Bacnet driver and get more info. Normally looking at the list and the controllers internal clocks will point out the problem pretty quick. Guessing you have a million entries in there which would be a bit more of a hassle.
We have over 15 EC-BOS connected with at least 20 MSTP devices. The application director only says -->
[bacnet] timeSynchronizationRecipients: writeAsn: listElem is null or type mismatch!
[bacnet] utcTimeSynchronizationRecipients: writeAsn: listElem is null or type mismatch!
Which doesn't tell me anything. I've checked the TimeSyncService on each bos and they are reporting OK. Checked the Time Synchronization Recipients and they are setup for address correctly.
So how do I tell what BACnet device it's trying reach which is failing.
There's got to be a method to see what writeAsn: listElem is coming from.
-
Compare your list of time sync devices with the real world inventory?
Set the station time ahead 10 minutes, trigger a time sync and check time on controllers and see who didn't change?
Also I thought time sync was broadcast and not specific? Something not even on your list might be kicking that back.
-
Originally Posted by
MaxBurn
Compare your list of time sync devices with the real world inventory?
Set the station time ahead 10 minutes, trigger a time sync and check time on controllers and see who didn't change?
Also I thought time sync was broadcast and not specific? Something not even on your list might be kicking that back.
thanks for the suggestion
I changed our Windows Server and in the server platform it changes to match the time. I then looked at each bos platform and from the TimeSyncService selected action - sync. This changed the local time to match the windows server time. I then did a spot check on one device to see if's local time change which it did.
With that, we must have a third party device that which is kicking this back. Would this be something which is on the MSTP bus or could it be from another manufacture which is reading in various objects into their system using BACnet/IP.
-
Originally Posted by
MaxBurn
Also I thought time sync was broadcast and not specific? Something not even on your list might be kicking that back.
I am not sure about tridium, but I believe in general BACnet time sync can be set to broadcast and/or only to specific recipients.
-
You can do it either way. Least what I see, if someone has bothered to set this up they almost always plug in the individual device instances. Quite the PITA for more than a handful of devices. Can't be bothered with reading the manual I guess.
-
Originally Posted by
orion242
You can do it either way. Least what I see, if someone has bothered to set this up they almost always plug in the individual device instances. Quite the PITA for more than a handful of devices. Can't be bothered with reading the manual I guess.
Here's one thing which is odd
Under the Station Server --> Services and TimeSyncService when I view the status it says OK. But when I view the Services which list all of them it says it's in fault.
-
WARNING [12:08:58 12-Jan-21 CST][bacnet] utcTimeSynchronizationRecipients: writeAsn: listElem is null or type mismatch!
That would point me to the BACnet driver and its time sync.
What your looking at under services looks like the old school AX time sync for Jaces. If that's what it is, that hasn't been supported for a long time now.