12-11-2014 08:44 PM
So, I removed the wait time. When it runs, it seems to be running well. The issue is that it runs 1 out of every 5 or 8 times. The other times, I'm getting my original error code 1073807253.
I run it, get the error. Run it again (not changing anything) and it works. Then it won't work and again, I didn't change anything.
Thoughts?
12-12-2014 08:36 AM
And there does this Error happen? In the while loop or before?
Does it help to power recycle the GPS between runs?
12-12-2014 11:11 AM
Ok, so I ran this a bunch of times this morning.
The error happens that the first Visa Read just within the loop. Doesn't seem to matter if I cycle power. The program doesn't always run first time.
I decided last night that I would play around with this and see if we coudl record the test data. I didn't care how many times it took to work, once it worked, we would perform a brake test to see how the data looked. Glad I did, the data is horrible.
We did a brake test from 60 to 0 and the GPS recorded that our speed never changed throughout the entire braking event. In fact, we were stopped for probably 2 seconds and it was still registering that we were doing 60 (while we were stopped). I don't understand why that would be the case.
So, we performed a little bit of analysis on the file and the GPS is registering that we are covering ground while completely stopped.
We cleared everything out and performed another test. Same thing, we were completely stopped and the GPS still had our vehicle speed quite high (just about 60mph). Then after a few seconds, it stared falling down in what appears to be a linear patern.
What do you make of the poor quality of data gathered?
(Data is below. The Feet Traveled and the MPH were obtained through calculations. The rest of the data is directly recorded by the GPS program. This is just the last few seconds (where the braking event happened). I didn't worry about setting the time because this was just to test the accuracy of the measurement.)