Inverter Firmware 5.32.R

Yahha777
Posts: 52
Joined: Wed Feb 27, 2019 7:03 am
Location: Belorussia. Borisov
Has thanked: 15 times
Been thanked: 1 time
Contact:

Re: Inverter Firmware 5.32.R

Post by Yahha777 »

johu wrote: Sat Sep 16, 2023 12:58 pm I guess this was bound to happen. With this software there is no way to exchange throttle signal between inverters. Simply due to the lack of a running counter that can be mapped to CAN.
This suggests that the board from a Prius (Yaris) with two controllers can no longer be controlled as before, or I read the instructions upside down:https://openinverter.org/wiki/CAN_commu ... _CAN_-_new!
User avatar
johu
Site Admin
Posts: 5807
Joined: Thu Nov 08, 2018 10:52 pm
Location: Kassel/Germany
Has thanked: 161 times
Been thanked: 1037 times
Contact:

Re: Inverter Firmware 5.32.R

Post by johu »

No, not with this version. With the next release I will add a cyclic counter that satisfies the control message requirement. CRC checking can be turned off on the receiving side.
For now you can stick with version 5.27.R on the receiving side to retain the functionality
Support R/D and forum on Patreon: https://patreon.com/openinverter - Subscribe on odysee: https://odysee.com/@openinverter:9
Yahha777
Posts: 52
Joined: Wed Feb 27, 2019 7:03 am
Location: Belorussia. Borisov
Has thanked: 15 times
Been thanked: 1 time
Contact:

Re: Inverter Firmware 5.32.R

Post by Yahha777 »

The "pot" and "pot2" parameters are not saved on both controllers (that is, Rx and Tx) after a power failure. Before the power is turned off, everything works and the slave controller receives messages identical to the master. Is this a feature of the firmware? Or am I doing something wrong? I haven't tried it since 27.
Image MG2
Image MG1
Attachments
Screenshot_20240221_225240.png
pot.png
User avatar
johu
Site Admin
Posts: 5807
Joined: Thu Nov 08, 2018 10:52 pm
Location: Kassel/Germany
Has thanked: 161 times
Been thanked: 1037 times
Contact:

Re: Inverter Firmware 5.32.R

Post by johu »

Indeed 5.32 removes any mapping from pot and pot2, even TX mapping. That should be changed. So 5.27 on both sides. You need to hit Save to Flash to make mappings permanent
Support R/D and forum on Patreon: https://patreon.com/openinverter - Subscribe on odysee: https://odysee.com/@openinverter:9
Yahha777
Posts: 52
Joined: Wed Feb 27, 2019 7:03 am
Location: Belorussia. Borisov
Has thanked: 15 times
Been thanked: 1 time
Contact:

Re: Inverter Firmware 5.32.R

Post by Yahha777 »

johu wrote: Fri Feb 23, 2024 9:19 am That should be changed. So 5.27 on both sides. You need to hit Save to Flash to make mappings permanent
Yes - everything works with the previous firmware. The settings are saved.
Spot_values_MG2_Tx.png
MG 2 sends
Spot_values_MG1_Rx.png
MG 1 receives
can_map_MG2.png
But nothing is displayed in the CAN map. But this seems to be a problem in the web interface. In the old (gray) mode, all CAN data is visible.
wacomg
Posts: 11
Joined: Mon Dec 21, 2020 12:27 pm
Has thanked: 1 time
Been thanked: 1 time

Re: Inverter Firmware 5.32.R

Post by wacomg »

Hello !
I have this setup :
Prius Gen2 Inverter
Prius Gen3 MG2 , engine is a bit loaded with another one, which is connected to another Gen2 inverter (switched off )
60v LiFePo battery
board made with prius-gen2-v1.1.zip from johu's github

firmware 5.32
defaults loaded, resolver shows angle, pot calibrated ( i use single pot)

pinswap 5 : MG2 didn't move at all with any syncofs settings
pinswap 7 : i'm able to find both syncofs

first syncofs: "enter a small value for "manualiq" and set "manualid" to 0.1, the motor" spins "smooth in both directions"
second syncofs: motor spins only in one direction

i've chosen first .

Now try to use pot and direction swith . Start pressed, direction , pot .. on small pot values it rotates , but after some point it tries to overspeed . After reading forum i found something about field weakening . Then i played with fwcurmax parameter and realised that motor works correctly with 0 > fwcurmax > -80. But in this case i can't get more than 80A

current with any values fmax,ocurlim,throtcur

Seems like fwcurmax limits max current

what to do next ?
Post Reply