|
|
Post by Alex Eberle on Apr 3, 2017 6:38:39 GMT -7
Every time our team tries to calibrate the ground station by following the user manual, we are met with the attached error message in Spyder. We are currently using Ver. 6 of the calibration script. Any advice on how to resolve this issue would be greatly appreciated. Bluegrass Community & Technical College Balloon Sat. Team  |
|
|
|
Post by Alex Eberle on Apr 3, 2017 6:40:48 GMT -7
|
|
|
|
Post by leviw on Apr 3, 2017 8:12:20 GMT -7
Just checking, are you connected to the internet when you run the program?
|
|
|
|
Post by nachie on Apr 5, 2017 12:54:00 GMT -7
Yes, we've checked the connectivity on everything and have tried to get it to work at two campuses.
|
|
|
|
Post by David MSGC on Apr 5, 2017 17:05:59 GMT -7
I would have to confirm which version of the software you should be using,(i didn't know the ground station laptops had more than one version installed, at least they shouldn't have) it looks like you are using the wrong version since the database it is trying to connect to is wrong. The 153.90.202.22 is not correct.
|
|
|
|
Post by leviw on Apr 6, 2017 11:14:28 GMT -7
I don't have the laptop code in front of me to compare it, but it looks like that's the IP on github. If the github code is not up-to-date, it should be! |
|
|
|
Post by Alex Eberle on Apr 10, 2017 7:29:41 GMT -7
I would have to confirm which version of the software you should be using,(i didn't know the ground station laptops had more than one version installed, at least they shouldn't have) it looks like you are using the wrong version since the database it is trying to connect to is wrong. The 153.90.202.22 is not correct.
Just to clarify, which version should we be using for the calibration? It is our impression that we should be running the latest V6 found on GitHub found here. We double checked the code to make sure we had the right IMEI number for our payload and it still didn't work. If it's the case that we just need to change the IP of the mysql server, then can we just change that line in the code to the correct IP? Thanks |
|
|
|
Post by David MSGC on Apr 10, 2017 16:30:39 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.
|
|
|
|
Post by Alex Eberle on Apr 18, 2017 11:27:22 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. |
|
|
|
Post by Alex Eberle on Apr 18, 2017 11:42:35 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.
Not sure why it removed my text but basically I was just saying that we ran the calibration with the correct IP and double checked our set up and we are still getting the same error. Not sure what's wrong. I think we are going to arrange a tech call through shane (possibly over skype) with you to go through everything. We are going to also double check everything with another team nearby beforehand to make sure. Pic of new error: imgur.com/a/8n7hx |
|
|
|
Post by David MSGC on Apr 18, 2017 16:56:33 GMT -7
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.
|
|
|
|
Post by David MSGC on Apr 19, 2017 14:04:50 GMT -7
Also make sure you are setting the static IP on ethernet adapter and not the wifi adapter. Ethernet will be static for ubiquity and the wifi will have to be set to what your wifi network is expecting. Ethernet for ubiquity and wifi for internet. Some cases teams were setting the static IP for wifi and not ethernet. If you try to ping the database it will time out if you have the adapter settings mixed up, if get a response from the ping and still cannot connect make sure you have the right IP, username, and password.
|
|
|
|
Post by Alex Eberle on Apr 26, 2017 6:57:51 GMT -7
When I try and ping 153.90.202.51 as of today, I am getting 100% packet loss. I am connected to the internet. When I perform a network test I have an download of 8+mbps and an upload of 4+mbps. I do not believe the internet connectivity is a problem. From our point of view we are just seeing that the server is simply unresponsive.
|
|
|
|
Post by David MSGC on Apr 27, 2017 21:12:18 GMT -7
The .51 machine is still active and being used daily. Can you ping google or other addresses outside your local network?
|
|
Alex Eberle
New Member
Posts: 4 
Univerisity/Program: Bluegrass Community & Technical College
|
Post by Alex Eberle on May 3, 2017 15:56:49 GMT -7
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. |
|
