hihptsi
Full Member
Karma: +6/-0
 Offline
Posts: 52
|
 |
« on: December 05, 2010, 12:12:43 AM »
|
|
|
i tried useing the flash tool avail here to read my ecu in an attempt to modify the .bin,I have much experience with writig code and editing hex for the 1g and 2g dsm applications and have added many extras to those ecu's. now im interested in tweeking on this audi, anyhow to get back to the point. I have the ebay cable the software is able to connect to my ecu i used Slow initialization and connected good. BUT the screen shows the option to pull the .bin greyed out. I will update with a log from the ecu shortly. anyone have any ideas?
also does anyone have any .bins or info regarding modding this application?
thanks everyone
Walter
|
|
|
|
|
Logged
|
|
|
|
kls
Full Member
Karma: +12/-0
Offline
Posts: 97
|
|
« Reply #1 on: December 05, 2010, 12:51:19 AM »
|
|
|
Exactly the problem I had, looking forward to seeing if you find a solution.
|
|
|
|
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #2 on: December 05, 2010, 12:53:54 AM »
|
|
|
ok, please do the same as well. i am going to go outside in few min to get the ecu log maybe someone can help further.
|
|
|
|
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #3 on: December 05, 2010, 01:46:56 AM »
|
|
|
when i "read ecu info" i get this.
Reading ECU info.
Negotiating communication timings.
Successfully changed to new communication timings.
Reading ECU identification option: ECUIdentificationScalingTable
Successfully read ECU identification information
Reading ECU identification option: systemSupplierECUHardwareNumber
Read ECU Identification systemSupplierECUHardwareNumber: 0261207939,
Successfully read ECU identification information
Reading ECU identification option: systemSupplierECUSoftwareNumber
Read ECU Identification systemSupplierECUSoftwareNumber: 1037366883,
Successfully read ECU identification information
Reading ECU identification option: vehicleManufacturerECUHardwareNumber
Read ECU Identification vehicleManufacturerECUHardwareNumber: 0x0D, 8E0909018A , 0xFF,
Successfully read ECU identification information
Reading ECU identification option: calibrationDate
Read ECU Identification calibrationDate: 8E0909518AF , 0003, 0x0300413D, 0x36353236, 0x3836, 1.8L R4/5VT , G03 ,
Successfully read ECU identification information
Reading ECU identification option: calibrationEquipmentSoftwareNumber
Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000100,
Successfully read ECU identification information
Reading ECU info succeeded.
|
|
|
|
|
Logged
|
|
|
|
SundayNightDriver
Jr. Member
Karma: +9/-1
Offline
Posts: 25
|
|
« Reply #4 on: December 05, 2010, 09:12:42 AM »
|
|
|
Maybe you forgot using the "validate memory" option first?
Or display info.. reading the firmware doesn't always seem to work as the first operation.
|
|
|
|
« Last Edit: December 05, 2010, 12:20:25 PM by SundayNightDriver »
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #5 on: December 05, 2010, 06:19:32 PM »
|
|
|
i did try each of the memory maps that are available in the install directory and each one failed. I will go back out in a few in and see if i am missing something. will report back shortly. does anyone else have any tips?
|
|
|
|
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #6 on: December 06, 2010, 02:51:27 AM »
|
|
|
i tried everythingposible i think to try and get this to read the binary on the ecu but it just does not work, here is the log file generated can someone please advise? I cannot contribute to the B6 1.8t stuff until im able to get his thing going. kinda sucks.
----------------------------------------------------------------------------------------------
06/Dec/2010 02:36:54.719: USER: Validating memory layout.
06/Dec/2010 02:36:54.724: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
06/Dec/2010 02:36:54.762: LOG: Sent message with service ID ReadECUIdentification
06/Dec/2010 02:36:54.806: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
06/Dec/2010 02:36:54.845: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000100,
06/Dec/2010 02:36:54.861: USER: Successfully read ECU identification information
06/Dec/2010 02:36:54.889: USER: ECU reports programming session preconditions have been met.
06/Dec/2010 02:36:54.892: LOG: Starting diagnostic session type: ProgrammingSession
06/Dec/2010 02:36:54.919: USER: Starting diagnostic session.
06/Dec/2010 02:36:54.932: LOG: Sent message with service ID StartDiagnosticSession
06/Dec/2010 02:36:54.960: LOG: Received message with service ID NegativeResponse
06/Dec/2010 02:36:54.963: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
06/Dec/2010 02:36:55.001: USER: Start diagnostic session failed, ECU reports security access is required.
06/Dec/2010 02:36:55.012: USER: Validating memory layout failed.
06/Dec/2010 02:36:57.610: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:36:57.624: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:00.124: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:00.134: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:02.639: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:02.653: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:04.098: USER: Validating memory layout.
06/Dec/2010 02:37:04.104: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
06/Dec/2010 02:37:04.131: LOG: Sent message with service ID ReadECUIdentification
06/Dec/2010 02:37:04.145: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
06/Dec/2010 02:37:04.189: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000100,
06/Dec/2010 02:37:04.199: USER: Successfully read ECU identification information
06/Dec/2010 02:37:04.227: USER: ECU reports programming session preconditions have been met.
06/Dec/2010 02:37:04.241: LOG: Starting diagnostic session type: ProgrammingSession
06/Dec/2010 02:37:04.273: USER: Starting diagnostic session.
06/Dec/2010 02:37:04.277: LOG: Sent message with service ID StartDiagnosticSession
06/Dec/2010 02:37:04.305: LOG: Received message with service ID NegativeResponse
06/Dec/2010 02:37:04.308: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
06/Dec/2010 02:37:04.359: USER: Start diagnostic session failed, ECU reports security access is required.
06/Dec/2010 02:37:04.368: USER: Validating memory layout failed.
06/Dec/2010 02:37:06.812: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:06.823: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:09.328: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:09.345: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:11.850: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:11.863: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:14.371: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:14.382: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:15.025: USER: Clearing ECU diagnostic information.
06/Dec/2010 02:37:15.029: LOG: Starting diagnostic session type: StandardSession
06/Dec/2010 02:37:15.056: USER: Starting diagnostic session.
06/Dec/2010 02:37:15.063: LOG: Sent message with service ID StartDiagnosticSession
06/Dec/2010 02:37:15.122: LOG: Received message with service ID NegativeResponse
06/Dec/2010 02:37:15.150: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
06/Dec/2010 02:37:15.191: USER: Failed to start diagnostic session.
06/Dec/2010 02:37:15.207: USER: Received negative message response with code: SubFunctionNotSupported_InvalidFormat
06/Dec/2010 02:37:15.238: USER: Clearing ECU diagnostic information failed.
06/Dec/2010 02:37:17.618: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:17.648: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:20.155: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:20.185: LOG: Received message with service ID TesterPresentPositiveReponse
06/Dec/2010 02:37:22.692: LOG: Sent message with service ID TesterPresent
06/Dec/2010 02:37:27.152: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.154: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.158: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.163: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.168: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.170: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.174: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.176: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.180: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.182: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.187: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.659: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.722: LOG: Failed to read the number of bytes pending receive from the FTDI device.
06/Dec/2010 02:37:27.752: LOG: Resending message. Send attempts: 2
06/Dec/2010 02:37:27.787: USER: Disconnecting because there was no successful communication within the max time limit.
06/Dec/2010 02:37:27.802: USER: Disconnected
06/Dec/2010 02:37:27.806: LOG: Closing FTDI device.
06/Dec/2010 02:37:27.820: LOG: Send receive thread now terminated.
06/Dec/2010 02:40:57.411: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
06/Dec/2010 02:47:16.680: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
|
|
|
|
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #7 on: December 06, 2010, 09:44:09 AM »
|
|
|
as a sidenote i did hve the Revo trial intalled before an has expired. if tis makes any difference.
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #8 on: December 06, 2010, 08:22:57 PM »
|
|
|
That Revo tune should not be a problem. From what Tony has said, if the code to communicate the flash out is present on the ECU, it will spit it out to his software, and the software will write all the chunks to a file.
But back to the point. You will need to select a memory layout _before_ the software will let you click that button to read the flash out. I am not sure which chip the ECU of the B6 Audis have, but maybe there is info in the Wiki -- look there for it.
Once you load the right memory layout file, the gray button will become usable and you will be able to command the software to pull the flash to a file.
And a final remark. I have a B5 S4 Abox with an ECu that supposedly came from the factory with the stock program. Having done this before and successfully having pulled flashes from a different ECU that I have for this car, I have consistently failed to get the flash out and the software terminates with errors. Tony and I have been trying to figure out what is going on. Just letting you know that there may be an issue like that, but you'd get to a potential problem like this if you had successfully loaded a memory layout as I mentioned earlier.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #9 on: December 06, 2010, 11:18:35 PM »
|
|
|
i have tried each memory layout availabe in the 1.6 release (4 in all) and when i clicked verify memory layout it returns a failed each time. It will not lt me read or clear DTC's as well. From what i gather it has a 800 chip in it. His wicki states a 2002 conains a 800BB, BUT mine is 2003 not sure if it is still the same. Im hopeing i get to figure this out because i got some cool ideas id like to work on, to possibly add a couple new features to these ecu's.
ive devloped and sucessfully tested for the DSMS,
Antilag
Studderbox
Native wideband for the ecu
RPM activated switch off an ecu output.
converted the boost guage to read other engine peramaters
and a bunch more.
id really like to do something similar for the audi community.
I
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #10 on: December 07, 2010, 08:46:12 AM »
|
|
|
The 800BB should be the right chip. Reading and Clearing DTCs does not require a memory layout. I think that functionality is simply OBD2 directives, not "programming mode" commands for the specific chip, which requires a memory layout.
Something else is going on. It sounds like you are having the same problems I am having. I cannot verify the memory either. However, when I load the wrong memory layout, it gives an error right away, while the correct memory layout (800BB for my car) goes a lot farther until an error is returned.
Nice work on those DSMs. I did not know that the DSM had such an advanced ECU. I am sued to the DSM from pre-OBD2 days, which a couple of friends of mine have turned into dragsters... I think we will all benefit from your work and experience. Also, the Motronic and the flashes that we use have plenty of empty memory to put your own functions. It may not be exactly easy to implement, but it is worth the try. Did you write assembler functions for achieving the modifications and augmentations that you mentioned?
I will PM Tony about this thread.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #11 on: December 07, 2010, 12:58:39 PM »
|
|
|
interesting, Why am i not able to read or clear DTC's then if a memory layout is not required? It returns a failed everytime i try to read DTC's and or clear them.
Also should i just try reading the flash, im a lil leary of trying to read the ecu if the memory layout is returning a fail, im not new to ECU modding, but these ECU's in the audi seem very picky and finiky i just really dont want to cause any problems.
All my work in the dsm world was done in ASM and compiled i then just put jump to commands in the orginal .bin via Hexidecimal and pointed them to a area of the .bin that was empty and wrote in my new assembled hex with the modifications.
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #12 on: December 07, 2010, 01:48:15 PM »
|
|
|
Go ahead and read the flash with the memory layout loaded. It should work... Nothing will go wrong. When you start and stop a programming mode (reading the flash, etc) cycle power to the ECU with the ignition.
As for the finickiness and pickiness of the ECUs, it is the protocols that are important, not the chips. having said that, I cannot rule out problems because of noise in the wires, etc, which cannot be tackled by electronic means if they are a product of the physical layer of things. What I am saying is that errors may be a result of noise in the serial line from the OBD2 port to your "tester" (that is the laptop running the software).
Yup, I figured you had codes those new functions in just that way.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
kls
Full Member
Karma: +12/-0
Offline
Posts: 97
|
|
« Reply #13 on: December 07, 2010, 03:05:53 PM »
|
|
|
I suspect this is the issue:
06/Dec/2010 02:37:04.308: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
06/Dec/2010 02:37:04.359: USER: Start diagnostic session failed, ECU reports security access is required.
|
|
|
|
|
Logged
|
|
|
|
hihptsi
Full Member
Karma: +6/-0
Offline
Posts: 52
|
|
« Reply #14 on: December 07, 2010, 03:38:19 PM »
|
|
|
Ok, i will go out in a few and try and read this flash hopefully it works.
i still dont get why it will not read DTC's and clear them (not that i have any)
My cable works fin with VCDS so i dont beleve its an issue with the cable.
|
|
|
|
|
Logged
|
|
|
|
|
