Frame error in NT - Works fine in HyperTerm

[djstatic]

I think I know the problem (and it probably requires mods to NT), but here goes:
OK so when I connect to the gauge via HyperTerminal I get the proper output.

In NisTune I just get errors that tick over till they tally 100.

I believe this is happening because my gauge is set to P01 (Lambda) I set it to P01 because I'm running E85 (and obviously want the gauge displaying Lambda).

Cheers.

[Matt]

Can you post here a sample of what the data in Hyperterm looks like

As you guessed Nistune is looking for xx.x format in terms of AFRs. If the data is much different it will not recognise and raise 'frame errors'

[djstatic]

it seems to "glitch" at the start with a XX.X then corrects to X.XX

[Matt]

Yeah that is a bit dodgy. It adjusted the format before changing the actual data from AFRs to lambda half way whilst pumping the data out! Called a 'race condition'

Anyway I'll update the code and my AFR simulator

[djstatic]

Awesome news Matt, you're the best!

I can't believe someone hasn't raised this issue before.

so what beta version should I be waiting for?

[Matt]

Next one will be 0.10.20 version. Probably about a week away depending how things go. I've got a few fixes still to go in

[Matt]

Code has been added and tested today

[djstatic]

Code has been added and tested today

Confirmed. Thanks for adding this Matt.