labveiw can problem

[cmwilson13]

we use the serial can adapter to control 3 jags. we are having a issue where the cpu utilization is always at 100% and getting the error for loops running to slowly. we also gt a error form the set output vi for the can jags. i have shutdown everything that i can think of that could be slowing it down. everything is initialized properly as far as i can tell. i don't have the code with me or i would post pictures. i was wondering if anyone else has used can with the serial converter this year specifically with successes as i think it has something to do with the can code. possibly the set output vi

[cmwilson13]

it might also be unrelated to can so if anyone has any ideas what might be hogging the cpu utilization please say. the camera is disabled so its not that

[Alan Anderson]

I don't think what you're seeing is something that can be blamed on the CAN communication. Look through your code for any while loops that don't have a delay inside them. Start with Periodic Tasks and Teleop.

[cmwilson13]

i have disabled periodic tasks and vison vi,s to troubleshoot and it doesn't help the only thing running is teleop and its the default code with the the jaguars added in. i have everything else disabled i spent 1 hr disabling everything except the drive and the can jags we have no feedback yet from sensors so everything is just wired to the joy sticks to test functionality before we wire sensors. i think its related to the can jag set output vi as it errors right before we get the error for loop running too slowly

[Joe Ross]

Can you communicate with all jaguars using BDC-COMM?

[cmwilson13]

we could when we assigned device numbers and updated im going to check again tomorrow

[Alan Anderson]

I missed this the first time through:

Originally Posted by cmwilson13

we also gt a error form the set output vi for the can jags.

That error is probably telling you what's wrong. What exactly does it say?

[cmwilson13]

all it says is that there is a error at the set output vi
the set vi it specifics is controlling a 550 motor. i am now wondering if it was a problem with the jag itself. i know can is a 2 way interface i wonder if the vi is not receiving something back from the jag that its expecting?