[808AWD325xi]

Hi Node,

I wrote a quick INPA script to test your control application. It does in fact work, but perhaps not in the way you intended.

This is a screenshot of my test script. I was not connected to a car, nor did I have an EDIABAS interface attached to the computer:


I executed your control application prior to executing my test script.

My test script calls the same SGBD as the INPA main menu. It calls the UTILITY SGBD to determine the battery and ignition status. For the battery status, it executes the STATUS_UBATT job which returns STAT_UBATT and for the ignition status, it executes the STATUS_ZUENDUNG job which returns STAT_ZUENDUNG:

The UTILITY SGBD does not truly read voltage. To illustrate this, my test script calls the INTERFACE job which returns BATTERIE. BATTERIE is supposed to report Terminal 30 [KL30] voltage in millivolts:

Code:

[...]
  INPAapiJob("UTILITY","INTERFACE","","");
  INPAapiResultLong(long_var,"BATTERIE",1);

  text(5, 5, "Battery Voltage per SGBD UTILITY INTERFACE Job:");
  longtoreal(long_var, real_var);
  real_var=real_var/1000;
  multianalogout(real_var, 6, 5, 0, 22, 12, 16, "", 1);
[...]

BATTERIE will always return 14000 mV. Your control application is able to adjust that value.

The reason that the ignition is off in the above screenshot is because I set the ignition voltage to 9.9 V.

I hope that this additional information helps to clarify things.