NIStune 0.9249 available
Moderator: Matt
NIStune 0.9249 available
Just a bug fix release
- Fixes for log player
RECORDING and consult/wideband disconnect will stop and save log and then put into playback mode
RECORDING and STOP will temporarily stop the log
RECORDING and STOP then STOP will close the file (saving it) and then idle
RECORDING and STOP then PLAY will close the file (saving it) and then disconnect consult and wideband and then put into playback mode
RECORDING and BROWSE will then STOP the file, allow opening of a new file and put in playback mode
That should all be working properly now. If you do see any more problems, let me know what the combination of button presses is and I can look into it
- Fixes for Trace Window crashes. A change to allow multiple windows caused problems when closed and updates were attempted to be made to closed windows. I went through and found the problems and fixed them tonight. Cant seem to crash it now!
- Fixes for scalers in fuel/igniton will now be adjustable using +/- keys when moving the cells on them and update the correct memory location on the ECU (previously would attempt upload to invalid address)
- Swapped cold/warm start table entries around to correct address file parameters
- Updated MOTEC PLM wideband module to also read in checksum bytes
- Fixes for log player
RECORDING and consult/wideband disconnect will stop and save log and then put into playback mode
RECORDING and STOP will temporarily stop the log
RECORDING and STOP then STOP will close the file (saving it) and then idle
RECORDING and STOP then PLAY will close the file (saving it) and then disconnect consult and wideband and then put into playback mode
RECORDING and BROWSE will then STOP the file, allow opening of a new file and put in playback mode
That should all be working properly now. If you do see any more problems, let me know what the combination of button presses is and I can look into it
- Fixes for Trace Window crashes. A change to allow multiple windows caused problems when closed and updates were attempted to be made to closed windows. I went through and found the problems and fixed them tonight. Cant seem to crash it now!
- Fixes for scalers in fuel/igniton will now be adjustable using +/- keys when moving the cells on them and update the correct memory location on the ECU (previously would attempt upload to invalid address)
- Swapped cold/warm start table entries around to correct address file parameters
- Updated MOTEC PLM wideband module to also read in checksum bytes
v.9249 isn't working properly for me. The problem is with the consult log view crashing nistune almost every time. The only time it doesn't crash is if I open the log view without any log files loaded but as soon as I hit record it crashes. I can load the bin file just fine and I can use the consult just fine also. I also am using a brand new dell laptop with a fresh install of this version of nistune and xp pro sp2. I never had this problem with my old thinkpad 390x and older versions of nistune win98se. I also tried the v.925 that was available when I downloaded the .9249 version and got eh same problem.
thanks
thanks
Can you send me through a debug log (see the FAQ or the sticky in the bugs thread)
I did a fresh reinstall of NIStune on this machine (Dell running XP Home SP2) and connected to a Z32 ECU and started logging with no problems, except for the log files now landing at c:\ as the default directory which I'll have to fix up
I've got another one here which I can try out tomorrow Dell Vostro running XP Pro SP2
I did a fresh reinstall of NIStune on this machine (Dell running XP Home SP2) and connected to a Z32 ECU and started logging with no problems, except for the log files now landing at c:\ as the default directory which I'll have to fix up
I've got another one here which I can try out tomorrow Dell Vostro running XP Pro SP2
My new laptop is a Dell Vostro 1500 series w/ XP Pro SP2. Thanks for the help Matt.
Jimmie
For reporting any problems include the following
(a) With a problem description - Nistune crashes when I try to use log view
(b) Exact error message (if any) - Just the default windows message
(c) Vehicle type (and what Address file you used) - 1989 Z31 5spd non turbo using Z31_VG30_256_E_86-89.adr
(d) Equipment used (emulator, wideband unit, Type1-4 etc) - Type1 on an 88na ecu, nothing else yet
(e) Steps required to reproduce the problem (if possible) - Open Nistune, load Z31_VG30E_1988_FEDERAL.bin, turn car on, click consult botton, open consult display, open log view, click record then crash. Also after crashing if I go through the same steps the previous attempted log opens when I open the log view and immediately crashes Nistune.
(f) Debug logs - Attached to post
* Enable File-Configuration-Debug Logging
* Logs are stored in C:\Program Files\NIStune\logs
* Log files are datestamped and end with .log
* Log files get very big very quickly
* Only do what is required to show the problem. ie. If it is a wideband problem then dont enable consult
* Turn off debug logging when you have finished!
Jimmie
For reporting any problems include the following
(a) With a problem description - Nistune crashes when I try to use log view
(b) Exact error message (if any) - Just the default windows message
(c) Vehicle type (and what Address file you used) - 1989 Z31 5spd non turbo using Z31_VG30_256_E_86-89.adr
(d) Equipment used (emulator, wideband unit, Type1-4 etc) - Type1 on an 88na ecu, nothing else yet
(e) Steps required to reproduce the problem (if possible) - Open Nistune, load Z31_VG30E_1988_FEDERAL.bin, turn car on, click consult botton, open consult display, open log view, click record then crash. Also after crashing if I go through the same steps the previous attempted log opens when I open the log view and immediately crashes Nistune.
(f) Debug logs - Attached to post
* Enable File-Configuration-Debug Logging
* Logs are stored in C:\Program Files\NIStune\logs
* Log files are datestamped and end with .log
* Log files get very big very quickly
* Only do what is required to show the problem. ie. If it is a wideband problem then dont enable consult
* Turn off debug logging when you have finished!
- Attachments
-
- nistune-0412-0929.log
- (5.34 KiB) Downloaded 195 times
Thanks for all the information. I went through the scenario on the same laptop as you but it didnt crash
Next step was looking at the messages. I found a problem where it was trying to visit a line when it was recording (should only be done in playback) so I have fixed that up. I dont know if that was the cause however, but I've updated the software and 0.9251 is available tonight for you to try out.
Please let me know how that goes
Next step was looking at the messages. I found a problem where it was trying to visit a line when it was recording (should only be done in playback) so I have fixed that up. I dont know if that was the cause however, but I've updated the software and 0.9251 is available tonight for you to try out.
Please let me know how that goes
Thanks for the fast response. I tried the new beta .9251 ver but it still did the same problem on my laptop. It crashes with any version I install onto the laptop when I try to us the log view. Even when not connected to the car and I just try to view someones log files from here, Stinky's from the test area, it crashes. It crashes no matter what I do but it only crashes upon trying to use the log view in any situation. I also noticed that with any current NIStune version loaded on my laptop that the consult view gauge needles weren't center to the gauge face. So I updated my geforce video drivers from dell and still the same problem. I still have ver .9249 and .925 loaded, separately tested, on my desktop pc and it works just fine no problems. I can open the log view and play both Stinky's and Bernardd's uploaded log files and everything works great. I think it's boiling down to my new laptop, maybe it's missing some driver or something. I just can't figure out what might be missing. I did a windows update last night and that didn't help. I just bought this laptop 1 week ago and the only program I've installed on it is NIStune so far, along with the few things dell installed previously. Any ideas?
After looking at this post I should have posted it in the Software bugs section. Please feel free to move it.
thanks
After looking at this post I should have posted it in the Software bugs section. Please feel free to move it.
thanks
I've got the exact same laptop Vostro 1500 but I attempted to make it a dual boot with Win98 the week before and that failed
I lost my recovery partition and had to reinstall XP and drivers from the CDs supplied. I dont know if that has changed the configuration from yours somewhat?
I did find that using the mousepad scroll feature actually crashed Microsoft Visual C++ application and had to disable that
Some type of message passing glitch from windows to the log player might be causing the problem. I'll have another look at it... might have to do some test versions to round the problem down if I cant repeat it here
I lost my recovery partition and had to reinstall XP and drivers from the CDs supplied. I dont know if that has changed the configuration from yours somewhat?
I did find that using the mousepad scroll feature actually crashed Microsoft Visual C++ application and had to disable that
Some type of message passing glitch from windows to the log player might be causing the problem. I'll have another look at it... might have to do some test versions to round the problem down if I cant repeat it here
Jimmy - I have been able to get the crash happening on this laptop now. Its occurring with the release of the version put out last night and one of the log files I was trying
Now I can get the problem can continue investigating it. Problem is that it disappears in 'debug mode' which makes it very difficult to find where the problem is happening and why. Anyway just let you know what is happening
Now I can get the problem can continue investigating it. Problem is that it disappears in 'debug mode' which makes it very difficult to find where the problem is happening and why. Anyway just let you know what is happening