Impossible to connect to Subaru implant
Moderators:R!C0, JonMan, RickS
Hi,
I got problem to connect to a implant "Subaru 2K G2.61" : eatch time the PC doesn't identify the ecu properly. It's reconise as "yyùùù.." or differents names but any time the correct ECU type.
My laptop have real com port, not USB adaptor. ( Dell Lattitude D810 )
The good com port is selected
The baud rate is 38400
I have the Gin file installed
I put ignition on after laptop comunication.
My com parameters are : 38400, 8 bit, no parity, 1 bit stop, Xon/Xoff
The car is an Impreza GrN year 04
In the connection windows, the stream show message "parity error" and sometimes, he ask to install Gin files but with an incorrect and inconsistant name, so impossible to find.
Have you some suggestion?
Thanks to your help
I got problem to connect to a implant "Subaru 2K G2.61" : eatch time the PC doesn't identify the ecu properly. It's reconise as "yyùùù.." or differents names but any time the correct ECU type.
My laptop have real com port, not USB adaptor. ( Dell Lattitude D810 )
The good com port is selected
The baud rate is 38400
I have the Gin file installed
I put ignition on after laptop comunication.
My com parameters are : 38400, 8 bit, no parity, 1 bit stop, Xon/Xoff
The car is an Impreza GrN year 04
In the connection windows, the stream show message "parity error" and sometimes, he ask to install Gin files but with an incorrect and inconsistant name, so impossible to find.
Have you some suggestion?
Thanks to your help
Re: Impossible to connect to Subaru implant
Hi there,
A couple of things to try:
* Click 'connect' in GW when there is no power to the ECU, and then power up the ECU. This can help avoid the ECU going into telemetry stream mode.
* Check that there is nothing interfering on the serial bus (e.g. another controller that is outputting data such as an ACD).
* Buzz out the wiring to check that it is OK with no short-outs and that there is minimal noise.
* You could check that the COM port is working correctly (e.g. download + install teraterm pro and connect up the TX and RX lines on the COM port. Then try typing in teraterm to see if you get the dsame info echoed back.
Hope this helps.
A couple of things to try:
* Click 'connect' in GW when there is no power to the ECU, and then power up the ECU. This can help avoid the ECU going into telemetry stream mode.
* Check that there is nothing interfering on the serial bus (e.g. another controller that is outputting data such as an ACD).
* Buzz out the wiring to check that it is OK with no short-outs and that there is minimal noise.
* You could check that the COM port is working correctly (e.g. download + install teraterm pro and connect up the TX and RX lines on the COM port. Then try typing in teraterm to see if you get the dsame info echoed back.
Hope this helps.