|
|
Post by ShaneMG_MSGC on Jun 9, 2017 20:17:42 GMT -7
|
|
|
|
Post by Trevor MSGC on Jun 11, 2017 21:23:15 GMT -7
Please note that in the video the repository has changed. If using the AntennaTracker_withRFD repository make sure you select the oldServo branch. Otherwise you can just use the AntennaTracker repository.
|
|
|
|
Post by Manu on Jun 16, 2017 8:35:36 GMT -7
Hi,
We updated the new ground station software but were unable to calibrate it. When we open the tracker and try to calibrate it shows an error saying no arduino connected.
We had no problem streaming though. But we lost signal when we were too far from the ground station. The servos did not move at all.
How do I correct this error?
|
|
|
|
Post by Austin MnSGC on Jun 16, 2017 9:23:03 GMT -7
Hi, We updated the new ground station software but were unable to calibrate it. When we open the tracker and try to calibrate it shows an error saying no arduino connected. We had no problem streaming though. But we lost signal when we were too far from the ground station. The servos did not move at all. How do I correct this error? Does the COM port for the arduino autofill in the settings tab connections section? |
|
manoj
Novice Ballooner
Posts: 5 
|
Post by manoj on Jun 16, 2017 12:52:39 GMT -7
Yes it does autoffill.
|
|
|
|
Post by Austin MnSGC on Jun 17, 2017 15:40:31 GMT -7
Is the COM port that autofills correct? Also, is the error saying "No Arduino Connected" a pop up window? If so, make sure that the checkbox next to the arduino COM port entry is checked if you want to use an Arduino.
|
|
|
|
Post by markshancock on Jun 17, 2017 20:53:57 GMT -7
When you create the batch file, add a Pause command as the last line. That way you can examine the command window do see if there is an error. We found most of our issues through errors that were listed in the command window.
|
|
|
|
Post by markshancock on Jun 19, 2017 7:56:04 GMT -7
Warning! AntennaTracker_withRFD oldServo branch has a bug in it that prevents you from receiving GPS data from the Iridium database that was found but never fixed in this branch.
It looks like the bug was fixed in the Antenna_Tracker repository
|
|
|
|
Post by David MSGC on Jun 19, 2017 9:27:46 GMT -7
Warning! AntennaTracker_withRFD oldServo branch has a bug in it that prevents you from receiving GPS data from the Iridium database that was found but never fixed in this branch. It looks like the bug was fixed in the Antenna_Tracker repository You should not be using AntennaTracker_withRFD, that is the wrong repo and is a testing repo. You should be using Antenna_Tracker repo and master branch. |
|
manoj
Novice Ballooner
Posts: 5
|
Post by manoj on Jun 19, 2017 10:24:11 GMT -7
It is checked but it shows the same error saying no arduino connected when we try to calibrate it.  |
|
|
|
Post by David MSGC on Jun 19, 2017 10:39:25 GMT -7
You can try to unplug and replug the Arduino and also check device manager to confirm the com port number. If it does not show up in device manager you may have to reinstall Arduino to reinstall the drivers.
|
|
|
|
Post by Austin MnSGC on Jun 19, 2017 11:37:10 GMT -7
It is checked but it shows the same error saying no arduino connected when we try to calibrate it. I haven't seen this error before. That window only appears if you have Get Local selected and the Arduino checkbox is not checked, or if you try to recalibrate the center bearing and the Arduino checkbox is not checked. Is anything printed out to the prompt when you get this error? |
|
|
|
Post by markshancock on Jun 19, 2017 13:04:49 GMT -7
Warning! AntennaTracker_withRFD oldServo branch has a bug in it that prevents you from receiving GPS data from the Iridium database that was found but never fixed in this branch. It looks like the bug was fixed in the Antenna_Tracker repository You should not be using AntennaTracker_withRFD, that is the wrong repo and is a testing repo. 1) We are using it because we were told to use it. There was a bug in Antenna_Tracker that had been fixed in AntennaTracker_withRFD 2) The Release Announce directs us to use it. See the very top of this thread where it says: 3) Why are you using a separate repo for testing? You should be using a branch within the same repository (or at least a fork) and release points to manage that. If the repository is for development then maybe you should use a fork under a separate user to prevent confusion. I know all of our students are confused by this approach and the same seems to be true for the those doing (and likely reading the release announcements). 4) The last two bugs I found were pretty clear coding mistakes that would have never passed basic testing/verification. After I found and reported the bugs I was told "we already fixed that"; but, the fix was in the other repository. This back-and-forth on which repository to use and having to debug code onsite that was clearly never tested is rather frustration, especially right before and out-of-town field test. |
|
|
|
Post by Trevor MSGC on Jun 19, 2017 13:31:56 GMT -7
You should not be using AntennaTracker_withRFD, that is the wrong repo and is a testing repo. 1) We are using it because we were told to use it. There was a bug in Antenna_Tracker that had been fixed in AntennaTracker_withRFD 2) The Release Announce directs us to use it. See the very top of this thread where it says: 3) Why are you using a separate repo for testing? You should be using a branch within the same repository (or at least a fork) and release points to manage that. If the repository is for development then maybe you should use a fork under a separate user to prevent confusion. I know all of our students are confused by this approach and the same seems to be true for the those doing (and likely reading the release announcements). 4) The last two bugs I found were pretty clear coding mistakes that would have never passed basic testing/verification. After I found and reported the bugs I was told "we already fixed that"; but, the fix was in the other repository. This back-and-forth on which repository to use and having to debug code onsite that was clearly never tested is rather frustration, especially right before and out-of-town field test. The separate repository was never supposed to be sent out. I use two different repositories so that people that are less familiar with git don't need to worry about how to switch between branches and I can keep track of two different repositories without checking out branches throughout the work day. I can simply keep one open on my computer that has been pushed out to the rest of the teams while I use the other one for our system in Montana which is slightly different. Hopefully in the future both will be merged together. As far as the rest of your concerns, we would appreciate if you posted constructive feedback instead of argumentative destructive remarks. You're more than welcome to open pull requests on our github repositories, this is why we have them public instead of private. |
|
