Thread: [Gpredict-discussion] Tracking Issues
Real time satellite tracking and orbit prediction
Status: Beta
Brought to you by:
csete
Menu
▾
▴
gpredict-discussion
|
From: Luca B. <luc...@st...> - 2016-05-05 09:06:16
|
Hello, I'm using Hamlib 3.0 with Gpredict in order to control a Alfaspid Rotator with a Rot2Prog controller and I'm experiencing some problems. I can give orders via the controller (using its buttons), via cmd with rotctl and within the Rotator Control of Gpredict (calling rotctld in cmd) and as long as these commands are given manually there are no issues. However when I track a satellite something strange happens. The rotator will be out of position while the controller indicator give a wrong reading. For example let's suppose that a tracking should finish in 0° Azimuth and 0° Elevation: the controller and all the readings give (0,0) while the antenna is still pointing up and not at North. Every time I have to recalibrate the direction, and I can't say with accuracy when it sart to lose it. I am assuming that is a software error since, as i said before, the other methods do not give errors. I am using Gpredict V 1.3-3, with the Hamlib 3.0 in Windows 8.1 (I know, but the laptop is not mine). To activate the Hamlib driver I use: rotctld -m 901 -r COM7 -T 127.0.0.1 -t 4533 -vvvvv For the tracking: 3000 ms cycle and 1° Tolerance >From the verbose in the cmd all seems fine, but I'm no expert. Thanks in advance for any help. Luca |
|
From: Eric S. <wb...@sb...> - 2016-05-05 19:42:22
|
Hello Luca You don't say whether or not your system has ever worked correctly so its hard to give appropriate guidance. Having had similar problems with Gpredict but using other rotor controllers I can only guess about your situation. When tracking GP spits out additional data than AZ/EL coordinates and at a rate that may be faster than your controller can digest. Put a port sniffer on your PC/GP link and see what is passing thru. You may be surprised. Best of Luck Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Thursday, May 05, 2016 1:50 AM To: gpr...@li... Subject: [Gpredict-discussion] Tracking Issues Hello, I'm using Hamlib 3.0 with Gpredict in order to control a Alfaspid Rotator with a Rot2Prog controller and I'm experiencing some problems. I can give orders via the controller (using its buttons), via cmd with rotctl and within the Rotator Control of Gpredict (calling rotctld in cmd) and as long as these commands are given manually there are no issues. However when I track a satellite something strange happens. The rotator will be out of position while the controller indicator give a wrong reading. For example let's suppose that a tracking should finish in 0° Azimuth and 0° Elevation: the controller and all the readings give (0,0) while the antenna is still pointing up and not at North. Every time I have to recalibrate the direction, and I can't say with accuracy when it sart to lose it. I am assuming that is a software error since, as i said before, the other methods do not give errors. I am using Gpredict V 1.3-3, with the Hamlib 3.0 in Windows 8.1 (I know, but the laptop is not mine). To activate the Hamlib driver I use: rotctld -m 901 -r COM7 -T 127.0.0.1 -t 4533 -vvvvv For the tracking: 3000 ms cycle and 1° Tolerance >From the verbose in the cmd all seems fine, but I'm no expert. Thanks in advance for any help. Luca ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion |
|
From: Luca B. <luc...@st...> - 2016-05-10 14:56:22
|
Hi Eric, sorry for the delayed answer. No accurate testing was ever done on the rotor (an Alfaspid Ras Az/El), just checked if the motors were operative. as far as I've been told so possibly this problem was already present (this is an univeristy project). I used a port sniffer to check the packets sent and received from the Rot2Prog controller, and no particuarly strange orders were presents, or at least I could not identify any. I don't think that the problem is the speed, since i set the port at 600 bps (as the protocol requires) and use a ~3000 ms refresh rate. If you know how to further limit the speed please let me know. I also tested the rotor tracking with Orbitron and its driver, and I noticed that the problem is also present with it, even if with lower severity. This may confirm that there is an hardware problem with the rotor or the controller, but that would not explain why when issuing manual commands it behaves like it should. Tomorrow I will run more tests to confirm this, but honestly I'm at a loss here. Thank you again for your time. Luca ________________________________________ Da: Eric Schumacher <wb...@sb...> Inviato: giovedì 5 maggio 2016 21.42.13 A: 'Gpredict discussion' Oggetto: Re: [Gpredict-discussion] Tracking Issues Hello Luca You don't say whether or not your system has ever worked correctly so its hard to give appropriate guidance. Having had similar problems with Gpredict but using other rotor controllers I can only guess about your situation. When tracking GP spits out additional data than AZ/EL coordinates and at a rate that may be faster than your controller can digest. Put a port sniffer on your PC/GP link and see what is passing thru. You may be surprised. Best of Luck Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Thursday, May 05, 2016 1:50 AM To: gpr...@li... Subject: [Gpredict-discussion] Tracking Issues Hello, I'm using Hamlib 3.0 with Gpredict in order to control a Alfaspid Rotator with a Rot2Prog controller and I'm experiencing some problems. I can give orders via the controller (using its buttons), via cmd with rotctl and within the Rotator Control of Gpredict (calling rotctld in cmd) and as long as these commands are given manually there are no issues. However when I track a satellite something strange happens. The rotator will be out of position while the controller indicator give a wrong reading. For example let's suppose that a tracking should finish in 0° Azimuth and 0° Elevation: the controller and all the readings give (0,0) while the antenna is still pointing up and not at North. Every time I have to recalibrate the direction, and I can't say with accuracy when it sart to lose it. I am assuming that is a software error since, as i said before, the other methods do not give errors. I am using Gpredict V 1.3-3, with the Hamlib 3.0 in Windows 8.1 (I know, but the laptop is not mine). To activate the Hamlib driver I use: rotctld -m 901 -r COM7 -T 127.0.0.1 -t 4533 -vvvvv For the tracking: 3000 ms cycle and 1° Tolerance >From the verbose in the cmd all seems fine, but I'm no expert. Thanks in advance for any help. Luca ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion |
|
From: Eric S. <wb...@sb...> - 2016-05-10 16:33:39
|
Hello Luca The rotor controller in use here is Arduino based using K3NG software (https://github.com/k3ng/k3ng_rotator_controller) using step motors. This puts everything about the controller operation under my control. I have LEDs on each axis and direction. These are very useful in determining tracking behavior. Sometimes I hook a scope across an LED for precise measurement of timing. When tracking correctly all LED ON periods should be the same since satellite speed is relatively constant update to update. And all updates should be in the same direction (indicating no overshoot) The simple minded LED strategy has proved very useful. So far I have had no issues with Gpredict only with the rotor software. Don't forget to analyze Hamlib, rotctl gets in there and does stuff. Something else to check into is the Alfaspid controller. It is quite unusual in that the position sensor is on the motor shaft rather than the antenna with no provision to automatically correct position calibration. There is lots of room for mischief in that system. Good Luck, unfortunately you have about maxed me out as a help resource. Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Tuesday, May 10, 2016 7:40 AM To: 'Gpredict discussion'; wb...@sb... Subject: Re: [Gpredict-discussion] Tracking Issues Hi Eric, sorry for the delayed answer. No accurate testing was ever done on the rotor (an Alfaspid Ras Az/El), just checked if the motors were operative. as far as I've been told so possibly this problem was already present (this is an univeristy project). I used a port sniffer to check the packets sent and received from the Rot2Prog controller, and no particuarly strange orders were presents, or at least I could not identify any. I don't think that the problem is the speed, since i set the port at 600 bps (as the protocol requires) and use a ~3000 ms refresh rate. If you know how to further limit the speed please let me know. I also tested the rotor tracking with Orbitron and its driver, and I noticed that the problem is also present with it, even if with lower severity. This may confirm that there is an hardware problem with the rotor or the controller, but that would not explain why when issuing manual commands it behaves like it should. Tomorrow I will run more tests to confirm this, but honestly I'm at a loss here. Thank you again for your time. Luca ________________________________________ Da: Eric Schumacher <wb...@sb...> Inviato: giovedì 5 maggio 2016 21.42.13 A: 'Gpredict discussion' Oggetto: Re: [Gpredict-discussion] Tracking Issues Hello Luca You don't say whether or not your system has ever worked correctly so its hard to give appropriate guidance. Having had similar problems with Gpredict but using other rotor controllers I can only guess about your situation. When tracking GP spits out additional data than AZ/EL coordinates and at a rate that may be faster than your controller can digest. Put a port sniffer on your PC/GP link and see what is passing thru. You may be surprised. Best of Luck Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Thursday, May 05, 2016 1:50 AM To: gpr...@li... Subject: [Gpredict-discussion] Tracking Issues Hello, I'm using Hamlib 3.0 with Gpredict in order to control a Alfaspid Rotator with a Rot2Prog controller and I'm experiencing some problems. I can give orders via the controller (using its buttons), via cmd with rotctl and within the Rotator Control of Gpredict (calling rotctld in cmd) and as long as these commands are given manually there are no issues. However when I track a satellite something strange happens. The rotator will be out of position while the controller indicator give a wrong reading. For example let's suppose that a tracking should finish in 0° Azimuth and 0° Elevation: the controller and all the readings give (0,0) while the antenna is still pointing up and not at North. Every time I have to recalibrate the direction, and I can't say with accuracy when it sart to lose it. I am assuming that is a software error since, as i said before, the other methods do not give errors. I am using Gpredict V 1.3-3, with the Hamlib 3.0 in Windows 8.1 (I know, but the laptop is not mine). To activate the Hamlib driver I use: rotctld -m 901 -r COM7 -T 127.0.0.1 -t 4533 -vvvvv For the tracking: 3000 ms cycle and 1° Tolerance >From the verbose in the cmd all seems fine, but I'm no expert. Thanks in advance for any help. Luca ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion |
|
From: Luca B. <luc...@st...> - 2016-05-12 07:42:08
|
Hello Eric, Seems like that I resolved the problem. I took your suggestion about the communication speed, and further decreased the cycle time to 4000 ms. Now it appears to work properly, but I'm still on the look out for eventual issues, since this whole situation was strange. Thank you for your help. Luca ________________________________________ Da: Eric Schumacher <wb...@sb...> Inviato: martedì 10 maggio 2016 18.20.34 A: Luca Bellavista; 'Gpredict discussion' Oggetto: RE: [Gpredict-discussion] Tracking Issues Hello Luca The rotor controller in use here is Arduino based using K3NG software (https://github.com/k3ng/k3ng_rotator_controller) using step motors. This puts everything about the controller operation under my control. I have LEDs on each axis and direction. These are very useful in determining tracking behavior. Sometimes I hook a scope across an LED for precise measurement of timing. When tracking correctly all LED ON periods should be the same since satellite speed is relatively constant update to update. And all updates should be in the same direction (indicating no overshoot) The simple minded LED strategy has proved very useful. So far I have had no issues with Gpredict only with the rotor software. Don't forget to analyze Hamlib, rotctl gets in there and does stuff. Something else to check into is the Alfaspid controller. It is quite unusual in that the position sensor is on the motor shaft rather than the antenna with no provision to automatically correct position calibration. There is lots of room for mischief in that system. Good Luck, unfortunately you have about maxed me out as a help resource. Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Tuesday, May 10, 2016 7:40 AM To: 'Gpredict discussion'; wb...@sb... Subject: Re: [Gpredict-discussion] Tracking Issues Hi Eric, sorry for the delayed answer. No accurate testing was ever done on the rotor (an Alfaspid Ras Az/El), just checked if the motors were operative. as far as I've been told so possibly this problem was already present (this is an univeristy project). I used a port sniffer to check the packets sent and received from the Rot2Prog controller, and no particuarly strange orders were presents, or at least I could not identify any. I don't think that the problem is the speed, since i set the port at 600 bps (as the protocol requires) and use a ~3000 ms refresh rate. If you know how to further limit the speed please let me know. I also tested the rotor tracking with Orbitron and its driver, and I noticed that the problem is also present with it, even if with lower severity. This may confirm that there is an hardware problem with the rotor or the controller, but that would not explain why when issuing manual commands it behaves like it should. Tomorrow I will run more tests to confirm this, but honestly I'm at a loss here. Thank you again for your time. Luca ________________________________________ Da: Eric Schumacher <wb...@sb...> Inviato: giovedì 5 maggio 2016 21.42.13 A: 'Gpredict discussion' Oggetto: Re: [Gpredict-discussion] Tracking Issues Hello Luca You don't say whether or not your system has ever worked correctly so its hard to give appropriate guidance. Having had similar problems with Gpredict but using other rotor controllers I can only guess about your situation. When tracking GP spits out additional data than AZ/EL coordinates and at a rate that may be faster than your controller can digest. Put a port sniffer on your PC/GP link and see what is passing thru. You may be surprised. Best of Luck Eric WB6KCN -----Original Message----- From: Luca Bellavista [mailto:luc...@st...] Sent: Thursday, May 05, 2016 1:50 AM To: gpr...@li... Subject: [Gpredict-discussion] Tracking Issues Hello, I'm using Hamlib 3.0 with Gpredict in order to control a Alfaspid Rotator with a Rot2Prog controller and I'm experiencing some problems. I can give orders via the controller (using its buttons), via cmd with rotctl and within the Rotator Control of Gpredict (calling rotctld in cmd) and as long as these commands are given manually there are no issues. However when I track a satellite something strange happens. The rotator will be out of position while the controller indicator give a wrong reading. For example let's suppose that a tracking should finish in 0° Azimuth and 0° Elevation: the controller and all the readings give (0,0) while the antenna is still pointing up and not at North. Every time I have to recalibrate the direction, and I can't say with accuracy when it sart to lose it. I am assuming that is a software error since, as i said before, the other methods do not give errors. I am using Gpredict V 1.3-3, with the Hamlib 3.0 in Windows 8.1 (I know, but the laptop is not mine). To activate the Hamlib driver I use: rotctld -m 901 -r COM7 -T 127.0.0.1 -t 4533 -vvvvv For the tracking: 3000 ms cycle and 1° Tolerance >From the verbose in the cmd all seems fine, but I'm no expert. Thanks in advance for any help. Luca ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Gpredict-discussion mailing list Gpr...@li... https://lists.sourceforge.net/lists/listinfo/gpredict-discussion |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X