¿ªÔÆÌåÓý

  1. Gemini-II
  2. Topics

Star Trails/No Tracking in RA

 

Hi All,
?
I recently hooked up a Linux PC/indi driver to my Gemini 2, and it seems that ever since then my ASCOM driver or Gemini 2 does not track in sidereal (RA). I¡¯ve reset my USB Settings in Windows, I¡¯ve reset my Gemini 2 controller, powered off, and then cold restarted, and I¡¯ve also re-inputted my mount¡¯s settings. Still, when the mount is commanded to slew to a point, such as when calibrating PHD2 guider or starting a sequence in SGP, it does perfectly but instead of the expected point stars, I observe star trails and no sidereal tracking upon reaching the target point. I¡¯ve uploaded a set of troubleshooting logs located in files/ ¡°promero 12-3-2024¡±. A look at the gemini webpage for iphone shows nominal voltage and battery voltage.
?
I have tried going back to the .25 ASCOM driver version, but nothing changes. I have the latest firmware updates. The mount is a MI-250.
?
In a perhaps related issue, when used, my ethernet connection disconnects after a minute or two, but my USB connection seems stable. This started occurring after I changed my router model and network physical setup. All other network devices work fine.
?
Clear Skies,
?
Paul
 

Hi Paul,
?
The only thing I see is that your mount is set not to track. When you bring up ASCOM driver virtual HC and connect to Gemini, try a Goto to any object, first. Then be sure to click on "Track" checkbox in the driver. Let me know what happens at that point. Does the check box stay checked or unchecks itself? Does the mount start tracking?
?
?
Your mount is set to park mode '1' which means it will not wake up and start tracking until you do a Goto or explicitly wake up the mount using Wake Up command from the physical HC. That's why I suggest to do a Goto, first.
?
Regards,
?
? -Paul
?
On Tue, Dec 3, 2024 at 11:58 PM, Paul Romero wrote:

Hi All,
?
I recently hooked up a Linux PC/indi driver to my Gemini 2, and it seems that ever since then my ASCOM driver or Gemini 2 does not track in sidereal (RA). I¡¯ve reset my USB Settings in Windows, I¡¯ve reset my Gemini 2 controller, powered off, and then cold restarted, and I¡¯ve also re-inputted my mount¡¯s settings. Still, when the mount is commanded to slew to a point, such as when calibrating PHD2 guider or starting a sequence in SGP, it does perfectly but instead of the expected point stars, I observe star trails and no sidereal tracking upon reaching the target point. I¡¯ve uploaded a set of troubleshooting logs located in files/ ¡°promero 12-3-2024¡±. A look at the gemini webpage for iphone shows nominal voltage and battery voltage.
?
I have tried going back to the .25 ASCOM driver version, but nothing changes. I have the latest firmware updates. The mount is a MI-250.
?
In a perhaps related issue, when used, my ethernet connection disconnects after a minute or two, but my USB connection seems stable. This started occurring after I changed my router model and network physical setup. All other network devices work fine.
?
Clear Skies,
?
Paul
 

Will Do (this weekend hehe)!
?
Paul
 

On Thu, Dec 5, 2024 at 07:11 AM, Paul Romero wrote:
Will Do (this weekend hehe)!
?
Paul
?
Success??
?
--

Chip Louie Chief Daydreamer Imagination Hardware?

Astrospheric - South Pasadena, CA?
 

Hi Chip et al,
?
Not yet.. I had to solve a problem with my new Stellarmate OS X to Gemini connection last weekend, then got called out of town for work, now its clouds. Its looking like the weekend before Christmas before I can get out under the stars, which us convenient since Ill be on the lookout for Santa, anyways.
?
Clear Skies,
?
Paul
 

Hi all,
?
The clouds cleared tonight, and I was able to test the ASCOM driver (with the tracking button selected on in virtual handcontroller) and an indi driver to my Gemini 2. Both PCs were connected via ethernet, so they were able to connect at the same time. Both exhibited the same behavior, which is the same as what I observed when I started the thread:
?
1) Mount slewed to wrong side of the meridian (told it to go to Pollux, but it went West). I tried reversing RA on both virtual handcontrol in ASCOM and indi, but this did not change anything.
2) Star Trails evident in all instances and exposures from 2 to 5 seconds. Unable to plate solve, except at pole.
?
I'm thinking perhaps the new firmware, since both indi and ASCOM connected PCs did exact same thing?
I have uploaded the logs from tonight in the files, under Romero.
?
Let me know, and I'll upload the previous firmware using the GFU and test tomorrow night.
?
Clear Skies,
Paul
 

Hi Paul,
?
I don¡¯t know how to read the logs so I can¡¯t help with that. However, the mount pointing in the wrong direction when commanded to goto makes me think a setting is not properly set. Make sure your lat/lon are correct and pay special attention to the signs. Maybe you set it up for southern hemisphere? That would explain the mount going in the opposite direction and star trails as the mount is also tracking in the opposite direction? A wild guess but worth a quick check
?
Also make sure your motors are connected correctly. I believe everyone in these forums has made that mistake at least once :)
?
other than that, if the problems persist maybe try reloading your firmware or, even load the previous one just to test the outcome. But this is mostly a last resort option
?
good luck
 

Check the RA/DEC reversal checkboxes on the HC->Menu->Mount->Gearing screen. Make sure they are not checked unless you have custom gearboxes that reverse tracking direction.
?
?
On Sun, Dec 15, 2024 at 02:12 AM, Paul Romero wrote:

Hi all,
?
The clouds cleared tonight, and I was able to test the ASCOM driver (with the tracking button selected on in virtual handcontroller) and an indi driver to my Gemini 2. Both PCs were connected via ethernet, so they were able to connect at the same time. Both exhibited the same behavior, which is the same as what I observed when I started the thread:
?
1) Mount slewed to wrong side of the meridian (told it to go to Pollux, but it went West). I tried reversing RA on both virtual handcontrol in ASCOM and indi, but this did not change anything.
2) Star Trails evident in all instances and exposures from 2 to 5 seconds. Unable to plate solve, except at pole.
?
I'm thinking perhaps the new firmware, since both indi and ASCOM connected PCs did exact same thing?
I have uploaded the logs from tonight in the files, under Romero.
?
Let me know, and I'll upload the previous firmware using the GFU and test tomorrow night.
?
Clear Skies,
Paul
 

Hi all,
?
Thank You. I am sure that one of those things is the problem!
?
Clear Skies,
?
Paul

1 - 9 of 9