Appendix 1 42
Appendix 2
Results of research during studies
Innovative statement of thesis of the network college 45
Introduction
1. 1 question/background and purpose of the paper
As the domestic real estate sector continues to develop, so does the lighting sector, the energy problem is growing. In buildings, electricity consumption is about 60 to 80 per cent, with lighting consuming 10 to 20 per cent of total electricity. As the temperature insulation of buildings increases and other heating and cooling measures are used, the proportion of electricity consumed for lighting will continue to rise, resulting in the emergence of various types of light controllers and associated systems in the market。
At the research and development or manufacturing stage of the new light controller, the strength and weakness of its function are measured by the measurement and analysis of a large amount of data. Traditional testing methods are generally manual and testers are first subjected to a series of steps, such as regulation, electrical access, preheat, measurement, reading, recording, reconciliation, each of which requires manual handling and recording of test results by surveyors. Upon completion of the test, the test data will be manually entered into the computer on a case-by-case basis, leading to a complete test report. Because of manual measurements, unexpected errors are inevitable, and manual data entry increases the probability of errors. This has resulted in extensive manual and time-based test reports, which have significantly reduced accuracy and affected the import and volume timing of the final product。
In order to compensate for the problem points of the traditional testing chain, the advantages of automated testing should be realized using existing technologies, subject to the stability of the testing process, the timeliness of the collection of test data and the traceability of test data. Automated testing systems have the advantage of rapid automated testing, low maintenance and implementation costs, high accuracy and stability. The completion of the testing system will significantly improve the efficiency of the testing and save significant editorial time for reports, thereby reducing the time required to detect to produce reports, improving the accuracy of reports and better meeting client needs. It would also free the technicians concerned and allow them to devote more energy to other, more meaningful things. For the production line, the test is responsible for the final product quality, and after automated testing, the test data and results will be automatically backed up by the system in the database to a certain extent to avoid the risk of human-induced data errors, enhance the reliability and authenticity of the detection data, while automated testing will standardize the testing methods of the relevant projects at the research and development stage, reduce errors resulting from inconsistent understanding of standards by the tester manually and ultimately reduce the risk of testing。
1. 2 analysis of the status of national and international research
There are a number of organizations and institutions both inside and outside the country currently engaged in research on functional testing systems, especially in the production or marketing of instruments. Of these, more mature foreign research is done by fluke, whose main software product met/cal testing software, which is simple, comprehensible, easy to learn and integrated aesthetic features, has been published and sold externally. However, the software could not be used directly after it had been acquired, it would still need to be modified and the template for its certificate would need to be modified accordingly, with some requirements for standard equipment. The software is expensive and cannot be combined with some of our existing testing software, so it is not adaptable on our side. As a result, testing software developed by foreign manufacturers or institutions is not sufficiently applicable in the country。
There are a relatively large number of units developed for automatic testing of light controllers in the country, mainly in the long and bead triangles, which have extensive development experience. They have more than a decade of project experience. They are currently developing software using a more popular labview testing platform, which also has an absolute advantage in low-cost solutions. For example, in areas such as audio testing, radio frequency testing, temperature testing and embedded development design, the programme has been adopted and recognized by a growing number of smes with its short, efficient and low-cost advantages。
In general, domestic research on and use of automated functional testing systems has started late, with a weak theoretical base and technical capacity, and a gap between international levels. It is confident that in the near future, domestic research on functional testing systems will catch up and exceed world averages。
1. 3 main work elements of the papers
The subject was derived from a working project of the author aimed at changing the method of measuring the light controller function from manual to automatic testing. The main elements of this work are as follows:
(b) to become familiar with the operation of the light controller and to gain insight into the testing needs
Select an appropriate software development platform to optimize design using the various functions that the platform can provide
Design hardware programmes for testing systems and select appropriate hardware and equipment
Designing software programmes for testing systems and selecting software structures for use
The software is combined with hardware to produce a bottom program module
Test systems for measurement and validation。
In all, each of the six main elements is not independent of each other, and some of the work needs to be carried out in a multi-person manner. The detailed structure and design methodology of the various components will be explained in detail in the body of the paper。
Key technology development for functional test systems
2. 1 working principles and application scenarios for light controllers
Developing energy codes, changing lighting technologies and high-performance buildings require strong and flexible solutions. The adaptive digital lighting management (dlm) technical platform provides a control infrastructure for each switch, plug and light load to achieve optimal energy performance and provide solutions to meet the cable or wireless needs of each building and space。
The lmrc-110 series of indoor controllers, consisting of one or two relay switches with a total capacity of 10 amperes, is an efficient switch power source and double 0-10 volt output/relay control to adjustable loads, including compatible led drives or electronic ballasts. They are basic management (dlm) systems for digital lighting and allow access to integrated sensors, light control and energy efficiency switches. The plug n'go automatically configured the dlm room controller to build functional installation components on the basis of the plug-in automated system. When the room controller is connected, only the encumbrance sensor is used, and the system defaults for automatic switch/off. If a wall switch is added to a system with a switch, the loading default is manual/automatically closed. If there is a wall switch and multiple loads, load 1 opens for automatic loading, with the default for manual load control; all loads automatically close. When the system is activated, the default luminous parameters include: brightness scenario presets 1-4; fades; decay; and gradient rates。
The lmrc-110-series room controller operates at a 120 or 277 voltage, 10 ampere feed and 2 power source sensors and switches through the dlm local network. Once powered, plug n'go automatically configures the energy-saving operation of most system components. The room controller is then darkened or the switch lighting or electrical load is used to respond to input from the communication equipment. When a tuning input is received, when it rises to above zero, the relay switch is turned on when it reaches zero to coordinate the control of the power and 0-10 volts to load. They also monitor the total connection load from the current. Each room controller stores up to 16 scene preset levels for each fuzzy output. In addition, the lmct-100-2 wireless configuration tool can be used to load the configuration. The room controller, including the circuit that opened their 0-10v signal, lost the lmrc power, so that any single powerer or driver connected to the 0-10v line would achieve maximum brightness。
The lmrc-110-series room controller is the ideal single or multiple area switch/off or light-control application, including private offices, open offices, conference rooms and classrooms. Measurement models help facility managers to track electrical use of buildings for lighting or other loads. The dlm local area network (lan) is open and requires a web bridge (lmbc-300) power source measurement reading to a segment manager or bas。
2. 2 software development environment selection
The functional test system software described in this paper was developed using labview, a virtual instrument developed by ni, as a development environment, as a graphical programming language, easy to understand and easy to produce. The current mainstream virtual instrument is programmed in two languages, general programming and professional graphical programming. The former are typically represented by visual c++, visual basic, c, delphi, etc.; the latter are typically represented by ni, lab view, hp, vee, iotech, dasylab, hem, snap-master, etc。
Based on a needs analysis for the development of the pilot software for light controller functionality, the development environment is required to have the following characteristics:
1. Be easily and quickly programmed, and be easily understood and modified
2. The design of the interface programme has been extended to allow the development of a software interface that is easily interactive and simulates the front boards of complex instruments
3. Data visualization analytical capabilities and the development of processes that require interface-driven programming with instruments and bus resources。
Graphical programming languages are more appropriate in the development of virtual instruments. The u. S. N. Virtual instrument development software labview, as an environment for development, is broadly consistent with other languages in programming terms, but as a graphical programming language, text programming languages have their own unique characteristics, as shown below:
Labview provides a visualized human interface, which is essentially “as seen and as obtained”。
In the course of its development and commissioning, labview may use high-light execution, single-step operation, breakpoint setting, etc。
3. Labview uses the data stream programming model, operating multiple parallel nodes at different threads, as required, and automatically operating multiple threads。
4. Labview applications carry their own standard functional functions of communication bus lines pci, gpib, daq, vxi, pxi, rs-232, and support hardware modules of a wide variety and variety, including data acquisition cards, vxi instruments, bus and special hardware card。
The external interface of labview software is powerful, and common applications (e. G. Word, excel, notebooks, etc.) can be called through an external interface, or the writing module of dll to other programming languages can be loaded。
Labview, with its powerful internet function, supports various networked communication protocols, with its own tcp/ip, active x, dde standard function library, which greatly facilitates the development of remote sensing and control。
7. Transplantation between multiple operating system platforms。
This automated testing software was therefore eventually selected for the ni virtual instrument development software labview as a platform and environment for development, mainly for the following reasons:
1. Labview has been widely applied as an industry-recognized language in test system design research, with significant advantages in the field of monitoring and control. This language is itself developed by ni for measurement instruments and is widely used in the field of test measurements. As a result of its extensive application, all mainstream instrument manufacturers are equipped with a dedicated lab view driver at the time of the release of their products to enable the labview program to achieve control over these hardware devices。
2. Labview application development interfaces are strong intuitive and complete with toolkits and modules required in various monitoring and control areas. In the development of virtual instrumentation programmes, users need to simply call on the software's own toolkit function to quickly form the various program modules and the benefits of the project's development progress are self-evident. The development of the labview language is statistically more than 10 times more efficient than the development of the normal text language。
The main task of this light controller function testing system is for data collection and data transmission. Labview has significant advantages in accessing various functions such as data acquisition and communication boards, and ethernet communication is supported by a dedicated toolkit that will help test system network research。
This light controller functional test system requires real-time data processing, real-time transmission, and labview's data flow programming model and multi-wire mode of operation can significantly speed up program implementation, improve program efficiency and meet system data real-time processing and transmission requirements。
In view of this, this automated test software eventually adopted the development environment of labview。
2. 3 summary of technology for virtual instrument development
In order to improve product quality, shorten the development cycle and improve product reliability, 1986, the united states national instrument corporation (natio)Engineers from nal information ni developed a practical virtual instrumentable programming software, labview. The widespread availability of this software has allowed engineers and scientists to focus on their areas of study without having to devote their time and energy to the control of the instrument and the achievement of algorithms, thus liberating the process workforce to achieve results as soon as possible. To this day, labview has taken over half of the fences programmed by virtual instruments。
At the enterprise level, engineers use labview to develop large-scale test measurement software systems. Because of its strong strengths in the field of test measurements, labview has been greatly developed in a wide range of industries, including aerospace, auto manufacturing, telecommunications and electronics, the medical industry, oil and electricity, and new energy sources。
In the automobile industry, technology is increasing, and a car tends to combine hundreds of sensors, requiring a vehicle's electronic control unit (ecu) to be faster and more capable of processing. At the same time, the growing configuration and interaction between cars and drivers has led to an increase in the number of euu interfaces that respond to user instructions. For this reason, the performance test of the euu is particularly important。
Labview has also developed considerably in the medical sector, with an implanted hearing aid issued by cochlear in sydney, which has gained considerable resonance within the industry, where the testing platform for the product is based on ni hardware. The test platform uses the test software developed by labview not only to select the test sequence, monitor the testing process, but also to generate test reports automatically, and to write test data into the database for subsequent queries and analyses。
Labview programming can be applied not only to large-scale testing, measurement and data analysis systems, but also to the absolute advantage of labview in low-cost solutions. For example, in areas such as audio testing, radio frequency testing, temperature testing and embedded development design, the programming developed with labview has been adopted and recognized by a growing number of small and medium-sized enterprises with short, efficient and low-cost development cycles。
The project built a small automated testing platform to enable data acquisition and also studied the libview-based file generation and data storage techniques, eventually combining the software's data-processing advantages with the design of a data query and reporting generation system to facilitate future data search and analysis。
2. 4 software development technology critical
2. 4. 1 labview design mode
In the labview program design, a flexible configuration, widely used program modules and architecture are referred to as labview design models. Labview design uses the following three modes: queue message processor mode, simple status machine mode, operator frame mode
Queue message processor mode, as graph 2-1 icon
Figure 2:1 queue message processor mode
This is the queue message processor design mode. The event processing cycle generates messages by operation of the user interface. The “message processing cycle” handles information generated by the “incident handling cycle” or other messages. Message content is a string value, so it is easy to add new messages to the " message branch " condition structure of the " message processing " cycle. Each message stream can also selectively provide a variant of the message data, which can be converted to any type of message data required。
Simple status machine mode, as shown in figure 2-2 icon
Figure 2 - 2 simple state mode
Each branch of the condition implements its corresponding state code and calculates the next state to be transferred. Status is expressed as an itemized value. These count values are examples of a custom type that allows rapid addition. If you want to change the custom type, you can click the right click on an item and choose to open the custom type. If an error occurs, the status machine will stop. If an error is to be handled in a more advanced manner, a "error" state can be added to handle errors occurring in other states。
Operator framework model, as shown in figure 2-3 icon
Figure 2 - 3 operator framework mode
The labview application created by the operator framework template can contain several independent tasks that require communication with each other. The framework is specifically designed to address problems encountered in common development situations: the extension of functionality or the addition of other processes requires a large number of duplicate codes。
Each operator is defined as a labview class, and one example of a starter operator can exemplify labview class, where the operator is represented by labview objects. All offspring of the basic operator category (“operator”) contain the “operator core” method. The earliest achievement of actor. Lvclass: actor core. Vi is equivalent to a queue message processor. The vi receives and responds to messages and data sent to it by other operators in the system. However, because the operator is labview, it is easier to reuse and expand than the traditional queue message processor。
Communication lines between operators always form a hierarchical tree. Usually in the operator framework application, a small stub vi starts a root operator. The operator becomes the caller operator for one or more embedded operators. Each embedded operator may activate its own embedded operator, by analogy. The " caller to operator " relationship and the operator hierarchy tree are the basis of the operator framework application. Normally, an operator can only communicate with its caller or its own embedded operator. NatioNal industries recommends avoiding any direct communication in the operator-level tree. In some cases, however, the establishment of direct communications across nodes in hierarchical trees enhances performance。
2. 4. 2 labview interface design
The aesthetic and practicality of the interface depends on how the developer works in the design and layout of the interface, including such factors as the design of the control, the placement of the location and simplicity. The developed interface is ultimately the front board of the software and the design profile is based on the following principles:
Direct operating principles: a visualized human interface is provided in the labview program, which essentially “is what you see” is used to design the instrument panels. In the development of automated testing software, input and output units for the testing, measurement and manipulation of light controllers need to be distributed on the front boards of the software, including tables, keys, indicators, etc. These controls can be operated directly by mouse during validation。
2. The principle of simplicity in the front panel: the software panel should be designed and configured in a concise and understandable manner. Because of the complexity of virtual instruments, associated controls can be spread to different panels in the form of split panels。
3. Principle of importance: control and display of the layout of the units by frequency and importance of access, and placement of the most important and frequently visited units in the most visible position, and so on。
4. Control image selection and annotated principles: this controller's functional automated testing software labels easily misleading controls. In the context of designing controls, the partial controls are identified as text alerts to prevent error。
The design of the front board of the software needs to be functionally efficient and practical; easy to remember for use; and desirable for effect. In order to achieve the above objectives, the software development process created a beautiful labview interface in five ways:。
1) colour
The colour mix is dominated by a light tone, with the use of colours that are obvious to the attention of users for the parts that need to be highlighted, and the clever use of colours to group desktop controls can increase the readability of the entire interface, as shown in figure 2-4。
Figure 2 - 4 classification of desktop space using colour
2) controls
Labview provides a wide range of control layouts, which can be modified on the basis of its controls if you want to further beautify them, or create custom controls using stickers and control templates. You can also use the activex control to expand the display and effects of lab view, as shown in figure 2-5。
Figure 2:5 custom controls
3) layout
The most important is in the most visible places, where most people read (left - > right, top - bottom), so the most specific part is in the top left corner. Proficiency in layout tools to align controls, inter alia. Categorize controls using decorations and tabs and subvi, as shown in figure 2-6。
Figure 2 - 6
4) experiential
Perfect experientiality can be found in “user-to-user direct access”. The description of the additional controls sometimes helps users to use the program better. Sets the state of the mouse to be busy in some cases to prevent error by the user。
5) interface mode
The interface can be divided into instrument interfaces, testing platform interfaces and windows platform interfaces. Interface design can be guided by the following principles: rational functional design, emphasis on availability and, to the extent possible, pleasure for users. For the testing platform interface that we often use, more use should be made of custom controls and sub panels。
2. 5 summary of this chapter
The chapter provides a systematic description and analysis of the subjects tested in this automated testing system software, an inventory of software development software and hardware technology and a presentation of key aspects. The following is an introduction to the subject matter of this paper, which describes and describes the specific design and development process of the software:
Functional test system needs analysis
3. 1 main testing project for light controllers
This functional test system is designed for room controllers in the lmcc-110 series and is presented below as an example of a controlr with the lmcc-112 model, similar to the normal power module test method, and briefly describes some of the main test items below。
Electro-testing
When electrically controlled by relay to the controller, a data set is launched externally via the data line, while red leds are flashing on the product. The frequency and colour of led light needs to be judged。
2. Key test
The controller has three keys, each of which has a separate function and each of which needs to be pressed separately to determine whether the function is present. For example, when the key is pressed, the status of the corresponding load light will change and the corresponding blue light will light up or go out with the load light。
3. Electricity test
The controller has six sets of voltage output, with a maximum voltage of about 25 v. The voltage values vary in different states. Communications wire voltage range 14. 5-15. 5 v; product output voltage range 23. 5-24. 5 v; 4 group pv range 0-10. 5 v。
4. Calibration of circuits
The product is connected to the zero calibration function to obtain the required feedback circuits during the zero calibration。
5. Zero detection
A waver collection module is used to obtain the wave shape of the load light in a flash, and the required test values are obtained through software algorithms。
6. Communications testing
The exchange of data is carried out by communicating with computers through data lines and data conversion modules. Store relevant information such as the serial number and date code of the product into the product's chip。
3. 2 light controller test software needs analysis
The test signals required for the functional test system include 16 digital output signals, 8 digital input signals and 6 analogue input signals. In order to be flexible and to facilitate expansion, this functional test system requires the use of a uniform test structure. In order to accommodate an increase or decrease in the number of test items, a uniform test item number is required. In order to facilitate the tracking of test information on the subject, the test data need to be fully maintained. In addition to the above, the entire test system needs to be equipped with manual testing, tricolour marking, printing, etc. The procedural frameworks are shown in figure 3-1
Figure 3-1 main program box for the light controller function test system
The test software for the controller functionality test system is at the core of the entire test system. For automated testing software, which requires high performance, flexibility and functionality, the overall performance indicators of the controller are highly covered and the testing is complete. Its main test tasks include the following:
Automatic testing: automatic testing of technical indicators based on a pre-set test process, completion of the analytical determination of test data, resulting in test results, and results of the tests for output and storage。
Manual testing: manual testing is used in the debugging and troubleshooting of controllers, with selective independent testing of various technical indicators and parameters to achieve trouble location. This function can only be operated by field test engineers or technicians。
Based on the above requirements, the results of the analysis of the software needs for this automated test are as follows:
1. Communication function: a modbus bus communication function to control and monitor data acquisition card data; a rs232 bus communication function to control oscilloscope settings or read data。
2. Data collection function: 16 digital export and 8 digital entry points for collection, corresponding to non-used control agencies。
Simulation measurement function: simulation tests with a maximum measurement range greater than 25 v and a resolution less than 0. 01 v。
Data-processing function: disaggregates data analysis, processing and test results from each test project in the course of the test, and processes them in various waveforms to enable the operator to judge the lead function。
3. 3 summary of this chapter
This chapter provides a detailed analysis of the testing needs of this automated test software, as required by the software development mission, and a detailed description of the different test projects and test functions, which form the initial thinking for software design and development. The next chapter will describe the specific design process of the software
