外文文獻(xiàn)翻譯-labview程序框圖設(shè)計-其他專業(yè)-資料下載頁
2025-01-19 09:03本頁面
【導(dǎo)讀】出的風(fēng)格能確保我們實(shí)際應(yīng)用中在規(guī)定時間內(nèi)開發(fā)出整潔，結(jié)構(gòu)清晰的程序。結(jié)合其他規(guī)則，我們能。開發(fā)出可讀性好的，易于維護(hù)的LabView源代碼。LabVIEW的程序框圖長于源代碼表述。一個真正好的程序是發(fā)人深省的，甚至是令人敬畏的，就。事實(shí)上，這兩種極端的。情況就像《風(fēng)格的重要性》中MeticulousVI和SpaghettiVI所表現(xiàn)的那樣。而大部分程序處于藝。術(shù)品和意大利面條之間。一些程序開發(fā)者有連線整齊的習(xí)慣，但程序框圖往往卻大而寬泛。而仍有一些編程人員喜歡使用變量方。兩者之間取得平衡下為特征下完成工作的?？傮w結(jié)論就是在吸引人的程序外觀，個人喜好和程序功能。似乎快速開發(fā)程序的和程序具有美感是相矛盾的。從窗口的工具條中取消選擇包括VILib,包括全局變。取決于設(shè)計樣式，許多頂層程序都應(yīng)包含結(jié)構(gòu)，連線，VI組件和子VI。每個子VI程序代表在內(nèi)存中同一屬性節(jié)點(diǎn)的備份。LabView函數(shù)和將子VI打包成的，因而不需
【正文】 order, and out of structures through their right border. Avoid tunneling wires through the top and bottom borders. Also avoid passing wires through structures if they are not utilized within the structure, unless their purpose is clearly labeled. It is particularly annoying to flip through many frames of a multiframe structure, such as a Case or an Event structure, searching for places where the data in the wire is modified. Place any unwired terminals of front panel objects in a consistent location on the diagram so that developers can find them easily. Note that any terminals not contained by a repeating structure are read only once. Most local and global variables and Sequence structures used in practice are not neces sary. Most often, they are overused by developers who have not learned efficient dataflow principles. The best way to master data flow is to force oneself to avoid variables and Sequence structures unless absolutely required. Indeed, mastering data flow is synonymous with minimizing variables and Sequence structures. To avoid wire clutter and maintain anization, space most shift registers tightly, and group them near the top of the loop. This creates a data highway that is limited to an area near the top of the loop and minimizes wire crossovers. Leave just enough space between the shift registers to apply free labels on each wire near the left terminals. Exceptions to shift register grouping include error clusters and case selectors. Error clusters normally enter and exit near the bottom of loops. Also, case selectors are frequently positioned near the middle. Therefore, error clusters and case selectors are usually kept separate from the data highway at the top. For example, the task ID and error control terminals are improperly labeled task ID out and error out. Additionally, one of the indicators has the generic label Numeric. What is curious is that the subVI has a custom icon and description, and the control terminals are within reasonable proximity to the structure. Perhaps it was partially repaired. The wiring and terminal labels have been cleaned up in Figure 414B. Also, Figure 414C contains equivalent code using the waveform data type and the newer sound output VIs released with LabVIEW 8. This is the preferred implementation. Close inspection reveals that the righttoleft wire is a file path that is formed by some lowlevel functions within an inner Case structure. Whenever a collection of lowlevel functions that work together to perform a cohesive routine appears on the diagram of a highlevel VI, it is a good opportunity for a subVI, This chapter presents style rules that ensure neat and anized diagrams that are practical to implement in real applications with tight deadlines. Combined with the rules in other chapters, they ensure readable and maintainable LabVIEW source code. Moreover, mastery of these style rules may lead to aweinspiring LabVIEW diagrams. 7
畢業(yè)設(shè)計相關(guān)推薦
鄂ICP備17016276號-1