RIOlog Issues

[Darkseer54]

We are trying to use the Eclipse RIOlog to get feedback from the roboRIO. We have communications working just fine, but anything we print using cout is ignored, or at least the Riolog isn't detecting it and remains blank. We have communications when we use the driverstation, and the subnet mask is set for us properly. We have followed the advice from these threads to no avail. Any assistance is helpful. We are programming in C++.

[diswed0226]

Did you enable RioLog when you imaged the roboRIO?

[hibbsconnor]

I am in the RoboRIO imaging tool and not seeing anything about RioLog. Is that the console out? We have ours checked and still nothing is exported to the RioLog.

[diswed0226]

My bad, console log is the right setting. We got out robot to log by making sure the the subnet mask on the radio, computer, and roboRIO were set to 255.255.255.0

[Darkseer54]

Originally Posted by diswed0226

My bad, console log is the right setting. We got out robot to log by making sure the the subnet mask on the radio, computer, and roboRIO were set to 255.255.255.0

We have set the computer and radio's subnet masks to this, but how do you do it for the roboRIO? I can't seem to find it in the imaging tool.
Thanks,
Zach

[Darkseer54]

We have set everything to a /24 subnet mask. However, we were unable to get any feedback. A mentor from another team was able to get feedback using labview, but we have had zero success with the RIOlog. Has anyone had success with it? Is there anything that we are not doing?

Thanks
Programming Team 1086

[Darkseer54]

We found our issue. It was the Firewall. Thanks for everyone helping. To those having their own issues, make sure you have your firewall turned off. Once we did this, we got connection over wireless. However, our new problem is that once we enable, it only prints once it is then disabled . Is there any way to get real time feedback from RIOlog?

[BradAMiller]

Also, there was an update posted last night that fixed some issues with RIOlog. The netconsole sending program on the roboRIO, in some cases, was waiting for buffers to fill before actually sending messages. Should be better now.