04-21-2008 07:56 AM
Yes, the previous serail output was while MAX was unable to see the controller. The S2 (User-defined Safe Mode) switch on the unit was in the ON (forward) position.
I have added two other serial outputs.
The Vaid PXI.txt is with the S2 switch being OFF. The controller is functioning properly and can be seen from MAX.
The Valid Safe Mode PXI.txt is with the S2 switch being ON. The controller is functioning properly and can be seen from MAX.
I see no difference between the original post of the serial output where the controller was bad and the Valid Safe Mode PXI.txt.
How do you set the controller to Safe-Mode from the BIOS?
04-22-2008 04:01 PM - edited 04-22-2008 04:02 PM
Hi Nate,
The BIOS configuration is specific to each controller, so you might not be able to set it as such on the 8145.
Since you can set the static IP when the system is not working correctly, the hard drive does no appear to be completely corrupted, but there may be some conflicts due to the fact the you are not using a reserved IP.
Are you able to ping or FTP to the controller when it is not showing up in MAX? Can you recreate this bad state, where the controller does not show up in MAX, using a reserved IP (such as 192.168.1.x or 10.0.x.x)?
Regards,
Lauren
04-24-2008 12:27 PM
04-24-2008 01:07 PM
04-24-2008 02:40 PM
Hi Nate,
The PXI-8145 RT has a different safe mode than our other controllers (due to it's size/performance specs). The non-standard IP may be causing the difficulty in communication, since the RT Safe Mode may be trying to communicate to the 1.1.1.48 on the web instead of the 1.1.1.48 static IP assigned to his target.
Regards,
Lauren
04-25-2008 11:35 AM
04-28-2008 03:46 PM
Hi Nate,
Yes. Try to use reserved IP addresses as often as possible when using static IPs. It reduces any possible confusion that may occur over where the system will search on the network.
Regards,
Lauren