0.10.13R crash

[bachig24u]

Hi Matt,
First and last run of the night suffered a loss of data logging again.

attached are the debug logs.
the first and last debug logs are software crashes with nistune hanged.
usb did not need reconnecting, the software ended abnormally and required restarting.

only thing changed this week was an overtop upgrade of 0.10.13R to clear the expiry message.
somehow lost the USB type 1 drivers after the install.

W7 32bit SP1.
VLT image with a MAF address file mod (1500mv) removed


Kind regards
Sime

[Matt]

If the uninstall/reinstall drivers tickboxes were enabled during the installation, that might have cleared your existing drivers out

The re-release is exactly the same build as 0.10.13 just with an updated black list

Cant find anything from those crashes in the logs, but I've fixed quite a few problems since that version. Will look at that VLT ROM opening however. Why was the file used 32K (and needed to be split?)

[bachig24u]

I sometimes combine roms for map switching with my e-Tune boards modes. up to 64k
e.g. multiple fuel types or dedicated maps for cruise/power, use wireless fob or switch to alternate between them.

[Matt]

Check your 'Nistune USB communications device' in Device manager is Version 2.8.14.0 (18/3/2011)

You can also untick File > Configuration > Retry connect on error

This will stop Nistune re-enumerating the USB device and reconnecting. If the driver fails to respond to our request it causes a hang of the application. I could put the call in a thread but then the thread would be stuck instead

[bachig24u]

retry was unticked when this happened. (unticked since we spoke regarding the injector latency issue)

I pointed the devmanager to grab the files from C:\Program Files\Nistune\FTDI_Win2K_XP_Vista_Drivers\
ftdibus.inf:
DriverVer=03/18/2011,2.08.14
current usb driver.

Is there anything else u need to diagnose these erratic crashes?

[bachig24u]

more logs with multiple crashes.

I'm beginning to think the type 1 board is the issue now.
logworks is fine, never misses a beat, just nistune not recovering from usb consult issues.

[Matt]

Only good news is that I've seen these crashes occasionally in my R31. It only appears to happen when I have got Innovate and Type 1 going together (usually with the log player)

However the crashes have been very rare and intermittent (usually when the car is cutting out and then and finally disconnects was when I got the crash). I've added changes to the 0.10.19 version to start dumping proper crash logs to help me trace it back. I'll see if I can find those on my laptop I was testing with in the next few days

[bachig24u]

I only use logworks when I've given up for the night with nistune.

generally always use nistune to log the lm-2 or LC-1.
lm-2 is usb, the lc-1 is using belkin usb/serial adapter.
could a third usb device cause this like Maxon or Huawei device?

[Matt]

Sorry I meant Innovate (edited post) wideband device and Type 1 at same time. I haven't seen it crash with just one by itself yet