Pseudo code, strategy for CAN PHEV control methods?

Please refer to page-9 of following document.
http://www.autoshop101.com/forms/Hybrid06.pdf

Ken@Japan

 

You should use two wires; CAN_L (low, pin 14), CAN_H (high, pin 6) compared to GND (ground, pin 5). To power your micro, there is 12 Volts on pin 16.
In my case the ELM interface will act as an interpreter, in you case you will have to interact with the CAN bus directly. That seems more difficult, let’s say it's a greater challenge.
I assume what is meant in the document is that the ELM can handle several protocols, on which page did you read about the six different messages?

Thanks Vincent and Ken for your input, it is slowly becoming clear to me how it all works.

Progress at this end: I added a label field that displays the interface identifier. When sending ‘AT Z’ the ELM responds with ‘ELM327 v1.3a’ and this is displayed as the caption of the label, also a button in the program that lights up from read to green. Now I need to do the same in order to check if the connection with the CAN bus is working properly.

Next thing will be a constant loop in which a the value of a variable is displayed. The rpm seems a good one to start with. Maybe I should put an extention cord to the car and program behind the wheel.

Still a long way to go and I wonder if we will ever be able to spoof the system the way we want but this is a lot of fun anyway.

 

It is the max if you're using COM port. If you're using USB, it can be set up to 500kbps (page 50). See e.g. on page 53.

Some owners are already using ELM327 with VB. Have you check the links I provided?

 

Sounds logical. Wouldn't the ICE stay off if the car assumes the SOC is still somewhere around 70% and you are still driving at low speed?

@ Vincent1449p: when writing the previous message I was in a hurry to get to work, but I will read those messages now. Hopefully I can do some more tests this evening.

 

Whom it may interest, a little about the VB code. The first time the MSComm.Input command is used it does not show the ‘>’ command prompt but it will after that. I captured the response to the ‘AT Z’ command in a string, it shows the sent command and the identification of the ELM bridge/interface, and used this routine in the Connect_Click() event. The string includes the initial command (it seems default the ECHO is ON), linefeeds and carriage returns so I had to clip them out. The result is displayed as the caption on a label so that other devices can be used as well.

It results in: ELM327 v1.3a
It takes about half a second before a response is given, so as a temporary measure I added a simple loop that does some needless counting and then continues. Not a very elegant solution but I will get to that later and put a delay timer in.

Next thing I did was see if I could get some information directly from the CAN bus. I use rpm because that is an easy one to start with.
This time it is returning 3 lines of 4 bytes each, and it takes a bit longer so I used a delay of about 2 seconds. I will tidy that up later and include it in a loop so the value is constantly updated.

Stripped of the ‘>’ prompt and the original ‘010C’ command the result with the ICE off is:

When revving the ICE a little the values were:

With the formula (( A*256) + B ) /4 I should be able to calculate the RPM and display the value. But I wonder why 3 lines of values are returned? This also happens in the RealTerm program so it has nothing to do with the VB code.

 

Hi Floyd,

Good to see that you are finally progressing with your Elm327 SOC spoofing project. I believe that such a device has to be connected close to the battery ECU on the CAN bus. This allows the device to capture the SOC message going out of the Battery ECU and change the SoC value. This information I found on Dick Norms website ://www.hybridinterfaces.ca]CAN-view index , I am taking a shortcut as i have a BMS+ on order which has SoC spoofing. Anyhow there is probably information about this on this website. Similarly there must a way to fool the ECM so that EV keeps staying on over 45km/h so the ICE will not start.

 

SOC spoofing will not make any difference in EV mode. But in stealth mode it should cause the the Hybrid ECU to draw more power from the HV battery pack to run the electric motor so more electrical power is drawn. The same applies during ICE assist mode.

 

The problem of SOC spoofing is that you need to keep monitoring the real SOC. Otherwise if the real SOC strays outside the 40% and 80% limits the Toyota HV battery will most likely be damaged. So Floyd needs to write a VB program to calculate the amp hours going in and out of the HV battery and calculate the SoC whilst spoofing and then you can setup the fake SoC to be 10-15% higher than the real SOC.

If the real SOC runs down to 0% it can kill the HV battery. If the real SOC runs to 100% and the HV fan is not running the HV battery could explode. At the very least you would be shortening the HV battery life.

 

A lot of answers to your questions can be found on this website

(www.hybridinterfaces.ca)

 

I read that this BMS
48 cell system: $950 | Orion Li-Ion Battery Management System
is a pin-for-pin replacement of the battery ECU. It manages your lithium packs, and gives the desired data to the prius. so while your lithium pack is 100% to 30% it will report 80% SOC and a high CDL to the prius (making it want very much to discharge the battery) and then once your lithium pack hits 30% it'll tell the prius 65% SOC to make it happy not to draw or charge the battery too much (normal prius mode).


I don't think the price of the big PHEV kits is outrageous, there is probably $2,000 or so profit in each.

 

bump
did anyone get anywhere with the soc spoofing?
or after trying gave up and got a device already doing this ;-)