Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-35829

Document interface for readDaq in ts_m2fpga project in Phase 1

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_main_telescope
    • Labels:

      Description

      The ts_m2fpga project will have three subVIs created. This ticket is to document the interface for the readDaq subVI in FPGA code.

        Attachments

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-35736 Document the interface for M2 FPGA code

          • Done
          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-36929 Find the cRIO settings to avoid rebooting it before running an application

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-36940 Document interface for readDaq in ts_m2fpga project in Phase 2

          • Done

            Activity

            Ascending order - Click to sort in descending order
            4 older comments
            Hide
            Permalink
            pcortes Patricio Cortes added a comment -

            If you want to connect to the M2 cRIO Simulator from the Terminal, you have to:

            • ssh to the m2-crio-simulator.ls.lsst.org.
            • enter user and password.
            • execute top to check whether the application is running or not.
            • cd /etc/init.d.
            • execute ./nilvrt start to start the application.
            • execute ./nilvrt stop to stop the application.

            If you want to connect to the M2 cRIO Simulator from the LabVIEW project, and the startup.rtexe is running and set as Run As Startup, you will be asked to abort the statup.rtexe. If you say Yes, the startup.rtexe will be aborted and you will be able to connect to the cRIO from the LabVIEW project.

            However, after you abort the startup.rtexe you will not be able to run the application with the ./nilvrt start again.

            The workaround is rebooting the M2 cRIO Simulator, connecting from the LabVIEW project with the Build Specification created, setting the Run As Startup option, and rebooting the cRIO from the LabVIEW project. This will let the startup.rtexe run again and then you will be able to execute the ./nilvrt start and ./nilvrt stop.

            Show
            pcortes Patricio Cortes added a comment - If you want to connect to the M2 cRIO Simulator from the Terminal, you have to: ssh to the m2-crio-simulator.ls.lsst.org . enter user and password. execute top to check whether the application is running or not. cd /etc/init.d . execute ./nilvrt start to start the application. execute ./nilvrt stop to stop the application. If you want to connect to the M2 cRIO Simulator from the LabVIEW project, and the startup.rtexe is running and set as Run As Startup , you will be asked to abort the statup.rtexe . If you say Yes , the startup.rtexe will be aborted and you will be able to connect to the cRIO from the LabVIEW project. However, after you abort the startup.rtexe you will not be able to run the application with the ./nilvrt start again. The workaround is rebooting the M2 cRIO Simulator, connecting from the LabVIEW project with the Build Specification created, setting the Run As Startup option, and rebooting the cRIO from the LabVIEW project. This will let the startup.rtexe run again and then you will be able to execute the ./nilvrt start and ./nilvrt stop .
            Hide
            Permalink
            pcortes Patricio Cortes added a comment -

            I need to check if there is another way to do what I wrote in the previous comment to avoid using LabVIEW Project Explorer. I created the ticket DM-36929 to investigate it.

            Show
            pcortes Patricio Cortes added a comment - I need to check if there is another way to do what I wrote in the previous comment to avoid using LabVIEW Project Explorer. I created the ticket DM-36929  to investigate it.
            Hide
            Permalink
            pcortes Patricio Cortes added a comment -

            Te-Wei Tsai please check this ticket and give me your comments to modify it and continue with Phase 2. Thanks.

            Show
            pcortes Patricio Cortes added a comment - Te-Wei Tsai  please check this ticket and give me your comments to modify it and continue with Phase 2. Thanks.
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Looks good to me. Just need to create (trigger) the ticket phase 2 and continue the work. This process should be helpful for you to understand more in Linux and C language. This is important to have a good and useful interface between the LabVIEW and C/C++ languages. Good job!

            Show
            ttsai Te-Wei Tsai added a comment - Looks good to me. Just need to create (trigger) the ticket phase 2 and continue the work. This process should be helpful for you to understand more in Linux and C language. This is important to have a good and useful interface between the LabVIEW and C/C++ languages. Good job!
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Do not forget to experiment the acquire function in LabVIEW C/C++ API in phase 2 ticket.

            Show
            ttsai Te-Wei Tsai added a comment - Do not forget to experiment the acquire function in LabVIEW C/C++ API in phase 2 ticket.

              People

              Assignee:
              pcortes Patricio Cortes
              Reporter:
              pcortes Patricio Cortes
              Reviewers:
              Te-Wei Tsai
              Watchers:
              Patricio Cortes, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.