Hello everyone!
:whistle: I'm moving my first steps inside the wonderful world of IEC61850 so please be clement... :dry:
As in BACnet we have a magic option for switching to polling mode if COV/UCOV is unavailable at tag level... is there something similar in IEC61850 for automatically switch from URCB/BRCB to polling mode (DataGroup) if xRCB is unavailable for a particular tag?
As you know we are unable to import 61850 descriptive files (xCD) in PcVue, and unfortunately we don't have all real devices in laboratory to test online mapping for all tags. Global parameter can be a workaround but not a real solution, since it can require a lot of time to place them correctly if late, in commissioning phase, we discover some
Any idea? Do I miss something?
Thanks a lot!! 🙂
Hello,
The purpose of the data group is to poll data without any configuration in the device and in particular xRCB.
Now please, could you give us the exact PcVue version ?
Could you describe the communication problem you meet ?
thanks
Ciao Brice! Thanks for your reply!
We are using the latest 11.2.
We don't have a real communication problem, we are only wondering if there's already in IEC61850 a magic option to switch automatically in polling mode if the configured address is not available in xRCB - like in BACnet if COV/UCOV is not available.
The reason is that we are developing the application without real devices (and without the definitive mapping), and we want to avoid the needs to modify the project onsite if some tags are not available inside xRCB in definitive devices. In other words, we're configuring the big part of the variables inside BCRB, but we are not 100% sure that all of these tags will be available inside BRCB in definitive devices - to avoid manual mapping modification to Datagroup.
Hi Filippo
I am afraid this option is not available for this protocol.
But I am surprised by one point: Your customer is not able providing the .cid files? Normally, the company that have configured the IEDs must provide them...
Nico
Hi all,
The true answer to the question in the spirit of 61850 is to support dynamic datasets - The service allowing a 61850 client to change the content of a dataset so that it fits its data acquisition needs.
Your proposal Filippo would be a smart move for better handling with devices not supporting dynamic datasets. But to follow a pragmatic rule, it would be better for us to support what 61850 standardizes (dynamic dataset) before the plan B for devices not supporting it.
Regards


