RomRaider Logo

RomRaider

Open Source ECU Tools
 FAQ •  Register •  Login 

RomRaider

Documentation

Community

Developers

It is currently Sat Feb 17, 2018 7:08 pm

All times are UTC - 5 hours [ DST ]





Post new topic Reply to topic  [ 84 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Wed Nov 02, 2016 9:32 am 
Offline
Newbie

Joined: Wed Dec 05, 2012 11:00 am
Posts: 94
SubaruEnthusiast wrote:
Semi old thread here, but will the tune.hex trick work with this as it did on LV standalone app prior?

I am one of the unfortunate 512kb USDM 04sti's... :(


dschultz wrote:
Not at this time.


What is the tune.hex trick spoken of? I have an 04 STi; IDC so much about the ranges being blank, but I would like to know with certainty whether or not the logger knows where the learned knock values are; does it display all zeros if not defined? Just want to make sure that my table of zeros is really a table of zeros.


You do not have the required permissions to view the files attached to this post.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Wed Nov 02, 2016 12:49 pm 
Offline
RomRaider Developer

Joined: Wed May 20, 2009 9:49 pm
Posts: 5713
Location: Canada eh!
The trick, which the standalone LV application used was to read the table headers from a copy of the ROM file stored on your computer. RR LTV doesn't do this.

If LTV can't determine the addresses to query it will inform you, so the values you plugged are accurate.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 03, 2016 11:47 am 
Offline
RomRaider Donator

Joined: Tue Jan 28, 2014 10:48 am
Posts: 107
Does that mean I can feed standalone application new ROM's someplace and it will pickup the headers?


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 03, 2016 8:34 pm 
Offline
RomRaider Developer

Joined: Wed May 20, 2009 9:49 pm
Posts: 5713
Location: Canada eh!
covertrussian wrote:
Does that mean I can feed standalone application new ROM's someplace and it will pickup the headers?

Have a read here in the Known issues section.
viewtopic.php?f=32&t=2772


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Fri Nov 04, 2016 10:03 am 
Offline
RomRaider Donator

Joined: Tue Jan 28, 2014 10:48 am
Posts: 107
dschultz wrote:
covertrussian wrote:
Does that mean I can feed standalone application new ROM's someplace and it will pickup the headers?

Have a read here in the Known issues section.
viewtopic.php?f=32&t=2772


That's awesome, thanks! :D


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 17, 2016 9:25 am 
Offline
Newbie

Joined: Wed Dec 05, 2012 11:00 am
Posts: 94
What do I need to do to update Logger and/or Editor definitions so I can pull LTV for ROM ID A2ZJ710J that's been patched with MerpMod?

I am willing to do all the work, but I don't really have a grasp of how the different definitions work and define to the software everything. It looks like the latest logger def's (317) have all the MerpMod stuff in them already, so I need to update my Editor def's?


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 17, 2016 5:16 pm 
Offline
RomRaider Developer

Joined: Wed May 20, 2009 9:49 pm
Posts: 5713
Location: Canada eh!
You need an Editor def that translates the ECU ID that the ECU splits out during connection initialization to the stock CAL ID for your ROM.
In stock form ECU ID 2E12495306 is linked to CAL ID A2ZJ710J.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 17, 2016 6:35 pm 
Offline
Newbie

Joined: Wed Dec 05, 2012 11:00 am
Posts: 94
dschultz wrote:
You need an Editor def that translates the ECU ID that the ECU splits out during connection initialization to the stock CAL ID for your ROM.
In stock form ECU ID 2E12495306 is linked to CAL ID A2ZJ710J.


Isn't that what this is?
Image

Quote:
And assuming that's what that is, then maybe the logger def isn't pulling the ECU ID from the right memory location. I think he moved it for MerpMod. I know the CAL ID location changed.

Nevermind, I see now that the ECU ID that is being pulled in the logger matches this screenshot.


Last edited by ilarson007 on Thu Nov 17, 2016 7:11 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 17, 2016 6:43 pm 
Offline
Newbie

Joined: Wed Dec 05, 2012 11:00 am
Posts: 94
This is what I get in the logger when I'm logging (I am connected to the ECU):
Image


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Thu Nov 17, 2016 7:49 pm 
Offline
Newbie

Joined: Wed Dec 05, 2012 11:00 am
Posts: 94
My stupidity knows no ends... I didn't have the MerpMod defs loaded in the editor....


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Fri May 19, 2017 2:04 pm 
Offline
RomRaider Donator

Joined: Sun Jan 03, 2016 10:05 am
Posts: 41
I have ECU ID 2F220A4706 and logger_STD_EN_v232.xml in Logger. In the Ecu Editor I have the experimental definition RR_E2ZK001A_3A.xml defined. When I go to try to do learning view I get an error suggesting the ignition isn't on, wrong com port, etc. Here is the log - any thoughts?

I can edit the rom and/or use romraider logger on this ecu ID otherwise.

Code:
79223 DEBUG [Thread-6] - Serial sending line break
79476 DEBUG [Thread-6] - Serial clearing line (stale data): 00
79599 INFO  [Thread-6] - Connection closed.
79599 INFO  [Thread-6] - TX Manager Stopped.
79600 DEBUG [Thread-6] - QueryManager stopped.
79601 DEBUG [SwingWorker-pool-2-thread-2] - LoggerControllerImpl - QueryManager Thread-6 state: TERMINATED
79603 INFO  [SwingWorker-pool-2-thread-2] - RegOpenKeyEx error [2]
, trying serial connection...
79649 INFO  [SwingWorker-pool-2-thread-2] - Connected to: COM4
79650 INFO  [SwingWorker-pool-2-thread-2] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
79654 INFO  [SwingWorker-pool-2-thread-2] - Retrieving vehicle info & A/F values...
79654 DEBUG [SwingWorker-pool-2-thread-2] - Mode:0 ECU Request  ---> 8010F08CA800FF20B0FF20B1FF20B2FF20B3FF20B8FF20B9FF20BAFF20BBFF20C0FF20C1FF
 20C2FF20C3FF20C8FF20C9FF20CAFF20CBFF20D0FF20D1FF20D2FF20D3FF20D8F F20D9FF20DAFF20DBFF20E0FF20E1FF20E2FF20E3FF20E8FF20E9FF20EAFF20EB0000D100 10C00002300001C000008FF74F0FF74F1FF74F2FF74F3FF2B64FF2B65FF2B66FF2B670000124B
81789 DEBUG [SwingWorker-pool-2-thread-2] - Serial Bad Read response (read timeout): 8010F08CA800FF20B0FF20B1FF20B2FF20B3FF20B8FF20B9FF20BAFF20BBFF20C0FF20C1FF
 20C2FF20C3FF20C8FF20C9FF20CAFF20CBFF20D0FF20D1FF20D2FF20D3FF20D8F  F20D9FF20DAFF20DBFF20E0FF20E1FF20E2FF20E3FF20E8FF20E9FF20EAFF20EB0000D1000
 10C00002300001C000008FF74F0FF74F1FF74F2FF74F3FF2B64FF2B65FF2B66FF2B670000124B
81790 DEBUG [SwingWorker-pool-2-thread-2] - Mode:0 ECU Response <--- 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
81938 INFO  [SwingWorker-pool-2-thread-2] - Connection closed.
81939 DEBUG [Thread-10] - QueryManager started.
81939 INFO  [Thread-10] - RegOpenKeyEx error [2]
, trying serial connection...
81942 ERROR [SwingWorker-pool-2-thread-2] - Retrieving vehicle info & A/F values... Error retrieving values
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
   at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.assertEquals(SSMResponseProcessor.java:93)
   at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.validateResponse(SSMResponseProcessor.java:65)
   at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.extractResponseData(SSMResponseProcessor.java:77)
   at com.romraider.io.protocol.ssm.iso9141.SSMLoggerProtocol.processReadAddressResponses(SSMLoggerProtocol.java:101)
   at com.romraider.logger.ecu.comms.io.connection.SSMLoggerConnection.sendAddressReads(SSMLoggerConnection.java:132)
   at com.romraider.logger.ecu.comms.learning.SSMLearningTableValues.doInBackground(SSMLearningTableValues.java:152)
   at com.romraider.logger.ecu.comms.learning.SSMLearningTableValues.doInBackground(SSMLearningTableValues.java:70)
   at javax.swing.SwingWorker$1.call(Unknown Source)
   at java.util.concurrent.FutureTask.run(Unknown Source)
   at javax.swing.SwingWorker.run(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
81992 INFO  [Thread-10] - Connected to: COM4
81992 INFO  [Thread-10] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
81993 DEBUG [Thread-10] - ECU Init Request  ---> 8010F001BF40
84151 DEBUG [Thread-10] - ECU Init Response <--- 80F01039FFA210022F220A4706FFFFCFA6230403FC000000E0CE7CF9B8E4000C2000000000
 00DC0000451F30C0F03C000043FB00E1000000000000C1F0C4
84151 INFO  [Thread-10] - ECU ID = 2F220A4706
84264 INFO  [Thread-10] - Connection closed.
84264 INFO  [Thread-10] - RegOpenKeyEx error [2]
, trying serial connection...
84311 INFO  [Thread-10] - Connected to: COM4
84311 INFO  [Thread-10] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
84311 INFO  [Thread-10] - TX Manager Started.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Fri May 19, 2017 7:25 pm 
Offline
RomRaider Developer

Joined: Wed May 20, 2009 9:49 pm
Posts: 5713
Location: Canada eh!
It's possible the query or response length is too long.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Sat May 20, 2017 7:28 am 
Offline
RomRaider Donator

Joined: Sun Jan 03, 2016 10:05 am
Posts: 41
dschultz wrote:
It's possible the query or response length is too long.


Would that be caused by something I am doing?


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Sat May 20, 2017 10:56 am 
Offline
RomRaider Developer

Joined: Wed May 20, 2009 9:49 pm
Posts: 5713
Location: Canada eh!
No. The ECU might not be able to handle the long query/response that the LTV application is throwing at it.
You can test by clearing all logged items and then add items to the logging list until it stops responding correctly.
This will provide info about how big the query/response can be.
Provide the rr_system.log for this experiment.


Top
 Profile  
 
 Post subject: Re: RomRaider Learning Table Values feature
PostPosted: Tue May 23, 2017 2:49 pm 
Offline
RomRaider Donator

Joined: Sun Jan 03, 2016 10:05 am
Posts: 41
Here is the rr_system.log.

I added about 18 items to be logged and I think I got the error on #19.

It looks like the last working request was 261 characters long and the one that broke is 285.

[qoute]357725 DEBUG [AWT-EventQueue-0] - Adding logger: [E66] A/F Learning #2 (4-byte)*
357737 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81BD6000000003C03686F713F6153440368BD978D3CBD978D3C1C2A000000007
777000000003F5EDAFC8D
357738 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
359908 DEBUG [Thread-4587] - SSM Bad read response (read timeout): 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
359908 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
359908 ERROR [Thread-4587] - Error occurred
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.assertEquals(SSMResponseProcessor.java:93)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.validateResponse(SSMResponseProcessor.java:65)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.extractResponseData(SSMResponseProcessor.java:77)
at com.romraider.io.protocol.ssm.iso9141.SSMLoggerProtocol.processReadAddressResponses(SSMLoggerProtocol.java:101)
at com.romraider.logger.ecu.comms.io.connection.SSMLoggerConnection.sendAddressReads(SSMLoggerConnection.java:132)
at com.romraider.logger.ecu.comms.manager.TransmissionManagerImpl.sendQueries(TransmissionManagerImpl.java:59)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.sendEcuQueries(QueryManagerImpl.java:303)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.runLogger(QueryManagerImpl.java:235)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.run(QueryManagerImpl.java:153)
at java.lang.Thread.run(Unknown Source)
359909 DEBUG [Thread-4587] - SSM sending line break
360191 DEBUG [Thread-4587] - SSM clearing line (stale data): 00
360364 INFO [Thread-4587] - Connection closed.
360364 INFO [Thread-4587] - TX Manager Stopped.
360364 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
360364 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
360364 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
360364 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
360505 INFO [Thread-4587] - Connected to: COM5
360505 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
360505 DEBUG [Thread-4587] - ECU Init Request ---> 8010F001BF40
362662 DEBUG [Thread-4587] - ECU Init Response <--- 80F01039FFA210022F220A4706FFFFCFA6230403FC000000E0CE7CF9B8E4000C200000000000DC0000451F30C0F03C000043FB00E1000000000000C1F0C4
362662 INFO [Thread-4587] - ECU ID = 2F220A4706
362836 INFO [Thread-4587] - Connection closed.
362836 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
362836 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
362836 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
362836 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
362852 DEBUG [AWT-EventQueue-0] - Removing logger: [E66] A/F Learning #2 (4-byte)*
362977 INFO [Thread-4587] - Connected to: COM5
362977 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
362977 INFO [Thread-4587] - TX Manager Started.
362977 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20 C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
363358 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C3A000000003C036671713F63F0F10366BD999985BD9999851C5D0000000076
76000000003F63C84759
363360 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
363742 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C9D000000003C036673743F6866D10366BD999985BD9999851D0D000000007
676000000003F65AA7BE5
363744 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
364126 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C96000000003C036672733F66C2D40366BD999985BD9999851CD8000000007
676000000003F63C6B456
364128 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
364509 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C54000000003C036671723F632A050366BD999985BD9999851C65000000007676000000003F61CBC94D
364511 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
364893 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C2A0000000036037070723F6339850370BD999985BD8DF8071C670000000077
77000000003F603D0040
364895 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
365277 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81EAD000000003C036679723F645E7F0366BD999985BD9999851D19000000007676000000003F66D03A8F
365279 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
365661 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE819D40000000046036680803F8000000366BD999985BD99998520000000000076
76000000003F80000009
365663 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
366045 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81C7A000000003B03796C6B3F56A4690379BD999985BD854D341B4C000000007
878000000003F7333337A
366047 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B000009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF2 0B1FF20B2FF20B3FF5904FF5905FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
366430 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE82000000000003A036680803F8000000366BD999985BD9999852000000000007676000000003F80000030
366432 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
366830 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE82000000000003A036680803F8000000366BD999985BD99998520000000000076
76000000003F80000030
366832 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
367214 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE82000000000003D036D7D803F7A86CB036DBD999985BD8DF8072000000000007
777000000003F731195F9
367216 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
367597 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE81DBA0000000041036675763F6B78FF0366BD999985BD9999851D6F0000000076
76000000003F60F25ED7
367599 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
367981 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE820000000000041036680803F8000000366BD999985BD99998520000000000076
76000000003F80000037
367983 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F07DA800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF703CFF703DFF20B8FF20B9FF20BAFF20BB00000A00000CFF20C0FF20C
1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EF55
368356 DEBUG [AWT-EventQueue-0] - Adding logger: [E66] A/F Learning #2 (4-byte)*
368368 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 80F0102AE820000000000041036680803F8000000366BD999985BD99998520000000000076
76000000003F80000037
368369 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
370539 DEBUG [Thread-4587] - SSM Bad read response (read timeout): 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
370539 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000
370540 ERROR [Thread-4587] - Error occurred
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.assertEquals(SSMResponseProcessor.java:93)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.validateResponse(SSMResponseProcessor.java:65)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.extractResponseData(SSMResponseProcessor.java:77)
at com.romraider.io.protocol.ssm.iso9141.SSMLoggerProtocol.processReadAddressResponses(SSMLoggerProtocol.java:101)
at com.romraider.logger.ecu.comms.io.connection.SSMLoggerConnection.sendAddressReads(SSMLoggerConnection.java:132)
at com.romraider.logger.ecu.comms.manager.TransmissionManagerImpl.sendQueries(TransmissionManagerImpl.java:59)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.sendEcuQueries(QueryManagerImpl.java:303)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.runLogger(QueryManagerImpl.java:235)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.run(QueryManagerImpl.java:153)
at java.lang.Thread.run(Unknown Source)
370540 DEBUG [Thread-4587] - SSM sending line break
370822 DEBUG [Thread-4587] - SSM clearing line (stale data): 00
371025 INFO [Thread-4587] - Connection closed.
371025 INFO [Thread-4587] - TX Manager Stopped.
371025 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
371025 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
371025 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
371025 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
371167 INFO [Thread-4587] - Connected to: COM5
371167 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
371167 DEBUG [Thread-4587] - ECU Init Request ---> 8010F001BF40
373324 DEBUG [Thread-4587] - ECU Init Response <--- 80F01039FFA210022F220A4706FFFFCFA6230403FC000000E0CE7CF9B8E4000C2000000000
00DC0000451F30C0F03C000043FB00E1000000000000C1F0C4
373324 INFO [Thread-4587] - ECU ID = 2F220A4706
373498 INFO [Thread-4587] - Connection closed.
373498 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
373498 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
373498 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
373498 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
373639 INFO [Thread-4587] - Connected to: COM5
373639 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
373639 INFO [Thread-4587] - TX Manager Started.
373639 DEBUG [Thread-4587] - Mode:0 ECU Request ---> 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
375809 DEBUG [Thread-4587] - SSM Bad read response (read timeout): 8010F089A800FF703EFF703FFF20C8FF20C9FF20CAFF20CB0000D0FF7040FF704100000B00
0009FF56E8FF56E9FF56EAFF56EBFF7042FF7043FF20B0FF20B1FF20B2FF20B3FF5904FF59
05FF5906FF5907FF5908FF5909FF590AFF590BFF703CFF703DFF20B8FF20B9FF20BAFF20B
B00000A00000CFF20C0FF20C1FF20C2FF20C3FF56ECFF56EDFF56EEFF56EFE7
375809 DEBUG [Thread-4587] - Mode:0 ECU Response <--- 000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000
375809 ERROR [Thread-4587] - Error occurred
com.romraider.logger.ecu.exception.InvalidResponseException: Invalid header. Expected: 80. Actual: 00.
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.assertEquals(SSMResponseProcessor.java:93)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.validateResponse(SSMResponseProcessor.java:65)
at com.romraider.io.protocol.ssm.iso9141.SSMResponseProcessor.extractResponseData(SSMResponseProcessor.java:77)
at com.romraider.io.protocol.ssm.iso9141.SSMLoggerProtocol.processReadAddressResponses(SSMLoggerProtocol.java:101)
at com.romraider.logger.ecu.comms.io.connection.SSMLoggerConnection.sendAddressReads(SSMLoggerConnection.java:132)
at com.romraider.logger.ecu.comms.manager.TransmissionManagerImpl.sendQueries(TransmissionManagerImpl.java:59)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.sendEcuQueries(QueryManagerImpl.java:303)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.runLogger(QueryManagerImpl.java:235)
at com.romraider.logger.ecu.comms.manager.QueryManagerImpl.run(QueryManagerImpl.java:153)
at java.lang.Thread.run(Unknown Source)
375810 DEBUG [Thread-4587] - SSM sending line break
376092 DEBUG [Thread-4587] - SSM clearing line (stale data): 00
376264 INFO [Thread-4587] - Connection closed.
376264 INFO [Thread-4587] - TX Manager Stopped.
376264 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
376264 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
376264 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
376264 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
376406 INFO [Thread-4587] - Connected to: COM5
376406 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
376406 DEBUG [Thread-4587] - ECU Init Request ---> 8010F001BF40
378565 DEBUG [Thread-4587] - ECU Init Response <--- 80F01039FFA210022F220A4706FFFFCFA6230403FC000000E0CE7CF9B8E4000C2000000000
00DC0000451F30C0F03C000043FB00E1000000000000C1F0C4
378565 INFO [Thread-4587] - ECU ID = 2F220A4706
378614 DEBUG [AWT-EventQueue-0] - LoggerControllerImpl - Stopping QueryManager: Thread-4587
378614 DEBUG [AWT-EventQueue-0] - LoggerControllerImpl - Waiting for QueryManager Thread-4587 to terminate
378739 INFO [Thread-4587] - Connection closed.
378739 DEBUG [Thread-4587] - Found J2534 Vendor:Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM | Library:c:\windows\system32\op20pt32.dll
378739 INFO [Thread-4587] - Trying new J2534/ISO9141 connection: Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
378739 INFO [Thread-4587] - Tactrix Inc. - OpenPort 2.0 J2534 ISO/CAN/VPW/PWM is not available: J2534 initialization: PassThruOpen error [8:ERR_DEVICE_NOT_CONNECTED], no devices available
378739 INFO [Thread-4587] - J2534 connection not available, trying serial connection...
378880 INFO [Thread-4587] - Connected to: COM5
378880 INFO [Thread-4587] - Serial connection initialised: SerialConnectionProperties[baudRate=4800, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=55]
378880 INFO [Thread-4587] - TX Manager Started.
378880 DEBUG [Thread-4587] - SSM sending line break
379161 DEBUG [Thread-4587] - SSM clearing line (stale data): 00
379349 INFO [Thread-4587] - Connection closed.
379349 INFO [Thread-4587] - TX Manager Stopped.
379349 DEBUG [Thread-4587] - QueryManager stopped.
379349 DEBUG [AWT-EventQueue-0] - LoggerControllerImpl - QueryManager Thread-4587 state: TERMINATED

[/qoute]


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 84 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Style based on FI Subsilver by phpBBservice.nl