[joshR515]

we made our own custom Gyro and Accelerometerand we had to use National Intsterments LabView to help understand how it was working, and this is how it worked.
We were using the Nation Insterments to further debug our gyro. We created our own dashboard that read out our voltage output (0-5 volts) on a graph. We then displayed the averages and we also had the average minimum voltage and max voltage for every line on our graph. Then used that information to further calibrate our gyro and make it more accurate when turning. We use the analog inputs (0-4 IO inputs) to gather information from our 5 volt input, our gyro output, the fine and coarse controls; also we used our
Clear High and NClear Low readings from the gyro; also we has a reference point that would stay at half of the voltage reading (which was 2.5 volts). Soon after that, our gyro was getting to be more accurate and made it easier to make adjustments to it. We didn’t find it necessary to use it on the accelerometer, mainly because we didn’t find a good reason to and it seemed to work fine as it was.
The dashboard we made consisted on DAQ assistance in a while loop, and a wave form graph. The averages of the voltage were measured with an Amplitude and Level Measurements. On our graph we made had a line for the flowing, reference, 5volt input, gyro output, fine output, coarse output, clear high, and NClear low.
We then ran it so it didn’t stop every second by clicking on the loop button in the bottom right corner of the while loop square. We would then run it and then turn the robot with the gyro on it to about 90 degrees and read out the output to further know what was going on with it and why it wasn’t accurate the second time turning it. This process helped us understand what was being put out by our gyro. We then used this information to help us learn about the nonlinear system the gyro was.