Nistune Forums

no, no crash.. just WB connection stops.

I really enjoy this version compared to 0.10.x family.
Log files are correctly names each time (no more 0KB files)
No spurious disconnectS
Keeping Nistune opened, going into standby mode or switching ignition off w/o precaution doesn't crash Nistune (it just takes a while to get it back to life, responding to user commands).

Matt wrote:Note - Windows Firewall can block 'Innovate MTS' from being available in Nistune. I've been getting this tonight on Win7 Pro when doing various builds and saying that Innovate OCX is not registered (and windows firewall messages sometimes)

If after reinstalling logworks still not showing then enable Nistune through the firewall (or disable the firewall on private network to see that this is the issue temporarily)

Matt,
I think it was the firewall issue after the 0.11 over the top install.

I deleted firewall entries after you you mentioned this and the option to choose "public, domain, home, work " etc popped up. I allowed on all network options and its worked well tonight and we ran a very happy datalog session..

I also may have found that the consult dropping issue could be caused from a failing USB connector on the type 1 board.

by simply gaffa taping the external usb cable to the lower dash panel, the consult seemed to stay connected for long periods.

As I have a huge ANDRA weekend coming up on the 29th I'll need a to source on the USB connectors to test further and confirm.

Shoot me a txt/email through if you need another USB connector plug going to the Type 1 board. So after all the diagnostics with electrics etc ... ended up being the cable?!

it just takes a while to get it back to life, responding to user commands

Found and fixed this one up yesterday (consult freezing on disconnect)

Matt wrote:Shoot me a txt/email through if you need another USB connector plug going to the Type 1 board. So after all the diagnostics with electrics etc ... ended up being the cable?!

email sent...

Today I used the .11 version to tune my car on the dyno.

At one time (being in tuner-mode)
Nistune would not update any cell in the (fuel) grid.

I repeatedly clicked on the cell and tried to change it, but it would not update.
There was no error in the status window, and I was in tuner mode.

I had to close all windows and then open the fuel window again to make it work.

I swear the window/cell was active when I tried.
(And I tried really hard)


Also I would like to suggest that:

The trace in fuel/ignition window would be erasable by a key.
(It is not really practicable having to close/re-open the window just for the erase of the trace)

The font-size in the grid has to be larger!!
(nothing new, but should really be done)

Apart from these issues .11 had no further problems.
(except for that my clutch gave up)

turning trace on/off was the same key.

maybe its broken?

Nistune would not update any cell in the (fuel) grid.

There might have been a dialog box (message prompt) hidden in the background. This still stop any keyboard functionality until prompted. I've noticed this if I click on the Nistune window, it hides the prompt

The trace in fuel/ignition window would be erasable by a key.

Click the 'trail' tickbox to clear or right click 'trail'

The font-size in the grid has to be larger!!

I finally figured out how to get the fonts to scale correctly without looking messed up (given you can size the grid vertical and horizontal). This will be in the next release.

I've just done some emulator fixes (hardware maptracing causing dramas since the Moates emulator doesnt respond as it should when the ECU is off and messes up subsequent upload/download etc command)

At the moment just got to
- retest emulator functionality (dual emulator)
- finish the crash report work
- Techedge and PLX iMFD wideband fixes
- Fix support for VEMS round for incremenetal wideband firmware versions

Then after this will be another version built this time from VS2010

Nistune would not update any cell in the (fuel) grid.

Matt wrote:There might have been a dialog box (message prompt) hidden in the background. This still stop any keyboard functionality until prompted. I've noticed this if I click on the Nistune window, it hides the prompt

Is this a message from Nistune?
If so, it should rather be on top of the window stack (before I break my finger).

The trace in fuel/ignition window would be erasable by a key.

Matt wrote:Click the 'trail' tickbox to clear or right click 'trail'

But That would mean disabling it, and then enabling it again?
That's not what I was getting at, too much redundant mouse action.

I find handling a mouse in a car on the dyno is a bit awkward, especially when you have to click tiny boxes.
Also sometimes I take a log while roadtuning doing a graphical trace to get
an idea what is going on.
I am very often in the situation where I just want to clear the trace to get a new sample done.
(so erasing the old plot)

The font-size in the grid has to be larger!!

Matt wrote:I finally figured out how to get the fonts to scale correctly without looking messed up (given you can size the grid vertical and horizontal). This will be in the next release.
I've just done some emulator fixes (hardware maptracing causing dramas since the Moates emulator doesnt respond as it should when the ECU is off and messes up subsequent upload/download etc command)
At the moment just got to
- retest emulator functionality (dual emulator)
- finish the crash report work
- Techedge and PLX iMFD wideband fixes
- Fix support for VEMS round for incremenetal wideband firmware versions
Then after this will be another version built this time from VS2010

I understand that you have many issues to fix, but can't you just increase the font size by 2 points as an interim solution?
Or would that throw off the whole GUI?

Understand the development for the next release is already in progress. Changes currently implemented are untested. I could roll the code back to the previous release version and re-release but not for one single change when I'm going to release in about another week. Its just not work the wasted effort

Hi Matt,

NP and fair enough.

My first post here.

This new iMFD functionality sounds poised to take Nistune to the next level and I will definately volunteer to share any information I get from working with iMFD hardware as I should be in possession of a PLX kiwi with the iMFD expansion by month's end.



Exciting times.

Hi Matt,
Can you confirm if the "temp conversion" scaling is correct for the type 1 cr31/VLT.

the horizontal scale hit 28 volts. The log I took the other day before our trusty test bed died showed 8v but I think its actually half of the displayed value.

1) Open Nistune
2) Open a map (timing or fuel)
3) Enable Trail on the map
4) Open log player
5) Load a CSV file
6) FAST play the log ... cells reached are highlighted in purple
7) Once finished, try to move windows ... NIstune hangs up