There is a problem either in parsing in Sigfox module, or in the way data is sent to the Sigfox module. If you send a message in an array like following:
there would be a parsing error produced and your message will not be sent to Sigfox servers, due to msg[2]=13; //0xD. If you change it to msg[2]=16; //0x10 the issue will be resolved. It seems that this part is seen as a nibble instead of a byte, as long as the value is equal or less than F in HEX. The complete and simple example is as below.
In this way there is a limitation in sending different values and as long as the value is <= 0xF, there would be a problem.
Is there a fix for this issue?
There is a problem either in parsing in Sigfox module, or in the way data is sent to the Sigfox module. If you send a message in an array like following:
uint8_t msg[12]; msg[0]=76; //0x4C msg[1]=20; //0x14 msg[2]=13; //0xD //complete example below//
there would be a parsing error produced and your message will not be sent to Sigfox servers, due to
msg[2]=13; //0xD
. If you change it tomsg[2]=16; //0x10
the issue will be resolved. It seems that this part is seen as a nibble instead of a byte, as long as the value is equal or less than F in HEX. The complete and simple example is as below.I also tried with the following message structure and nothing changed. The issue still exists.
In this way there is a limitation in sending different values and as long as the value is <= 0xF, there would be a problem. Is there a fix for this issue?