Open XC Smoke test.

[Morgan Thompson]

I want to use this to capture can logs with my phone.

So I have the Ford reference VI and I am connecting to a 2004 Nissan Quest. The CAN bus is on pins 6 and 14 but I am not seeing any data on the openXC app.

I see the device connected  to my phone but no CAN data.

what am I missing?

What firm ware should be on my Ford VI?

There were 4 options 

vi-default-firmware-FORDBOARD-ctv7.2.0.bin

vi-emulator-firmware-FORDBOARD-ctv7.2.0.bin

vi-obd2-firmware-FORDBOARD-ctv7.2.0.bin

vi-translated_obd2-firmware-FORDBOARD-ctv7.2.0.bin

Thanks,

MT

[Zac]

Hi Morgan,

You can attempt to get diagnostic data from your Nissan using the vi-translated_obd2-firmware-FORDBOARD-ctv7.2.0.bin firmware. That should attempt to grab as many obd2 standard diagnostic requests. Here's what the firmware is looking for: https://github.com/openxc/vi-firmware/blob/master/src/obd2.cpp#L41.

If you want to see if you can log raw CAN traffic, then you will need to compile your own firmware to do that. Details for doing that are mentioned here: http://vi-firmware.openxcplatform.com/en/master/config/raw-examples.html

Once you try out the translated_obd2 firmware, let us know! Would be curious to see if it works on your Nissan.

Thanks,

Zac

[Morgan Thompson]

SO I used vi-translated_obd2-firmware-FORDBOARD-ctv7.2.0.bin

and I was able to connect via blue tooth. Still no information :-(

I am getting data off of torque. 

I will look into the CAN logging and compiling my own firmware. but I would like to have something working before I dive sown that rabbit hole

[Morgan Thompson]

EDIT: 

I am getting data from the Torque app VIA an ELM327 interface... Not the Ford VI.

[Eric Marsman]

Hi Morgan,

From the Enabler screenshot you provided, you are NOT connected over Bluetooth. Perhaps it is paired with Android, but not the app. What are the lights on the VI doing? You should get 1 blue light on the VI when plugged in to OBD-II and working correctly. Then another blue LED when paired with Enabler correctly.

For the Nissan, what pins are the busses on and what are the bus speeds? 

Regards,

Eric

[Zac]

Hi Eric,

Looks like Morgan's VI is connected. She's got the bluetooth icon and the "XC" notification on the top bar indicating connection. And Morgan mentioned that CAN is on pins 6 and 14 on the VI.

It is possible that your Nissan does not support CAN for diagnostics and instead uses another protocol. The ELM327 supports many variations of connections including CAN, but also others.

Is there a way to tell from the Torque app what protocol is being used?

Thanks,

Zac

[Morgan Thompson]

Eric,
-I get one red LED on the Open XC module.

-Nissan Canbus is on the Mandated pins 6 and 14 AT 500Kbs

Zac,

-It is possible that since this is a 2004 model the ELM327 could be using diagnostic over K-line (Pin 7)

I'll try it on some other vehicles I have access to and report back.

Thanks for the support! 

[Eric Marsman]

Hi Morgan, Zac,

I was basing my not connected comment on the fact that you hadn't gotten device ID or version back yet either. No blue light on the VI implies no connection either. I've seen the icons not always refresh after a lost connection.

A way to test your BT connection with Enabler is to flash the VI with the "emulator" firmware. Then the device can be powered over USB on the desktop and you can test your connection. It will just generate random CAN data. 

You might be right on k-line. A quick search and I don't see any Nissan CAN support until 2005: http://pinoutsguide.com/CarElectronics/nissan_obd2_diag_pinout.shtml. 

Let us know how it goes with the other vehicles.

Regards,

Eric

[Morgan Thompson]

Connected it to a 2016 Nissan and I was able to get a connection!
I didn't grab a screen shot of what PID's were being captured but it was grabbing RPM, TPS%, coolant Temp and MAF readings in real time!

Thanks guys for the help :-)