Koxx3

it seems the master VESC is interpreting the slave VESC reply as an order and not something to forward to the requester.

running vesc on rpi ?! good luck ! 😅

+1

thanks a lot for the answer. I've spent a lot of time tracking this issue... I switch to IDF 4.4.5, but no improvement. I'll try to patch IDF-4.4.5 BT controller...

ok, thanks again. I'll keep you updated of the 4.4.5/4.4.7 patch tests. if it fails, yes, it would be really interesting to have few APIs to monitor the memory and...

ok. I am currently trying with IDF 4.4.7 version. I'll be out of the office for few days, I'll be back in few days to continue tests. If it's not...

ok, let's go for a test in IDF 4.4.4 + libbtdm_app.a patch before the long weekend. compilation test : ``` 15:29:32.558 > I (216) BTDM_INIT: BT controller compile version [d166426]...

in debug level : ``` D (1299) BTDM_INIT: Release DRAM [0x3ffb2730] - [0x3ffb6388] D (1300) intr_alloc: Connected src -5 to int 29 (cpu 1) I (1300) BTDM_INIT: BT controller compile...

I managed to remove Tasmota dependencies and work with "pure" packages now (thanks to Jason2866): ``` PACKAGES: - framework-arduinoespressif32 @ 3.20016.0 (2.0.16) - framework-espidf @ 3.40407.0 (4.4.7) - tool-cmake @...

ok, I'll try to switch back to officiel 4.4.4 and use ke_get_heap_free_size