Why Won't My VxWorks Controller Reboot or Ping Itself?

Hardware: CompactRIO>>Controllers>>cRIO-9012

Problem:
Why won't my VxWorks controller (such as a cRIO 9012) reboot itself with the RT Reboot Controller VI? Also, why won't my VxWorks controller detect itself on the network with the RT Ping Controller VI?

Solution:
LabVIEW 2009
In LabVIEW 2009, RT Ping Controller VI and RT Reboot Controller VI have been replaced with the RT Get Target Information (MAC, IP, All) VI and RT Restart Target (IP, MAC, Self) VI.

On VxWorks targets RT Get Target Information (MAC) and RT Get Target Information (All) do not return the target on which the VI is run. Use RT Get Target Information (IP) to get this information. This can be seen below.

VxWorks targets don’t support RT Restart Target (MAC). Use RT Restart Target (Self) to restart the target. This can be seen below.

LabVIEW 8.6 and Below
A target running VxWorks Real-Time Operating System, and controllers running this real-time operating system cannot reboot or ping themselves as of LabVIEW Real-Time 8.6 and below. You can reboot your controller using the Watchdog Timer. An Example of doing this can been both below and in the related links.

A target running Pharlap ETS Real-Time Operating System, and controllers running this real-time operating system can reboot themselves (using RT Reboot Controller) and ping themselves (using RT Ping Controller).

To know which Real-Time Operating System is running on a particular controller, see the following KnowledgeBase 4LRA4IQ0: What Operating System is my Real-Time Controller Running and Why?

Report Date: 11/25/2008
Last Updated: 09/30/2009
Document ID: 4ROEMHXY

Your Feedback!

Poor | Excellent

Yes

Document Quality?

Answered Your Question?

Please Contact NI for all product and support inquiries.