Tunerstudio and Zeitronix prob

[Mikekir]

Hi,

I would appreciate some help here. I installed a PNP MS to my 91 miata combined with a zeitronix wideband sensor.
Despite the fact that my sensor seems to work fine (AFRs in my little LCD look normal) when i connect my laptop and start Tunerstudio, AFRs are way to off from what i get in the LCD. In matter of fact the AFR meter in TS goes like crazy unable to keep a stable number.
I opened a new project and made all the configutations needed including the zeitronix declaration but nothing seems to work. The funny thing is that when i datalog a session and open the diagramm in Megalogviewer the AFRs look very close to what i see when i drive.

Any suggestions?
Thanks in advance.

[LT401Vette]

So they are bouncing around on the Gauge, but the log file looks right...

What Dashboard are you using?

[Mikekir]

So they are bouncing around on the Gauge, but the log file looks right...

What Dashboard are you using?

Exactly.
I use the default dashboard

[LT401Vette]

With the default Dash, it would be logging the same value as the gauge is getting for sure... So that doesn't really make sense.

Can you describe the bouncing? Bouncing within a range, or just all over the place?

[Mikekir]

I 'll upload a video tomorrow on tube so that you can see it. It bounces all over the place. If i step on the gas and maintain my rpm it doesnt respont except from 1 or 2 secs thats look like it's close to real AFRs i see in my LCD. After that it goes bouncing all over again. Maybe i am doing something wrong..

[Mikekir]

Here is the video..
http://www.youtube.com/watch?v=DMATMCZX ... e=youtu.be

I changed from the Project Properties the EGO O2 Sensor form zeitronix non linear to Tech Edge sensor giving 0-5V-19:1 AFR and it seems to work better.. Didnt try to datalog though..

[LT401Vette]

It isn't just bouncing around, it is reading irrational numbers....

Can you zip you whole project folder and send it to me at:
p_tobin <at> yahoo . com

Then i should be able see what is screwy.

[Mikekir]

Email sent, thank you for your support.

[LT401Vette]

It is reading correctly here using your project.

However, when using 1.004 I did get an error for TargetAFR. This shouldn't effect afr though.
Where you getting this error when open the Project while set to the Zeitronix?

1 Errors:
Error: Malformed [OutputChannel] entry, Problem at:
[./inc/lambdaSensors.ini]:[Line:85]: TargetAFR = { table( afrtarget*5/255 ,"zeitronix.inc") }

There looks to be an error for MS1 Zeitronix Non-Linear in 1.004, this appears to have been fixed some time ago. Try the Beta TS and see if it reads properly.

If you Change a Gauge to Rear Bank O2 Volts, what sort of readings do you get?

[Mikekir]

Sorry for the delay. Got the car today..

I installed the beta version of TS and AFRs meter looks normal now! It may have a difference of a ~0.3 but.. who cares.. No irrutional reading or bouncing all over.
The bad news is that although i dataloged for about 10 minutes with Beta TS, when i open the .msl file it has no records..

[LT401Vette]

I installed the beta version of TS and AFRs meter looks normal now! It may have a difference of a ~0.3 but.. who cares.. No irrutional reading or bouncing all over.
The bad news is that although i dataloged for about 10 minutes with Beta TS, when i open the .msl file it has no records..

Are you sure it has no records? Check the File size. I think this might be related to an issue where the beta TS makes the 1st record a MARK if you started the data log before going online, then MLV can't handle that. I will have an updated MLV out later today that fixes this.

[Mikekir]

2012-02-06_18.12.14.msl

empty datalog using Tunerstudio Beta

(989.37 KiB) Downloaded 8 times

I installed the beta version of TS and AFRs meter looks normal now! It may have a difference of a ~0.3 but.. who cares.. No irrutional reading or bouncing all over.
The bad news is that although i dataloged for about 10 minutes with Beta TS, when i open the .msl file it has no records..

Are you sure it has no records? Check the File size. I think this might be related to an issue where the beta TS makes the 1st record a MARK if you started the data log before going online, then MLV can't handle that. I will have an updated MLV out later today that fixes this.

Thats why its so awkward. A get a file of nearly 1Mb so it cant be empty! I attached my datalog to see it yourself.

Should i uninstall TS v1.004, megatune and beta TS and install only the 1.007 TS instead? I think this will fix the issue. When unistalling all these programms should i backup some data beside my logs, manually?

Ps: I havent registered for MLV and i use an old version v2.74 I want to buy TS to use the live analyzer but have to solve these issues first.

Sorry for asking so many things in one post..

[LT401Vette]

Ok, that log file is fine, but the beta TS writes units to the log file. A MegaLogViewer that old probably doesn't know how to handle them, that started at around 2.99.
It opened fine with MegaLogViewer 3.02. You need to upgrade to a current version.

TunerStudio doesn't care what other programs are installed, or other versions for that matter. It is fine to run 2 versions of TS on the same computer. Just make sure you install them to separate folders.

[Mikekir]

Ok, that log file is fine, but the beta TS writes units to the log file. A MegaLogViewer that old probably doesn't know how to handle them, that started at around 2.99.
It opened fine with MegaLogViewer 3.02. You need to upgrade to a current version.

TunerStudio doesn't care what other programs are installed, or other versions for that matter. It is fine to run 2 versions of TS on the same computer. Just make sure you install them to separate folders.

I see. I 'll try both upgrading and installing 1.006* and see what happends.
Thanks

[Mikekir]

I 'll post it just in case anyone else has the same problem with zeitronix.

With the valuable help and patience of Phil we found that the irretional numbers caused from the old version of Tunerstudio i had. Installing the latest version fixed the issue.

For those who have linear zeitronix widebands they should open lambdasensors.ini. and replace the lines of zeitronix sensor with these:

afr = { 9.6 + egoADC * 0.039216 }
lambda = { afr / 14.7 }
TargetAFR = { 9.6 + afrtarget * 0.039216 }
TargetLambda = { TargetAFR / 14.7 }

[Ondonti]

I can't remember if I set mine to linear or normal zeitronix output (it has both) but I had a problem at first getting the values to match and it was actually the fact that the grounds for each device were so far apart. I grounded them to the same point and the numbers matched up (everything else being correct). That said I have not plugged into my MS box since August 2010 using whatever TS was available back then.