hobDrive Support

Hello, I need to convert these type of settings for hobd, but I'm not sure where to insert the header.

Name, "ShortName", "ModeAndPID", "Equation", "Min Value", "Max Value", "Units", "Header"
Fuel Input, "flv", "2129", "A / 2", "0", "127.5", "Liter", "7C0"

I created these parameters, but do not work. The pid works correctly on Torque

<parameter id="Fuel_Input">
<description>
<name>Fuel input</name>
<unit>liters</unit>
<description>Fuel input</description>
</description>
<raw>2129</raw> <--I also tried 7C02129
<valuea>1</valuea>
</parameter>


This parameter works perfectly:

State of Charge,"SoC","015B","20 / 51 * A","0","100","%","7E2"

<parameter id="State_of_charge">
<description>
<name>State of charge</name>
<unit>%</unit>
<description>State of charge</description>
</description>
<raw>015B</raw>
<valuea>0.3921</valuea>
</parameter>

what is wrong in Fuel Input?

thank you very much

Hello Christian,

Thanks for purchase!

The first It looks correctly at most, but please try this:

Код: Выделить всё

<valuec>1</valuec>

The reason is when you use rawcommand, the reply bytes offset includes the header of the reply (which is extra 2 bytes).

Also, please enable TRACE logging (in system settings) and put here the log.txt file. We'll see whats happening.

is that possible for hobdrive in next future, all cars catalogue would be available, so we just need choose our car and the parameter would be filled automatically? so it's possibly simply vehicle setting
Go HobDrive Go!

Hi Cail,
I tried many parameters, but no one returns the correct value (19.5 liters).

I tried to interpret the logs, but I did not understand what values ​​should I read, I think the problem is 7F. 7C should be .... I think!

[TRACE] 01/01/2009 11:22:00 PM.137 [OBD2Engine] -> SENSOR
[TRACE] 01/01/2009 11:22:00 PM.154 [OBD2Engine] ----> Extra.Fuel_Input_c
[TRACE] 01/01/2009 11:22:00 PM.171 [OBD2Engine] sendCommand: 2129
[TRACE] 01/01/2009 11:22:00 PM.196 [OBD2Engine] -> SENSOR_ACK
[TRACE] 01/01/2009 11:22:00 PM.356 [OBD2Engine] HandleReply: 7F 21 12



tks

Christian,

Think this is the header which should be settled up separately. Hobdrive now does not support header setup per message, but I'll look into this.

For now, you can try reading these PIDs by setting header in ELM Init string (vehicle settings):
ATSH 7C0

This however most probably will lead to the issue where the regular OBD2 PIDs are no more available.

ok thanks, this could be a problem. I have this list of pid for my toyota with different headers, try setting the init ELM.



tks.

ok I tried the set command header (ATSH 7C0) and the fuel sensor works, but I lost all the other sensors. For now, I used the command ATSH 7E2 is to have sensors that OBD2 other active sensors toyota.
I hope you can modify to read other headers in the future! I have other interesting sensors.

Another problem I need to read the values ​​of D, E, F, G, but if I put <valued> or <valuee>, hodb does not recognize them. what is wrong?

example:
Inverter Coolant Temp, "ICF", "2175", "D", "-40", "100", "C", "7E2"

tks

I'll checkout on this, hope it'll be not so difficult.

Another problem I need to read the values ​​of D, E, F, G, but if I put <valued> or <valuee>, hodb does not recognize them. what is wrong?

Think thats a limitation, I'll improve this as well.

Now you may read any offset f.e. with <value-7>, but only via <base-raw> indirect extra sensor. See some other ecuxml files on how <base-raw> and <value-XX> are used.

Hi, the latest 1.1.70 beta supports custom headers in ecuxml.
Checkout the updated prius.ecuxml inthere!