Opening CAN0 stops CAN1 from working?

[doogle]

We are using the C programming API to do some comms on CAN0 of a series 2, 2 channel CAN interface.

The comms works fine BUT if we try to open the CAN1 interface in MAX, it is not available for use to monitor CAN0 etc.

Alternatively, if we have CAN1 open in Max, then CAN0 fails to configure in our C program.

Is it possible to overcome this?

If we do a similar thing configuring and opening CAN0 in Labview, then we still have access to CAN1 so we can use it for monitoring.

Also if we have CAN1 open in MAX, the Labview program still successfully uses CAN0.

[shruti.v]

Hello, yes that should be a problem we can overcome. If you can send me your code then I can try to recreate the problem for you which would help me see where the problem is.

[doogle]

Thanks for responding Shruti,

I attach two files(zipped) from a project which uses a Java front end to talk to a .cpp DLL which manages CAN0 of a series 2 NI-CAN two port card via NI-CAN.

When the our program opens CAN0 using the InitialiseC function, then this must also tie up the CAN1 port as you cannot use MAX to monitor comms on CAN1.

If you need any more information, let me know

[shruti.v]

Hello, I have a few quick questions to ask you before i can try your problem out

1) what CAN cards are you using

2) what is your hardware set up

3) When you say 'the comms works fine BUT if we try to open the CAN1 interface in MAX, it is not available for use to monitor CAN0 etc' does this mean that you cant select the CAN1 or is there an error message that pops up?