and too little time
oh, and also an experimental integration of w5100/w5500 ethernet shields into lwip as additional interfaces
:D I feel that way myself about some of what the fellow developers have done. That bearssl alternative to axtls was a huge piece of code, the migration to lwip2 was mindboggling, as is the integration into lwip of the ethernet shields, and don't get me started on the available heap improvements and stack placement voodoo
@ashthespy I have it working using my own bastardized method but still want/need to understand typecasting. 'int setpointVariable100 = setpointVariable / 10;
int setpointVariable10 = setpointVariable - (setpointVariable100 10);
int targetGroundSpeed100 = targetGroundSpeed / 10;
int targetGroundSpeed10 = targetGroundSpeed - (targetGroundSpeed100 10);
uint8_t payload[4] = {0, 0, 0, 0};
payload[0] = setpointVariable100;
payload[1] = setpointVariable10;
payload[2] = targetGroundSpeed100;
payload[3] = targetGroundSpeed10;
webSocket.broadcastBIN(payload, sizeof(payload));'
int setpointVariable10 = setpointVariable - (setpointVariable100 10);
int targetGroundSpeed100 = targetGroundSpeed / 10;
int targetGroundSpeed10 = targetGroundSpeed - (targetGroundSpeed100 10);
uint8_t payload[4] = {0, 0, 0, 0};
payload[0] = setpointVariable100;
payload[1] = setpointVariable10;
payload[2] = targetGroundSpeed100;
payload[3] = targetGroundSpeed10;
webSocket.broadcastBIN(payload, sizeof(payload));'
stupid markup
uint8_t payload = (uint8_t *)data;uint8_t *payload = (uint8_t *)data;
?
Sooo need to understand this stuff.
void sendSettings() {
uint16_t data[] = {setpointVariable, targetGroundSpeed};
uint8_t* payload = (uint8_t *)data;
webSocket.broadcastBIN(payload, sizeof(payload));
}
there are other ways of doing what I think you want, which is essentially to serialize two values
if you're sure that your values will always fit in a uint16_t, then your original approach is not too bad. You probably want something like this:
void sendSettings() {
uint16_t data[] = {setpointVariable, targetGroundSpeed};
webSocket.broadcastBIN((uint8_t *)(&data[0]), sizeof(data));
}
agnostic to datatypes that is
none of these uC have hw floats. All floats are software, which means that float-based calculation is rather expensive. That said, the AVR is pretty weak compared to the ESP, which is most likely why you got jumped. Doing floats on the ESP is still expensive computationally, and there is a lot of code that is linked in for the float stuff, but it shouldn't have trouble calculating a simple PID
@ashthespy So I just avoid floats untill human interface time.
about work, that reminds me that I'm done with it, and I gotta head home :p later all!
@devyte ..perhaps you could help with a few simple questions that are driving me loco