#70 NI_FPGA_PPG: incomplete state definition in instr. driver VI

closed-fixed
5
2010-02-08
2009-12-02
LC
No

After execution of a command sequence the FPGA goes with the released version into a "stopped" state. This state is not taken into account in the two VIs of the instrument driver: NI_FPGA_PPG.load_comand.vi and NI_FPGA_PPG.load.vi. If the FPGA target is in the "stopped" state and the user try to load new command on the card both VIs return an error defined about the "reset..run" (default) case. This is from my point of view not correct because after finishing the user should have the possibility to load new commands on the target. In principle the "idle" case should extended with the "stopped" state?

Discussion

  • Dietrich Beck

    Dietrich Beck - 2009-12-02

    the above is correct for the "load_command", but not for the "load", where the "stopped" has already included

     
  • Dietrich Beck

    Dietrich Beck - 2009-12-02
    • assigned_to: nobody --> dhbeck
    • status: open --> open-later
     
  • Dietrich Beck

    Dietrich Beck - 2010-02-08
    • status: open-later --> closed-fixed
     
  • Dietrich Beck

    Dietrich Beck - 2010-02-08

    fixed by version 0.02 of package DPNI_FPGA_PPG

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks