openinverter forum

Jack Bauer wrote: ↑Thu Jun 10, 2021 5:57 pm Have you selected GS450H from the inverter menu?

Dilbert wrote: ↑Sat Jan 02, 2021 3:50 pm OK, i can select GS450H now and i'm seeing HTM / REQ & CLK being generated. All 3 signals look good.

I'm not getting anything back from my inverter on the bench on the MTH line, so i'll need to investigate that a bit more. I have flipped REQ and CLK in the harness, so that should be ok. I'm going to scope the inverter connections and see if i can spot anything.

chuuux wrote: ↑Fri Jun 11, 2021 8:31 am

Dilbert wrote: ↑Sat Jan 02, 2021 3:50 pm OK, i can select GS450H now and i'm seeing HTM / REQ & CLK being generated. All 3 signals look good.

I'm not getting anything back from my inverter on the bench on the MTH line, so i'll need to investigate that a bit more. I have flipped REQ and CLK in the harness, so that should be ok. I'm going to scope the inverter connections and see if i can spot anything.

So, I have exactly the same troubles with serial communication between the inverter and VCU. HTM / REQ & CLK being generated and nothing on the MTH line.
Should every line be connected to negative pair contact on the other side, right? like REQ+ -> REQ- ?
And also I don't have any voltage on the "Inverter power", "Precharge" and "Main contactor" pins in the "Run" opt mode.

Jack Bauer wrote: ↑Fri Jun 11, 2021 5:09 pm First : make sure you are wirring as per the wiki : https://openinverter.org/wiki/Lexus_GS450h_Inverter

Is it a GS450H inverter or some other variant?

Dilbert wrote: ↑Fri Jun 11, 2021 5:31 pm My problems were all of my own making and based on my wiring .

Based on your above description, you are seeing nothing on the MTH lines coming from the inverter. So either the inverter is not seeing the REQ signal or the inverter is not seeing the CLK line. Once the inverter gets both these signals it will output data on the MTH.

One technique i used for debugging mine was doing continuity checks from the 4 CAN drivers on the VCU all the way to the inverter connector, checking that each pair was connected correctly.

Jack Bauer wrote: ↑Fri Jun 11, 2021 6:10 pm The 2013+ is a different inverter and most like uses a different serial stream to the older model.

chuuux wrote: ↑Wed Jun 16, 2021 4:30 am I've tried to get MTH signal from 3 different inverters with the same results: Camry 2013, G9200-30070 (Lexus GS300h I guess), and Toyota Aqua (I choose Prius Gen3 in the web interface with it).

Jack Bauer wrote: ↑Wed Jun 16, 2021 12:24 pm Did you do make get-deps?

EV_Builder wrote: ↑Wed Jun 16, 2021 7:26 pm I think that If you use the clone option you need to doit with the recursive option. Then it will also get the dependencies.

Dilbert wrote: ↑Thu Jun 17, 2021 10:28 am Here is the initial enum for the VCU States, I'll code up something in the next couple of days to test on the GD_Zombie

enum VCU_STATES{
SYSTEM_INIT_STATE,
SYSTEM_LOW_POWER_IDLE_STATE,


SYSTEM_PRE_CHARGE_B_MINUS_CHECK, // should see zero current as we close pre-charge relay, if a B- contactor used
SYSTEM_PRE_CHARGE_TEST, //should see zero current as we close B- contactor
SYSTEM_PRE_CHARGE_ACTIVE, //close Pre-charge contactor
SYSTEM_PRE_CHARGE_COMPLETE,//close B+ Contactor
SYSTEM_PRE_CHARGE_FAULT,


SYSTEM_INIT_CHARGE,
SYSTEM_CC_CHARGE,
SYSTEM_CV_CHARGE,
SYSTEM_CHARGE_COMPLETE,
SYSTEM_WAIT_FOR_CHARGER_DISCONNECT,



SYSTEM_HV_READY, //waiting for throttle == 0
SYSTEM_NEUTRAL, //waiting for gear selection
SYSTEM_STOPPED,
SYSTEM_MOVING, //provide torque request to inverter

SYSTEM_DISCONNECT_CONTACTORS,
SYSTEM_DISCONNECT_WAIT, //return to low power state

SYSTEM_DISABLED,

SYSTEM_GENERAL_FAULT

}

EV_Builder wrote: ↑Fri Jun 18, 2021 7:44 am

Dilbert wrote: ↑Thu Jun 17, 2021 10:28 am Here is the initial enum for the VCU States, I'll code up something in the next couple of days to test on the GD_Zombie

enum VCU_STATES{
SYSTEM_INIT_STATE,
SYSTEM_LOW_POWER_IDLE_STATE,


SYSTEM_PRE_CHARGE_B_MINUS_CHECK, // should see zero current as we close pre-charge relay, if a B- contactor used
SYSTEM_PRE_CHARGE_TEST, //should see zero current as we close B- contactor
SYSTEM_PRE_CHARGE_ACTIVE, //close Pre-charge contactor
SYSTEM_PRE_CHARGE_COMPLETE,//close B+ Contactor
SYSTEM_PRE_CHARGE_FAULT,


SYSTEM_INIT_CHARGE,
SYSTEM_CC_CHARGE,
SYSTEM_CV_CHARGE,
SYSTEM_CHARGE_COMPLETE,
SYSTEM_WAIT_FOR_CHARGER_DISCONNECT,



SYSTEM_HV_READY, //waiting for throttle == 0
SYSTEM_NEUTRAL, //waiting for gear selection
SYSTEM_STOPPED,
SYSTEM_MOVING, //provide torque request to inverter

SYSTEM_DISCONNECT_CONTACTORS,
SYSTEM_DISCONNECT_WAIT, //return to low power state

SYSTEM_DISABLED,

SYSTEM_GENERAL_FAULT

}

Please implement in C++ with a base class which can be inherited by the application. Then we can easy customize the base class behavior. If you make the states more generic we can use the class as a base class for more devices. The next step is then to couple those statemachines in-between them. I prefer a statemachine per device instead of one big catch all state machine.

For a reference and examples i invite you to take a look at the packml standard.

For a VCU it means we should identify states of the vehicle only.
INIT
STANDBY
STARTING
RUNNING
STOPPING
STOPPED

Now in code it would be this (coming from the 'hidden' base class logic).

INIT()
STANDBY ()
STARTING()
RUNNING ()
STOPPING ()
STOPPED ()

In the stopped method we check if the charger is connected and we could start the charger statemachine to starting etc...