Nistune Forums

ok, interesting.. I've got Nistune installed on my pc here at work so I can play with the bins and check out the cool improvements while my car is down.

There is no LM1 here..

but if I select com1, and Wideband, it gives me the same error.

both com2 and 3, when selected and clicked on wideband, Nistune freezes for a second, then reports 'Wideband Connection failed'..

hrmm.. maybe something just doesn't like Com1?

I'll try it with the usb guy tonight then.


NISTUNE LOG Jun 13 2006 00:16 0.906a
23:16:32 statusbar: Valid Communications port not selected for MTS
23:16:44 statusbar: Wideband Connection failed

i'll have a quick look at it also tonight when i get time

uugh i stuffed up a check that affected com1. ive removed that. the trace log will now indicate which port its trying to communicate with

no idea about the AFR not showing through. i'm just reporting AFR now 'as is' and also taking lambda and x by AFR mutiplier (assuming this is 14.7 if not I'll have to hard code that number)

i need log files to help me look at the voltages reported though

i got the protocol information for zeitronix also (another wb sensor) so that will be going in soon too!

oh yeah check the directory for next test version (2) also...

Here's a log from this morning (Innovate version 1). It appears that the input for the top right of the Wideband window is derived from rpm. I have the rpm converter installed and its the first input so that makes sense. It reads in the voltage format though. (0.12 = 1200rpm). The second input is active but I still cant tell which input its actually coming from.

Also, the wideband button doesnt seem to go red to indicate that its connected.

I'm not able to connect to Consult with the Innovate version. Version 905 works fine. Did you implement the new patch code that you mentioned before and this is causing a problem?

Also it seems that the debug logs are being saved straight to c:. Is it possible to have this changed so it goes to c:\nistune\ or something like it did before? Am I being dumb?

I'll try the next Innotave version asap.

yeah, not working on com1.. forced com1 to become com8.. worked like a champ..

I've got the sensor in my downpipe.. but the downpipes sitting on top of the car... so for this test, I flooded the sensor with mapp gas from a torch...

will try the new version tonight.

Otherwise, my experience is identical to Stinky's... haven't tried connecting to Nistune yet..

but I have noticed that the 'Nistune Communications Device" driver had stolen my usb-serial convertor (FTDI drivers)..

ok, getting an error when trying to connect to Consult

"error, could not load Nistune.dll"
next msgbox is
"FT_ListDevices is not valid!"
and the next is
"ListDevices failed"

this is on my work pc.. but the Nistune.dll shouldn't be erroring should it?

ok, this probably doesn't deserve it's own post..

but I found the NisTune.dll file, and tossed it in the same directory as the exe, and the errors went away..
now it's
"No NIStune USB device is connected to your PC"
..as expected..

probably just have the sub-directory hosed up someplace.

thanks for the logs guys. i'll make some more fixes tonight

- NIStune.dll file as a result of the installation package now used this was moved to a subdirectory but the app code not updated to reflect that. The next build will be ".\USBdriver\NIStune.dll" from the installation directory

- USB must use the next patch code version for ID. I have to finish updating the patch code and test those out. As a result these prelim releases wont work with USB devices....

- Logs show upto 6 sensors reported. AFR sensor is showing strange values however. I will need to use the correct Trace statement for the software to print out all raw data first. Not as much info from logs at I hoped, so will add some more trace code.

I have added the tracing in now.... please try this next version out (Innovate v3 uploaded)

ok, raw lambda equation

AFR multiplier is stochiometric AFR value of current fuel setting in the LM-1 times 10. E.g. 147 for gasoline (14.7).
Air/Fuel Ratio = ((L12..L0) + 500)* (AF7..0) / 10000

L12, I'm assuming to be a lambda value, AF I'm assuming to be 14.7..

tried it, here's the log
com1 issue: resolved

it reported "heating sensor" when it was warming up.

I can't remember, but does it report battery voltage as well? mines currently 10.4ish as reported on the LM1.. so it takes a while to heat up.

here's the log.. still not displaying AFR in the nistune window though.
*EDIT*
ok, running the equation I just posted with a value I picked out of my test

AFR=(7691 + 500) * 14.7 \10000
I end up with 12.04, which I do believe was a value that I saw while hitting the thing with mapp gas..

I think this is the right equation though..
The actual Lambda value is (Number + 500)/1000


Matt, I'll be up for a couple more hours tonight, and am home.. if you want to push out any updates for testing.. I'm all yours ;D

http://www.innovatemotorsports.com/foru ... #post21179

unfortunately i had to work so no more changes until tonight...

anyway i have fixed
- connect/disconnect button highlight. should work. please let me know
- Lambda / AFR settings for channel LM1_02 should both display as AFR with correct numbers now. please configure for both settings
- RPM will be displayed as an RPM entry in the consult dialog if consult not connected
- the other channels (2-6 configured by default) are not used for anything unless configured by logworks. currently they just display the raw sample data. if you wish to use two of these (aux1,aux2) for other purposes then you need to update the CSV files to match (lookup table). currently i think they are just floating voltages

ok, test4 here we go..

still not displaying the calc's AFR..
but the logfile is showing' "AFR is out of range..:##"

which.. I'll admit, the mapp gas I'm using is giving out of range values..

BUT! the AFR's displayed in the log, are in the same neighborhood that I saw on the test.

You may want to take off the range check? At least temporarily to test the display?

I'm around.


**EDIT**
the wideband bar did turn red..
but the display lost the 'heating sensor' portion.

also, could you patch up the 88SS_nt binary? That should give me some more testing ability ;D

Heres a log i did this morning. I'll have to check again but I dont think the Wideband button is highlighting as it should. I'll check again later. No AFR display yet but the data does seem to be coming in.

firstly the 0615-0945 log looks like the old one becuase i forgot to put carriage returns in the trace writes in the older version
09:45:52 Type: 009:45:52 Sample: 49009:45:52 AFR: 0.000000

looking at the AFR input from the latest log

11:39:09 Current input: 0
11:39:09 >Input name: LM1_O2
11:39:09 >Input type: 1 (AFR)
11:39:09 >Device name: LM-1
11:39:09 >Device ID: 0
11:39:09 >Device channel: 0
11:39:09 >Units: AFR
11:39:09 >AFR Multiplier: 14.700000
11:39:09 >Min value: 7.350000
11:39:09 >Max value: 22.388100
11:39:09 >Min volts: 0.000000
11:39:09 >Max volts: 5.000000

first thing i buggered up in the new code changes was the wideband status
11:39:10 Func: 4
11:39:10 Sample: 416
11:39:10 OnNewDataMts: Unsupported input type
11:39:10 Current input: 1

This should detect '4' as a status type like it did before... so will fix that soon

The next problem is that

11:39:46 Current input: 0
11:39:46 Func: 0
11:39:46 Sample: 7691
11:39:46 AFR: 120.407698

(7691 + 500 ) / 1000 = 8.191 * 14.7 = 120.40 not right

just checked that thread you posted on the Innovate forum

whoops i missed a zero that should be / 10000 to get 12.04 as AFR only / 1000 for actual lambda values

have to fix this sometime soon

matt[/b]