Wednesday, 25 June 2014

Week 9 : Export data to Excel file

            














We use the New Report.Vi in the diagram (on the left ) to specify the template given by the operator to save the data exported inside the template. 













                                                  This is how we connect the New Report .Vi .














The VIs in the both diagrams above are Excel Easy Table.Vi and Excel Bring to Front.Vi.



 
This diagram shows how we connect the Excel Easy Table.Vi in the program.It use to store the data exported to specified rows and columns.






 
We export the data to the excel template given by operator accordingly. 




 
We have modified the original template given and add in more measurements ( e.g  frequency, RMS, etc. ). In addition,we also generate some formulas to calculate the total input power for both open circuit test and short circuit test. As we all can see from the above diagram, the results for section 3.4.1 ,3.4.2, 3.6 and 3.7 are successfully filled in.




   


 


Our next job is to improve our program by creating a diagnostic program to check the communication,errors and instruments every time before the operators run the real test. With this program, we are able to save lots of time in troubleshooting.







Tuesday, 17 June 2014

Week 8 : Testing of Automation Software on ATU/GATU Test Bench

 

We set up the connection for ATU by following the procedure in the ELS desktop. This is a no load, open circuit test.



After that we connect the power meter and measure unit with this GPIB - GPIB cable then the output is connected to desktop using GPIB - USB cable.


 We activate the test bench to test ATU unit after finish setting up all the connection.



Our software is a success as it can show all the readings on the screen accurately. However we experience some delay with the export button. Our next task is to improve the speed and export the data to excel format with specified row and column.







Tuesday, 10 June 2014

Week 7 : User Manual and Software Overview

 We decided to use case structure which acts like a if-else statement in C++ programming for our export button.



 When the users didn't press the ACQUIRE(OSCI) button, the output is FALSE and hence false statement, which is blank, will be executed.



 When the users  press the ACQUIRE(OSCI) button, the output is TRUE  and hence the true statement, will be executed. After it executes all the 4 block diagrams above, the output of the button will become FALSE as we have set the mechanical action fo the switch to Latch When Release. By doing this the data will be exported in set by set format.



After we have completed the programming part, we need to book a time slot on the test bench to test our program. At the same time we are required to prepare a presentation and a user manual about our program for the operators.


Sunday, 1 June 2014

Week 6 : Improvement on Front Panel & Exporting data

 
We further improve our front panel by using tab control so that the users can select the instrument data they want to see.


The light indicates the instrument is undergoing SHORT CIRCUIT TEST mode.


The light indicates the instrument is undergoing OPEN CIRCUIT TEST mode.


This is the measure unit tab.


 
We further improve the exporting data feature by using the event structure. When the users press the acquire button, only 1 set of data will be exported. However the program is no longer a real time simulation. Hence our next task is to overcome this problem.