I get already a little bit further with nefmoto but I still can't connect with ecu... I use 10400 baud and slow init because I found it on the forum here somewhere that is needed for an ME7.5.10 ecu...
I was able to get further than coudn't read device in nefmoto by disabling verify cable in dump mode in nefmoto...

But now I Get this:

20/jan/2016 10:25:59.056: LOG: FTDI device info - Description: Ross-Tech HEX-USB Device Type: FT_DEVICE_232R Device Flags: 0x0
20/jan/2016 10:25:59.056: LOG: FTDI ChipID DLL is loaded, checking chip ID...
20/jan/2016 10:25:59.061: LOG: FTDI device chip ID: 0xB98E1FD9
20/jan/2016 10:25:59.066: LOG: Starting send receive thread.
20/jan/2016 10:25:59.067: LOG: Send receive thread now started.
20/jan/2016 10:25:59.068: USER: Disconnected
20/jan/2016 10:25:59.074: LOG: Setting communication timings to defaults.
20/jan/2016 10:25:59.075: USER: Connecting...
20/jan/2016 10:25:59.081: LOG: Setting communication timings to defaults.
20/jan/2016 10:25:59.082: USER: Starting slow init connection.
20/jan/2016 10:26:01.684: USER: Connecting to address 0x01.
20/jan/2016 10:26:04.485: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
20/jan/2016 10:26:04.527: LOG: Not enough key bytes, read: 0
20/jan/2016 10:26:04.533: USER: Slow init failed.
20/jan/2016 10:26:04.535: USER: Disconnected
20/jan/2016 10:26:04.548: LOG: Setting communication timings to defaults.
20/jan/2016 10:26:04.550: USER: Connecting...
20/jan/2016 10:26:04.558: LOG: Setting communication timings to defaults.
20/jan/2016 10:26:04.560: USER: Starting slow init connection.
20/jan/2016 10:26:07.164: USER: Connecting to address 0x01.
20/jan/2016 10:26:09.966: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
20/jan/2016 10:26:10.008: LOG: Not enough key bytes, read: 0
20/jan/2016 10:26:10.013: USER: Slow init failed.
20/jan/2016 10:26:10.016: USER: Disconnected
20/jan/2016 10:26:10.031: LOG: Setting communication timings to defaults.
20/jan/2016 10:26:10.033: USER: Connecting...
20/jan/2016 10:26:10.049: LOG: Setting communication timings to defaults.
20/jan/2016 10:26:10.051: USER: Starting slow init connection.
20/jan/2016 10:26:12.653: USER: Connecting to address 0x01.
20/jan/2016 10:26:15.455: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
20/jan/2016 10:26:15.496: LOG: Not enough key bytes, read: 0
20/jan/2016 10:26:15.501: USER: Slow init failed.
20/jan/2016 10:26:15.503: USER: Disconnected
20/jan/2016 10:26:15.517: LOG: Setting communication timings to defaults.
20/jan/2016 10:26:15.525: LOG: Closing FTDI device.
20/jan/2016 10:26:15.528: LOG: Send receive thread now terminated.

Thanks for your answer!
What is the best way to do that? Is it also possible through obd to read eeprom from the valeo immo box?
I know its possible to read it via an MAX2990 I²C interface... But I its not that easy anymore to take out the immobox to do that because there are added quite some electrics that are placed before the immo box so I can't get it directly out of the car...

did you read pin from valeobox by obd??? that should be impossible, think you got it from ecu then?

you can just desolder the 24c04 from immobox and read it in external programmer. Or power the immobox and read it using a clip

Hi!  so i just read the bin from the valeo immo box 24c04 using an old school willem chip programmer. I did it while on the board using jumper wires and an ecm stand. I looked at the file and used info about where the skc was from info I found in OBD 365. c o m. Used the vagcom and it accepted the code! so a small victory. I had only 5 pins connected. I researched the datasheet from the chip to decipher how to read the chip as far as what to probe. There were pin out holes i put my leads into as some spots so that was handy. Hope this helps! I haven't found info on reading and re writing the ecm to eliminate the immo yet but still fighting.