RomRaider 0.5.4b RC1

mdedwar · **Joined:** Sun Jan 04, 2009 8:41 pm **Posts:** 46

All looks good except my innovate lc1 stops working after a few minutes and I have to restart RR to get it working again.

Anyone else had the same problem?

Cheers,
Matt.

hebs · **Joined:** Tue Nov 21, 2006 5:31 am **Posts:** 319

dschultz wrote:

Hmm... never seen or heard of any other reports of it doing that.
When my ignition goes off the data stops flowing so there is nothing to log/write. I test on a 32bit ECU, what are you using?
I'm not even sure where the data would come from if the ECU was off. How many logs does it create, one or one every 5 seconds?

Does it still do it with this latest 0.5.4 release? If so then set the debugging to Trace in the Logger Help menu, shut the ignition off and wait a bit then send me the rr_system.log (found in the log directory opened from the help menu Debug item).

I am on a 32 bit ecu as well (07 wrx). It creates one log, like the one I posted above. It has done this since I started tuning. I have just gotten into the habit of hitting the disconnect button before I turn the car off. I will try to get this RC installed and get you the system log in the next few days.

As always, thanks for the time you put into RR... you are greatly appreciated.

dschultz · **Posted:** Thu Nov 03, 2011 12:16 pm

mdedwar wrote:

All looks good except my innovate lc1 stops working after a few minutes and I have to restart RR to get it working again.

How long before it stops?
No changes were made to the LC-1 plugin. Does all logging stop or just the LC-1?
If you submit a trace log that may help.
Set the debugging level to Trace in the Logger Help menu, wait for the problem to happen, then submit the rr_system.log (found in the log directory opened from the help menu Debug item).

goixiz · **Posted:** Fri Nov 04, 2011 7:14 am

Dweeb wrote:

One feature I would request:
Is that the gauges that now always get rearranged in “alphabetical” order when you restart the logging window would not do that. It would be nice if they retained the order that they were in, when originally selected (as in the order that they were selected with the check box.). allow us to save the window layout....
It’s easier to view/monitor if you keep certain gauges beside each other.

Or am I missing something somewhere to do that. :wink:

I second this request if its not on this current release

Just a thought is to instead of having a check mark for selection maybe a number instead of check mark so when it places the selection on the screen it follows the sequence the user has made. that way it will always be the way it was intended and can easily be changed to the user preference

dschultz · **Posted:** Fri Nov 04, 2011 9:22 am

Thanks for the suggestion.
I was think that I could accomplish this using a sequence that incremented with each selection made. That sequence number would also be written to the profile and used as the display order when the profile was reloaded.

Carbibbles · **Joined:** Tue Aug 30, 2011 3:17 pm **Posts:** 628

Dale, finally got a chance to get a trace log. The issue happened every time if the "log with defrost" option was turned on. It also didn't matter if I turned the key to acc. or completely off. Hopefully the log can show what is happening. I included the csv log that was created.

Jason

mdedwar · **Joined:** Sun Jan 04, 2009 8:41 pm **Posts:** 46

mdedwar wrote:

All looks good except my innovate lc1 stops working after a few minutes and I have to restart RR to get it working again.

Anyone else had the same problem?

Cheers,
Matt.

This appears to have been a problem with windows and the com port.

The weird thing I'm seeing now is to do with the order of the output in the log files and unexplained values.

See link
http://www.romraider.com/forum/viewtopic.php?f=15&t=7814

Out of the five WOT runs I did today this anomoly was in two of them.

Code:

time       rpm     Knock        MRP       Throt       AFR     FKC
1788   3512   4   15.02   100   11.2   0
1810   3545   4   15.02   100   11.11   0
1849   3576   4   15.35   100   11.11   0
1884   3612   4   15.35   100   11.11   0
1904   3594   4   15.57   100   11.29   0
1948   3606   4   15.57   100   11.29   0
1974   3632   4   15.62   100   11.39   0
2008   3672   4   15.62   100   11.39   0

note 1904

Cheers,
Matt.

dschultz · **Posted:** Fri Nov 18, 2011 12:36 am

What seems to be the problem with 1904?

mdedwar · **Joined:** Sun Jan 04, 2009 8:41 pm **Posts:** 46

dschultz wrote:

What seems to be the problem with 1904?

If you look at the RPM column the value has gone down from the previous line. Also at time 4654 in the log on the referenced post the rpm as gone down plus the MRP value.

Both logs were full throttle so I'm not sure why this has happened.

dschultz · **Posted:** Fri Nov 18, 2011 10:17 am

All I can say is that the RR Logger only reports the values the ECU sends in the response. If the value is different than expected, the ECU sent it that way. If the value was corrupt then the RR Logger would toss the entire packet and not report the values at all.

If you run the Logger debug in Trace mode and check the rr_system.log file you can see the raw packets and if any errors are detected which caused the packet to be tossed.

dschultz · **Posted:** Sun Nov 20, 2011 1:38 pm

Carbibbles wrote:

Dale, finally got a chance to get a trace log. The issue happened every time if the "log with defrost" option was turned on. It also didn't matter if I turned the key to acc. or completely off. Hopefully the log can show what is happening. I included the csv log that was created.
Jason

This log is kinda messed up.
First suggestion for you, since you don't appear to have LogWorks3 installed on that computer, pull the LM-2 (mts) plugin out of the \plugins directory to stop it from trying to load. You can always put it back if you want to use it later. The Logger will start up faster too!

Next I see this odd thing:

Code:

166676 INFO  [Thread-26] - Trying J2534 connection...
166676 INFO  [Thread-26] - J2534 connection not available [com.romraider.io.j2534.api.J2534Exception: Error: [8] no devices available], trying serial connection...
166677 INFO  [Thread-26] - Connected to: COM1
166677 INFO  [Thread-26] - Serial connection initialised
168507 INFO  [Thread-29] - Trying J2534 connection...
168509 INFO  [Thread-29] - J2534 connection not available [com.romraider.io.j2534.api.J2534Exception: Error: [8] no devices available], trying serial connection...
168618 INFO  [Thread-29] - Connected to: COM3
168618 INFO  [Thread-29] - Serial connection initialised
168701 INFO  [Thread-26] - Connection closed.
168701 INFO  [Thread-26] - Error sending init: Parameter response must not be null or empty
169703 INFO  [Thread-26] - Trying J2534 connection...
169703 INFO  [Thread-26] - J2534 connection not available [com.romraider.io.j2534.api.J2534Exception: Error: [8] no devices available], trying serial connection...
170810 INFO  [Thread-29] - ECU ID = 3D04EA4605
171747 INFO  [Thread-26] - Connection closed.
171747 INFO  [Thread-26] - Connection closed.
171747 INFO  [Thread-26] - Error sending init: com.romraider.logger.ecu.exception.SerialCommunicationException: Port is currently in use: COM3

You start a connection on COM1 with Thread-26 and it fails. 2 seconds later you try a connection on COM3 with Thread-29 and it succeeds. BUT, Thread-26 continues and now tries to use COM3 which is in use by Thread-29. Thread-26 continues through the entire log to try and connect. It's like there are two Loggers running or two ECU comm threads running which I don't understand.

After a connection is made by Thread-29 I see the addition of the Defrost Switch, Battery Voltage and Engine Speed. The Logger runs in Fast Poll for 30 seconds then gets a bad response.

Code:

214506 DEBUG [Thread-29] - SSM Bad read response (read timeout): 
214506 DEBUG [Thread-29] - Mode:1 ECU Response <--- 00000000000000000000
214506 ERROR [Thread-29] - Error occurred
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
214538 DEBUG [Thread-29] - SSM sending line break
214804 DEBUG [Thread-29] - SSM clearing line (stale data): 00
214960 INFO  [Thread-29] - Connection closed.
214960 INFO  [Thread-29] - TX Manager Stopped.

The connection is cleared and closed.

Then Thread-29 tries to re-establish comms, as does Thread-26.

Code:

214960 INFO  [Thread-29] - J2534 connection not available [com.romraider.io.j2534.api.J2534Exception: Error: [8] no devices available], trying serial connection...
215024 INFO  [Thread-26] - Trying J2534 connection...
215024 INFO  [Thread-26] - J2534 connection not available [com.romraider.io.j2534.api.J2534Exception: Error: [8] no devices available], trying serial connection...
215055 INFO  [Thread-29] - Connected to: COM3
215055 INFO  [Thread-29] - Serial connection initialised
215055 DEBUG [Thread-29] - Ecu Init Request  ---> 8010F001BF40
217012 INFO  [Thread-26] - Connection closed.
217012 DEBUG [Thread-26] - Error sending init
com.romraider.logger.ecu.exception.NotConnectedException: com.romraider.logger.ecu.exception.SerialCommunicationException: Port is currently in use: COM3
217074 DEBUG [Thread-29] - Ecu Init Response <--- 
217262 INFO  [Thread-29] - Connection closed.
217262 DEBUG [Thread-29] - Error sending init

Thread-29 sends an ECU Init but gets no response and closes the connection. This sequences goes on for 124 seconds then the Query Manager is stopped and the Logger is shutdown. Both Thread-26 & Thread-29 are terminated. Again it looks like two Loggers were running...?

Then 115 seconds later the Logger is started again (it appears as if you have started the Logger from the ECU Editor menu item) with debug already set to Trace level.

A single Thread is created and starts querying the ECU on COM3.

Code:

458491 DEBUG [Thread-8857] - QueryManager started.
458491 INFO  [Thread-8857] - Trying J2534 connection...
458491 INFO  [Thread-8857] - J2534 connection not available, trying serial connection...
458670 INFO  [Thread-8857] - Connected to: COM3
458670 INFO  [Thread-8857] - Serial connection initialised
458670 DEBUG [Thread-8857] - Ecu Init Request  ---> 8010F001BF40
460825 DEBUG [Thread-8857] - Ecu Init Response <--- 80F01039FFA2100F3D04EA460573FAEB800A43FEAA00100070DE54F8B4000000000000000000DC0000451C000000000000000000800000000000000000D7
460825 INFO  [Thread-8857] - ECU ID = 3D04EA4605

A profile is loaded containing Battery Voltage and Engine Speed.

Code:

461043 DEBUG [AWT-EventQueue-0] - Adding logger:   [P17] Battery Voltage
461043 DEBUG [AWT-EventQueue-0] - Adding logger:   [P8] Engine Speed

Queries go on for 30 seconds and then they stop.

Code:

490950 DEBUG [Thread-8857] - SSM Bad read response (read timeout): 
490950 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 00000000000000000000
490950 ERROR [Thread-8857] - Error occurred
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
490981 DEBUG [Thread-8857] - SSM sending line break
491247 DEBUG [Thread-8857] - SSM clearing line (stale data): 00
491435 INFO  [Thread-8857] - Connection closed.
491435 INFO  [Thread-8857] - TX Manager Stopped.

Then the connection is initialized again and the ECU Init is sent, but there's no reply.

Code:

491435 INFO  [Thread-8857] - Trying J2534 connection...
491435 INFO  [Thread-8857] - J2534 connection not available, trying serial connection...
491546 INFO  [Thread-8857] - Connected to: COM3
491546 INFO  [Thread-8857] - Serial connection initialised
491546 DEBUG [Thread-8857] - Ecu Init Request  ---> 8010F001BF40
493564 DEBUG [Thread-8857] - Ecu Init Response <--- 
494781 INFO  [Thread-8857] - Connection closed.
494781 DEBUG [Thread-8857] - Error sending init
java.lang.IllegalArgumentException: Parameter response must not be null or empty

Finally!
In the Trace data bytes I see that the Defrost Switch was off initially, but then became ON when your log file was created as the engine shut down. This would seem to be what triggers the Logger to write a new file.

Raw Data	Battery	RPM	Byte 64	Crankshaft	Camshaft	Defrost	Blower
486938 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AD0FE8D8E9	13.84	1018	D8	1	1	0	1
486971 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AD0FE8D8E9	13.84	1018	D8	1	1	0	1
487001 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AD0FE8D8E9	13.84	1018	D8	1	1	0	1
487018 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8B30FDDF804	14.32	1015	F8	1	1	1	1
487051 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8B30FDDF804	14.32	1015	F8	1	1	1	1
487085 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8B30FDDF804	14.32	1015	F8	1	1	1	1
487102 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8B00EF9F81C	14.08	958	F8	1	1	1	1
487134 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8B00EF9F81C	14.08	958	F8	1	1	1	1
487144 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AC0DF4F812	13.76	893	F8	1	1	1	1
487176 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AC0DF4F812	13.76	893	F8	1	1	1	1
487194 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8AC0DF4F812	13.76	893	F8	1	1	1	1
487227 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A80CE0F8F9	13.44	824	F8	1	1	1	1
487259 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A80CE0F8F9	13.44	824	F8	1	1	1	1
487271 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A80CE0F8F9	13.44	824	F8	1	1	1	1
487289 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A50BBAF8CF	13.2	751	F8	1	1	1	1
487322 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A50BBAF8CF	13.2	751	F8	1	1	1	1
487339 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A30B09F81C	13.04	706	F8	1	1	1	1
487373 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A30B09F81C	13.04	706	F8	1	1	1	1
487399 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A30B09F81C	13.04	706	F8	1	1	1	1
487417 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A20A7FF890	12.96	672	F8	1	1	1	1
487450 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A20A7FF890	12.96	672	F8	1	1	1	1
487467 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10923F832	12.88	585	F8	1	1	1	1
487501 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10923F832	12.88	585	F8	1	1	1	1
487518 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10923F832	12.88	585	F8	1	1	1	1
487544 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10854F862	12.88	533	F8	1	1	1	1
487576 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10854F862	12.88	533	F8	1	1	1	1
487593 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A10854F862	12.88	533	F8	1	1	1	1
487623 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A1079AF8A7	12.88	487	F8	1	1	1	1
487641 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A1079AF8A7	12.88	487	F8	1	1	1	1
487671 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A106A7F8B3	12.88	426	F8	1	1	1	1
487689 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A106A7F8B3	12.88	426	F8	1	1	1	1
487722 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A106A7F8B3	12.88	426	F8	1	1	1	1
487741 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A005B6F8C0	12.8	366	F8	1	1	1	1
487767 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A005B6F8C0	12.8	366	F8	1	1	1	1
487799 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A005B6B880	12.8	366	B8	1	0	1	1
487817 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A005B6B880	12.8	366	B8	1	0	1	1
487850 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A005B6B880	12.8	366	B8	1	0	1	1
487869 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
487895 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
487913 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
487946 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
487975 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
487992 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
488023 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
488070 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0045DF866	12.8	279	F8	1	1	1	1
488073 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488091 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488140 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488171 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488189 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488215 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488246 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488248 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294F89B	12.8	165	F8	1	1	1	1
488266 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294B85B	12.8	165	B8	1	0	1	1
488299 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294B85B	12.8	165	B8	1	0	1	1
488331 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294B85B	12.8	165	B8	1	0	1	1
488342 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294B85B	12.8	165	B8	1	0	1	1
488374 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A00294B85B	12.8	165	B8	1	0	1	1
488392 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0029438DB	12.8	165	38	0	0	1	1
488423 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0029438DB	12.8	165	38	0	0	1	1
488440 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A0029438DB	12.8	165	38	0	0	1	1
488473 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488492 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488519 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488535 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488567 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488598 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488616 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488649 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488667 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488700 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488732 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488743 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488775 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488792 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488825 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488843 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488876 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488894 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488917 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
488934 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 80F01005E8A000003845	12.8	0	38	0	0	1	1
490950 DEBUG [Thread-8857] - Mode:1 ECU Response <--- 0000000000000000000000	0	0		0	0	0	0

Maybe you can try another experiment for me. Log the same parameters plus add the Ignition switch as well. I tried to replicate this on my own ECU and there is no change in the Defrost switch state, so that's why I can't see this file being created in me setup. Maybe the 32bit ECU has different logic with respect to switches or the BIU could be at fault here.

MFB · **Posted:** Tue Nov 22, 2011 8:49 am

Wow, congrats on the new build. Will go use and see what I can contribute to the thread. Thanks!

Jochen_145 · **Joined:** Wed Nov 10, 2010 7:56 am **Posts:** 211

RomRaider Logger:

Cal-ID of my Diesel-ECU isn´t displayed anymore (unknown), ECU-ID is ok
RR 0.5.3b RC10 did it it correctly...

BR

dschultz · **Posted:** Thu Nov 24, 2011 11:51 pm

CAL ID is cross-referenced by ECU ID and read from your defined set of ECU defs in the Editor.

Carbibbles · **Joined:** Tue Aug 30, 2011 3:17 pm **Posts:** 628

Ok, I cant start my car right now because the trans is out of it. But I was able to do some key on/engine off testing. And this time I noticed something very odd, if I turn my key on and then back off, my ECU stays "alive" for a minute or so, even with the key completely out of the ignition. Then I hear a relay or something click and it shuts down. Maybe something to do with not actually starting the car? But its interesting to note that when I turn the key off, the defrost bit goes to "1" even though the ECU is still "alive" and transmitting data for the selected parameters. Im assuming that this is the issue, maybe have the logger code check the state of the ignition switch along with the defrost switch to determine if logging to a file should take place?

Heres the trace file and the log it created. It started logging to a file as soon as I turned the key off. The ECU stayed alive for a bit and then shutdown, the logging to file disconnected 5-10seconds after that.

RomRaider

Forum rules

RomRaider 0.5.4b RC1

Who is online