This is a screen of my 1000m ride up hill (on the mountain) .
I used all the battery except 2 % the last 150 meter were not logged (lost my phone xD … i was able to recover it later but no tracking xD)
1000 m on a 10-12km hike trial. Great test for that little Free drive 
Normally i get 45km with 300m uphill. So as you can see it was a massiv, but very successfull attempt. The last 400 metre up the mountain I had to hike cause there was no real path anymore 
so a total of 1400m but the last 400m were quite the challenge the board is like 18kg which i had to carry
Fine. So I’m looking at the momentary switch. It seems to be a simple issue with just two traces that needs some modification. Going to bread-board it. And then of course, I would like automatic turn off functionality.
Latch Circuit for momentary switch with MCU shutdown
This has been a little tricky due to the D1 diode that needs to be there to prevent back-flow of current from large capacitors. But should be tuned now.
In case anyone wants to play around with the Kicad files of the Latch Circuit:
latch_circuit_test.zip (16.7 KB)
So after looking at the schematics, I see why the Motor Temperature is not working. It’s a hardware issue… A 10k resistor and small capacitor is missing. Thanks for pointing a the issue.
Mr. Shambler.
At the time when you were fiddling around with a replacement IMU for the BMI160, did you consider using the BMI323. It is pin-compatible with the BMI160
just a little more precise. And it’s cheap on LCSC.
Sorry this is a fast comparison made by chatgpt and there might be hallucinations. But just wanted to ask before trying it out.
so it could be fixed on v1 hardware ? I am building another board so I could test if this is working on that one good to know 
Sure but I havent found anything about it to be compatible with the current VESC firmware, thats why I used the other IMU
We may have to ask BenjaminV, if the IMU has been tested with VESC already or if there could be any problems using it. The thing is there are filters and stuff that need to work in order to use it correctly. As it is my understanding you cannot use just a more precise IMU and hope everything will work the same. I mean more precision means it could be more subsceptible to vibrations and so on. I guess its not that easy to just use something else but I could be wrong … (Its a problem in FPV (Drones) . Which is also a hobby of mine)
You’re right it needs investigation for this particular part…
From where did you get the information that ICM-20948 works with Vesc?
its in the change log and source code of vesc:
i mean I am software DEV thats why I first look at the source before considering hardware changes
Ah yeah, and I just forgot that there’s a communication interface to the IMU - SPI or I2C, I don’t remember, but it’s probably going to be different for different IMUs…
i mean i haven’t tested the ICM-20948 implementation yet, I just tried to implement everything from the spec sheet.
Little FOCer 3 apparently uses LSM6DS3
“If IMU was detected properly, the Frequency at the bottom should read as the correct sample rate for your IMU. For example, LFoc v3.1 (LSM6DS3) should read 832Hz (Again, can be set manually later if need be).”
yeah but it is EOL as well , thats why i dropped that as well
also JLCPCB has a big stock of ICM-20948
This message is just so I remember the URLs if I should decide to evaluate bmi323 vs bmi160
