OK, thanks, they do change, and the 32 was incorrect. It's a very confusing trial and error process as the wifi disconnects every 30 seconds or so, so always a lottery if it actually refreshed or accepted the command.

A working config is:

can rx idcmin 1300 0 16 -1
With Orion settings:
0x514, PACK ...

Refresh the values on the webinterface.


idcmin and idcmax under "parameters" remain at the values I originally set, not what the BMS is transmitting. Should they reflect the received values?

The messages sent by Orion:
image.png

The custom config used (copied from that post linked above ...

Thanks, I have tried it the "old way", but will look into updating if that's possible.
Is there any way to validate that the correct value is received, or is it only possible by mashing the accelerator and see what happens?

There was actually a link to a thread on that page, I missed it:

viewtopic.php?t=1468

Will confirm...

Hi, creating a thread for this topic since I can't see it explained anywhere (please link if it has been)

On the SDU web interface, there is support for bmslimhigh and bmslimlow. I believe this is associated with a digital input from a BMS to give a fixed change of limits for "turtle mode" type ...

Massive thanks for sorting this out Tom! I was worried that my replacement Teensy was defective. But it's all working again now with the roll-back version.

Has anyone used the VoltBMSV2 code yet? My Simp was constantly restarting because the watchdog wasn't updating. I got it to "work" by commenting out the cleartime block of the main loop, but I'm wondering if this version of the code is still in progress. It's possible I just don't have the ...

Yes, I meant we changed from Zombieverter to "old" GS450H control board. May change back if the situation changes but the Zombie had too many issues that I wasn't able to solve myself.

As far as I know neither option has automatic gear change implemented. The Catphish version uses the brake ...

FWIW we finally swapped out to the GS450H Inverter Controller board, and it's been night and day in terms of understanding how to set it up, adding functionality and the development cycle. For my skillset anyway!

Already have working regen, a throttle map, current limit with PID control, safety ...

I’m just guessing here but it’d be worth checking tmphs isn’t too high and also that the brake signal isn’t switching on.

P.S. Also check that the inverter is getting a really good 12v supply. I’ve had problems switching it on when the 12v battery is a bit weak.


Thanks - I did check these and ...

Hi all, posting here in case other GS450H / Zombie users have any ideas...

This setup has been working rock solid for a year - when the drive is powered, it works fine and dependably, apart from the various control software bugs.

However it has developed a fault where it will just stop after about ...

Again, great that this regression is finally fixed! Thank you Damien.

I still experience what seems like a hard cut on idcmax - causes hard juddering once you reach the set limit, totally smooth if you stay below it. On GS450H, 1.11.A. Is this to be expected, or am I on the wrong version or wrong ...

Thanks very much, weird that it changed, and to such an "unusual" configuration!

I previously managed to send out some bytes on the UART3 (that is normally used for the wifi module) to try to trace and debug the code.

But in recent versions, I find I can't even read the normal data output to the module. This should be 115200 baud, 8N1, 3.3V levels.. Switching back to an older ...

Yes, saw the update on github and already tried this version 1.11A-

"Fix the non working idcmax param caused by move to float calcs in throttle.".

So it was a bug, and was at least partly related to the line I identified in utils.c, which is now
Throttle::IdcLimitCommand(finalSpnt, ABS(Param ...

Wondering the same thing myself, having been away from the project for a long time to work on other things, it seems that the same problems are outstanding:
No usable current limit, and some bug causing violent hard cut and re-application of torque
No regen
Hard cut for RPM limit as well.

It's ...

Hi all, just putting it on here in case anyone else researches the same thing:

Denso 92600-5SA1A

I think this is the compressor from the later "heat pump" version. It has the same type of connector, but I don't have success sending it the LIN message mentioned in the thread above.

If anyone has ...

The idea back then was that you create a deadzone by setting potmin to a higher value than it is at absolute minimum.
However the problem is that it makes detecting a faulty throttle pedal really hard. Therefore I changed the behavior to the opposite. So if it potval is ever outside of it's ...

Also from the 1.06A release notes:
"#Please check your potmin, pot2min, potmax, pot2max values: They are the ABSOLUTE minimum and maximum. Please set them in a way that the potval can never reach them, otherwise an error will be stored."

Has how these work changed? That seems to be the opposite of ...

Can everyone please update to the latest V1.06A code here :
https://github.com/damienmaguire/Stm32-vcu/releases/tag/1.06A
Following a few very intensive days testing and coding by some very kind patrons we uncovered a very significant bug in the throttle handling routine. This is now fixed ...

Jack Bauer wrote: ↑Fri Nov 18, 2022 6:42 pm you can increase throtmax. I just had it set low for testing. In other news there is a big bug fix release soon thanks to some fantastic work by one of my patrons.

That will fix the torque cut problem? Good news, we’ll wait for that and stop fiddling with it then

You are right about the possability of a loose connection and I am sure you know how hard it can be to prove or find. I am using economiser contactors.

The use of the video was to demonstrate that precharge seems to be energised all the time.

Have you manged to road test yet?


I'm going to ...

Just been doing some testing on axle stands. First run of the day and I was trying to plot the Torque drop issue after changing a few parameters.

The usual torque drop happened and the torque plot dropped to zero. I took my foot off the accelerator and then tried to re apply a small amount of ...

You mean like

Throttle::IdcLimitCommand(finalSpnt, 5);

?


Never mind, I came at it another way.
-> Changed the code back to original
-> checked the problem still exists
-> changed the idcmax from 300 to 3000

Problem is gone (on the ramp at least).
So it seems to be a scaling issue, maybe just ...

update viewtopic.php?p=48720#p48720