Yes I had indeed planned to use VWs water cooling plates but then shoehorning reality got in the way ;) For one I have very little space to play with. So Fitting 1 plate per "floor" is not possible. Sandwiching one between the modules would be the only possibility but for that to make sens...

Yes 180 kg would be plausible as each cell is less than 1 kg and there are 192 of them. "Flying Tools" youtube channel once ripped apart an MEB module and the modules are thermally connected to the bottom plate mostly. That is the issue: grafik.png I'm blowing in air through 2 small holes ...

The battery box is aluminium. The plan was to do just that but I screwed up. The distance between the upper modules and the box is 3mm :? It's super hard to get everything out again. The lower half I have more of a chance. They don't touch the cover plate at all. I would like to add something soft t...

I decided this needs more data. So I went to a V4 super charger and charged for 10 minutes from 35 to 58%. Outside temperature was 23°C and fan running at full speed. Raw data is attached, here is some plots Voltage drop is lost in measuring accuracy. It was always less than 1V. You can see the CCS ...

Added a sub version number. The new version now advertises '3', '1' instead of '3', '0'. When '0' is advertised the ESP will insert an additional delay before sending the page count.

Created a new release: https://github.com/jsphuebner/stm32-CAN ... s/tag/v1.2

Easy fix. Just included the PROGRAM state in the if The PROGRAM state can only be left by the actual programming routine, so that is now safe. Now just have to worry about a backward compatibility hack.

Found it! It's indeed a timing issue: grafik.png The CAN messages come in so fast that "if (state == PAGECOUNT || state == PAGE)" hasn't been reached. Instead we are in state CRC, the entire block is skipped and we proceed straight to sending "D". Ok, will do something about it i...

The STM32 bootloader enables the independent watchdog and the firmware is expected to feed that at least once a second or so. If it fails to do so, the STM32 is reset. This is used to recover from a failed update. If a firmware is just partially flashed it is usually not runnable and won't feed the ...

Luckily I made a video


Seems like 4V @ 220A. From all I know this includes the voltage drop over the dispenser cable as well.

255W * 256 kg * 0.90 J/g ° C for Aluminium gives you a temperature change rate °C / s Oh thanks, that's something to play with :) Shouldn't 256kg be in the denominator? Now I arrive at 58752 °C/s ;). With 255W/256000g * 0.9 * 2h I arrive at 6.4°C rise in 2 hours, of course neglecting heat exchange ...

And back to square 1. It doesn't go into drive. Probably the next cable has now come loose, I suspect the one from the drive selector buttons.

So again, make a bid

Congratulations, seems fixed :) I drove to my local Aral Pulse which has two Alpitronic HyperChargers. I just took the chance and plugged in. Only a minute later a Danish family arrived and I asked them to plug into the other charge port on the same charger. When they started I saw my power briefly ...

We only have this: https://www.lgensol.com/assets/file/LGES_spec_sheet_cells_2022.pdf (it's two E78 cells in parallel) So 1.48 mOhm per cell, should be 0.74 mOhm per cell pair, times 96 71 mOhm. Driving at 20 kW would be about 60A. So 60²*0.071=255W power loss. That's where my knowledge ends, how do...

Well actually those plots sort of align. I add 10 °C by driving 250 km with a taller and heavier vehicle while you add 5°C by driving how many km? Also it looks like the Ioniq battery also collects most heat towards the end.

What's way better in your case is the cool down.

Another road trip and more data. First trip was to the seaside, 450 km one way. Temperature was 30°C and the battery heated up while waiting 4 hours for an accident site to be cleared. Unfortunately no charger at the resting area the we waited at. We charged after around 250 km on a 50 kW charger an...

Oh, indeed the wrong boot loader is linked in the README, will correct.

But again, have you flashed the latest https://github.com/jsphuebner/esp32-web-interface to the ESP module?

We solved the problem and he'll keep the car

Well, not that fast. I took the plunge and drove 400 km down to Thomas (while taking care of many other things along the route as well). Turns out while fiddling with the vacuum hose the two gentlemen (Thomas and his mechanic) loosened the (admittedly poorly crimped) resolver cable. So we added some...

It seems the esp32 firmware isn't up to date. Is it the latest github source?

Cool
Would be very happy to see many photos and screenshots
Have you connected to cells yet?

Foccci is the first firmware to support at least 0x00000312 kind of mappings. No real extended IDs are yet possible as I foolishly started out with only space for 11-bit IDs in the map. Don't want to change it now so people don't loose their maps. When the first use case comes up I guess we'll have ...

stm32_sine.bin it is for the py script

Yes just stick some jumper cables in there and hold them under tension.

uart-updater.py is what you want to use https://github.com/jsphuebner/stm32-CANBootloader/

Ok then maybe the utility tries to flash the hex file as a binary blob. It probably needs a command line switch to treat it as hex

Please omit the address!

But the actual cause of the error seems to be the binary size. It is 68k but should be more like 25k. How did you obtain it?

You can get prebuilt bin/hex here: https://github.com/jsphuebner/FlyingAdc ... 9399397611