Search the Community

Support "Tag Engine" to interact with your program a variable transfer bridge. Support "Lv_muparser", variables can be operated through expression. Support for drag-and-drop editing of your sequence like in TestStand. The logical steps in the Flow Control "support infinite levels of nesting. In addition to the preset steps in the "Step Pane" ", you can also develop your own test steps according to the project requirements. They will be automatically placed in the" Addon "catalogue. Support user define "Flag" like Skip and Pause(Breakpoint). Unlike TestStand, all of the features in the toolkit can be integrated into your source code, and the toolkit is based on the DQMH architecture. Later, you will be able to call DQMH API in your program to start Sequence Editor or execute sequence (you need to wait for the subsequent package to be uploaded to VIPM).

Support "Tag Engine" to interact with your program a variable transfer bridge. Support "Lv_muparser", variables can be operated through expression. Support for drag-and-drop editing of your sequence like in TestStand. The logical steps in the Flow Control "support infinite levels of nesting. In addition to the preset steps in the "Step Pane" ", you can also develop your own test steps according to the project requirements. They will be automatically placed in the" Addon "catalogue. Support user define "Flag" like Skip and Pause(Breakpoint). Unlike TestStand, all of the features in the toolkit can be integrated into your source code, and the toolkit is based on the DQMH architecture. Later, you will be able to call DQMH API in your program to start Sequence Editor or execute sequence (you need to wait for the subsequent package to be uploaded to VIPM).

I have a VI that reads an image directory and the user can cycle through the images with a next and previous button. The image directory is stored in the SQL database just wondering how would I cycle through the images and display the information on the images that is stored in the database sequentially as the user cycles through the images? Cycle Through Images.vi

Hi Lava's, I have an application which I have constructed around Slave loop obects (Daklu's approach) using the Lapdog messaging library, and I'm currently struggling to decide upon the best approach for implementing a sequence of operations. The application involves doing some DAQ with a USRP device where by I require it to sweep an entire spectral range and acquire samples for each subset, what would seem standard state machine material. I currently have a slave process/loop named "scanner", which I planned to have sit there and wait for a "start scan" message to be sent to it from the powers that be. Upon receiving this start command, it would need to initialise, acquire, move local oscillator, acquire, move local oscillator, acquire... and so on, until it reaches the end of the range. Aside from the slave loop using its own input queue to enqueue messages to itself and carry out this sequence, how else could it be approached? I'm asking because I've been reading around for quite some time on the topic of QSMs and I can see they are widely disliked for reasons I can generally appreciate, however, I'm struggling to think about a better way for a slave loop in this scenario to carry out a sequence of operations when instructed. I.e. for a mediating loop to send it the "start scan" command and then for the scanner to return a message via its output queue to say its done and here are the results. Many thanks in advance for any contributions,