In the communication window, the below comment is written:
"This push is sent every minute, but max 10 seconds over."
We want to know what do you mean by the "10 seconds over" represented by the end variable?
We are facing a weird issue concerning the object list of the data notification:
- When we add to the object list first the data cosem logical device name them the active power register value, the data notification is send correctly (check the picture left side) :
<OctetString Value="4752583030303030303031323334353600" /> (GRX0000000123456)
<UInt16 Value="000E" /> (active power L1 : 14000)
- When we inverse the same object in the list (start with the register then the cosem logical name), the push setup message send as notification is wrong (check the picture right side) :
<UInt16 Value="000E" /> (active power L1 : 14000)
<OctetString Value="020212000E09" /> expecting (GRX0000000123456)
There is a lot of another example covering the issue above. The object list is affected by the order and the type of the added object.
Maybe there is an issue in the generation of the push setup messages that is done in the sendPush() function more specifically in the notify_generatePushSetupMessages() function.
1. This push is sent every minute, but max 10 seconds over
You can give a time window when push messages are sent. During that time window meter try to send push message. Meter will try to re-send the message if it fails.
2. We'll check this. Usually Logical Meter Name is sent first. We have made some improvements and release a new version in next week.
Concerning the issue above, it is not only related to the cosem logical meter name. In fact the issue appears within several scenarios (check the picture for another example).
The objects list :
1- Load profile generic attribute 8 : profile entries equal to 150
2- Active power L1 register attribute 2: value equal to 11
3- Event log attribute 7: entries in use equal to 1
The data notification sent by the server:
1- <UInt32 Value="00000096" /> CORRECT
2- <UInt16 Value="000B" /> CORRECT
3- <OctetString Value="0203060000009612000B09" /> WRONG should be <UInt32 Value="00000001" />
We have a question: in the objects list what do you mean by data index?
Hi,
Hi,
1. This push is sent every minute, but max 10 seconds over
You can give a time window when push messages are sent. During that time window meter try to send push message. Meter will try to re-send the message if it fails.
2. We'll check this. Usually Logical Meter Name is sent first. We have made some improvements and release a new version in next week.
BR,
Mikko
Hi Mikko,
Hi Mikko,
Concerning the issue above, it is not only related to the cosem logical meter name. In fact the issue appears within several scenarios (check the picture for another example).
The objects list :
1- Load profile generic attribute 8 : profile entries equal to 150
2- Active power L1 register attribute 2: value equal to 11
3- Event log attribute 7: entries in use equal to 1
The data notification sent by the server:
1- <UInt32 Value="00000096" /> CORRECT
2- <UInt16 Value="000B" /> CORRECT
3- <OctetString Value="0203060000009612000B09" /> WRONG should be <UInt32 Value="00000001" />
We have a question: in the objects list what do you mean by data index?
Best Regards,
Lara Wakim
Hi,
Hi,
Thanks for this information. Data index can be used ex. in profile generic to get only one row. It's not widely used feature (as far as I know).
BR,
Mikko
Hi Mikko,
Hi Mikko,
Any update concerning the new release that you told us about above "We have made some improvements and release a new version in next week."
Best Regards,
Lara Wakim
Hi,
Hi,
Tests are on progress.
BR,
Mikko