Quote:
Originally Posted by Mark McLeod
With some robots there was a similar problem last year, too.
|
Ugh. The underlying "problem" is that the cRIO only attempts to acquire a DHCP address at boot-up; if it doesn't find a DHCP server, it negotiates/acquires a link-local address. There is a way to prevent this from happening - there's a token you can add to an INI file on the cRIO that will tell the cRIO that if it cannot find a DHCP server it will reboot itself and try again up to 3 times.
FTP to the target, and find the following file in the root directory:
ni-rt.ini
In the file, you'll find a section called, "[TCP_Stack_Config]". Under that section, add the following token:
[TCP_Stack_Config]
Halt_On_Error=TRUE
Yup, I know, it's poorly named, but for legacy reasons the name has lived on way past its deserved lifespan. Anyway, this will cause the cRIO to reboot up to 3 times looking for successful communication with a DHCP server. After 3 times, that's it, you must reboot the cRIO yourself (via power or reset button). Give it a shot?
-Danny