Before commenting read Forum rules
Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
Forums
Good morning,
I found a few links to this forum when I was searching for some information about Decoding of APDU frames and Smartmeter.
I'm fighting for 2 days now with my Sagemcom T210-d-r. I get out a APDU Frame at the application layer it seems. I also received now the Key and Auth Key from my provider. The problem is I don't get out useful data.
My question would be if someone can check my APDU and try to encrypt it if he get out some useful data.
FRAME:
DB085341473500009F388201F2300002DCDFDB132EB79E501DE47E524C98D9EBB7D1E88175B8D200
2FD114FC0557DC638F2C625662B3566BD205F1334E50450E06D829BA5501BD980ED08D9B462D9A0B
32093444A482A9E90C9E30055628DDB9E68B827FE3A3DC32E1698E27AD61E30B63BAB7E9B1752676
86DCC2BC6320139A1E5731A483E4CB5EBCBC3A37EC0A65B116A4F8E345F19A281A5C658584EA1D75
735F6A7A4D226E7ECCF396F4DD2561D80C07858AFF830002E65D914CD28C13630223DA17F6A59459
BEC31D69FB7EA1999D9F232ACFA7391DECC41C96D6E4D0C6FAA56B4250B6D2F0FC8A136F3D63E4E8
A50E404C7CC95A61DBABCBB420E8ECD107D058180A9B03860F8AB38EB02774EE31B0DA6E917DBD5A
C091CB972E9B07D60120CEC62AEA1F4C56251B0CF7B94AF8448B36DBD133D29E22BED03BD6AF4F3A
1A1B7D8219B4D02C5239563F1C243FA21A7D6434BD6D79E6C200091A0465BBF26F91F807BCEB1284
92CCDCCCBDCBFF22B4185C3C1CE3994F576719F0DA265EE02628EC6509488F338C9A9C1B412C1429
CF53593DC2FC7B463B2006BF3A8D7A1E72ECEA98CCC6B25ED777ADF3480B00E5FB030D236BF08BF2
E4180C170825B593654793FF7B1CCE34B9516D50E6B9CBEDF2EBA71790A55B8879D9C4C9C1823008
E597AEBA9DBC3CB0912E342EAEC27C2BBC93A0A090FD83A093477ED20CABB3
KEY:
C3DB997F8B85282D0C01FF284E376AA4
AUTH:
3E64987516665F30A23ADB894C89AB39
Thank you
Hi,
Hi,
I did try to convert this, but it failed. You need to check your block cipher and authentication keys. I believe that one of them is wrong. You need to ask them from the meter vendor.
BR,
Mikko
Hello,
Hello,
Thank you for the try. I was also thinking that something is wrong with the cipher or the key but they are right. :(
The output I get from the encryptor is:
2F455354355C3235333731373538345F410D0A0D0A312D333A302E322E38283530290D0A302D303A312E302E302832323036323930373434313953290D0A312D303A312E382E30283032343637313139302A5768290D0A312D303A312E382E31283031373639383536302A5768290D0A312D303A312E382E32283030363937323633302A5768290D0A312D303A312E372E30283030303030303633362A57290D0A312D303A322E382E30283030303131343038302A5768290D0A312D303A322E382E31283030303131343034382A5768290D0A312D303A322E382E32283030303030303033322A5768290D0A312D303A322E372E30283030303030303030302A57290D0A312D303A332E382E30283030313331333830312A76617268290D0A312D303A332E382E31283030303932313439372A76617268290D0A312D303A332E382E32283030303339323330342A76617268290D0A312D303A332E372E30283030303030303038342A766172290D0A312D303A342E382E30283030353136313338392A76617268290D0A312D303A342E382E31283030333333383537352A76617268290D0A312D303A342E382E32283030313832323831342A76617268290D0A312D303A342E372E30283030303030303237362A766172290D0A21454239410D0A
When I convert this to a string I got my data!
/EST5\xxxxxxxxx_A
1-3:0.2.8(50)
0-0:1.0.0(220629074419S)
1-0:1.8.0(024671190*Wh)
1-0:1.8.1(017698560*Wh)
1-0:1.8.2(006972630*Wh)
1-0:1.7.0(000000636*W)
1-0:2.8.0(000114080*Wh)
1-0:2.8.1(000114048*Wh)
1-0:2.8.2(000000032*Wh)
1-0:2.7.0(000000000*W)
1-0:3.8.0(001313801*varh)
1-0:3.8.1(000921497*varh)
1-0:3.8.2(000392304*varh)
1-0:3.7.0(000000084*var)
1-0:4.8.0(005161389*varh)
1-0:4.8.1(003338575*varh)
1-0:4.8.2(001822814*varh)
1-0:4.7.0(000000276*var)
!xxxx
Hi,
Hi,
This data is IEC 62056-21 and not DLMS/COSEM.
https://www.gurux.fi/DLMSCOSEMFAQ
It's not a standard way to send IEC 62056-21 readout in a push message. I'm wondering why this is done because now it breaks the DLMS compatibility.
All this is causing that you can't use Gurux DLMS libraries to parse the push messages from this meter.
BR,
Mikko