Create object gxData with value of date-time format

Hi,

Sorry but we did not get what do you mean and what are we supposed to do. Can you please write for us an example code in order to understand how to create this object?

When we tried to create this object using GX_DATETIME and we tried to capture a profile generic having one of his columns equal to this object, it is crashing. There is a problem in the function dlms_setData() used in the getProfileGenericBufferColumnSizes() function.

Best Regards,

Lara Wakim

Hi Mikko,

Thank you really appreciated.

We will start checking and testing the new release. We will be waiting for the server example so we can test more easily and efficiently the new features.

Best Regards,

Lara Wakim

Hello Mikko,

We downloaded the latest version and when we tried to run it, it showed a lot of errors related to the ws2def.h and winsock2.h files (check the picture).

Any idea what is the problem and what we should do?

Best Regards,

Lara Wakim

Hey,

We downloaded the latest release and it worked. We were able to run it and connect with the client.

If you remember we did have a problem with the event notification (it is looping forever in the GXDLMSDirector until it is crashing). We tested it with the new release and the problem is still here.

To repeat the problem, these are the steps:

1- In the svr_preaction add sendEventNotification when triggering the disconnect control:

updateState(GURUX_EVENT_CODES_OUTPUT_RELAY_STATE);
line 2616 -> sendEventNotification2(settings); <-

2- Then connect with the client and try to trigger the reconnect method of the disconnect control object

3- The issue should appear. We are supposing that the problem is from the client side because we did visualize the message sent from the server, it is sending only one message not multiple one.

If you can please check it and tell us the origin of the problem if it is our code or from the server or from the client.

Best Regards,

Lara Wakim

Hi Mikko,

You are welcome if you need more information to repeat the problem feel free to ask.

We have three questions till now concerning the new release:

1 - When downloading the latest release we noticed that in the preread() function you replaced DLMS_DATA_TYPE_DATETIME by DLMS_DATA_TYPE_OCTET_STRING when reading the clock1 object

Is there a clear reason or explanation for this change? because we tested with the both type and the result is the same in the both cases

2 - If we create an object of type octet-string but we want to see it in the GXDLMSDirector as format date-time we wrote the same code of the clock1 object. But surprisingly in the client side, when we read this object, it has a format of octet-string but a meaning of date-time (check the picture).

What are we supposed to do to see it as date-time format also? If you know another way to do it please share like creating it as date-time format from the start (but we are finding difficulties to initialize this type)?

3 - When we create an object of type octet--string this way:
char* dt = "012345678901";
GX_OCTECT_STRING(passiveEndOfBillingPeriod1Contract1.value, dt, strlen(dt));
and we try to restart the meter it is crashing when loading the settings files more specifically in the function getOctetString() (dlms.c file) it is returning DLMS_ERROR_CODE_OUTOFMEMORY because value->capacity(4) < len (12). Why is this happening?

But when we replaced the above by this:
static char dt[12] = "012345678901";
GX_OCTECT_STRING(passiveEndOfBillingPeriod1Contract1.value, dt, sizeof(dt));
The problem was solved and the load of the settings worked fine but we didn't understand why it is working for one not for the other way. Is it a bug or a normal thing? if you please can clear this idea

Best Regards,

Lara Wakim

Hi,

Thank you for these precious information. Yes sure we will filter the objects needed as date-time format and share it with you through email.

Let me now highlight a possible bug that we found in the new release:
- After connected the client-server for the first time, we read the action schedule disconnect control object then we added 2 execution time.
- Then when we restarted the code it is failing to load settings file
- So we followed the failure to know the reason, we noticed in the ser_loadObjects() -> ser_loadObject() -> ser_loadActionSchedule(), the hlp_getObjectCount2(serializer, &count) function is giving count = 2 like expected BUT the size of the executionTime is equal to 0 not 2 so when we are looping the function ret = arr_getByIndex(&object->executionTime, pos, (void**)&tm, sizeof(gxtime)) is returning
DLMS_ERROR_CODE_OUTOFMEMORY because index(0) >= arr->size(0 instead of 2)

We are supposing that there is a problem when saving the execution time in the postWrite more specifically in the ser_saveActionSchedule() function.

If you can check it and if you need more information feel free to ask.

Best Regards,

Lara Wakim

Hi Mikko,

Let me kindly add another bug we think it is important to correct.

We noticed that in the saveSecurity() function, we are saving the blockCipherKey, authenticationKey, kek, invocationCounter and minimumInvocationCounter but we were not saving the security policy level.

So when we activated the security policy from none to authenticatedEncrypted and then restarted the code and loading the security information, it was back to none instead of being authenticatedEncrypted like expected so we think you should save also the security policy level.

Best Regards,

Lara Wakim

Repetition

Hi,

Kindly check your email, we sent you the list of Spain identifier to be supported as date-time in the GXDLMSDirector.

We are sorry for the same message sent twice above.

Best Regards,

Lara Wakim

Hi Mikko,

We want to highlight a problem that we faced. We uncommented the DLMS_IGNORE_PLC in the gxignore.h file for testing purposes. A lot of errors appeared (check the picture).

If you please can solve this problem by repeating it.

Best Regards,

Lara Wakim

Hi Mikko,

We tried to trigger the scriptTableGlobalMeterReset, we noticed the below points:
1- You did not call the createObjects(), but you called only the loadSettings() and loadSecurity() functions, is it intended and enough or not?
2- You only cleared the settings file so it will be saved again, but we think you forget to clear the security file so it will be saved as new not load the old one.
3- Then we tried to clear both files settings and security so saveSettings() and saveSecurity() were triggered, but we noticed that the value of the keys were saved as the new one and were not reset like expected to the old values but the minimumInvocationCounter was back to 0. So more specifically the value linked to the settings.base.cipher was not cleared and reset to the original value (the last updated values were the ones to be saved) but the security setup object was cleared so the minimumInvocationCounter was only the one to be cleared.

If you please can check it .

Best Regards,

Lara Wakim

Hi Mikko,

Thank you for the above answers.

There is an important issue that should be solve in the next release. We created an object of interface class Data (ID = 1) and the value type is equal to array[2] of bit-string[256] (the one that you help us to create)

You can find attached the function that we wrote to create that object (check the picture)

When we save the settings for the first time it is done successfully, but when we try to load the list of objects from the file settings it is crashing when trying to load the object above and returning DLMS_ERROR_CODE_INVALID_PARAMETER.
getVariantFromBytes
To follow the error : ser_loadObjects()->ser_loadObject()->ser_loadData()->getVariantFromBytes()->cosem_getVariant()->dlms_getData() in this function we have "switch (info->type)" but obviously the value type array[2] of bit-string[256] is not supported yet because it is going directly to the default case where is written "assert(0);" instead of entering the "case DLMS_DATA_TYPE_ARRAY" for example.

There is something wrong because the type seems unknown, the problem could be coming from the saving or loading part of this object. We hope that you will try to repeat the problem.

PS: Let me add that the same problem is appearing with another object gxData with value type equal to array[2] of octet-string[12] (the second new type that you help us to create)

Can you please check this major issue?

Best Regards,

Lara Wakim