Wierd result for get data about ethercard HOT 3 CLOSED

I don't know what's happening, but for an ATmega with limited RAM, I'd prefer to use calls with predictable behavior:

// Construct GET payload
strcpy(buf_full, "t=");
strcat(buf_full, dtostrf(temp,7,3,buf));
strcat(buf_full, "&u=";
strcat(buf_full, String(unit)); // or perhaps with itoa?

This is more old-fashioned C, but might work better here.

from ethercard.

You are using the String object, which as it says, is an object. I've not looked at the implementation, but it has to allocate some memory just to create itself and a few extra bytes for its own use. It would create space for a string of characters of a minimum size so that it doesnt have to keep allocating more memory as the string is added to.

As jcw commented, using a fixed length character buffer and traditional C functions is a better solution for limited memory systems, you know where you are and how many bytes you are using.

Andy

from ethercard.

I'm assuming this issue has been resolved by now. Please re-open if this is not the case.

from ethercard.