Moderator: Matt
Yeah, but this is the highway to make Nistune more convenient, no more USB cables .... laptop in the 100m car surrounding with class1 BT converters and dongle.Matt wrote:Romchip2000 - will look at this one but it will be a lower priority to the other issues since you're the only one using this device at the moment
And based on your own assumptions or code deciphering ? Because that's the ECU taking the decision of using one map or another (cold, warm enrich maps, engine temp initial, engine current temp, ...)Matt wrote:This is map highlighting. It indicates which maps the ECU is using
It uses TPS, start, TPS idle, neutral, speed, RPM and knock select input from the ECU to work this out
ive been on the dyno since 930. Its now 12;30 and i have only done 4 runs. Nistune keeps freezing and i have to completely reboot which takes forever on my laptop. ArrrrrghBased on code decipheringAnd based on your own assumptions or code deciphering ?
-constant/scalar
-address EA22 or 0A22
-size 16 bits
-units of Volts
-conversion formula of 'X * .005'
-title: EA22 - Low MAF Voltage Enrichment Trigger
- RPM displaying 0 on some PCs (Z32 ECU). Please confirm if still an issue
- AFR vs RPM graph
- Blank line in log player with different Innovate sensors
Little OT but I notice MTS latest version instability also wit some other applicationsMatt wrote: - Looking into the Innovate MTS crash on disconnect. I've got a workaround in there for the meantime but still looking into it
On top of that, with 0.10.4, I got frequent disconnections of Innovate while logging, after 3mins or 10 mins (random btw). Log player (recording) goes on in this case. I stop it manually to keep the log file.Matt wrote:Issue is that I dont see the same disconnect issue in the 0.9.14.22 version whilst debugging. However I agree that MTS has crashed inside the software. I've seen debug stack traces coming from MTS.DLL and not from the Nistune call stack. Also had PCs due blue screens of death whilst using it with older Nistune versions too
This is intentional now - so you can reconnect and keep on recording with same log fileLog player (recording) goes on in this case. I stop it manually to keep the log file.
Tonight, I still got spurious disconnection from Innovate and I've been obliged to reconnect both Innovate and Log recording while driving, very dangerous ! (I thought it went on with recording last time, not this time, strange).Matt wrote:Will have a look at that next then. Hooked lc1 to r31 for testing this week. See if disconnects come from mts or are internal. We just process events from mts and have no control over comms
This is intentional now - so you can reconnect and keep on recording with same log fileLog player (recording) goes on in this case. I stop it manually to keep the log file.
I noticed this also this morning too whilst testing the 0.10.5 prerelease version. Got a disconnect using the LC-1 and that nasty ebay Prolific USB-serial converterTonight, I still got spurious disconnection from Innovate
Sorry but that isnt too smart ... trying to reconnect whilst driving?!!! At least pull over then reconnect. Press the 'R' key to continue recordingI've been obliged to reconnect both Innovate and Log recording while driving, very dangerous !
It should 'pause' the recording if one of the units (consult or wideband) disconnect. And stop all together if all two/three disconnectI thought it went on with recording last time, not this time, strange).
Okay will look into that. I probably have that in my logs also from this mornings drivingBut everything is in the same file with new time base starting from 0 in the middle of the file.
Consult does automatic reconnection (retries anyway) but not currently with wideband. The problem here is that Innovate when it disconnects usually is hosed (I belive it does try to reconnect anyway).You should add a new feature in Nistune, an automatic reconnection !:_if spurious disconnection occurs, Nistune should try to reconnect by itself and going on with recording by itself too.
You are still losing logging sessions? Ie its not saving the file? Not noticing that any moreLosing a logging session or getting it partially is a nightmare !
What it makes:Matt wrote:Okay will look into that. I probably have that in my logs also from this mornings drivingBut everything is in the same file with new time base starting from 0 in the middle of the file.
Code: Select all
13:22.0 2875 2.63 95 90 1.46 -50 4.49 4.51 34 126 93 93 98 98 6400 [25] 1.36 1 20.1 14.7 25 10
13:22.0 2875 2.535 95 90 1.28 -50 4.17 4.19 40 126 93 94 101 101 5632 [22] 1.36 1 20.1 14.7 22 9
13:22.2 2900 2.485 95 90 1.24 -50 4.1 4.02 45 126 93 94 101 102 5376 [21] 1.36 1 20.1 14.7 21 9
13:22.3 2900 2.485 95 90 1.24 -50 4.15 4.07 45 126 93 94 101 102 5376 [21] 1.36 1 20.1 14.7 21 10
13:22.4 2900 2.405 95 90 1.14 -50 3.83 3.89 48 126 98 94 101 103 4864 [19] 1 14.7 19 9
00:00.0 3137 1.93 94 98 0.78 -50 2.29 2.37 44 126 100 99 99 103 2048 [8] 0.96 0.97 14.21 14.34 8 5
00:00.1 3137 1.94 94 98 0.78 -50 2.29 2.33 44 126 100 99 99 103 2048 [8] 0.97 1.01 14.34 14.89 8 5
00:00.2 3137 1.935 94 98 0.78 -50 2.28 2.32 44 126 100 99 99 103 2048 [8] 0.94 0.96 13.9 14.24 8 5
00:00.3 3162 1.95 94 98 0.8 -50 2.38 2.34 45 126 100 99 99 103 2048 [8] 0.93 0.96 13.72 14.15 8 6
00:00.4 3137 1.995 94 98 0.86 -50 2.46 2.48 46 126 100 99 99 103 2304 [9] 0.93 0.97 13.8 14.39 9 6
00:00.5 3162 2.045 94 98 0.9 -50 2.54 2.56 48 126 100 99 100 103 2560 [10] 0.94 1 13.93 14.72 10 6
00:00.6 3162 2.08 94 98 0.92 -50 2.59 2.61 49 126 100 99 101 104 2560 [10] 0.96 0.96 14.18 14.14 10 6
00:00.7 3162 2.1 94 98 0.92 -50 2.61 2.65 50 126 100 99 101 104 2816 [11] 0.96 0.97 14.17 14.28 11 6
00:00.8 3175 2.115 94 98 0.94 -50 2.73 2.75 50 126 99 98 100 104 2816 [11] 0.96 0.98 14.2 14.43 11 7
1) in my case of wideband losing connection, I'm not obliged to unplug-replug the USB Prolific cable, I just press the Wideband button in Nistune again and it reconnects. But remember, I use Prolific 2.0.0.26, this is the only version allowing to have both cables working at the same time on the same USB bridge (PC in ternal hardware). I have mentioned that earlier in this post.Matt wrote:Consult does automatic reconnection (retries anyway) but not currently with wideband. The problem here is that Innovate when it disconnects usually is hosed (I belive it does try to reconnect anyway).You should add a new feature in Nistune, an automatic reconnection !:_if spurious disconnection occurs, Nistune should try to reconnect by itself and going on with recording by itself too.
What I have noticed using that Prolific USB-serial converter this morning is that unplogging power to the LC-1 and/or disconnecting the serial connector to USB-serial converter does not allow it to reconnect (either with Nistune OR Logworks)
I had to physically pull the USB-serial converter on either program when it loses connection to allow it to reconnect again. That means that either (a) MTS is not letting go of the USB handle on disconnect or (b) Prolific driver version I am using is not releasing the handle properly itself. Either way it happens with logworks so I'm going to check the driver version next
The other issue I have found with the current Prolific drivers I am using is if I have two devices like yourself, and wideband is connected on one device, consult is unable to receive any data on the second device. As soon as the first device is disconnected, consult will receive data. This means that there is a confict with the drivers when using multiple prolific devices. I will look at what drivers you were using at the start of this thread and try a more reliable version
No, what I meant is spurious disconnection jeopardizes my logging sessions because losing some logging data makes me spending some precious time.Matt wrote:You are still losing logging sessions? Ie its not saving the file? Not noticing that any moreLosing a logging session or getting it partially is a nightmare !