Unreliable Peer-to-Peer points in CCT (Issue Solved)

This is an advanced Blog and I am assuming that you already know how to setup points in CCT for peer-to-peer.

Have you ever seen out of nowhere one or more of your Metasys peer-to-peer points going unreliable?

I’ve seen this when my controller loses power and then restarts. Then you Upload your CCT application and go into Commissioning to see what’s going on and your point is unreliable. In my case it, my point is a Network Input:

When you double click on your unreliable point the following window opens:

Notice that your Object Reliability shows Source Unavailable, your object Status shows Unreliable, and under Peer to Peer, an Error Status of Remote object not yet found.

You double check your Device Instance Number (or BACnet ID) and Object Identifier type and address and it all looks good. So now you don’t know what to do.

The Quick Fix

For some reason your point gets stuck in a state that it can’t read the remote object, and you have to kinda re-trigger the point address. So what I do I go to Edit and down to my Object Identifier:

I then change my Object Identifier to any other number, and click Apply. In my case I decided to change it from 17666 to 27666:

As soon as the changes take effect, you will see a different Error Status. In my case, since I put a number of an object that does not exist in my CCT application, I got Unknown object as my error:

The magic

OK, so the magic happens when you go back to Edit, and return the Object Identifier back to it’s original value, and Apply changes:

Your point will go back Reliable, Status back to Normal, Current Value will show the actual value, and the Error Status will show Ok.

Hope you find this helpful. I still have not figured what exactly causes and how to fix it permanently, but at least here is a temporary fix. Thanks!