|
|
Post by markshancock on Jun 16, 2017 20:29:11 GMT -7
Sometime when we start we do not see Incoming GPS Data I have confirmed the Iridium Payload location is active at eclipse.rci.montana.edu/ and IMEI matches between website and tracker app. Command prompt that Tracker was launched from is scrolling what looks like it might be calibration data. Accel value is still showing '0'. - Will incomplete calibration holdup Incoming GPS Data?
- How can you tell when calibration is complete (from UI)?
- What triggers the GPS Database Query?
- How can you tell why there is no GPS Data? (Ex: Could we be failing to connect to DB?)
|
|
|
|
Post by markshancock on Jun 17, 2017 14:50:29 GMT -7
Looking at GetData.py, I see that the problem may be connected to an error we are getting
File GetData.py, line 63 in run
time.sleep(2)
NameError: global name 'time' is not defined
|
|
|
|
Post by markshancock on Jun 17, 2017 15:26:47 GMT -7
The problem was GetData.py was missing an "import time" statement.
|
|
|
|
Post by Austin MnSGC on Jun 17, 2017 15:31:06 GMT -7
Until you hit Update Settings for the first time after launching the tracker, nothing will happen. Once you hit update settings, the connections are set, the auto track options are loaded, and your chosen method for acquiring a center bearing and ground station location will load. Balloon location information will not be acquired from any source until a center bearing and ground station location are set (calibration is complete if you chose Get Local, otherwise the values in the boxes and the cardinal direction chosen).
If you selected Get Local as your center bearing and location option, then the program will confirm that an arduino is connected. If it is, a window will pop up and fill with information from the arduino about the calibration status of the various sensors. Once the calibration value for each sensor is a 3 (or you're done waiting and will accept an off calibration), put the IMU in place on your tracker and hit ready on the calibration window. This will load the location and center bearing of the ground station from data returned from the arduino.
After a center bearing is found, the auto track methods are assessed. If you selected Iridium as an auto track method, it will create a thread that will continuously check for new information from the database and pass it to the main thread (the GUI).
There are various outputs to the terminal window (print statements) that relay most errors that have occurred. If settings are successfully updated (the bottom left Ground Station Info table is populated), then your selected auto track methods should be trying to receive data. Check the terminal, which is Anaconda Prompt, for any statements that could offer you any help, such as "Failure to connect to the database".
|
|
|
|
Post by Trevor MSGC on Jun 19, 2017 8:18:16 GMT -7
The import time should have been fixed last week, if you see that in your code you need to do a git pull and grab the newest code. If it's still not there then you are using the wrong repository/branch
-Trevor
|
|
|
|
Post by markshancock on Jun 19, 2017 15:23:34 GMT -7
The import time should have been fixed last week, if you see that in your code you need to do a git pull and grab the newest code. If it's still not there then you are using the wrong repository/branch -Trevor Yes, I saw that is was fixed, just not on the branch we were running. The problem was that we still running AntennaTracker_withRFD to work-around the index error that hadn't been fixed in Antenna_Tracker. Also we were running the old_servo branch as directed and the import error was not fixed in that branch. Once the team returns from the Trial Run, we will shift back to the Antenna_Tracker repository. Right now they have something they feel they can work with. As you can see, having multiple repositories and branches can certainly complicate life. We use Atlassian SourceTree to help make that a bit easier to manage. Mark |
|
|
|
Post by Trevor MSGC on Jun 19, 2017 15:38:15 GMT -7
The import time should have been fixed last week, if you see that in your code you need to do a git pull and grab the newest code. If it's still not there then you are using the wrong repository/branch -Trevor Yes, I saw that is was fixed, just not on the branch we were running. The problem was that we still running AntennaTracker_withRFD to work-around the index error that hadn't been fixed in Antenna_Tracker. Also we were running the old_servo branch as directed and the import error was not fixed in that branch. Once the team returns from the Trial Run, we will shift back to the Antenna_Tracker repository. Right now they have something they feel they can work with. As you can see, having multiple repositories and branches can certainly complicate life. We use Atlassian SourceTree to help make that a bit easier to manage. Mark Thanks for the heads up about Atlassian SourceTree, I'm checking it out now and it looks pretty useful. |
|
mahe
Novice Ballooner
Posts: 7 
|
Post by mahe on Jul 14, 2017 13:50:01 GMT -7
1. what is it that populates the fields in the box marked "Incoming GPS Data" in the antenna tracker software? 2. If we are setup to use the iridium tracker will those be populated, or will they remain blank? 3. Attachments:
|
|
|
|
Post by Austin MnSGC on Jul 17, 2017 5:55:47 GMT -7
1. what is it that populates the fields in the box marked "Incoming GPS Data" in the antenna tracker software? 2. If we are setup to use the iridium tracker will those be populated, or will they remain blank? 3. The fields in the box Incoming GPS Data are populated with the most recent GPS data from one of the autotrack sources, either RFD, Iridium, or APRS. If you only have Iridium selected as an autotrack option, then that is the only data source that will fill that box. If there isn't anything in there, then either the settings were configured wrong, there was an error, or there simply wasn't any new GPS data. |
|
