Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:TSSW Sprint - Jan 03 - Jan 17
-
Team:Telescope and Site
-
Urgent?:No
Description
Install the LabVIEW RT OS on PXI-PC2, which is in the base data center. This will need the USB from Eric, which has the LabVIEW RT OS inside. I also need to work with IT for this.
This is the reference provided by Eric: Converting a Desktop PC to a Phar Lap ETS Real-Time Target.
For the requirement of desktop PC, follow Requirements for Desktop PCs as Phar Lap ETS Real-Time Targets.
For the installation steps, follow:
1. PC Compatibility with LabVIEW Real-Time or LabWindows/CVI Real-Time for Desktop ETS
2. Using Desktop PCs as RT Targets with the Real Time Module.pdf
Attachments
Activity
- A windows install and no.
- Compatable with RT OS, you only need to remove 1 PXI ethernet card and move to PXI-PC1
- Yes.
- NI-Max is installed on the windows VM tma-windows.ls.lsst.org and will be used to provision the PXI controller. This means that once the USB is used to install Phar lap, I think it can be removed after the reboot that occurs.
- Yes, I believe that is correct.
Eric Coughlin
added a comment - - edited
A windows install and no.
Compatable with RT OS, you only need to remove 1 PXI ethernet card and move to PXI-PC1
Yes.
NI-Max is installed on the windows VM tma-windows.ls.lsst.org and will be used to provision the PXI controller. This means that once the USB is used to install Phar lap, I think it can be removed after the reboot that occurs.
Yes, I believe that is correct.
As part of this ticket
1. Find a flash drive and make it available to the Windows VM
2. I then run the speedgoat kernel transfer tool to write to the flash drive.
3. Then plug in the written drive to the speedgoat.
Eric Coughlin
added a comment - As part of this ticket
1. Find a flash drive and make it available to the Windows VM
2. I then run the speedgoat kernel transfer tool to write to the flash drive.
3. Then plug in the written drive to the speedgoat. 4. Reboot the speedgoat and wait for the kernel transfer to complete.
5. Then unplug the usb and the speedgoat will reboot into the updated kernel.
Eric Coughlin
added a comment - 4. Reboot the speedgoat and wait for the kernel transfer to complete.
5. Then unplug the usb and the speedgoat will reboot into the updated kernel. The speedgoat is the white machine on the top shelf in the same cabinet. There is no account and password. Its IP address is tma-windows.ls.lsst.org.
Windows VM is tma-windows.ls.lsst.org
Eric Coughlin
added a comment - Windows VM is tma-windows.ls.lsst.org We will need IT to help setup a Windows VM for this flash drive to use. Eric will need it to run the transfer tool.
Specifically the tma-windows VM needs to see the flash drive.
Eric Coughlin
added a comment - Specifically the tma-windows VM needs to see the flash drive. We put the one of PXI card from PXI-PC2 to PXI-PC1 (see the red circle):
We tried the options of "Boot using software installed on the hard-disk" and "format". None of them worked for the following errors:
I also tried to use my own USB (with the NI MAX to install the real-time OS), and it did not work as well.
Hernan found the following references:
1. Unable to Find Boot Program Ph_exec.exe in Real-Time Target
2. How to Restore LabVIEW RT Target to Factory Default Configuration
Is this PXI-PC1 or PC2?
Eric Coughlin
added a comment - Is this PXI-PC1 or PC2? Reformat the system and it will ask for the setup of network and installation of software (real-time target software):
The system rebooted by itself and ask for the installation of real-time target:
The PXI-PC2 sets the network configuration to have the IP of 169.254.52.143. But I do not understand why I can not ping it. I thought I am in the control network. I used the VPN as well. Do I need to use the NI MAX to reset the static IP?
I think based on Unable to Find Boot Program Ph_exec.exe in Real-Time Target, I am in the correct condition that the system was formatted. Check with Eric what else he wants.
The PXI-PC2 is reformatted to the LabVIEW real-time OS and can reboot itself (by hard disk) to the safe mode if no software is installed.
We need to put the USB to the machine of windows 10 instead to let Eric to format and install the software to it.
Need to make sure I could use the NI MAX to see two machines and let Eric know to deploy the related software.
I installed the software to the PXI-PC2 and set the IP to be 139.229.145.230. We rebooted it and make sure this value is persistent:
Fan in PXI-PC1 has the failure all the time:
I installed the software to the PXI-PC1 and set the IP to be 139.229.145.231:
PXI-PC1
Name in NI MAX: NI-GenericDesktopPC-B3655747
IP: 139.229.145.231
PXI-PC2
Name in NI MAX: NI-GenericDesktopPC-21111363
IP: 139.229.145.230
Both of PXI desktop PCs had installed the LabVIEW real-time OS and can be reached from the NI-MAX from LSST-WAP (or VPN) now. Please see the comments for the IP and detailed information. Thanks!
Work is complete and looks good on my end.
Eric Coughlin
added a comment - Work is complete and looks good on my end.
Eric Coughlin, please help to answer the following questions in my mind. And if I lost anything, please help to comment as well. Thanks!
1. What files do we have in the PXI-PC2 and do we need to backup the files? This is because the installation of LabVIEW RT OS will format the desktop PC to FAT32.
2. What are the hardware specs of PXI-PC2 and are they compatible with the RT OS? Do we need to remove any PXI card to avoid the resource conflicts?
3. Is the USB prepared by NI MAX and have the ability to reboot, format, and install the RT OS?
4. Should we keep the USB to PXI-PC2 after rebooting with safe-mode or we need to try to install the Real-time module to let the desktop PC can reboot itself from hard-disk? If so, can we do this by NI MAX?
5. It looks like we need to use the NI MAX to set the IP address of this PXI-PC2. Is this correct?