Techstream not seeing modules (1 Viewer)

[pax]

I have a 2008 GX470 with 180K on it. Trying to program new keys, but Techstream only sees the first 2 modules. All others show white with an asterisk. Anyone ever see this? What am I doing wrong?

 

[Jstawgn]

Not sure. Not expert by any means.

What cable and what version of Techstream?

 

[white_lx]

By first two modules, you probably refer to the ECM and ABS modules? Those modules communicate with the via CAN protocol in the '08 GX. Most other modules (TPMS, air suspension etc), communicate via the KLINE protocol. These to protocols use physical different pins on the diagnostics port.

If you have one of Mongoose knock-off cables, the KLINE protocol sometimes stops working. Either because of a hardware issue with the cable, or because of some software issues. Was your set-up working before? In that case, it would point at the cable. Can you try another computer?

Lately I have been using a Tactrix Openport (US made, not the knock-off) and results have been much more predictable. My knock-off cable just stopped working one day. Another option is the VCX nano for Toyota, which also comes in a WIFI version.

 

[pax]

Not sure. Not expert by any means.

What cable and what version of Techstream?

I am using the VirtualBox version posted on this site (12.20.024) and a Mini Vci J2534 Diagnostic Cable with the 1.4.1 firmware.

 

[pax]

By first two modules, you probably refer to the ECM and ABS modules? Those modules communicate with the via CAN protocol in the '08 GX. Most other modules (TPMS, air suspension etc), communicate via the KLINE protocol. These to protocols use physical different pins on the diagnostics port.

If you have one of Mongoose knock-off cables, the KLINE protocol sometimes stops working. Either because of a hardware issue with the cable, or because of some software issues. Was your set-up working before? In that case, it would point at the cable. Can you try another computer?

Lately I have been using a Tactrix Openport (US made, not the knock-off) and results have been much more predictable. My knock-off cable just stopped working one day. Another option is the VCX nano for Toyota, which also comes in a WIFI version.

On mine the first two were ECM and Cruise Control.

I have tried the VirtualBox (12.20.024) and a 18 something version on a windows 7 32 bit laptop. No luck with any of those setups getting past just 2 modules. I tried doing a virtual ssetup on my Mac with the same results.

Do you have a link for that cable? I'd be willing to give that a try.

 

[white_lx]

On mine the first two were ECM and Cruise Control.

ECM and cruise control is actually the same ECU. There is no stand-alone cruise control ECU. It is handled by the ECM.

CAN modules: ECM (incl. transmission and cruise), yaw rate sensor, steering angle sensor, ABS unit with actuator
K-line modules: immobilizer, body ecu, TPMS, suspension, VSC, airbag

If you are only able to access the ECM module, and not the yaw sensor, steering angle sensor or the ABS unit, the problem is most likely not a cable hardware issue. All these CAN modules use the same network and if communication to one of them is succesful, you should be able to connect to the others. I would at least try out the ABS module connection too.

Do you have a link for that cable? I'd be willing to give that a try.

Note: the fact that you are only able to communicate with the engine ECU (and the included cruise) and not a single other one makes it unlikely that the cable is the culprit. Here is a link to the Tactrix Openport that I have been using. It is not a low-cost option. I purchased it about 12 years ago, when it was the only option besides an official Mongoose cable.

 

[pax]

ECM and cruise control is actually the same ECU. There is no stand-alone cruise control ECU. It is handled by the ECM.

CAN modules: ECM (incl. transmission and cruise), yaw rate sensor, steering angle sensor, ABS unit with actuator
K-line modules: immobilizer, body ecu, TPMS, suspension, VSC, airbag

If you are only able to access the ECM module, and not the yaw sensor, steering angle sensor or the ABS unit, the problem is most likely not a cable hardware issue. All these CAN modules use the same network and if communication to one of them is succesful, you should be able to connect to the others. I would at least try out the ABS module connection too.



Note: the fact that you are only able to communicate with the engine ECU (and the included cruise) and not a single other one makes it unlikely that the cable is the culprit. Here is a link to the Tactrix Openport that I have been using. It is not a low-cost option. I purchased it about 12 years ago, when it was the only option besides an official Mongoose cable.

I did notice something earlier and am wondering if it could be this:

Battery voltage shows 11.8 volts when not running. I even connected a battery charger before starting to connect.

With the vehicle running, it bumps to 13.8, but I still can't connect to anything.

Could it be a weak battery?

 

[pax]

I

By first two modules, you probably refer to the ECM and ABS modules? Those modules communicate with the via CAN protocol in the '08 GX. Most other modules (TPMS, air suspension etc), communicate via the KLINE protocol. These to protocols use physical different pins on the diagnostics port.

If you have one of Mongoose knock-off cables, the KLINE protocol sometimes stops working. Either because of a hardware issue with the cable, or because of some software issues. Was your set-up working before? In that case, it would point at the cable. Can you try another computer?

Lately I have been using a Tactrix Openport (US made, not the knock-off) and results have been much more predictable. My knock-off cable just stopped working one day. Another option is the VCX nano for Toyota, which also comes in a WIFI ve

By first two modules, you probably refer to the ECM and ABS modules? Those modules communicate with the via CAN protocol in the '08 GX. Most other modules (TPMS, air suspension etc), communicate via the KLINE protocol. These to protocols use physical different pins on the diagnostics port.

If you have one of Mongoose knock-off cables, the KLINE protocol sometimes stops working. Either because of a hardware issue with the cable, or because of some software issues. Was your set-up working before? In that case, it would point at the cable. Can you try another computer?

Lately I have been using a Tactrix Openport (US made, not the knock-off) and results have been much more predictable. My knock-off cable just stopped working one day. Another option is the VCX nano for Toyota, which also comes in a WIFI version.

You were right, it was a cable issue. Got the Tacrix one and everything works exactly as it should. Thanks!