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
Dear Mikko,
CTT Test case also passed Or not
1.test case failed while proposed-dlms-version-number = 7, CTT VERSION 106 AND 107
2.General Block Transfer(GBT)(In US Association) not implemented in their GURUX Stack as memory constraint might exist
Dear,
Dear,
1 proposed-dlms-version-number = 7, release 107.
0'35.884 VERDICT: 2: proposed-dlms-version-number = 7 PASSED
This test is using 4 bytes addressing. Try to connect to the meter with GXDLMSDirector. I checked the values that you are using in the _CTI file. Set physical address to 255 and logical address to 1. If this fails, modify svr_isTarget for your needs.
2. GBT is using a lot of memory if ciphering is used because all data must be read to the memory before data is encrypted and sent to the client. This is a killer because ciphering is applied to the complete APDU and then ciphered data is sent as data blocks. Read more from the Green Book: 9.1.4.4.5 Transferring long messages
This is a big problem when you want to read thousands of rows from the profile generic. I believe that there is not enough memory in any consumer meter to do this.
BR,
Mikko
Dear Mikko,
Dear Mikko,
how to test proposed-dlms-version-number = 7, release 107.
and in server.c why need following code....
else if (ret == 0 && result == DLMS_ASSOCIATION_RESULT_ACCEPTED)
{
if (settings->base.dlmsVersionNumber < 6)
{
Hi,
Hi,
Please, don't modify the framework. Make all the changes for the main application.
That code will handle the previous test for proposed-dlms-version-number = 5.
Can you connect to the meter using GXLMSDirector if you set the Physical address to 256 and the logical address to 1. I believe that is the problem.
BR,
Mikko