cRIO Gateway Address cannot be set properly

[viScience]

Apparently setting the cRIO Gateway to 0.0.0.0 causes the VxWorks OS to barf.  Unfortunately MAX will not allow you to set it as a empty string which apparently is the correct and only setting

for things to work if you do not use the Gateway facilities (which most application do not).  If you use the Reset IP DIP SW then it will default to DCHP and if you are connected to a network PC you will receive a new IP as well as a Gateway address of 0.0.0.0  Does anyone understand this conundrum?

[Kareem_W.]

Hello Sachsm,

What is the model number of your cRIO controller? What version of OS are you running? Can you turn on the "Console Out" dip switch and attach the report? Also what exactly happens when the RT controller "barfs"?

[mattjsimps]

I am also suffering from gremlins in the networking config.

So far this week i have managed to prevent the system from networking at all, and now it seems to have alzheimers. That is to say, it forgets about the gateway and dns you just told it about.

I am also suffering from the inability to set 0.0.0.0.

cRIO 9023 with RIO 3.6.0 

[viScience]

The workaround for now is to set the Gateway to the address of your host pc.

[mattjsimps]

Not gonna help when deployed though.

[viScience]

It works for me and I do not always have a PC based HMI connected on
The cRIO network.