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
Where recently upgraded the Gurux software from 2015 version to the version from beginning this year.
Now where facing problems with datacollection on some older (<2012) Landis+Gyr meters in terminal mode.
Our meter specialist is telling me that the problem arises in the AARQ request.
After this it gets stuck.
The data sent from the manufacturer software is different than the Gurux software sends. The manufacturer software is sending one Hdlc frame and Gurux is sending two frames.
I saw that there was a modification https://www.gurux.fi/node/6280 on the frame size.
//Remove BOP, type, len, primaryAddress, secondaryAddress, frame, header CRC, data CRC and EOP from data length.
frameSize -= 11;
The max TX size for LG meters is 62 bytes. The AARQ data is 56 bytes. LG thinks it fits but Gurux 62-11=51 bytes won't let it fit and makes two frames.
So who is right? Is somewhere described that the TX frame size is for the whole packet or only for the data?
And I still won't know if sending the AARQ in one frame will solve our problem, where going to have to find out.
Hdlc frame size changed
Hi,
Frame sizes are for whole packet, not just payload. This is not a problem if the frame size is too large if serial or TCP/IP connection is used, but this is causing problems when wireless connections are used.
This meter doesn't pass new Conformance Certificate Tests. Can you modify the source code for your needs?
There is only one place what you need to change.
BR,
Mikko