Installed real time ETS will not boot

[Tom_Sz]

Hi,

I have verified that the target system is compatible. MAX sees the unconfigured system OK. Using DHCP to get TCP to work is OK after target is rebooted. Software installation looks like it went OK. Rebooting the RT system gives the following error:

User probram stopped at exception: 13
<register dump>
No host debug possible

Fatal error KERNEL.146080: System halted.
ETS Monitor halting with error code 200D.

Search of NI did not come up with a solution.

Thanks for your help

Tom

[JR_A.]

To help narrow things down, I'd start by formatting it to get it back to a clean state and then go through the same steps you did previously and just install the LabVIEW RT component (which should automatically select all of the ethernet drivers as well). That would remove the possiblity of it being related to one of the other driver components. If that still has the same result, or if that is what you did the first time, I'd recommend providing more information about the HW and software especially the version of LabVIEW RT.

-JRA

[Aitortxo]

Hi,

I have the very same problem Tom_sz described.

I'm using

LabView RT 7.1.1, on a

8196 PXI.

All was working fine until yesterday, I couldn't connect to it.

I connected a monitor and saw Exception code 13, kernel error 146080 and ETS monitor halting 200D.

I followed NI support directives to format de HDD and reinstall software.

The same problem after rebooting with reinstalled software.

I have removed all DAQ cards and left tthe controller and chasis alone, and installed just LabView RT 7.1.1

The same problem after rebooting.

I have another PXI on the plant, and will interchange controllers (if it's not being used) and see what happens.

Can someone give me any clue?

Thanks in advance

[Aitortxo]

NI Support told me to connect via FTP and erase all files

'These kind o f errors seem to be related to software problems.
What I recommend is:
If you are able to boot the system (from what you said it takes a while but
eventually succeeds) then target to it from the Host PC via FTP
(ftp://[ipaddress]/) and delete everything you possibly can from the /ni-rt
folder. Also in the root folder delete these files:
- hdmon.bin
- ph_exec.exe
- ni-rt.ini'
After this has been done, try and reboot the PXI system, reconfigure it
through MAX and download the software again onto it.'

But it didn't make any improvement (continuing with error 13, kernel error and monitor halt 200D

After that, they gave me a link to http://digital.ni.com/public.nsf/websearch/E7C79C598DDF40D1862573460026FDDA?OpenDocument to create a USB HDD and test if the HDD is ok.

I created the USB HDD, but the PXI didn't boot from it (it was recognized, and was the first in boot sequence).

So I decided to interchange PXI controllers (as I had 2).

The working one was ok in the failing chasis, so it was the controller or the HDD (or both :-s)

So I interchanged the HDDs between controllers.

The working controller with the failing HDD, fail. With same errors.

The failing controller with working HDD, ok.

So I think it's the HDD. Now I need a new HDD, but I'm in a little town with a single closed computer store. So I'll take one while lunching. I hope it'll be fixed soon.