There is now a new build of the simulator on the "combined" branch. This supports both F103 and F405 builds so will hopefully simplify my life maintaining it in the future. This should be a bit more robust to changes in parameter definitions in the OI project. Instead of having specific pa...

Romale wrote: ↑Tue Jun 20, 2023 1:01 pm and where can I see the settings file of this motor and the pinout drawing of the resolver socket? I recently bought such a motor, but I haven't figured out the connection yet

Best data I'm aware of is herehttps://openinverter.org/wiki/Mitsubish ... Drive_Unit

Thanks to @FFMan for taking some logs we now have data for the Outlander rear motor

Lq=0.36mH, Ld=0.20mH, Flux Linkage=60.8mWb, Rs 27mR

Also added to summary of motor data post here : viewtopic.php?p=52763#p52763

Domt177 wrote: ↑Tue Jun 20, 2023 9:12 am Yes I bought it from a scrap yard, used it with a leaf motor which worked (but I had the settings wrong so it only juddered)

Do you have the Toyota part number for it and/or a picture? Also what logic board is in it, is it still the Toyota one?

Interested in the Prius gen3 inverter, do you have any more details?

The logging code is now integrated into the auto-setup-withlogging branch on my github. Tested mainly on my F405 build but also on a F103 bluepill board (no motor connected on the later though so can't be totally sure the data is going through correctly but it looks believable). This now uses a zero...

Just pushed the timer_reset_flag() change. Pete, where can I find your latest logging code with the 1-byte spot value thing? Wouldn't mind integrating it into the PWM routine. I'll refactor it anyway as I already had the "SOMETHING_LIST" thing done. Pushed it back to the F103 code earlier...

Do you have the capacitor pack connected?

When I first powered mine up I didn't and it took a while to realise that you need different HV bus connections without it.

The possible firmware issues identified in another thread today have made me realise that I need to rewrite chunks of the logging code. The current F405 implementation is a hybrid of the two previous versions and runs a lot of the logging in the terminal thread, the issues have made me realise that ...

Need to get the logging sorted!! Just had a look through the CAN code, can't see anything that would produce the above but can see a way for transmit messages to get corrupted. Messages get sent from the scheduler thread via a call to Can::Send, if a hardware transmit buffer isn't immediately availa...

Good call. Though NOT calling the Ms100Task for extended periods (like 2s) would trigger a HW watchdog reset. Still, if enough calls were missed, it could just not see the brake signal on time. Literally just realised the watchdog bit and was just about to update the above! Don't really believe the...

Now that's not good :shock: Looks a bit like the 100ms scheduler task may not be running as this is where VehicleControl::CruiseControl() is called from and the brake input is read, everything else is done in the 10ms task which is obviously still running. Not too sure why this is the case though. H...

Not sure it's extending as such, think it's more reducing the limiting that is there to protect the battery on the lower power inverters.

Should it be this? y = ((canMsg.data[4]*256) + canMsg.data[3])/4; If canMsg.data is an unsigned char you may need the following cast too (the 256 should be an int anyway so probably not needed but good practise in any case) : y = ((((unsigned int)canMsg.data[4])*256) + canMsg.data[3])/4; As mentione...

I have similar reservations on WiFi in cars. My approach is to move the ESP32 off board by using a RS485 link from the OI board. This still gives a high bandwidth data link but allows the ESP32 to be positioned for good signal strength and low noise. It also allows it to be unplugged when not needed...

Had a bit more of a think about this and have decided that the current gui could really do with a proper update, the fixed OI parameter fields were nitially quick to do but are now too inflexible and too easily broken by OI code changes. The above idea goes some way to fixing, and the param::change ...

Bigpie wrote: ↑Thu Jun 15, 2023 8:12 am You're welcome to come mess around with my setup if you want.

Thanks, that would be good.

Probably makes sense to get the logging code ported across first though (and I could do with getting my laptop sorted out too - needs the OS updating and all the dev tools putting on it).

Bigpie wrote: ↑Thu Jun 15, 2023 6:35 pm Resolver Check working for me in auto tune.

That's great!

Bigpie wrote: ↑Thu Jun 15, 2023 6:35 pm Will hook up some some voltage next

Look forward to hearing how you get on (let me know if there is anything I can do to help).

I'd like to move away from needing to change the gui whenever parameters change so am thinking about changing it so that the user can enter say any 10 parameters by name and then edit them from the gui. The main issue with this is the sim would need to call the standard Openinverter param::change fu...

Is the resolver issue using the auto setup code or 5.27? If the former then it's sounding increasingly likely that I've messed something up in the code (Romale had a similar issue).

Got a logging setup here now using an old bluepill board but haven't got anything done on porting the code over yet.

Wondering whether the param_prj.h file in the simulator project directory could now just be deleted (the one in the OpenInverter source code would then be picked up and used by Qt instead and would still need modifying to suit your motor). If so it should fix the above problems. Trying to remember w...

Thanks for the heads up.

Looks like it's due to the changes on the param_prj.h file in the new release, probably just needs the Qt project version of the file updating to match the new format. Will try to have a look in the next day or so.

Also worth bearing in mind that the engine mounts aren't just there to support the engine, they also have to cope with the full torque reaction from the drive/prop shaft and with a GS450h box in low gear that could be substantial. In particular one mount will be in tension under acceleration and wit...

You might save a bit of money but you will be trading that for uncertainty and time. Lexus will have spent 1000s of hours tuning the inverter to work with the motor, changing to a different Lexus inverter may still work well, or well enough but it might not (all depends on how similar the motor and ...

That doesn't sound right, the measured values seem way too low. Just checked on my motor and read 15k on both sensors which is more the kind of value I would expect. For reference the resolver measures around 36R on the exciter and 77R and 80R on the sin/cos outputs. Pull down doesn't sound right ei...