Just ordered one of these (go me!)

From what I gather if exporting with OLS you can avoid the byteswap board as long as you export with swapped lines. Can anyone give a brief summation on that? I saw the diagram earlier (page2) but it leaves a bit to be desired.

Thanks!

Yes, I will gladly pay for a such adapter.

I don't see why not. Or you can use 2x Ostrich with a clever adapter.
I have 2x Ostrich and a Roadrunner, so makes no difference to me which way.

Great work friend. Can you post some pics? Do you use TunerPro with the RR and your own XDF definition?

@terok:
good to hear that it works. how did you do it? with wires?

27C1024 uses the same signal levels and pinout can be mapped to 28f800.

I've got mine now also set on a board and i could be ready to go....but: I can't connect to the ecu, as soon as the RR sits in the place of the 29f800. Neither Nefmoto Flasher nor VCDS could even find the ecu. If i read it out in Bootmode everything's fine! the read file is the same as loaded to the emulator before. This is already the second ecu, as i thought the first one might got smashed while i tried several EEprom contents to make it possibly work. It doesnt matter if i put a immo off + testmodel file on the eeprom or the stock content: i cant connect. Any ideas on this?

Bische: did you manage to find the ecu on the bench via vcds? Also: how did you overcome the problem with replacing the file while monitoring it? shut off monitoring, save it and monitor it again?
I think i'm going to try it tomorrow in the car, although i would guess, that it wont be really successful...

Hi..

I can connect with vcds etc, it shouldn't be any different..

Are you using the byte swap board on your setup?

With regards to the file saving, what I do ,depending on how I'm actually using it , is either use tuner pro rt and just make a change and save the file as is, or use the monitor feature of the emutility. With this is use tuner pro and use the "save as" to create a new different file but the "save" on the monitoring file.. Thus creating an ongoing monitored file and a new version to refer back to if needed.

I much prefer using emutility and monitoring as when you save it obviously does the checksums at the same time and doesn't lead to a locked up emulator , which can occur sometimes after a lot of changes and an ignition recycle . Sometimes fixed with another ignition recycle but sometimes needs a reflash of the EEPROM

yeah i'm using the byte-swap board! I did it step by step this time, because on the first ecu i did everything (soldering+re-programming of eeprom) in one step. With the same result. So i took a second one (both 06a906032HN 001) and programmed the eeprom first (original content immo offed and test model). Before programming the eeprom Nefmoto Flasher couldnt read it because immo seemed to be active (dont know why).  after reprogramming eeprom it was communicating with the non-bootmode progs more or less as normal, only one thing: Nefmoto Flasher couldnt read the content as the ecu seemed not to support security login? I thought it wouldnt matter quite a lot, as i wouldnt need to flash it via OBD anyways.

After soldering the header on, installing the RR and sending a file onto it via emutility - no communication at all... I'm really wondering what it is, as it's as already the second pcb, as said before. I think i'm going to take the first one and resolder a flash on it and check whether this one works like before i did the emu-conversion....never had any bricks after reflashing till now...

what might be worth to mention: I'm using argdubs programmer for the 95040 and i have to use v1.31, as 1.40 doesnt really work as intended (always errors, no connections etc.). Maybe i should take the eeprom out and program it direct? Although i checked the content again and again...



EDIT: ...ok....shame on me   after writing the post i took a look whether all pins of the header are good and by doing so i realized that i also have to have blown off the resistor near the flash while desoldering it and i was just too tired yesterday to see it....
its communicating now with vcds!


EDIT2: it worked for like 10 minutes orso....then tried to read the flash-content with nefmoto and at 4% an error occured and since that = absolutely no communication?
anybody had this before?

EDIT3: after soldering the flash back to ECU#1 and using original eeprom-content : works as if never anything happened....so its only while having the emulator on the pcb....