Alex Eberle
New Member
Posts: 4
Univerisity/Program: Bluegrass Community & Technical College
|
Post by Alex Eberle on May 3, 2017 16:03:45 GMT -7
I still have not been able to confirm which version of the code was installed on the laptops provided at the workshop or if they are set up to follow the github repo. Our laptops from the workshop don't even have a local repo for the antenna tracker. You should be using version 6 and the IP address should end in .51 (I don't want to post the whole IP here since web scrapers can get it and we should not even have it in a public repo on github. All the rest of the code should be the same so you should be able to change just that one line of code.(change xxx.xx.xxx.22 to xxx.xx.xxx.51) I would like another team, besides Montana, to try and change the IP address and see if it works so we can verify and let others know what to do. This code will be changing and I would like to create a whole new repo that the teams laptops will be associated with to clear this up once the new code is released. Sorry for the confusion but there have been some computers and repos that have not been consistently set up. The github has been updated with the information for the "new" server and database. You will have to enter your IMIE number in the antenna_tracker...gui...py file around lines 170. There will be instructions distributed shortly on how to make the update if needed. The "old" database .51 will still be operational for a couple weeks before we pull the plug. If you have the correct IP and everything else is setup properly the only thing really left is your internet connection. Make sure your ground station laptop is connected to the internet. You can even try to ping the database by typing "ping 153.90.202.51" at the command prompt, if you get no response there is a good chance you are not connected to the internet. FYI: you can drag and drop images into your post and they can be viewed from within the thread. 1. S000... When I ping that address I am met with the following: Notice how I am able to connect to google, however, not the IP you provided. 2. Before I go any further, I need to clarify something: Does iridium need to be on to run GS Calibration?
|
|
|
Post by David MSGC on May 3, 2017 17:40:41 GMT -7
If you are talking about the IMU callibration it does not need Iridium to keep the program from crashing if you don't care where the dish points, ie testing indoors etc. But you do need Iridium to callibrate when you care about where the dish points. It grabs the antenna location and balloon location at the very beigning of the program, it does not recalibrate after this point so if it does not have Iridium it will not calibrate correctly, note: the IMU recalibrates all the time but is only read from once during calibration. In other words if you don't care where the antenna points you can run the program, but if you care where the antenna points you need iridium for the initial calibration to work.
I appreciate the screenshot it help tell what is going on but in this case I think it strange you can not ping the .51. There are several other people using it. The only thing I can think of is if your IP address is getting blocked by our firewall or other security.
I would like to figure this out but the .51 database will be unplugged soon and we will not be using it. ********** UPDATE/EDIT: The only port open is for SQL, so pings will not work(this is resent change due to port scanners on our machines) and some IPs have been flagged in the last couple weeks but are not from your area ******* but your antenna tracker should still connect until we unplug the old server around May 14th
Shane should have distributed info and a link for a video I made to show everyone how to do a git pull to update their code. We will be changing the antenna tracker code a couple times and right now is a good time to do an update with git pull. The last change was directing the antenna tracker to using the new database. If you are not familiar with git or what I am talking about PM me and I can get you to the video or help via some other means like teamviewer or something.
The antenna tracker will not be using sql much longer and that is the next change to the antenna tracker code, so make sure to do a git pull once and awhile to make sure you have the newest code and we will be making announcements elsewhere to notify everyone of updates.
|
|
|
Post by David MSGC on May 4, 2017 10:10:54 GMT -7
You can still connect to the old server until it is unplugged May 14th, 2017 but I suggest updating to the new server
|
|
Alex Eberle
New Member
Posts: 4
Univerisity/Program: Bluegrass Community & Technical College
|
Post by Alex Eberle on May 16, 2017 13:53:33 GMT -7
You can still connect to the old server until it is unplugged May 14th, 2017 but I suggest updating to the new server Thanks so much David! After we updated our V6 code we were able to run the calibration connected to the new server without too many issues. I just have a few suggestions that would've saved us some time. - If I could just suggest that you add a note in the video on where to find that "git bash" software from github. It took us some time to figure out how to access that cmd portal you mentioned. Since we don't have any full-time computer science people on our team this is a challenging task for us.
- Besides that, the GS will regularly get an error halfway through the calibration when we run it by "updating settings" in the GUI. We generally have to run this a handful of times before we get the GS fully calibrated to track Iridium.
Lastly, I do have two questions. - Is there a logging protocol for when we use iridium?
- Is there a way to shut off iridium from the GS?
Thanks again David, you've been a huge help.
|
|
|
Post by Skylar MSGC on May 16, 2017 14:50:28 GMT -7
Hey Alex, if you were using one of the laptops from the workshop they should have all had git bash already installed on the computer.
When you have an error that you want to bring up with us please post what that error is/the error code. This helps us replicate and solve the error that you are recieving.
I'm not sure what you mean by logging protocol for the iridium.
You could send an email to the iridium modem to shut it off, but I would not recommend this since iridium is your primary GPS tracking system on the payloads. If you are 110% confident that your other systems can track your payload without using iridium then you could just disable during the flight if you want.
|
|