Error -52007
 

While running the LabView CAN Example code in - CAN Jaguar RobotDrive Robot Project

We get the error
--
Error Code -52007 Occurred at CAN Recieve.vi.
NI Platform Services: the requested operation did not complete in time.
--
We changed the code to use CAN Addresses 11 and 12 for the motors and limited our CAN network to include only those Jaguars.

We still get the error.

We disabled the CAN Firmware Version VI as indicated in other discussions. The error now changes to the CAN Send.vi instead.

--
Error Code -52007 Occurred at CAN Send.vi.
NI Platform Services: the requested operation did not complete in time.
--

We get other problems when we run our own code. We'd like to have confidence in the sample code before moving on to our own code.

Thanks for any ideas here.

ps
Additional info - BDC-COMM works great with the network of Jaguars we have. All the Jaguars have been firmware updates.

Re: Error -52007
 

This may sound like a stupid question, but are you sure your Jags are set to addresses 11 and 12? Also, what interface are you using? Serial or 2CAN? Did you properly install the plugin for whatever interface you are using?

Re: Error -52007
 

Make sure you truly have updated your jags. The latest firmware is 87
do you have termination resistor on both ends?
Of course make sure you are talking to the right jags.

Debug where the error is coming from. Ours generally came from setting the device into the speed/voltage mode where it waits for an ACK.
If it is still give you problems I just removed the part of the code that waits for the ACK at frist (not recommended) ,but then realized there was a newer firmware update I was unaware of and installed it and the error went away with default code.

Re: Error -52007
 

So we figured out what was wrong.

We are using a serial connection, and for testing we used only two jags, 11 and 12. The updates are good and all the wiring is correct. The part that was wrong was the dip-switch that controls the serial port. The instructions in setting up the CAN system say to set the switch to on, but we couldn't tell if it was set to off or on. On a hunch I tried it, now we get no errors when running example code.

For those who have a similar problem "on" for the dip-switch means that the low side is toward the edge of the Rio and the high side is toward the bulk of the rest of it.

Re: Error -52007
 

The directions on the First Forge site are copied here. So I want the switch in the off position which means the low side is toward the CRIO. I hope!

If you are using the BlackJagBridgePlugin, you must switch off the console out DIP switch on your controller (and reboot) so that the serial port can be accessed by the driver plugin instead of the operating system's console.

Re: Error -52007
 

You are right, I should have rechecked the instructions. I remembered that they said to do something to the switch I didn't remember if it was off or on. Right now the switch is "off" with the low side away from the cRio and right now it works, we have the robot drive example for Jag works.

We are still working on getting the position control example working, right now the vi for returning Jag info (CAN Jaguar Get Status.vi) doesn't work, and gives a 52007 error. I don't think it is a hardware problem this time, because the CAN open works just fine.

We will work on it.

Re: Error -52007
 

You are just ahead of me and my programming efforts. Is it my imagination or do you lose all of the gain settings each time you cycle power to the Jag?
Is there a way to store the settings in permanent memory or do I need to resend each time I power up?
Tony

Re: Error -52007
 

I believe the only persistent settings for the jag are the firmware and the CAN id. Even if there is other stuff stored, it is a good idea to put the important settings in your robot init code.

Re: Error -52007
 

Alatamors,

Did you ever resolve your -52007 CAN error? If so, how? I know another team having this issue and would like to help them out.

Re: Error -52007
 

Most of the times when I've encountered this error were because I had the CAN bus ID set incorrectly in my code. You can use BDCComm to enumerate the bus (assuming you're using a black jaguar) and validate your CAN IDs. Once that's done, make sure that you have the right ID in your code. Don't forget that termination problems can also cause this error. Termination problems can also show up as a firmware ID of 0.

HTH,

Mike A.