NetConsole during a Match

[JamJam263]

So as most people know, the FRC Communication Protocol limits what can be sent over the network during competition. Since no one knows what the specific list is, I was hoping someone could tell me if the UDP port that NetConsole uses is included in the allowed communication ports or not. Only because it would save a lot of time and energy to just make it into our dashboard and read the printf s we already have instead of rewriting them to be sent over the network another way.

[Radical Pi]

According to the field staff at one of our regionals, assuming they set up the field right, all non-FIRST UDP protocols are firewalled, not sure about TCP.

If you're desperate for the data, you could use DriverStationLCD (assuming C++, not sure what the name is for other languages), which will display on the DS for your personal display.

[jhersh]

Originally Posted by JamJam263

So as most people know, the FRC Communication Protocol limits what can be sent over the network during competition. Since no one knows what the specific list is, I was hoping someone could tell me if the UDP port that NetConsole uses is included in the allowed communication ports or not. Only because it would save a lot of time and energy to just make it into our dashboard and read the printf s we already have instead of rewriting them to be sent over the network another way.

The UDP port for NetConsole output is 6666. It is not supposed to be permitted on the field. Who knows if the field is configured correctly, however. The worst you can do is try it and have it not work. As suggested earlier, the DS LCD class is pretty simple to use as a replacement if it doesn't work.

[JamJam263]

Originally Posted by jhersh

The UDP port for NetConsole output is 6666. It is not supposed to be permitted on the field. Who knows if the field is configured correctly, however. The worst you can do is try it and have it not work. As suggested earlier, the DS LCD class is pretty simple to use as a replacement if it doesn't work.

Thanks for the info. Might as well try it like you said, if not well use the LCD class, but it would have been nice to have the stacktrace errors visible.