Calvin fixed the problem with continuous data saving in python and CNC movement in g-code
The continuous saving program now collects data from the load cell and stores it in a csv file along side a time stamp (See an example excel file of acquired data on our programming page)
Supplementary python programs (pyDAQ tools, etc.) were installed on two laptops in order to run the the program along side the CNC machine (Unfortunately these are not functional yet)
The program for CNC movement was successful ( The video of the program in progress can be seen in the following video)
The home screen for this new device is now being designed to allow sample parameters to be input and to provide a user friendly screen to control the tests.
Each step was tested seperately and we plan to combine them in the near future.
Our sponsorship letter was edited by the writing center and is now in the final stages of revision.
It was discovered throughout the last two weeks that Python 3.0 and editions above do not read our data saving code properly. We are working on making a compatible one.
Python 2.6 and all extra downloads needed were put on to a laptop so that we could test position, time, and load together.
The data acquisition program was made more concise by minimizing the time lapse between collecting and dumping data.
Tests were combined for the first time.
The new signal conditioner we have has not been calibrated with the load cell yet, so our load data from these first tests are not accurate.
The plans for the final step of the project were put in place
Our final product will include a video tutorial, a list of programs needed to duplicate our mechanical test, and the written programs to run a user friendly test.
We had difficulty getting the GUI (home screen) to work.
The GUI program will now be made in Python 2.6 rather than 3.1
The calibration and testing python programs worked and will now be split so that the GUI program can call upon them seperately.
A list of programs and downloads needed to run the tests were made, and it was discussed whether to list them online or provide them as a downloadable package.
The final stages include putting together the calibration code, testing code, and g-code converter with the GUI, and creating a help menu to setup the physical connections.
The website template now has over 20 pages which are being edited. It includes tutorials, information, etc.
The plan is to have a final video of everything working together made by monday. We will follow the finished tutorial to make sure that our instructions are concise and understandable.
Roland responded to our letter saying that their engineers could not share with us the information we need for the Creep Test. A clarification letter is being formulated.
