[Dsg-hallb_magnets] request to take Torus Fast-Daq offline for deployment debugging

[Ruben Fair]

Thank you Tyler. 

How does this affect your progress on the digital filters? 

Regards 

Ruben 



From: "Tyler Lemon" <tlemon at jlab.org> 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Wednesday, January 18, 2017 5:07:25 PM 
Subject: Re: [Dsg-hallb_magnets] request to take Torus Fast-Daq offline for deployment debugging 

Hello Ruben and Probir, 

The Torus Fast-Daq cRIO is back online. 

The findings of the deployment issue debugging are as follows: 


    1. Despite previous email, it does not seem that GitHub is the cause of the deployment issue. 
        1. I was able to successfully recompile the FPGA code and then deploy to the cRIO when using the GitHub Desktop app to open the programs. 
        2. Stopped, closed all LabVIEW and GitHub windows, GitHub app and used it to reopen LabVIEW project; was able to deploy without error. 
        3. Stopped and redeployed LabVIEW program several times without error. 
    2. Error seems to be caused by any discrepancy in the FPGA LabVIEW VI and the compiled FPGA .lvbitx executable. 
        1. I can force the LabVIEW FPGA error to happen by compiling the FPGA executable and then changing the FPGA LabVIEW VI after compilation. 
        2. This also explains why downloaded code from the "Releases" section on GitHub worked without error. 
            1. The FPGA .lvbitx executable that corresponds to the version of the FPGA VI is downloaded in the release. 

>From these findings, the best course of action will be to recompile the FPGA executable whenever a new version of the FPGA LabVIEW VI is saved. While this is time consuming (recompiling takes ~20 minutes), it should prevent the error from occurring. 

Best regards, 
Tyler 


From: "Ruben Fair" <rfair at jlab.org> 
To: "Probir Ghoshal" <ghoshal at jlab.org> 
Cc: "Tyler Lemon" <tlemon at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Wednesday, January 18, 2017 3:27:22 PM 
Subject: Re: [Dsg-hallb_magnets] request to take Torus Fast-Daq offline for deployment debugging 

Yup go ahead 



From: "Probir Ghoshal" <ghoshal at jlab.org> 
To: "Tyler Lemon" <tlemon at jlab.org> 
Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Wednesday, January 18, 2017 3:09:20 PM 
Subject: Re: [Dsg-hallb_magnets] request to take Torus Fast-Daq offline for deployment debugging 

Tyler, 

I have no problem..! 
Probir 

----- Original Message ----- 
From: "Tyler Lemon" <tlemon at jlab.org> 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Wednesday, January 18, 2017 3:05:46 PM 
Subject: [Dsg-hallb_magnets] request to take Torus Fast-Daq offline for deployment debugging 

Hello Ruben, 

Can the Torus Fast-Daq cRIO be taken offline for a few hours this afternoon to debug the deployment issues occurring? 

At the end of the debugging, the working code presently running on the cRIO will be redeployed. 

Best regards, 
Tyler 

_______________________________________________ 
Dsg-hallb_magnets mailing list 
Dsg-hallb_magnets at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets 
_______________________________________________ 
Dsg-hallb_magnets mailing list 
Dsg-hallb_magnets at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets 


_______________________________________________ 
Dsg-hallb_magnets mailing list 
Dsg-hallb_magnets at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170118/92b50a09/attachment-0001.html>