|
Title: Newbie Question - ME7 Logger Post by: 12Samsung79 on October 11, 2020, 01:44:01 AM Hello everyone,
I'm new to nefmoto so apologises for asking a question that has probably been asked one million times already. I am trying to use ME7logger but when I try to start the log I have the following message: can't open serial port COM2 Initialization failed, exiting ... exiting (cause=0x1)... I have created an ecu file from an original for my car, and my config has all the correct selections for my application. I'm using a HEX+CAN VCDS cable in dumb mode with VCP drivers. It's on COM2 and my specify com port is also #2 on ME7logger. I have the ignition on and cable plugged into obd port. I have complete understanding how to log my car using VCDS with all relevant blocks, but it's pretty useless because of the low sampling rate. Should I perhaps try pulling the cluster fuse on my car? (ME7.5 Polo GTI) Any help will be appreciated. Title: Re: Newbie Question - ME7 Logger Post by: Blazius on October 11, 2020, 02:36:13 AM Pull instrument fuse, connect while engine is off, ignition off, vice versa, try mode 0x00 init etc.
Title: Re: Newbie Question - ME7 Logger Post by: 12Samsung79 on October 11, 2020, 04:06:00 AM Pull instrument fuse, connect while engine is off, ignition off, vice versa, try mode 0x00 init etc. Thanks buddy, I will give it a go. Title: Re: Newbie Question - ME7 Logger Post by: BlackT on October 11, 2020, 06:52:09 PM 0x1 is cable issue
Title: Re: Newbie Question - ME7 Logger Post by: Geomeo on October 12, 2020, 10:32:14 PM Some other program is using comm 2. Is rosstech open while you are trying to connect with me7logger. If so close. Restart your pc. Make sure you are able to open comm 2 with any program that uses comm ports. Only one program can be used on the comm port at one time. Take a screenshot of the communications port on comm 2 as well and upload. There could be something up with the driver. You can also test the communications port with hyper terminal. It used to be part of Xp back in the day. There are other terminal programs you can use, but hyper terminal was the easiest ever
Title: Re: Newbie Question - ME7 Logger Post by: Blazius on October 13, 2020, 04:32:52 AM Just realised you cant even open port. I always change port to 3 or 4 , as 1 and 2 is usually taken but no matter really. What cable are you using ? Fake ftdi chips wont work with the vcp drivers.
Title: Re: Newbie Question - ME7 Logger Post by: 12Samsung79 on October 15, 2020, 12:54:39 PM Just realised you cant even open port. I always change port to 3 or 4 , as 1 and 2 is usually taken but no matter really. What cable are you using ? Fake ftdi chips wont work with the vcp drivers. I'm using a non-genuine ross tech VCDS 18.2 cable. I'll change to port 4 and see if this helps. Title: Re: Newbie Question - ME7 Logger Post by: 12Samsung79 on October 15, 2020, 10:59:34 PM 0x1 is cable issue If I change the comm options from COM4 and select FTDI instead it brings up this error. Echo test failed, check cable is connected and ignition is on Initialization failed, exiting ... exiting (cause=0x1)... I notice 0x1 is still there, so should I perhaps try a different cable? Title: Re: Newbie Question - ME7 Logger Post by: Blazius on October 16, 2020, 11:18:46 AM If I change the comm options from COM4 and select FTDI instead it brings up this error. Echo test failed, check cable is connected and ignition is on Initialization failed, exiting ... exiting (cause=0x1)... I notice 0x1 is still there, so should I perhaps try a different cable? yes , get galetto cable, its always ftdi because the program is hardcoded for ftdi drivers. Though for me7logger ch340 will work too, made a thread before about it. |