- #Ecm tools mediafire for free#
- #Ecm tools mediafire how to#
- #Ecm tools mediafire drivers#
- #Ecm tools mediafire driver#
- #Ecm tools mediafire software#
I started doing some research on you Scan9495 software and ended up reading about 10 pages of posts on firebird nation.
#Ecm tools mediafire driver#
I've only had the driver that returns the non-genuine-device string. Somehow i never ended up with a copy of the FTDI driver that bricked a chip.
#Ecm tools mediafire drivers#
Now their drivers just refuse to work with the clones.
#Ecm tools mediafire how to#
It took me whole day to learn how to recover them. As for the FTDI scandal, at least they pulled back the kill versions of the driver that rendered the cable unusable for most users. Same reasons.įor what it is worth you can get the mating Delphi/Aptiv connector pins and bodies from Mouser Electronics for a very reasonable cost (about $10 including ground shipping).
#Ecm tools mediafire for free#
I wrote the Scan9495 PC app (LT1-based Camaros and Firebirds 93-95) several years ago and I give that away for free also. And I really didn't want to go through the hassle of trying to collect a fee for it. I wrote this app for myself after I was so disappointed in the ScanerPro one I bought. Thanks a third time for your efforts and sharing! It was dirty-pool that FTDI decided to "break" all of those chip that folks bought with no knowledge that they were fakes. I spent much more time rolling back drivers than I spent actually connecting to the ECM. Sadly I chose one of those awful FTDI UARTs that was a fake. I also found that some wire ferrules worked pretty well as pins for the ALDL connector. If anyone needs a schematic and photo of my rig please let me know. I went ahead and built up my board with the diode and a weak pull-up so I could do a loop test and make sure the USB-TTL converter was working. The note about using a diode on the TX line several posts back was not lost on me. Again, thanks so much for your work and sharing it. MEFI seems to be a big secret and folks want hundreds of bucks for simple scan tools. We baby the boat. I'm really grateful that you've created a tool you're willing to share.
20047 mins today according to your software strikes me as reasonable. I guess the dealer who sold me the boat 9 years ago was honest about the engine hours.
My trailer related suffering continued today but that gave me the opportunity to test your software this evening. The lines for the requests (sent by the pc) are given in the adx file.īyte ptr Name "Value, conversion formula" Commentsġ Frame Length =0x95=0x55+ number of data bytes 0x40 data bytesĥ 0 Malfunction Byte1 "digital, bits correspond to error code" not verifiedĦ 1 Malfunction Byte2 "digital, bits correspond to error code" not verifiedħ 2 Malfunction Byte3 "digital, bits correspond to error code" not verifiedĨ 3 Malfunction Byte4 "digital, bits correspond to error code" not verifiedĩ 4 Malfunction Byte5 "digital, bits correspond to error code" not verifiedġ0 5 Coolant Temperature =N*0.75-40ġ1 6 Same as coolant temperature =byte 10ġ2 7 Startup Coolant Temperature =N*0.75-40ġ3 8 Throttle Position Sensor (TPS) =5*N/255 should be between 0.4V and 4.5Vġ7 12 "Time between Reference Pulses, MSB" Inverse proportional to the RPMġ8 13 "Time Between Reference Pulses, LSB"Ģ3 18 Oxygen Sensor Transition Counter Count=NĢ5 20 BLM Fuel Correction 128 = Unity should be 118-138 (typicaly)Ģ6 21 BLM Cell cells range 0-15 0=ideal 15=WOTģ0 25 Desired idle RPM =N*12.5 not verifiedģ1 26 External Pressure "=5*N/255, =(N+28.06)/2.71" uses the MAP on ignitionģ2 27 Manifold Absolute Pressure (MAP) "=5*N/255, =(N+28.06)/2.71"ģ8 33 Spark Advance =N/2.844 not verifiedĤ1 36 "255 when engine running, 0 when off" constantĤ2 37 Same as byte 40 + 68 =byte 40 + 68 analogĤ4 39 "Injector Pulse Width, LSB" =0.0153*(MSB*256+LSB) "not verified, range is 1-6msec"Ĥ5 40 Air Fuel Ratio (A/F) =N/10 Ideal ratio is 14.7ĥ0 45 Engine Run Time LSB =MSB*256+LSBĦ6 61 Checksum N=modulo256(sum of bytes 0.65) So, in our case, the data pointer really starts at byte 4. In our case, there are multiple request and reply messages possible. Byte 3 may be an extension of the header and, in our MEFI case, it is 0 for "message #0". The column named ptr is incorrect the real pointer starts at byte 3, not 5. The checksum at the end of both the request and reply is calculated by the program and must match what the ecm calculates or the request is ignored. The rest (3-65 in this line) except the checksum are all data. The Frame header, frame length and mode are given in the ADX file. The following is a sample of a typical data string coming from a particular GM ECM. Format is RS232 inverted (0=1, 1=0) at TTL (0-5v) levels. All I know came from the ADX file as far as the parameters.
It was already developed for another user in another forum.
0 kommentar(er)
