|
Re: wireless communication sparatic/dangerous
The two most likely causes are the DS and the code on the cRIO.
On the DS, verify that the CPU load is reasonable. Especially when the DS reawakens from sleep, there are tasks that can be run which cause the CPU load to be 100% for thirty seconds to perhaps a minute or two. For this reason, short sleeps are not a problem, but I'd recommend an end of day shutdown. It is also possible that multiple users are logged in and background apps are loading the CPU.
On the cRIO, you don't mention a language, but each of the environments has a way to determine the CPU usage on the cRIO. If you are using LabVIEW, go to the Tools menu>>Real Time Module>>System Manager. For the best CPU readings, flip to the VIs tab, disable the Track checkbox, flip back to the Resources tab, disable disk and enable CPU, then press the button to Start Monitoring. This will not tell you what is hogging the CPU, but will tell you if it is occurring.
There are other possibilities, but I'd check these first.
Greg McKaskle
|