TunerPro User Forum

The ECU is expecting the line to be driven low for 100ms. I've been trying to use an Arduino Mega2560 as a multiplexer between the ECU and PC. It's been kicking my ass. I finally got code written to send my 244 bytes of initialization sequence along with the special timings between certain bytes. On...

That sounds like a great project that will benefit a lot of people. I'd offer to help but my C+ programming skills don't go much further than programming an Arduino. Assembler is more my speed. I'd be in as a beta tester.

Thanks for the input. I've been trying my best to not have to program an Arduino to make this work. It seems awfully damned determined that's what it'll take. Are there any pitfalls you navigated that are worth noting?

I hit a snag with the L9637. Almost all the circuits I found for it had a 510 ohm pullup resistor on the K-line. This was preventing the data coming back from the ECU from registering. I could see the data from the ECU on the scope but it wasn't pulling the line close enough to ground for the bits t...

I had a "thinking in reverse" epiphany. I can't send a byte really slow to get the data line low for 100 ms but what if I raise the baud really high and send it a whole bunch of times. The stop bits will likely just be a bit of noise with the line appearing low over the duration. Fingers c...

After getting past the hurdles of getting a cable to communicate with my ecu I have a new issue. My ecu initialization protocol involves holding the data line low for approx 100 milliseconds. I was hopeful that lowering the baud rate really low would allow me to send a byte to drive the line low for...

Well if anything this project has taught me humility. I gave up on my homebrew connection circuit after finding the L9637 chip. Its specifically designed to interface with a K-line diagnostic circuit. My ecu doesn't use the common K-line protocols but it communicates pretty much the same way so the ...

I spent the weekend working on this. I used a USB to rs232 cable to get s serial stream. I feed that into a Max232 to convert it to TTL 5V, and then into a voltage translator to make TTL 12V. This almost worked but it wouldn't pull the data line low when connected to the ECU. What I found is that th...

I'm building an ADX file for my ecu and need a cable to connect to it. My ecu comms is asynchronous serial 9600 baud. The data line rests at 12v and the data is input/output by driving the line low. I'm rather unsure what I need in terms of a cable that is able to interface through USB with TunerPro...

That's awesome! How long has that been a thing?

In my search for answers to get my Ostrich working, I came across another emulator project that people were starting to use. It wasn't targeted at ECU tuning but a few tuners found its potential. A youtube search of eprom emulator will turn up results. At this time, I feel like the Ostrich still rem...

Hey, Thanks. I learned a few things along the way as well. The logic analyzer was less than 10$ and not only did it help diagnose the problem, I also used it to to analyze the diagnostic k-line with a scan tool connected to id the RAM address of RPM, coolant temp, throttle position, and air mass. Th...

I spent most of the day yesterday futzing with this thing. The logic analyzer was showing me the same resetting pattern as I was getting previously. After trying everything I could think of, I made another, slightly shorter cable. It still didn't work but I was now getting a lot of random noise inst...

My joy was short lived. I went to drive the car at lunch today and the test ECU was again dead in the water. I had uploaded a bin with a modified part throttle ignition timing table. It uploaded the bin without protest but upon cycling the key and trying to start, no joy. The up side is that I know ...

Success!!!!!!!!!!!!!!!!!!!!! Plugged in my testing ECU with the ostrich connected using my new short cable. Engine fired right up. After a round of self high fives, I grabbed a usb cable and connected it to the laptop. Opened the XDF and relevant bin to find that data tracing is working too!!! This ...

Supplies came in to make a new cable! Glad I ordered enough pieces to do several because I F-ed up a couple connectors before I got it right. The real pisser is that I had to order 25ft of cable to make one 4 inches long. If someone needs a cable, hit me up. I should be able to try it out tomorrow e...

What application?

ECU tuning from scratch isn't for those willing to easily accept defeat. Out of ideas for simple solutions, I bought a cheapo ebay logic analyzer. I soldered 90 degree pin headers to the back side of the eprom socket and set about logging the result. With the original chip in place, it was churning ...

Yes. That was my first instinct. It made me realize you can't simply sum a block of data if the checksum is within the data. There must be a formula that can account for it but the terms are too general for google to be of any help. On the up side, finding that the checksum sums the whole eprom seem...

The entire eprom is summed as 8 bits into a 16 bit checksum. At least thats what I think is happening. Using HxD and selecting the checksum-16 algorithim option, its dead nuts on for every OE rom I have.

My bin has a checksum value that resides within the checked data. When updating the checksum, the changed checksum value changes the sum of the checked block of data. This makes the checksum invalid. The default checksum plugin just chases its tail trying to update the checksum which invalidates its...

I got a chance to install the ostrich in my spare CIS ecu and try it out in the daily driver. Things aren't looking good for the Ostrich. I made sure the baud rate and latency were right and still no data tracing. Also noted that a lot of the time download from the Ostrich would fail and it would sh...

I found a webpage that had the Demon Reset utility download available. It connected and ran the utility just fine. Loaded the binary again and still no joy. This weekend I'll try to get it swapped back into the old CIS ecu to see if it works there.

I haven't replaced it but I did check its voltage and it was something like 2.98V, which I figure as good for a 3V battery... unless I'm wrong.

Had a chance to try again. I loaded the correct file, and wiped the 24/28/32 switches back and forth a bunch, and gave it a go. Unfortunately, no joy. Its still dead in the water. Pulling the ostrich back out to swap the chip in, I managed to bend a pin, and it didn't straighten. Doh! I have 28 pin ...

Thank you so much for the reply. I followed the links down a rabbit hole and found a test where Craig recommended writing to the ostrich and then reading it with an eprom reader. Kinda on the nose but it hadn't occurred to me. So I wrote my file with Tuner Pro and then read the ostrich with my Wilhe...

I have as Ostrich 2.0 that I am attempting to use, without luck. I ran it daily in my CIS ecu, emulating a 27C256. I'm now trying to use it to emulate a 27C512. The target ECU is a 93 Mercedes HFM, which is a bosch motronic 3.4 Before pulling the emulator from the CIS module, I figured I'd revisit t...

The table at 7750 that is full of the value 128, I'd suspect it could be a low load lambda table. I have a similarly populated table in my wholly unrelated but still Bosch xdf. Values higher than 128 would be richer and below 128 leaner. If you have a wideband and / or an emulator it would be fairly...

My German is more than a bit rusty. Any other sources on how to use this feature? I just get a blank screen that even with trace parameters defined, doesn't appear to do anything.

I've got a 16x16 block of code that contains most of the constants and it would be awesome to get a hit count on it.

I'm starting a thread about the Mercedes Benz 6 cylinder 55pin modules. Specifically for the 104 engine, but the 55 pin 103 module is very similar. The 119 V8 CIS module is almost identical in function, but its an entirely different beast on the circuit board and not addressed in this thread. The 6 ...