Nistune 0.10.20 Release

[Matt]

TPS idle trigger is only applicable to HCR32 for RB25 (V4) firmware loaded on boards used with RB25 engines. If the board does not have this firmware the value will be default 0xFF

When using an R32 Skyline ECU on a R33 Skyline RB25 the Series 1 models do not have a TPS switch. Since this is missing, the HCR32 doesnt 'see' when TPS is idle. So this firmware was added to set a TPS voltage to trick the ECU into thinking it was idle (you will see TPS idle lit in consult display)

If you are not using this firmware then the parameter doesnt matter since ECU doesnt use that memory address normally

This has nothing to do with MAF changes at all. If you upgrade the MAF to Q45 then do the MAF change option and then adjust Injection Multiplier until AFRs are back to normal

[djstatic]

BAH! AFM! i meant Throttle Body with TPS.. lol

[RomChip200]

This morning, 8:00AM, leaving my micro-PC from standby mode, Nistune/log player already opened, reconnecting Consult and widebands with F4 and F5 , starting record, it still uses the old filename (Nistune_2012-06-28_1857_07.csv) when I left my car yesterday !
The latest file I saved yesterday is Nistune_2012-06-28_1847_33.csv and it lasted 09:23.8
So, Nistune_2012-06-28_1857_07 is the name generated when I double-stopped to be sure to save the file Nistune_2012-06-28_1847_33.csv

The fact I keep the log player/recorder window opened b/w "sessions" is the trick. A new filename is not re-generated (but it should !) each time I reconnect Consult F4, then Widebands F5. I'm obliged to click on "Name" and then, Cancel, this triggers a new filename with current date and time.

[djstatic]

Is it normal for it to crash/hang after burning to rom?

I haven't messed with NT in awhile

[Matt]

Does it hang or does it crash (shut down)?

I've identified an issue with the current 0.10.20 code where it hangs following PIN entry and have rectified the problem. It may also occur in other situations where an extra operation in consult is performed. Planning to put the fix up soon but want to put the crash dump code in also

[djstatic]

Hangs after I get the prompt that says it was successful.

I had to kill it via Task Manager. It may close on it's own, but I was in a hurry to get to work. I was just bumping up the Crank Enrich and After Start Enrich (I need to separate post a topic about this).

Do you need me to log/record something?

[bachig24u]

Matt, some new strange happens are occuring.
when just running nis, the message at the bottom keeps saying retrying.
if lc-1 is connected the gauges screens keeps flashing at varying intervals.

[bachig24u]

nistune 0.10.20 hasn't crashed when used in conjunction with LM2 (3.08 logworks drivers).
even seemed stable with lc-1 via usb-serial adapter.

Managed a 20 minute logging session with less issues, had a few burn image failures. a quick resync and burn a second time always worked.

nistune often seemed to loose sync of the image. eg. consult connected, made changes to calibration, nistune reports message the resync required before changes were allowed. really became annoying, it must have something to do with the accumulating consult reconnect retry events that are being reported now.
No reported app crashing or needing to reconnect type 1 usb connector.

Also found that nis doesnt always show com13 or 14 (usb com port shown in device manager) mainly if no data stream is apparent from the LC-1 controller if when the unit doesnt init properly. Is this normal operation?
btw, I have debugs if you need them. 12MB compressed

[Matt]

I'll repeat the USB retry scenario here on the bench. Interesting about the 3.08 Logworks drivers showing improvement. ROM chip mentioned never had issues with 3.07 until the last release but I've known you've had crashes with LC-1 and I've had them here also (but when running in debug trace it always showed MTS.DLL crashing)

[RomChip200]

When you change consult registers to be logged (stream mode btw) with "Select consult registers" menu, once you click "OK" it takes a while to have Consult re-connected. Why does it take so much time ? It's so long you get the feeling Nistune hangs up.
Btw, I never understood you never made available these menus (e.g. select Consult registers / Select display gauges) when Consult is not connected.

[Matt]

Why does it take so much time ? It's so long you get the feeling Nistune hangs up.

there is probably a timeout occuring if latest version. I just rewrote the serial classes for consult in 0.10.20 so might be a glitch or two left. I've found with pin setting it will freeze and linked to several other items also. Will try stream mode out with nistune and factory ECUs again to see

Btw, I never understood you never made available these menus (e.g. select Consult registers / Select display gauges) when Consult is not connected

When consult isnt connected we dont know which registers will be available to the user. Its all ECU dependent on which ones are available for selection

[RomChip200]

ROM chip mentioned never had issues with 3.07 until the last release

My problem was more related to a new PC setup with Windows 7 64bits and install of both applications.

From the top of my head, since 2009, once Innovate LC1s were supported in Nistune (in daisy chained form/ MTS), I don't remember having trouble with mts.dll, even with older versions (2.0.0.1).
I started with PL2303 USB serial cables and drivers were a nightmare, each new Nistune version was a new story with these cables.
Since 1 year, I have FTDI cables and I would say, they are reliable even when used with 3m extension cable.

[RomChip200]

Btw, I never understood you never made available these menus (e.g. select Consult registers / Select display gauges) when Consult is not connected

When consult isnt connected we dont know which registers will be available to the user. Its all ECU dependent on which ones are available for selection

Hum, but the address file selected also dictates this, no ?

[Matt]

Even if we know the address file, we dont know the registers available until probing the ECU

[Matt]

Is it normal for it to crash/hang after burning to rom?
I haven't messed with NT in awhile

This has now been found and fixed

Matt, some new strange happens are occuring.
when just running nis, the message at the bottom keeps saying retrying.
if lc-1 is connected the gauges screens keeps flashing at varying intervals.

Had a look at the logs. On this vehicle you are getting a lot of electrical noise affecting the connection (it may eventually drop out if one or the more critical USB commands get affected)

Not all the USB data being received from the device in this case

03:04:45.821 TX: CA 07
03:04:46.071 RX: CA 07 00 3C 04 45 0F 0C 13 80 0A 23
03:04:46.071 USBDriver:read: Error got 12 of 18 expected bytes read

03:04:46.301 TX: CA 07
03:04:46.551 RX: CA 07 00 39 00 9F 04 45 0F 0C 13 80 0A 61
03:04:46.551 USBDriver:read: Error got 14 of 18 expected bytes read

03:04:51.741 TX: CA 07
03:04:51.991 RX: CA 07 00 3F 00 56 80 00 00 A6 04 45 8C 13 80 09 8B
03:04:51.991 USBDriver:read: Error got 17 of 18 expected bytes read

03:04:54.121 TX: CA 07
03:04:54.371 RX: CA 07 00 3C 00 56 80 00 00 AC 04 45 0C 13 80 09 B3
03:04:54.371 USBDriver:read: Error got 17 of 18 expected bytes read