Rustybkts wrote: ↑Fri Feb 14, 2025 10:14 am Zombiverter VCU pin-out info which is very incorrect

This is the pinout from the schematic which has the pin numbers reversed and the Can1 and Can2 swapped.
It doesn't really provide any useful information, so not sure why it was added to the wiki.

Really easy to get the correct frequency. The clock is 72MHz so need total division of 36000000, e.g. 9000 x 4000.
set Tim3_Presc to 8999, and Tim3_Period to 3999. Duty cycle is controlled with Tim3_x_OC, where x is 1 to 3. 1000 gives 25% duty cycle, 2000 gives 50%, 3000 75% etc.

#ifdeffing makes the code less readable and as I modified files based on F1 version rather than modifying old F4 version it did not seem necessary. It's an F4 branch not F1/F4.

For G4 and updated F4 version there are no modifications to libopencm3. They are all done in the libopeninv code.

G4 and recently updated F4 versions are at github below. F4 mostly untested, G4 mostly works except saving/reading flash still needs fixing. It uses 64 bit read/write so is different ...

WSB BSS138BK, WVS BSS84AK

I only had a quick look at can and digio, and found a few errors.

Can bus bit timings are wrong. The older version of F4 library assumed a clock frequency of 168MHz ( or 84MHz ) which gives can bus clock source at 42MHz. Timings in original version were correct but need to add values for 800kbps ...

potmin and potmax ( and pot2min, pot2max ) need setting correctly for each pedal to avoid above errors.

The "specifications" are typical values from a document explaining throttle position error code.
The best numbers I could find are the limits on a sensor tester in this post https://priuschat.com/threads/pedal-commander-for-faster-gas-pedal-response.230983/.

Sensor 1
0.4 - 1.4V Not depressed
3.1 ...

Python needs to be installed to generate some of the header files.


.....but is there really no other way?

Learn a little bit about virtual and pure virtual function declarations/definitions.

Some functions need to be in the child class as they are not defined in the vehicle parent class ...

The problem with the pnp transistor is the base and collector are swapped. In the schematic you have used a spice simulation symbol which has different pin numbers from the transistor used, and states it's for simulation only.

There is a problem compiling GVRET code. I tried when setting up a 2nd Due before searching the forum. Use GVRET firmware updater about half way down the page.
https://savvycan.com/
https://savvycan.com/GVRETupdate.zip

Assuming you have the the same version as on github, connect your wifi to ESP32-CHADEMO, password ChadMeO.
Then access the web page at 192.168.4.1 which is the default IP address for the ESP32 web server.

Damien does option 1. The other option is pin header on the board and standard header on the wifi module.

Watchdog is initialised in the bootloader, so a iwdg reset is required before the 2sec timer expires. Application address is 0x08001000 ( 4k offset from bootloader start address ).

Code was very similar to that posted by mane2. Hardware was Skpang triple can board, just used for Initial testing and balancing of BMW battery pack.

In the version I did for Teensy 4.0 I moved OUT5 and OUT6 to pins 3 and 4 as they were on the can bus pins ( 22 and 23 )

2020 gen2 pack.

This is what mine looks like with the blue shroud removed.

If you are not using one of the charging interfaces then why not just connect CP directly to the charger? In that case the cp spoof is not needed. As you have found CP_PWM does not work as Damien described in the video, setting it to a specific value is ignored as the line of code that would use ...

Ferrari F405 or STM32F405? I assume the later but this could be better reflected in the thread title.
There is a version of libopeninv library for the STM32F40x but the last update was Feb 2022, so will not work with most recent code. There are major changes in the CAN setup with the splitting of ...

Picture from wiki showing unused pin. https://openinverter.org/wiki/File:Gen2 ... _board.jpg

A google or wiki search would have easily found this but here it is.
https://openinverter.org/wiki/Nissan_le ... ter_plates

I don't understand it well enough to explain how it works but the callback occurs in CanHardware::HandleRx.

There is no need to use can_receive() directly. Can call back is set like this FunctionPointerCallback cb(CanCallback, SetCanFilters); but in ccsclara, I think, the can is all handled using ...