Owen White

Delays in loop() cause erratic PID.compute() values

4

I'm using the PID Library for a balancing robot and it seems to be exhibiting strange behavior. You can view the complete code here: [https://github.com/owhite/balancing_bot/blob/master/src/balancing.ino](https://github.com/owhite/balancing_bot/blob/master/src/balancing.ino) but I believe the relevant...

See: [https://github.com/davidmolony/MESC_Firmware/blob/FW_ADC_sampling/MESC_RTOS/MESC/MESCinterface.c](https://github.com/davidmolony/MESC_Firmware/blob/FW_ADC_sampling/MESC_RTOS/MESC/MESCinterface.c) starting around line 493 At present when we perform data logging, we export all these values: 1. mtr[0].Conv.Vbus , "vbus" 2. mtr[0].FOC.eHz , "ehz" 3. mtr[0].Conv.MOSu_T , "TMOS"...

Request: enable sending log data via the term.

1

Suggestion two levels of complicity for this. **FIRST VERSION:** User select items for configuring the payload with a command like `status log init` To configure: - frequency the payload is...