We have got an device from another supplier (Iskra) which provided that information as followed:
<?xml version="1.0" encoding="utf-8"?>
<x:xDLMS-APDU xmlns:x="http://www.dlms.com/COSEMpdu">
<x:data-notification>
<!-- Invoke ID: 6282 -->
<x:long-invoke-id-and-priority>6282</x:long-invoke-id-and-priority>
<!-- 8/24/2022 11:00:00 AM -->
<x:date-time>07E60818030B000000FF8880</x:date-time>
<x:notification-body>
<x:data-value>
<x:structure>
<!-- ISK1234567890123 -->
<x:octet-string>49534B31323334353637383930313233</x:octet-string>
<x:array>
<x:structure>
<!-- 0.0.1.0.0.255 -->
<x:octet-string>0000010000FF</x:octet-string>
<!-- 8/24/2022 10:30:00 AM+02:00 -->
<x:octet-string>07E60818030A1E0000FF8880</x:octet-string>
<!-- 0.0.96.10.2.255 -->
<x:octet-string>0000600A02FF</x:octet-string>
<x:unsigned>0</x:unsigned>
<!-- 1.0.1.8.0.255 -->
<x:octet-string>0100010800FF</x:octet-string>
<x:double-long-unsigned>9733489</x:double-long-unsigned>
<x:structure>
<x:integer>0</x:integer>
<x:enum>32</x:enum>
</x:structure>
<!-- 1.0.2.8.0.255 -->
<x:octet-string>0100020800FF</x:octet-string>
<x:double-long-unsigned>1696</x:double-long-unsigned>
<x:structure>
<x:integer>0</x:integer>
<x:enum>32</x:enum>
</x:structure>
<!-- 1.0.3.8.0.255 -->
<x:octet-string>0100030800FF</x:octet-string>
<x:double-long-unsigned>5606907</x:double-long-unsigned>
<x:structure>
<x:integer>0</x:integer>
<x:enum>32</x:enum>
</x:structure>
<!-- 1.0.4.8.0.255 -->
<x:octet-string>0100040800FF</x:octet-string>
<x:double-long-unsigned>415</x:double-long-unsigned>
<x:structure>
<x:integer>0</x:integer>
<x:enum>32</x:enum>
</x:structure>
</x:structure>
</x:array>
</x:structure>
</x:data-value>
</x:notification-body>
</x:data-notification>
</x:xDLMS-APDU>
This works basically based on indexes within the Structure. First the Obis code is send and next the value, etc. So I still have to describe on the receiver side how to interpret the data.
Ideally I would like to receive in a separable object within the message, the structure. So that can be parsed and the push object list can be created. Based on that push object list I would then parse the actual data.
So I am wondering, are there devices that actually provide the data as described? Or do you have an example how other device provide the push object list?
The meter can send all kinds of data in push messages. It depends on how it's configured.
Your meter is configured to send the meter serial number and logical name of the push setup in first.
Read the Push object list and you can see how it's configured. You can add a Push object list as a first parameter, but then the size of the push message is bigger.
You can read the push object list from the meter and then save it for the XML file. This is a good solution if all your meters are configured in the same way.
Our clients are receiving push messages where the push object list is at the first parameter and Iskraemeco meters that are configured just like yours.
It depends on you how you want to configure the push message and what you want to send as the content.
Hi,
Hi,
The meter can send all kinds of data in push messages. It depends on how it's configured.
Your meter is configured to send the meter serial number and logical name of the push setup in first.
Read the Push object list and you can see how it's configured. You can add a Push object list as a first parameter, but then the size of the push message is bigger.
You can read the push object list from the meter and then save it for the XML file. This is a good solution if all your meters are configured in the same way.
Our clients are receiving push messages where the push object list is at the first parameter and Iskraemeco meters that are configured just like yours.
It depends on you how you want to configure the push message and what you want to send as the content.
BR,
Mikko
Ok, thanks!
Ok, thanks!