|
Post by kendra on Jun 18, 2017 14:26:39 GMT -7
It is trying to point straight up, but the azimuth seems to be tracking. We didn't have this problem when we calibrated in the back yard before, even though we are maybe about 20 feet away from the iridium.
Kendra
|
|
|
Post by kendra on Jun 18, 2017 14:31:35 GMT -7
I moved it about 50 feet away and it is still pointed up. The altitude on the ground station is reading 0. What's up with that?
Kendra
|
|
|
Post by kendra on Jun 18, 2017 14:37:14 GMT -7
I tried restarting the tracker and it is pointing exactly opposite the payloads. We had this happen before occasionally. I have no idea why.
Kendra
|
|
|
Post by kendra on Jun 18, 2017 14:44:10 GMT -7
I restarted it again and it pointed to where the payloads were 15 minutes ago.
It looks like it locked up because I'm not getting any tracking data.
Kendra
|
|
|
Post by kendra on Jun 18, 2017 14:47:12 GMT -7
Restarted again. Exactly opposite again.
The calibration were all at 0s and then they were all at 3s. This makes me think that there was some residual calibration left from last time?
|
|
|
Post by kendra on Jun 18, 2017 14:54:22 GMT -7
I restarted the computer and did the calibration again. It is pointed in the right general direction this time.
Kendra
|
|
|
Post by David MSGC on Jun 18, 2017 15:03:35 GMT -7
I restarted it again and it pointed to where the payloads were 15 minutes ago. It looks like it locked up because I'm not getting any tracking data. Kendra To help understand what the Iridium is reporting have the tracking website open on your balloons data so you can see the Iridium reports as they come in, then you can see when the antenna should be getting updates.
|
|
|
Post by David MSGC on Jun 18, 2017 15:04:40 GMT -7
I restarted the computer and did the calibration again. It is pointed in the right general direction this time. Kendra You can also hit "update settings" or push reset on Arduino and then hit "update settings" again instead of restarting the computer.
|
|
|
Post by David MSGC on Jun 18, 2017 15:05:37 GMT -7
Restarted again. Exactly opposite again. The calibration were all at 0s and then they were all at 3s. This makes me think that there was some residual calibration left from last time? Going from 0's to 3's is not uncommon it just depends on how fast each sensor calibrates and it does store calibration data to help calibrate faster.
|
|
|
Post by David MSGC on Jun 18, 2017 15:10:59 GMT -7
It is trying to point straight up, but the azimuth seems to be tracking. We didn't have this problem when we calibrated in the back yard before, even though we are maybe about 20 feet away from the iridium. Kendra Look at the website to see that the Iridium data coming in, compare this to the value given in the GUI, also look at the bearing and elevation it shows it should be pointing in GUI then see if it is trying to point somewhere wonky, if it is wrong bearing than the Iridium payload could be too close to the antenna. It is also a good idea to make this check before turning on auto track to make sure the antenna won't spin around more than 180 degrees trying to point backwards. This could also indicate if you have the IMU mounted backwards.
|
|
|
Post by kendra on Jun 18, 2017 15:11:00 GMT -7
5/7 times when I start the program, it points the exact wrong way. I can't figure out the rhyme or reason.
Kendra
|
|
|
Post by kendra on Jun 18, 2017 15:11:48 GMT -7
I'm pretty sure the IMU is mounted correctly.
|
|
|
Post by kendra on Jun 18, 2017 15:12:23 GMT -7
The Yagi antenna is pointed forward and the IMU is pointed backward, correct?
|
|
|
Post by David MSGC on Jun 18, 2017 15:12:45 GMT -7
I tried restarting the tracker and it is pointing exactly opposite the payloads. We had this happen before occasionally. I have no idea why. Kendra Payload too close to antenna or IMU mounted backwards. The side of the IMU where the cable attache should be pointing the same direction as the antenna.
|
|
|
Post by kendra on Jun 18, 2017 15:27:37 GMT -7
I moved it well over 100 feet away and it is doing the same thing. I don't think that is the problem.
I am still not getting any data from the tracker to plot on the graphs.
|
|