cRIO netmask

[Joe Ross]

In case it helps anyone else, it looks like the default cRIO netmask in this year's image is 255.255.255.0 (it had been 255.0.0.0 in the past). We were able to change it in the measurement and automation explorer to get back to the old value.

This doesn't affect any of the supported network configurations, but did affect us the way our network is set up.

[rwood359]

There is some confusion about the two masks. In CSA training, we were told by Kevin Oconnor:
... occasionally changing the mask to the more limited 255.255.255.0 is necessary for imaging (seems to happen more often with the 4-slot). It should be changed back to 255.0.0.0 afterwards as both FMS and the Kinect Kiosk are not on the teams subnet when using the more limited 255.255.255.0 mask

[RufflesRidge]

I believe Joe is referring to the cRIO mask. The cRIO only needs to talk to the Driver Station so in the typical use case 255.255.255.0 should be fine.

The DS software sets the DS computer mask to 255.0.0.0 which is what it should be when competing on the field.

[rwood359]

Originally Posted by RufflesRidge

I believe Joe is referring to the cRIO mask. The cRIO only needs to talk to the Driver Station so in the typical use case 255.255.255.0 should be fine.

The DS software sets the DS computer mask to 255.0.0.0 which is what it should be when competing on the field.

Thanks, for the clarification. That's why I following all of the CSA discussions.