why can't I delete the can mappings

[medo]

Why is it that I can't delete the CAN mappings? On the web you have to delete them individually and you can't use the Remove all mappings button to delete everything at once. As soon as I restart, everything is back, the inverter isn't running either.

[johu]

Ah, "Remove All" doesn't work on the ESP-CAN module yet. After removing you need to Save to flash to make removal permanent

[medo]

I've tried everything, but as soon as I restart it, it appears again
I've rolled back to the official firmware 5.35 to test it, and everything works there. In 5.36.40.B, you can't even save the CAN IDs. There must be something wrong?

[johu]

Ok, will test tomorrow

[Zieg]

Huh, that's interesting. A couple days ago I was having trouble mapping CAN on my 5.35R inverter via the esp-can but Foccci accepted all the mappings no problem. Do you have an 8266 on your inverter?

[johu]

Oh, interesting... github deletes build artifacts after a while...

So I tested with my local build and indeed can reproduce. Will try to find the cause.

update: found it. The new SdoCommands class hadn't had it's canMap member set.

You can try it: https://github.com/jsphuebner/stm32-sine/actions

Makes me think about this new structure. Maybe the CanSdo class should be tightly coupled to SdoCommands. Right now there are many things you can forget when integrating it

[medo]

works, thank you very much

[medo]

I have a similar situation with the Teslacharger v1.19R. I can delete canbus mappings but I can't save them anymore. Can someone check this?

A second thing would be, if I want to update the firmware via ESP-CAN module, it stops at 4% and does not go any further. With LDU and VCU no problems with updating