Is there a limit on the amount of bytes the payload must be in the publish message? about paho.mqtt.embedded-c

[scaprile]

Make sure your topicString[0] is a MQTTString
Execute your code step by step and pinpoint where your payload is trashed.
Remember memcpy() belongs to your system.

[scaprile]

Execute your code step by step and pinpoint where your payload is trashed.
Remember memcpy() belongs to your system.

If you do find something in the code, I'll be happy to help (maybe others too)

[scaprile]

MQTTSerialize_publish() just calls memcpy(), it does not modify your payload; see source code.
Is it the header you see is not OK ? How ? What do you do, how do you call this function, what do you see, do you actually have enough free memory where your pointer points to ? What have you checked, have you stepped the code ?
MQTT msg length can be encoded in with a different number of bytes and handle up to 256MB; the actual system memory limits will mostly come first.

[hakam00ra]

This is how i call the function

unsigned char bufm[1500];
int bufmlen = sizeof(bufm);
rc = MQTTSerialize_publish(bufm, sizeof(bufm), dup, qos, retained, msgid, topicString[0], message, messageLen);

I get this in my console for a particular payload:

messageLen=580
sizeof bufm=1500
rc=600

The payload (bufm) is transmitted fine.

For a different payload:

messageLen=638 
sizeof bufm=1500
rc=658

And since the payload is larger than 600 bytes the payload (bufm) is now only 19 bytes and only contains some parts of the message array.
Notice how the rc is correct on both occasions.

Also there is enough memory where my pointer points to unsigned char bufm[1500];

thanks

[hakam00ra]

yup.....
It was a stack issue. My pointer was pointing to the stack...
Sorry and thanks for the help.

[scaprile]

Please close the issue, the moderator is busy