Hello,
sorry I am still quite new in DLMS. I have counter MCS301 and I have strange problem.
I said in subject that it's unstable error, because sometimes I get that error and sometimes not. I have no idea what that error means. Maybe anyone could help.
For any help great thanks in advance.
The communication looks like that:
I send:
7E A0 0A 00 02 88 1D 03 93 98 3F 7E
And I receive:
7E A0 21 03 00 02 88 1D 73 E7 99 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3B 7E
So it looks OK, and next frame I send is:
7E A0 47 00 02 88 1D 03 10 42 60 E6 E6 00 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 31 32 33 34 35 36 37 38 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F 03 E8 15 66 7E
And then SOMETIMES I receive that:
7E A0 3A 03 00 02 88 1D 30 33 2A E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 3E 1F 01 80 00 07 B3 57 7E
Which is also great. But Sometimes I receive that:
7E A0 0A 03 00 02 88 1D 31 F0 ED 7E
And it looks like something is wrong but I have no idea how to interpret that.
As you can see I always send the same frames to exactly the same counter, but I receive various answers.
You send an AARQ message and the meter returns AARE. When it fails, the meter is asking for the next frame. The reason for this is that all the data didn't fit into one frame. Our libraries can handle that. Just send the next part.
Another reason is that there is an issue with the meter and it fails randomly. That is happening sometimes. Just wait for a while and re-connect to the meter. Usually, errors like this come if you try to establish a new connection right after you have closed the previous one.
Hmm... Great thanks for your answer.
Yes I tried to translate that code by your DLMS translator. But as I remember normally the counter informs us that he is ready to send next frame, and then WE are who ask for next frame. But here it looks like counter is asking us for next frame. How is it possible? What we should send in that case to the counter?
And yes I know that there could be problems while we try to establish more that one connection while last one is not closed. But let's assume it's not my case. Because for first message (which is 7E A0 0A 00 02 88 1D 03 93 98 3F 7E) the counter always answers properly. I get various answers only for second question. So I think I should handle in some way that counter asking for next frame. But I have never before such case. So not sure what should I do?
In general, the meter is asking the next frame if all the data is not fit to one frame. This is common and happens all the time when data is written to the meter. This might happen with the AARQ, for example when the password is long and AARQ can't fit into one frame. :-)
The first frame is the SNMR frame and it establishes the connection and sets HDLC parameters. Connection to the DLMS level is not yet established.
But if you are using the same meter parameters (password, etc.) and this is happening randomly it's the meter issue.
Note! This usually happens If you don't close the connection properly and the next connection fails. Then wait a while and try again.
Hi,
Hi,
You send an AARQ message and the meter returns AARE. When it fails, the meter is asking for the next frame. The reason for this is that all the data didn't fit into one frame. Our libraries can handle that. Just send the next part.
Another reason is that there is an issue with the meter and it fails randomly. That is happening sometimes. Just wait for a while and re-connect to the meter. Usually, errors like this come if you try to establish a new connection right after you have closed the previous one.
BR,
Mikko
Hmm... Great thanks for your
Hmm... Great thanks for your answer.
Yes I tried to translate that code by your DLMS translator. But as I remember normally the counter informs us that he is ready to send next frame, and then WE are who ask for next frame. But here it looks like counter is asking us for next frame. How is it possible? What we should send in that case to the counter?
And yes I know that there could be problems while we try to establish more that one connection while last one is not closed. But let's assume it's not my case. Because for first message (which is 7E A0 0A 00 02 88 1D 03 93 98 3F 7E) the counter always answers properly. I get various answers only for second question. So I think I should handle in some way that counter asking for next frame. But I have never before such case. So not sure what should I do?
Once again great thanks for your support.
Hi,
Hi,
This might also be a meter issue.
In general, the meter is asking the next frame if all the data is not fit to one frame. This is common and happens all the time when data is written to the meter. This might happen with the AARQ, for example when the password is long and AARQ can't fit into one frame. :-)
The first frame is the SNMR frame and it establishes the connection and sets HDLC parameters. Connection to the DLMS level is not yet established.
But if you are using the same meter parameters (password, etc.) and this is happening randomly it's the meter issue.
Note! This usually happens If you don't close the connection properly and the next connection fails. Then wait a while and try again.
BR,
Mikko
Great thanks for your answer.
Great thanks for your answer. So I will try to speak with manufacturer of MCS301