Since these are all T3 controllers why not use the ‘instrinsic’ method. If these are panel 1, 2 and 3, then all you need to do is refer to the external points as 1IN1, 2IN1 and 3IN1 for example. This notation can be used in any of the controllers and the network points will automatically be taken care of. This is simpler than dealing with the bacnet instance in my opinion. Also if you were to give the inputs labels like 101TMP, 202TEMP and 303TEMP, then these names will automatically appear in your programs, floorplans, trend logs and so on.
That said, Chelsea will check into why the Bacnet objects are not updating. Set up a trend log on the remote points and you can see how often this is happening.
Can you try to update to rev65.0, I uploaded it today.
As shown in the picture sent before, the program is using direct reference to the points as Maurice suggested. It was not working either way.
After updating to rev65,0 reading network points is now good,!
It will be appreciated, If a simple explanation could be provided on what the problem was.
Thanks very much!
One more observation …
In the Network Points table shown above the Device ID and the Point Number are not shown.
There are many kinds of points in the Network points table, and the Device ID is available to other points.
I have modified the point number problem and will release the new code as soon as possible. Now the value of point number in the table is one less than the actual value。
