Reporting behaviour in version 1.1.1 about libiec61850 HOT 9 CLOSED

I forgot. Platform : Windows 7 64 bit , C API in Visual Studio 2013 32bit

from libiec61850.

I suspect that the MmsValue_update function fails for some reason. There has been a change in this commit 15ec6c7 . Maybe you can revert this commit and see if it works.

from libiec61850.

Yes, this is the problem.

Now it's working fine, I'm not losing anything from this SIPROTEC5 relay.
If you are interested I can sniff with wireshark the reporting packages that always fails and the packages that always works to check differences ..

Thanks a lot.

from libiec61850.

It would be great if you could sniff and post the packages that fails.

from libiec61850.

Sure!
I'm working on SIPROTEC5 7SA87
This is a reporting message of the RCB containing an electrical switch position.

In this case I've got an electrical switch open (reporting correctly recognize):

Then I send a command of close, so the switch it's moving.. (reporting correctly recognize):

Then it's closed.. (reporting correctly recognize):

Then I cause an opening by trip (reporting Not recognize):

I see the message it's quite different in this last case...

Hope I've been helpful.

from libiec61850.

Hello,
to make Wireshark to dissect PDU correctly, fill:
Under Edit/Preferences/Protocols/PRES/Edit... User Context List/
and fill in the following to a new line in the table:
Context Id: 3
Syntax Name OID: 1.0.9506.2.3

You can see correctly parsed 61850 packets then.
And, anyway, the best way is to extract packets and send in pcap format instead of screenshots.

br Pavel

from libiec61850.

@Morand84 Thanks for posting the information.

But as Pavel said, seeing only the bits makes it very hard to understand what is happening.

It would be great of you could post the pcap file.

Thanks,
Michael

from libiec61850.

Thanks, now it parse.
Here it is the pcap file.
libiec61850_111_reporting_probl.zip

Thanks a lot.

from libiec61850.

Thanks.
I guess the reason was the change of the size of the octet-string ("owner" I think). I updated the code to accept the different size octet string.

from libiec61850.