M48 GETLOG Communications Errors.

Discussion and support for MoTeC's earlier generation ECUs

M48 GETLOG Communications Errors.

Postby Iggsy on Tue Sep 03, 2024 10:33 pm

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.
Iggsy
 
Posts: 2
Joined: Sun Sep 01, 2024 1:18 pm

Re: M48 GETLOG Communications Errors.

Postby SprinterTRD on Thu Sep 05, 2024 5:04 pm

I seem to remember that Interpreter has a Getlog function key (possibly F8). Using it through Interpreter may work better.
SprinterTRD
Pro User
 
Posts: 377
Joined: Wed Jul 16, 2008 9:24 am

Re: M48 GETLOG Communications Errors.

Postby Iggsy on Sat Sep 07, 2024 4:55 pm

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.
Iggsy
 
Posts: 2
Joined: Sun Sep 01, 2024 1:18 pm


Return to M4 and M48 ECUs (including M2R and MLS variants)

Who is online

Users browsing this forum: No registered users and 2 guests