Centralized LabVIEW processing method for specified software and hardware resources

Abstract

The invention discloses a centralized LabVIEW processing method for specified software and hardware resources, the structure of a resource operation vi is composed of a while cycle and a condition structure, the stop condition of the while cycle is set to be normally-on true, and the vi is cycled once each time the vi is called; the enumeration type control operation items comprise all operations on resources, and are in one-to-one correspondence with all the operations through the condition structure branches; a resource handle generated after the resource is opened is recorded in a memory through a shift register of a while cycle, the resource is always in an open state and is recorded in the shift register, and other operations are executed by acquiring the resource handle from the shift register. According to the method, centralized processing is carried out on resource operation, and all operations on resources are completed by one vi. According to the method, the attribute of the resource operation vi is set to be non-reentry execution, and when a plurality of threads operate a single resource, resource conflicts cannot be caused. According to the invention, by adding one queue, the independent thread operation of the resources can be conveniently realized, and the main thread is not influenced.

Description

technical field [0001] The invention relates to the computer field, in particular to a centralized LabVIEW processing method for specifying hardware and software resources. Background technique [0002] In the usual project application programming process, it is often necessary to read, write and call external software and hardware resources, such as the database interface on the computer or the instrumentation connected to the computer RS232 serial port. These resources are unique in the entire system, which means that in any period of time, there is only one program thread calling this resource. If there is a thread that has called this resource, and another If the thread calls it, the program will have an unpredictable error, or the second thread will not be able to call the thread directly, causing a conflict. [0003] At present, the general practice is to write the entire application as a single-threaded mode as much as possible. At least the operation of a certain re...

AI Technical Summary

Problems solved by technology

In many cases, this is feasible, but this approach will lead to resource invocation speed, and the execution time of resources will be accumulated on the main thread of the program. For example, when the test data is saved to the database, the main thread must wait until the save is completed before performing the next operation. Once the saving speed is slow, it will slow down the rhythm of the entire main thread. There is also a premise that a resource must be operated by a single thread. If it must be multi-threaded, it will not work. You can only add a global boolean to mark whether the resource is in use. It is not so flexible, and every time the resource is operated, it must be closed, and another thread will be opened again, which will increase the running time virtually.

Images