GOOSE communication between the CI 868 and vamp 255 relay
If IED is sending GOOSE this is already a good sign. We shall analyze then what the CI868 is expecting to receive.
Could you please add to your comments the following screenshots:
1. Wireshark, showing details for sent GOOSE message: GCB name; GCBRev; DataSet size; Type of variables inside; MAC Address; APPID
2. CCFView on Control Builder, showing what the CI868 is expecting to read: GCB name; GCBRev; DataSet size; Type of variables inside; APPID
3. "Virtual IO board" created under CI868, where the variable is supposed to be read.
Then we can analize it better.
I am the Global Product Manager for Electrical Integration in 800xA group, so I am glad to help you to take the most out of our products!
I made some comments on your attached file, and reattached it. Please take a look.
But one thing I could see already is that the DataSet sizes are different, comparing what Vamp IED sends and what CI868 expects to read. If you see on Wireshark, DataSet has only 3 boolean variables inside; while CI868 expects to read a 6-variable DataSet (on CCF view). This is probably due to the ".q" attributes for each boolean variable that you forgot to add on the DataSet at Vamp configuration, but I can't be sure. That's why I asked some more screenshots from you.
Take a look and let me know.
I am Ramesh Maradana from ABB India PA-IS,working on Electrical Integration with System 800xA
This we are testing for one of new project.
As you correctly said about "q"attribute, we also suspected the same and checked to add "q" attribute from VAMP 255 relay. But option is not available in GCB data set, we can only select stVal attribute. So we deleted "q" attribute in dataset then tried once,still reasult is same.
So request you to advice accordingly..
Please let us know for any further detials if required.
Thanks & Regards
Good to know i am receiving support from the right person.
As you have rightly observed there is a variation in the dataset sizes and that is because of the quality attribute. The Vamp tool doesnot suppport inclusion of the .q attribute in the dataset (screen shot attached). Correct me if I am wrong, I understand the CI868 requires the .q attribute in the dataset it is subscribing, hence, I have included the .q attribute. Removing this .q attribute in our SCD also doesnot bring any significant change.
Unfortunately not all IEDs are fully-compliant with the standard, even if they pass on the KEMA test. This is just one example of the things we saw in our previous projects. Really sad! But anyway...
We usually recommend that you should include the .q on the DataSets sent to the CI868, but I don't know what happens if you just include the .stVal. Could you please try to do that, and reimport the CID file on CCT, generate a new SCD file, and then reimport it on Control Builder?
After doing so, take new screenshots of the Wireshark, Control Builder and send it to me.
No VLAN configuration has been made. I can confirm that the APP ID has been correctly configured on both sides. The screen shots and SCD has been attached.
I need to add that the goose communication from the CI to Vamp is happening.
We also tried performing a goose communication from the Vamp to a REF 615 we have here.
We observed that the received messages count of the GSEGGIO seen in the monitoring section of the REF 615 is incrementing, but the received goose message is not causing the change it is supposed to cause i.e. changing the value of a binary output to which it is connected. I hope this observation does help
X. Nishanth Mathew
Last things that came to my mind:
1. I saw that MAC Address to messages is the same for both, but APPID are different. Try to change configuration in a way that MAC Address and APPID have a unique correlation and are unique in the system. Ex:
MAC 01:0C:CD:01:00:01 - APPID 0x0001
MAC 01:0C:CD:01:00:03 - APPID 0x0003
2. Are you using SV5.1 FP4? If not, please map the logical nodes from the IED to a bay on Substation Section (on CCT).
3. Just for testing, add a VLAN configuration to all GOOSE messages and switch ports (like VLAN 2). Check if GOOSE from CI868 to IED continues to work, and see if the other way works.
If none of these works, I suggest you to contact L3 SupportLine; they will take a closer look to your case. But as not even with REF615 works, I assume something is wrong with the IED (maybe the lack of .q on the DataSet).
I am sorry I cannot be more helpful.