Hi,

The rule is: If it is a BACNet device then we can communicate with.

If you want to double check you must ask your customer to provide the PICS document or, if he has not this document, the exact device's model.

Nico

Hi,

If your customer talks about the addendum 135-2016be, it is not implemented in PcVue.
A addendum is an "extension" of the standard, not mandatory to implement.

This addendum talks about lighting BIBBS and device profile. So it is very specific with new objects and services.

more info : http://www.bacnet.org/Addenda/Add-135-2016be-ppr2-draft-12_chair_approved.pdf

Hope it helps.

Brice

HI,
Thanks Brice for this document. Actually I didn't know there was specific Profiles for Lightning.

Now, I would like to add more details because this answer: "...addendum 135-2016be, it is not implemented in PcVue" is too vague.

So, Alex, I would like to clarify a bit. If you need more details please Skype me.

What you have to understand is:
1. As I said, if the device is a Bacnet device then PcVue will be able to communicate with. That's the most important point.

2. Remember that PcVue is BAWS certified. What that means?
That means Pcvue is able to manage some specific BACNet objects and Services.
I give you an example: The Schedule object
This object has several properties and PcVue is able to read and write these properties but displaying these properties to an operator in a friendly way can be very complex. For example the property weekly-schedule represents the planning of a standard week. It is a long string formatted in XML. Showing this string as the planning of the week to an operator won't be useful isn't?
So, we have created 2 tools to display and interact with a Schedule object: The PcVue Helper (user is the project designer) and the WebScheduler (user is the operator).

Now, talking about the addendum mentioned by Brice, there are some BACNet objects that are specific to lightning market. For example Lighting Output object. Like any BACNet object it has a set of properties that PcVue can Read or Write.
But in case one of these properties is complex we wont have any specific tools to display or interact with.

Here is the point said by Brice when he said the "Addendum 135-2016be is not implemented."
It doesn't mean that Pcvue is not compliant with this device.

Finally, before giving a definitive answer to your customer, you must ask him the PICS of his device.
Reading this document will help us to determine if this device implements specific objects described in this addendum.

More clear I hope!

Nico

Thanks.

They are use 2012, we will test it in the shanghai office with their light controller.

Great!

It should be good if you give a feedback about the tests results for our information

Nico

In fact,they have use 2016, so we just can find the IO, but can't display and control. Waiting their PICS files.

Hi,

Did they make the tests by themselves or Mark helped them?
Even if they are using 2016 standard PcVue must be able to at least read the data.

Nico

Mark make the test with them.

I made a test together with the customer.

PcVue can browser all objects and properties of the device, and the object we tested is non-standard object in the mapping dialog tree.I think it is,just as Brice said, very specific objects and services for lighting devices. That's why PcVue treats it as non-standard object.

In the mapping dialog, PcVue regards set-value(something like that) property of the Output command object as a register. I set this value directly but failed. of course, after mapping a variable to this property read and write also failed. The most important thing is: the customer said this property is an Enum type, but PcVue send the command by sending a float value. They said they used BACnet for lighting of 2016 PICS.

So I think Brice's reply can answer this quesion.

BRs,
Mark