|
Title: Logging issues Code -8 already did slow0x00 bin Patch an 38400 baudrate Post by: RavenT on August 20, 2024, 03:22:10 AM Hey ppl,
I have an issue logging with ME7logger. The Car is converted from 512kb ME7.5 to 1MB ME7.5 ECU (S3 APY pre Facelift). I already did the Patch in the bin File and changed to slow0x00 and 38400 baudrate. I even can't connect stable with only ignition on. It is logging for some Seconds then give me Timeout with Error -8. If Dash fuse ist pulled it works fine. I See some doing Wire Work and switching the K Line to Bypass the Cluster. As this is a customer Car and i am Sure to get this Problem again in other Cars, i am wondering If there could be an other solution / easy removeable etc. Or Bypass the Cluster as a Software solution. I need the Cluster working while logging so without the fuse is no Option. Perhaps someone can Help. Title: Re: Logging issues Code -8 already did slow0x00 bin Patch an 38400 baudrate Post by: aef on August 21, 2024, 01:40:24 AM By patch in the bin file you mean the 3 changes to start the logger when car is running and dash is present?
Code: [Communication] Try this Title: Re: Logging issues Code -8 already did slow0x00 bin Patch an 38400 baudrate Post by: RavenT on August 27, 2024, 11:09:27 AM Yes this 3 Changes.
I already did slow0x00 and 38400 baudrate Like in your picture. Title: Re: Logging issues Code -8 already did slow0x00 bin Patch an 38400 baudrate Post by: dal on August 27, 2024, 04:36:33 PM There is an trick in this case.
Open nefmoto flasher, start the engine, connect do ECU, then disconnect. Right after this start me7logger. Title: Re: Logging issues Code -8 already did slow0x00 bin Patch an 38400 baudrate Post by: prj on August 28, 2024, 02:10:52 AM There is an trick in this case. Open nefmoto flasher, start the engine, connect do ECU, then disconnect. Right after this start me7logger. That just does the same double slow init as ME7Logger can do directly. |