Hyundai Coupe/Tuscani (Siemens ECU)

[cail]

Hi,

1) thats a junior school: = A*0.78125 - 100
)

2) Name it "FuelSystemStatus". If current value is 0/1, then multiply it 1024.

3) "fuel coefficient value" - whats that? For injector you only put number of cylinders, and injector performance (half value - 95) into vehicle settings.

4) Don't know how to locate it, but try to find slowly increasing "celsius like" value.

ps. doing now power/torque calculations, will give you soon a beta to try.

[cail]

Sent you a beta with Power&Torque.

Torque is probably invalid (should do some more math
Power is underestimated (it should also take into account air resistance, fuel in tank mass)

[alawadhi3000]

Junior school.

I didn't understand number 3, whats the injector performance in ms? The only thing I can find about the injector is that the size is 190cc/190ml.

I've having another problem, how do I get the STFT1 and LTFT1 to show at the "Fuel Trim" tab or "Lambda" tab, if I named it "STFT1" for example it still won't show in the Fuel Trim screen, same with "Oxygen_b1s1_stft" for Lambda.

Also Idle time in fuel economy still goes up even if the car is not running.

About Power and Torque calculation, they are largely off, after an acceleration run it said that my car is 273hp (which clearly is not because my car is ~185hp), also that value needs smoothing, you need to take like the last five speed readings and get the HP from there, because now if I cruise slowly it will say 0HP unless the speed changes, whenever it change it will display like 20HP for 0.5s and it'll get back to 0. The last thing is you already know is that air resistance should be taken into account (also you need to put the Drag Coefficient and Frontal Area into vehicle settings).

Thanks.

[cail]

3) This means you should put 95 (190/2) into the injector performance in vehicle settings.

I've having another problem, how do I get the STFT1 and LTFT1 to show at the "Fuel Trim" tab or "Lambda" tab, if I named it "STFT1" for example it still won't show in the Fuel Trim screen, same with "Oxygen_b1s1_stft" for Lambda.

Hm.. it should. Double check the names (typo?)

Also Idle time in fuel economy still goes up even if the car is not running.

Even with the ignition off? That could be because hobdrive fails to detect that your ECU is unavailable. Can you give log.txt with TRACE, reproducing this situation?

About Power and Torque calculation

Thanks, know that. Just a first tryout. If possible, could you capture a log.txt (in TRACE level) during a good acceleration? This'll help me to compare power/torque results with my own...

[alawadhi3000]

No, there is no typo, names are straight copy and paste from hobdSensors.html or other XMLs.

For the idle time, no It doesn't happen with ignition off since the ECU won't communicate without ignition, it happens when Ignition is on and the engine is off.

Will do the log.txt for the run, give me a couple of days though.

[alawadhi3000]

The attached log is for a 0-100KM run.

I still can't get the STFT1 and LTFT1 to work, O2 sensors are displaying fine but no matter what I put as a name for the Fuel Trims they won't show in the program.

Also, I filled the Excel sheet that was made from a log file when I was refueling, I had about 3-4L in the tank and I had put 51L (Tank is 55L), I can't get which value is the fuel sensor, if you have some free time please take a look at it, disconnecting the sensor is a no go since it is at the fuel tank and will take too much take to get there.

Thanks.

[cail]

Alawadhi, thanks!

Can you share your current ecuxml file? I'll check it for errors regarding LTFT.

Fuel level sensor is often not available to ECU, so there could be a chance you just don't have it.

[alawadhi3000]

I'm pretty sure my ECU can see the Fuel Level, because by looking at the service manual, it says that the ECM sets DTC P0461 if ECM detects that fuel level change from maximum to minimum is less than the threshold value.

Plus there's a signal wire that goes from the Fuel Level Sensor to the ECU.

ECU XML is attached.

EDIT:- The sensors that does not work are STFT1, LTFT1, Lambda fuel trims and Timing Advance.
EDIT2:- I have found out what is the problem with the XML, anything below TimingAdvance won't work. Weird !

[cail]

I see only value in CD (offset 81) changes in increasing way. try it. FF(255) seems to be 100%

[alawadhi3000]

Thats whats I figured, however I doubt that it is it. I'll monitor it closely these days.

Did you look at my previous edits? TimingAdvance is the culprit, any sensor below it won't work.

[cail]

your 'degree' character is in invalid encoding.
either resave it in Utf-8 encoding, or just write
<unit>degree</unit>
(hobdrive will replace the long name with degree character)

[alawadhi3000]

Working fine now with "degree".

Fuel Level is not the CD column unfortunately, maybe the sensor is there in 2102 command instead of 2101.

The program now gets a reading every 300ms-400ms, I now that my car is not using the fast CAN protocol and instead uses a slow 10.4kbps KWP protocol, but is there any way that I speed up that a bit?? since I'm only using one command instead of like 20+ for OBD-II.

Also is there a definition for the Absolute TPS sensor in Hobdrive? I don't see that in the sensors html.

Thanks.

[cail]

There are some commands to tuneup ELM performance, but they are not 100% effective. you may add ELM init commands from "ELM Aggressive timing" and "ELM short tmo" templates.
But notice that for KWP the preference is that each 300ms you normally get all the sensors.
In obd2, each 300ms you get only one sensor.

Absolute TPS

You may introduce whatever sensor you want. It is not required for all sensors to be in html.

[alawadhi3000]

I took a look at the ELM327 datasheet, so I used ATAT0 to disable auto timing and ATST10 to set the timeout to 64ms, still I'm getting ~350ms.

I also tried using ATAT2 to set it to auto aggressive timing, still the same ~350ms, however I noticed a weird thing, when I go to the sensors tab I get ~200ms only while in the general tab it is ~350ms, does that mean Hobdrive spend the extra time calculating values?? Because I get all my sensors using one command.

[cail]

You use hobdrive on win32 system, right? there should be no such a big differenct on it.
Calculation takes time, but not so much.
Can you first check that loglevel TRACE is disabled (this may impact..)
If that doesn't help, please reproduce these two different timings with DUMP logs enabled, and share the log.txt - I'll check this out.

[alawadhi3000]

Yep win32 version, I use it on an AMD E-350 processor, not that fast but more than enough for light apps like Hobdrive, also Trace is Disabled.

You want two logs (one for the sensors tab when it is fast) and one for general tab (when its slow)? Or only one log using both??

[cail]

two separate logs would be easier to analyse, thanks.

[alawadhi3000]

They are attached.

[alawadhi3000]

Anything new?

[cail]

to be precise, the stats shows 223ms vs 376ms in average.
That could be due to excessive updates of a graphics.

Could you try adding into user.gauge the following line:

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

  <gauge id="*" cache-interval="2000"/>

this'll cause charts to be redrawed only once per 2sec. I'm now adopting this setting into winCE version, because there a similar problem exists, but with worse timings.