NI 9862 CAN

[Meardon]

How should i connect that ODB setup. It has only 1 input 1 output and they appear to be error intput and error output and there is no context help for this block. Is it mandatory?

[Gucky]

The OBD Setup.vi sets two ADCS properties. (Wait Time CF = 0, Time between Waits = 1)

I guess it's not mandatory.

[Meardon]

Anyway how should i connect that OBD setup in that vi if i decide to use it?  Having some trouble with connecting it. As I said before i has only two wires and they look like error lines but if i connet it to error line an error appears. Could you please screen it or something?

Sorry for trouble and thank you.

[Gucky]

Which version of ADCS are you using?

[Meardon]

This version ADCS 1.1.1.f2

[Gucky]

The original ADCS OBD Setup.vi has no input and output. 

I guess you should take the VI from the Diagnostic Transport.llb in :  C:\Program Files\National Instruments\LabVIEW 2012\vi.lib\Automotive Diagnostic Command Set

Have you tried the demo without the OBD Setup.vi?

[Meardon]

I haven't try it yet dont have a car home right now. Tomorrow i will.. 🙂 Just hope it will work with my hardware. I installed NI-XNET 1.7 with CAN  compatibility  so it should work i hope. In NI max i can see my module normally I see him as 9862 module in chassis 9171 so we will see.    There are no errors without OBD setup.

[Karenh]

Hello, I have exactly the same problem with NI 9862. Have you managed to run the example ?

[Meardon]

Hey

I havent tried it yet having problem with car, it's still at service. I will try it on wensday. But I think it should work now. If you isntall NI-XNET 1.7 - with that CAN compatibility layer. Your device will be displayed in NI MAX as NI PCI-8512 (1port) it is above the 9862 module in chassis.  It has CAN set on port CAN 0 speed 125k. Module 9862 should be on CAN 1. But I think if you select CAN 0 and that speed in that VI it should work. Although it might be labeled differently in your NI MAX.

[Gibson]

we are preparing to upload a new OBD Demo which will offer native XNET support instead of going via the NICAN compability layer. We ll keep you updated as soon as the demo is online