Pages: [1]
Author Topic: Communication error with ecu  (Read 9959 times)
S4addict
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 80


« on: July 24, 2014, 07:19:31 AM »

I figured this is the correct thread to post this since its communication
Proticols. I have the blue ebay cable and i took the housing off to verify
That it has a ftdi chip on the board and it does.
But when i try and flash read with nefmoto it gets to communicating timing
And sits there  which is very frustrating now i also did digging before i posted
Ive tried this on 2 diffrrent b5 s4s  and i get the same place each time
The car is plugged into a battery charger.
I downloaded the ftdi drivers and installed them
And i have the com port set as 1
Also this happens if i try and logg the car through nefmoto the cable will connect
But when i hit start reading under the logger i get to timing and thats its
Any help is much appreciated
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: July 24, 2014, 09:10:16 AM »

I figured this is the correct thread to post this since its communication
Proticols. I have the blue ebay cable and i took the housing off to verify
That it has a ftdi chip on the board and it does.
But when i try and flash read with nefmoto it gets to communicating timing
And sits there  which is very frustrating now i also did digging before i posted
Ive tried this on 2 diffrrent b5 s4s  and i get the same place each time
The car is plugged into a battery charger.
I downloaded the ftdi drivers and installed them
And i have the com port set as 1
Also this happens if i try and logg the car through nefmoto the cable will connect
But when i hit start reading under the logger i get to timing and thats its
Any help is much appreciated

After connecting lower the baud rate to 38400.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
S4addict
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 80


« Reply #2 on: July 24, 2014, 09:40:05 AM »

Ok ill try that so far all ive tried was the 52800
Logged
S4addict
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 80


« Reply #3 on: July 24, 2014, 02:04:42 PM »

Tried diffrent baud settings and the
Baud you suggested and im still stuck at negotiating communication timings
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #4 on: July 24, 2014, 04:33:07 PM »

Uninstall whatever drivers you have and install the ones from ftdi's site.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
S4addict
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 80


« Reply #5 on: July 25, 2014, 05:21:12 AM »

it was the baud rate.
i didnt see that you select the baud rate to connect to the ecu.
and then select it again when you go to flash read
works great now
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #6 on: July 25, 2014, 10:27:25 AM »

Which is why I said

"After connecting lower the baud rate to 38400.

Smiley
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
SB_GLI
Hero Member
*****

Karma: +116/-10
Offline Offline

Posts: 1022


« Reply #7 on: July 25, 2014, 11:22:30 AM »

it was the baud rate.
i didnt see that you select the baud rate to connect to the ecu.
and then select it again when you go to flash read
works great now

That tricked me too.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)