Nistune 0.10.21 Release

[Matt]

I could offer to test it on my LogWorks installation.

No need I've done it here on three other PCs with prior log works installations. Installed 0.10.21 as per usual and tested on various machines. All wideband units were re-tested prior to releasing this version.

[bachig24u]

I'm running the latest ftdi as we've been through this before.
(unless in the last 2 months an ftdi upgrade has become available).

tell me what you need to do to troubleshoot this and I'll do what ever possible to get it done.

[Matt]

Main thing for now is your wideband issue. Try another USB-serial converter perhaps. Does it have a comms light on it at all? My Aten one has a light which flashes when the LC-1 is actively sending data to the PC (even with no app running). Check you have the terminating plug in also otherwise it wont work

Next is the comms issue with the retry frames etc on that vehicle. I've emailed about that already. Basically the noise levels are too high. If you cant get around that then do uploads only when engine is not running. Mainly uploads will fail since the comms is so noisy

As for FTDI you mentioned that you pointed during install to the driver

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.

could you confirm that is also what Device Manager > Universal Serial Bus Controllers > Nistune USB communications Device > Driver version also shows?

FTDI drivers have updated in April to 2.08.26 now so I've downloaded that and adapted the INF files for Nistune. These will be the ones to get signed off for Windows Logo testing so we dont have the 'you are using unsigned drivers' message in windows

I'll see what I can do with the hang issue otherwise in the meantime, and if you had saved any ZIPs when it shut down with dump output please manually email those through since the auto email didnt send them

[bachig24u]

lost me on the auto email.. I do not have an outgoing email app on my pc, is nistune sending mail somehow?

ftdi driver is using 2.08.14.

I will use an old lappie with serial port to t/s LC-1 as the two usb/serials i have give same connectivity results.
Device manager can see the devices, logworks can see the com ports but no data stream received. although strangely enough the XD-16 works flawlessly. pretty sure it's hanging off the serial bus too.
I checked the terminations last night... not the cause.

not sure what the zips are all about as nistune doesn't tell me anything about zip files.
Are these zipped files just compressed debug logs that nistune now does automatically?

[Matt]

If you arent seeing the crash report window when it shuts down (likely on Win7) then dont worry about those in the meantime. The crash report window allows the user to send an email to us containing dump contents as well as save the file compressed (ZIP) to hard disk

With logworks could try uinstalling/reinstalling that but cant see why that wouldnt work. Try the other laptop I guess. If that doesnt work then theres a problem with the LC-1

[Matt]

romchip2000 - put up another release tonight for timestamp fixes. Disconnecting consult and/or wideband should now put the logger in playback mode (wasnt doing that in 0.10.21). When you hit record next (after going out of standby) it will then update the date stamp

[RomChip200]

romchip2000 - put up another release tonight for timestamp fixes. Disconnecting consult and/or wideband should now put the logger in playback mode (wasnt doing that in 0.10.21). When you hit record next (after going out of standby) it will then update the date stamp

Will give it a try in few hours !

[Matt]

barely stays connected for 5 minutes. so lost another day in trying to sort warmup tables out.
nistune would freeze with white faded locked up screen, had to unplug type 1 usb and reinsert to make app work again.

As emailed. Gone through logs. Connectivity issues are not release related. There is a major problem with data errors due to engine noise shown from the log file

As for the lockup/freeze there was a FTDI driver issue identified. Added logic for checking previous driver command finishes before doing the next one in 0.10.23

FTDI 2.08.17 (August 25, 2011)
• Resolved issue with FT_ListDevices when a port is open in another process.
• Improved speed of FT_Close and FT_CreateDeviceInfoList.

2.08.19 (December 14, 2011)
• Resolved issue which could cause opening port to be slow.
• Improved reliability when plugging/unplugging other USB devices.