According to the software manual the point names (label, full label) should be unique within the system. Should this not say “unique within the controller”?
Unique within the entire building is correct. Its not enforced strictly, you can have duplicates but it can get messy when remote objects are passed around the network.
If you had two outdoor temperature sensors both named OAT and want to use them in another controller for say, free cooling sequences. It will be best if they are named OAT1 and OAT2 so the controller knows which sensor you are referring to.
1 Like
I thought remote objects used controller ID and point number for reference.
1 Like
I know a lot of folks are under the impression you can only use the panel ID and point number as you mention. But you can also use the label on a remote point as well.
I will review what we have in our documentation and make sure this is clear.
1 Like
Thanks Maurice
With only eight characters to pick from for a label, it would get difficult to keep unique names within a system that is using multiple controllers. I haven’t been using panel numbers for point sharing, only bacnet device id and point number
Jim
1 Like
Agreed on the naming, 8 chars is not much to work with. I will make a todo in the development qeue for enabling the 20 chars in progamming, graphics and trend logs. While we’re add it we may as well add an intellisense autocomplete type drop down in the editor like so:
1 Like
Maurice,
That would be a great tool!
Thank you,
Jim
1 Like