Trouble connecting CANopen Device NI-9881 on cRIO-9039

[FMDauto]

Hello,
I'm currently starting with my device cRIO-9039, and connecting some Serie C modules. The first module that I tried to connect is the NI-9881. I installed the drivers for cRIO and the NI-industrial communications for CANopen 16.0.

Once connected in the slot, I can´t find the NI-9881 module in MAX and neither in NI-DSM. The same appends with other modules. I read that for some cRIO I have to updated the firmware of my NI9881 with a bitfile, but according to this link the cRIOs in the series 903x and 906x should not require a blank FPGA bitfile.

I assume that I forget some step to achieve lo see my modules in MAX.

I would greatly appreciate any help on the matter (whether it be direct solutions or things I could try). 

[FMDauto]

Hello,

I will answer to myself:

- In the MAX software  the Modules installed in the chassis, can´t be recognized.

- In the NI-DSM, the Modules in the chassis should be able to be recognized in scan-engine mode. Some special modules, like CANopen moduel NI9881, can´t be recognized either in scan-engine mode, becouse they work only in FPGA mode.

- In Labview, all the modules can be recognized. The modules can be searched in scan-engine mode and in FPGA mode.

- My Problem 1: I have a cRIO9039 and a expansion chassis NI9144 both with some I/O modules. In NI-DSM, the modules in the expansion chassis can be recognized, but the modules in the cRIO9039 aren´t recognized.

- My Problem 2: In Labview, I can recognize all the modules in cRIO9039 and NI9144. But the problem is with the CANopen module NI9881. I try to use the example CANopen Read Write CAN Frame. I can compile it, but I have a error running it (image attached). There is a explanation of the meaning of the leds from the module in http://digital.ni.com/public.nsf/allkb/B8C39E05C2F217F58625796D006C983F . My module have both leds off, that means: "No open session on hardware".

Any Ideas how can I solve this 2 problems?

I would greatly appreciate any help on the matter (whether it be direct solutions or things I could try). 

[machinbidule77]

Hello,

I've experienced the same issue and my problem was that the NI9881 present in the project three at "Real-Time Scan Resources" was not deployed in the RT Target.

So basically from the start I did these steps :

- Installation of NI Industrial Communications for CANopen on Windows PC and cRIO9039

- Put the NI9881 module in slot 2, supplied in pins 9 (9-30VDC) and 6 (COM GND)

- Done the Firmware update by using the Example CANopen project

- Then in my project, added the NI9881 in "Real-Time Scan Resources"

- Deployed it to RT

- Tested it with the VI called "CANopen Read CAN Frame" found in the Example Project NI CANopen.lvproj, and a Frame sent each 100ms with PEAK PCAN-View