Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Story Points:2
-
Sprint:TSSW Sprint - Apr 1 - Apr 13, TSSW Sprint - Apr 15 - Apr 27
-
Team:Telescope and Site
Description
Give support to run the m2controller inside the cRio
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
Packages installed (handed to Julio Constanzo on a pendrive):
- 2015sp1FPGA-Eng.exe
- 2015sp1LV-WinEng(2).exe
- 2015sp1RealTime-Eng.exe
- NICompactRIO15.zip
m2controller software from Harris (handed to Julio Constanzo on a pendrive):
From the VI Package manager (this is installed by labview) you need to add (per Harris manual LSST_Bible.docs):
- STM 3.1.0.9
- VIPM 2017.0.0.55
I used the network volume license in:
- server: lsst-pdm:27000
It is recommended to move the folder: ts_MTM2_Harris/[Software and Dynamics & Controls|https://github.com/lsst-ts/ts_MTM2_Harris/tree/master/Software%20and%20Dynamics%20%26%20Controls]/Deliverable Software_Source Code_& Applicable Files/lsst-m2 to a windows path with shorter names (as Windows will complaint when directories names are too long)
| Attachment | image-2019-04-11-10-57-41-394.png [ 37616 ] |
Open M2CellController.lvproj, when opening the project it is not going to find some files, it will request for M2CellController_FPGATarget_4-portserialMaster.lvbitx, that you can find in the directory ~\lsst-m2\cRIO_FPGA_BitFiles and select it manually when LabVIEW request you to find it.
Then you should see this interface:
| Attachment | image-2019-04-11-11-02-41-735.png [ 37617 ] |
| Attachment | image-2019-04-11-11-03-09-031.png [ 37619 ] |
Make sure that the IP is correct and then connect to the cRio:
| Attachment | image-2019-04-11-11-05-48-478.png [ 37620 ] |
| Attachment | image-2019-04-11-11-09-50-256.png [ 37621 ] |
Build a new project before deploying it.
- Go to "Build Specifications", right click -> new -> Real Time Application
- Go to Source Files and select TopLevelVIs -> M2CellCtrlrTopVI.vi and click the right arroy on top
- Click OK
| Attachment | image-2019-04-11-11-11-22-669.png [ 37622 ] |
- Right click on the new file created and do Build
- Righ click and do Deploy
Added instructions... still need to move to Confluence
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
| Sprint | TSSW Sprint - Apr 1 - Apr 13 [ 879 ] | TSSW Sprint - Apr 1 - Apr 13, TSSW Sprint - Apr 15 - Apr 27 [ 879, 880 ] |
Andres helped John Bagnasco get the M2 up and running. Story complete.
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Epic Link |
|
| Labels | Chile Integration_Support M2 MainTelescope Software Summit |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
The main problem here was that the cRio didn't come with the m2controller software running by default. The solution was re-deploy it and set by default that the m2controller is executed at the reboot.
To do this, it was necessary to re-create the labview environment that Harris had in their installations with the proper licenses.