Zombie + GS300H Inverter Communication

[Marvin]

Hi all,

I have been checking all my connections and parameters the last days and yet I have no success to get to INVStatus "on". I even switched inverters to rule that one out. All other things like the Relay for 12V+, direction Switch, Sbox are working as they should. Is someone able to point me into a possible direction? I hope the attached documents and the WebUI make my mistake apparent.

Thanks in advance for the support.

Best Marvin

[tom91]

IS300h has a known issue in V2.20A can you try the previous V2.17A to see if the comms work.

[Marvin]

Good to know! Under 2.17 I had the same issue. But it used to work in the past so maybe I just need to go back further. Great then I will give that a try tomorrow. Thanks Tom.

IS300h has a known issue in V2.20A can you try the previous V2.17A to see if the comms work.

[tom91]

But it used to work in the past

I would go back to the version you had it working. It is likely you made changes to your setup after that caused comms problems.

[Marvin]

Ah one more point how do I correctly Reset the Zombie? As this is listed as an Issue with Toyota drivetrains?

[tom91]

Reset the Zombie

What do you mean?

[Marvin]

https://github.com/damienmaguire/Stm32-vcu/releases

NOTE : If you are using a Toyota drivetrain the VCU MUST BE RESET after loading new firmware or the inverter will not start.

[tom91]

As in powercycle the setup. It is key the inverter relay is used so that the Zombie starts comms and provides 12V power to the inverter in the right sequence.

[Marvin]

Hi again, so I have restored the Zombie to V2.05A. Inverter gets both 12V & HV (87V). But I still do not have any communication. What version are you guys running with the GS300H setup? Is there any obvious things I should check to get the inverter to spring to life? Are Grounding issues a thing (I mean I should have a good ground but …) I am just puzzled. Back in the day I had HV connected without the Sbox but that should not stop it? Relay for 12V to the inverter is also fine. I mean it is 8 wires…

Anyways any help is welcome.

Best Marvin

[tom91]

The latest release works the one released today 2.22A, so does any version except for 2.20A

[Marvin]

Hi again,

after flashing the newest V2.22A today and setting UDCmin to 0. + Reterminating the connection I am getting succesfull inveter whine. But I believe I am stuck at no potnom change (as so many) but all tips have to far not changed. If I start the inverter with drive direction already enabled I sometimes get some slight motor movement. Can someone pinpoint me towards a solution? I also referenced the example setting and they did not change anything.

Motor and Inverter are grounded to the Battery directly. Battery voltage is at 87V
12V Batt is connected to a charger so should be fine.

Pot 1 & 2 are changing values when pedal is pressed.

Best Marvin

[tom91]

Please show your spot values too.

Get the inverter into RUN opmode and dir as fwd then grab screenshots of the spot values please.

[Marvin]

Hi Tom, Please find them below. ONCE with Pedal pressed and once without.

[tom91]

Does it show a potnom with throttle in single potmode?

Does it show a potnom with forward direction selected?

Please plot pot and pot 1 on left and potnom on right.

[Marvin]

Hi Tom,

as requested.


... it feels like I am so close thanks for the help.

[tom91]

please set udcmin to like 30. Does anything change?

None of this seems to make alot of sense since I done a bunch of bench testing and have not run into this behaviour. Something is forcing it to o.

[Marvin]

Just tested it unfortunately no change.

I guess tomorrow I will do the following:

- Re-check wiring Inverter to Resolvers,
- try with the second inverter I have
- re-flash an apply Damians e46 file for parameters (is there a new loader for V2.22A?)
- pray to the ev gods

anything else I should consider? Motor three-phase wiring can be ruled out as an error source or? Could I manually apply a potnom value somehow for testing purposes?

Cheers for the support.

[tom91]

No this is nothing to do with the inverter.

The throttle pedal should be converter to the potnom regardless.

I can check on my bench to see if I can replicate it.

[tom91]

One last thing to try is set idcmax to 0, this will bypass current limit logic.

[Marvin]

Will try that first thing in the morning. Thanks

[Marvin]

Hi Tom, so setting the value to 0 did not change anything. Also not under V2.17A

I guess the Pedal is wired correctly as I am getting Pot and Pot2

Could grounding cause this?

[tom91]

Could grounding cause this?

No as I said its something particular to your param configs somehow. I will get my bench setup setup and test in the next hour.

[tom91]

My Benchtest findings:
1. Potnom only plots with direction selected - probally due to all the new features it no longer works before selecting a direction
2. udcsw needs to be 0 to go into run on the bench without voltage
3. udcmin needs to be 0 to get any potnom with direction selected
4. single or dual channel both work

Attached are a screenshot of my spotvalues and params.
A picture of a plot including direction
Params from my benchtest

Note:
Bench test Zombie is only connected to 12V supply, a bench test button setup (start/ign ect) and a dual hall throttle. Nothing else is connected.
I also wiped my Zombie and flashed the CAN bootloader and 2.22A release HEXs fresh

[Marvin]

Thanks Tom,

Alright i tried the following and get an interesting error. First i applied all parameters manually but UDCsw always jumps from 0 to 66,… V somwhere 20v below UDC.

I reset and flashed the Hex. Earlier i updated to V2.22 via the bin.

But same result. Fresh flash, apply parameters file only adjustment Pot min and max.

I assume UDCsw should not just jump around to a different value? Looks like a live value it is referencing.

[tom91]

UDCsw always jumps from 0 to 66

Yes because you are putting 86V into your Sbox, I am not running an Sbox.

Please check all your params against mine.

Leave the inverter connector removed for now, it is not needed to get potnom working.

You should get into run mode, without errors. then map:

L- pot & pot2
R- dir & potnom

Plot

Select drive

Press pedal.

literally what I did on the bench using the HEX file from the release. (I am not using the Sbox, but only have it configured)