M48 GETLOG Communications Errors.

[Iggsy]

I can get a connection established to the M48 ecu fine for tuning, however the GETLOG reaches varying levels of completion before throwing an errors.

Eg. Communications error
19
1D
1F
Etc.

The bigger the file, the worse it behaves.

Im running:

- The correct pci cable
- Windows 7 with a native rs232 serial port on coms 1.
- emp v6.20
- ecu v6.20
- data unload v6.14

I have emp installed directly on the computer and also an emulated version through dosbox. The dosbox version seems to work better for GETLOG, but still very flakey. Works fine for ecu connection.

If there is any guidance or workarounds, to get log files more consistently it would be appreciated.

[SprinterTRD]

I seem to remember that Interpreter has a Getlog function key (possibly F8). Using it through Interpreter may work better.

[Iggsy]

Thanks, I downloaded a version of interpreter, but it doesn’t appear to have a M48 download function.

I did have some success with mucking around with dosbox parameters and managed to get a 100% file download.

I added some rxdelay and it seems to have made the coms a bit more predictable.