We are having numerous issues trying to run a labview program. Sometimes we are able to deploy it, sometimes we get a timeout error when checking for conflicts on the Rio.
We have tried deploying a bare minimum mecanum project. Same problem.
We can connect to the Rio, we do have code on currently on the Rio and can control it okay. But if we try to make changes to the project, or deploy a new project, we get the timeout error.
We have rebooted computer, bot, radio, Rio, etc. Hit and miss on success to deploy a project. Yesterday, we were unable to deploy despite over an hour rebooting, trying to deploy bare project, etc.
We have tried 2 different computers, same timeout issue.
Is there a way to wipe the project (code) from the Rio? Is there a link to the Rio firmware to try and re-flash it?
We can connect to the Rio’s Webserver even when labview will time out trying to deploy.
Any help greatly appreciated. Pretty tech savy, but ALWAYS willing to learn from my shortcomings
You roboRIO IP address looks like it might have been hardcoded (static) to .2
Using the normal setup (dynamic) it would be automatically assigned .20 or higher.
You probably want to figure out why that is, or if you did it on purpose, you’d best tell us all the settings you may have made and review them yourself.
You could just have an IP conflict.
You can also try:
pinging roboRIO-4336-FRC.local vs 10.43.36.2 (In case the mdns name will fail)
resetting the nimDNSResponder in the Task Manager/Services (turning the PC off&on like Ari suggested will accomplish the same)
using the direct IP as your LabVIEW Target.
try connecting via USB 172.22.11.2
P.S.
You seem to be using a right-click on Target to transfer the program. Although that usually works, the recommended way is to select “Run as startup” from the Build Specification pop-up to transfer this (after the Build, of course).
Attached is an example of what I’d expect you to be doing to transfer the user program.
After flashing the router and rio a couple of times, the problem seems to have cleared up. We do have the occasional spam broadcast on the rio upon connecting, but a reboot of the rio normally will clear that up.
No real solution, but it is believed the router was/is causing the problem.
Thanks for the help.