Initial startup of PXI-8187RT results in system error

[dclampp]

I am trying to insert a new PXI-8187RT straight from NI into a PXI-1042 chassis. I have a monitor hooked up to it to see the BIOS proceedings. I also connected a laptop via ethernet to it to do the initial setup, IP configuration, etc. However, this error happens either way:

It seems to boot up fine initially; says "transferring control to user program", goes through RT Boot loader, finds the standard configured IP address, and says "Visa server started successfully".

Controller then reboots within a second or two and produces the following screen:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Transferring control to user program.

(RT Boot Loader)

(Ethernet found, IP address stuff)

Reboot due to system error
Redirecting output to log file
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

All NI-installed software on the RT controller is current. When in this "error log" state, I can inconsistently ftp in to see contents; PXISYS.INI is:

[version]
Major = 2
Minor = 1

[PXI System]
ChassisList = ""


I also have put in a S-Series DAQ into slot 2. I cannot get it to recognize this in MAX. Under remote systems, I have only the system identified by IP, with no controller or chassis identification found. Devices and Interfaces is empty.

I also cannot target the RT controller through LabVIEW for VI download ("Failed to connect to RT Engine"), even when I can explore drive contents via FTP.

Questions: Have I missed an integral step in the setup? How do I add these devices (DAQ, controller, Chassis) under Remote Systems? Is my controller hopelessly broken?

Thank you!

[Arun_V]

Hello dclampp,

From what you are saying I think that the issue is with software installation more than anything else. Under remote systems, right click on your PXI system and format it to wipe it clean. Then install all the required software from the Host Computer. This would ensure that it is a clean install and that the version on the host and target match.

Once everything is properly installed, and if the PXI system is in tha same subnet, then you would see it as 0.0.0.0 under your remote systems. Assign it an IP address (if you have used a crossover cable to connect to it then make sure that you have a static IP address). Once a proper IP address is assigned, you can install software through MAX from the host. Then Right click on the PXI system to identify the controller, followed by the identification of the chassis.

As for the DAQ devices not showing up, it depends on whether they are supported in DAQmx or Traditional DAQ. If it DAQmx it would show up under devices and interfaces. If it is only Traditional DAQ, then go to Tools>> Tradtional DAQ Configuration >> Remote DAQ Configuration and enter the IP address of your controller to get to the Tradiontional DAQ devices.

Once all the above are set, you would be able to successfully target it from LabVIEW.

Best of Luck.

Regards,

Arun V
National Instruments

[Angelantoni]

hi Arun

Even i am having the same problem as the query you answered, but i wanted to know if i format my harddisk then how do i install the operating system? i.e pharlap ETS which is already installed when we bought the system.


Thanx in advance
Arun

[Angelantoni]

Does LabVIEW Real-Time Embedded Software available with the controller has built in to it the RTOS?, i.e by just installing the labview embedded runtime engine i also install the RTOS?

Regards
Arun

[Arun_V]

Hello Arun,

The RT OS is installed from your Windows host computer when you install LabVIEW RT from MAX. So you can definitely go ahead and reformat the system. This is a fairly easy process and I am sure you would not have any issues.

Regards,

Arun V
National Instruments

[Dr_Laine]

I also had this problem, so formatted and reinstalled everything.  I still had the problem of "waiting for RT engine" when I tried to load VIs, and communication performance was very choppy.

I noticed that though my controller was identified, my chassis was not (it is 1006).  When I tried to ID the chassis in MAX, I received "Unhandled exception error executing RunPxiResmanEngine2".  After this, I again had the reboot due to software error and had to reformat and reinstall.

Now I have an unidentified chassis and poor communication performace from my 8187.  I am working with an NI Real-Time AE to resolve.

Is your chassis identified ok in MAX?