A rookie team I’m mentoring (therefore with the 2012 cRio and DLink) is attempting to program the cRio wirelessly, but is having trouble.
We are properly configured and able to program by wiring directly into cRio, and are able to communicate via Dashboard wirelessly. However, when we attempt to Deploy (using LabView) when connected to wireless, LabView does not detect the cRio.
Has anyone run into this issue? Is it actually possible to program the cRio through the AP?
I have been able to successfully deploy code to the robot wirelesly. However, it isn’t advisable because a loss of signal could cause undesirable operation. I would say just stick to the ethernet cord for best results.
You can program wirelessly through the AP, we do it all the time.
Did you properly set the projects IP address when you created it? When you first create a project you set the ip adress as 10.x.y.2 where x.y is your team number.
I dont program in labview i do it in Java all the time been doing it since the cROP has been our platform. I would suggest check your wireless network adapter setting. They need to be on the robots network 10.te.am.xx
Yes, the IP address is set correctly in the LabView project. We will try again tomorrow and report on status, as we programmed on a different computer than we ran our dashboard on (Classmate), so I will need to re-check the computer’s LAN config.
Either way, thanks for reporting that it’s possible, I didn’t want to attempt to chase this and then find out it wasn’t do-able.
Is the IP address for the wireless network settings on the COMPUTER set correctly? (the computer you’re downloading code from) In other words, is your wireless adapter/card/settings set just like you must have set your wired/LAN settings?
Program using a tether, yes it is less convenient but its a faster connection and less chance of interference from other wireless connections. This will also be the way you MUST tether in the pits in competition, so its better to get in the habit now. If you program wirelessly you may have a chance of corrupting the program requiring you to re-image the CRIO.
The only time we ever program with a wired connection is either in the Pits or when we are re-imaging the cRIO. We hardly ever have a problem with interference and have never had an issue where we had to re-image the cRIO because of any data corruption.
When this ability first came out I was skeptical and we had some issues then, but there has been a lot of work done to our control system to help make this option (in my eyes) the best option.
EDIT: We’ve only ever had 1 problem with interference. This was at the St Louis Science Center during a demonstration event. We had 6 FRC teams controlling their robots wireleslly along with many Science Center wireless networks as well. One of the Science Center networks was causing this problem and the next time we did a demo they had it turned off and we didn’t have any problems at all.