6/30/2010 7:24 PM | |
Joined: 9/27/2006 Last visit: 9/7/2025 Posts: 12399 Rating:
|
Hello Konstantin; I have very little experience in IEC protocols and Sicam, but I have worked with Sepam 40 (with Modbus RTU connections). Unsigned32bit is not at all the same as FloatingPoint 32-bit. In S7 terms, an Unsigned 32-bit value would be considered a DWORD, whereas a 32-bit Floating Point value would be a REAL datatype. So it would seem that you are not choosing the correct info type. Trying to read a DWORD as A REAL will give you very strange values! I would recommend you talk to our resident SICAM specialist, Mike J, as he would be the best reference on this subject. Hope this helps, Daniel Chartier |
7/1/2010 6:07 AM | |
Posts: 6 Rating:
|
Thank you Daniel, The problem, that is no possibility to chose correct telegram type in Sicam, there are only 32-bit Floating Point and Unsigned-16bit values types are available. And as I understood, it is not possible to change value type in Sepam. Ok, I will try to contact Mike. |
7/2/2010 5:38 AM | |
Posts: 6 Rating:
|
Dear Mike, Thank you for your efforts. There are something about interoperability in this manual.http://www.pq-ride.co.kr/dataroom/files/Sepam%20IEC60870.pdf. You are right, measurements’ coming in ASDU-9 (page 28 of Sepam manual). Page 39 make it clear that type of measured values from Sepam – 32-bit NoneSigned values, all except P,Q,S – are signed. So my question is – how can I read this values in SICAM? Thank you in advance. |
7/3/2010 10:24 AM | |
Posts: 6 Rating:
|
Dear Mike, thanks a lot! You are right, I do not pay attention that 32-NS telegrams are in "Tripping context files". I was thinking they are a regular continues values (analog), witch I permanently need in my system.Ok what can I do to take a values from ASDU-9?
Can you please tell me where I’m wrong? Attachmentattachments.zip (158 Downloads) |
Last edited by: Konstantin Larionov at: 7/3/2010 10:33 AMLast edited by: Konstantin Larionov at: 7/3/2010 10:31 AM |
|
Follow us on