No Coms w/ BCM Only

[AK_Eyes]

Hi Everyone,

I have a 2006 350Z and I can connect with all modules in my car except for the BCM using NDSII. I was just looking for some insight, does anyone know if the BCM on these cars uses a different communication protocol or something?

I have tried adjusting the latency timer in the FTDI driver but had no luck. Any suggestions would be appreciated.

Thanks!

[Tom]

Your car might be using the later model BCM. Try the Find ECU function under settings communication and see what active ECU Ids you get.

[AK_Eyes]

Thanks Tom,

I think you are correct. I scanned for ECUID's and all ECU's I would expect to show up do except for the BCM at 40. I do however get an ECUID at FE. I tried putting FE in place of 40 in the BCM ID location and then tried connecting to the BCM with no luck.

Also, I know I have the new style NATS module next to the ignition cylinder and can't calculate my NATS access code the same way as the old module. Any advice on that issue wold be appreciated as well, haha.

[AK_Eyes]

Tom - I was looking through the FSM for my car earlier today and came across something interesting. You are correct, the BCM must be the "new style" because it only communicates with the OBD2 port via CAN, all other ECU's are able to communicate via K Line except the BCM. So I actually have no idea what that other module at FC is?

Anyway, I noticed NDS3 supports CAN communication under the Consult III protocol. Do you know if NDS2 will (or already does) have support for CAN communication under the Consult II protocol?

Thanks!

[Tom]

Unfortunately this happens a lot with Nissan. Some ECUs use k-line, others use CAN or even DDL1.

NDSII doesn't support CAN and the basic VAG Com adapter doesn't support it either. NDSIII app supports CAN but only for ECM diagnostics.