Date   

Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

John Davis
 

I think that possibility has been eliminated by the tests which all involve the same guide camera operating with the same settings. There are no problems in the system until Stellarium is added to the mix with its connection to the Mach1 ASCOM driver. For me the question is how to determine if it is PHD2 or Stellarium that is causing the problem. The PHD2 guys naturally assume that it’s Stellarium, but I’m not convinced you can conclude that from the symptoms 


On Jan 9, 2022, at 10:15 AM, Cheng-Yang Tan via groups.io <cytan299@...> wrote:

 I think the problem is that there are so many variables :( One possibility is the guide camera not downloading the image and so PHD freezes. I use SBIG St-i and SC-2 for guiding and have not seen this problem.

cytan


Sent from Yahoo Mail for iPad

On Sunday, January 9, 2022, 9:06 AM, midmoastro <teche70@...> wrote:

John, I thought I noticed similar several weeks back but wrote it off to something I was possibly doing. The difference for me is that I was not running Stellarium, that I recall. I was running NINA and PHD would launch via NINA. Guiding would start out normal, then just stop. Mine would auto pick back up and start tracking again though. It was very odd and was repeatable. I was suspecting some kind of issue between NINA and PHD as I believe I ran just PHD to test. My memories are vague but I thought PHD by itself ran fine and the issue only occurred when I launched it via NINA and had them running together. Again vague memories here but if I ever get clear skies again I will test to try and clarify or see if it happens again.
Todd


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

Cheng-Yang Tan
 

I think the problem is that there are so many variables :( One possibility is the guide camera not downloading the image and so PHD freezes. I use SBIG St-i and SC-2 for guiding and have not seen this problem.

On Sunday, January 9, 2022, 9:06 AM, midmoastro <teche70@...> wrote:

John, I thought I noticed similar several weeks back but wrote it off to something I was possibly doing. The difference for me is that I was not running Stellarium, that I recall. I was running NINA and PHD would launch via NINA. Guiding would start out normal, then just stop. Mine would auto pick back up and start tracking again though. It was very odd and was repeatable. I was suspecting some kind of issue between NINA and PHD as I believe I ran just PHD to test. My memories are vague but I thought PHD by itself ran fine and the issue only occurred when I launched it via NINA and had them running together. Again vague memories here but if I ever get clear skies again I will test to try and clarify or see if it happens again.
Todd


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

ap@CaptivePhotons.com
 

On Sun, Jan 9, 2022 at 10:06 AM, midmoastro wrote:
I was running NINA and PHD would launch via NINA. Guiding would start out normal, then just stop. Mine would auto pick back up and start tracking again though. It was very odd and was repeatable.
There are many things in NINA that stop guiding, depending on your options setting.  Most stop it and restart it (e.g. an autofocus run might do that).  If you can reproduce that, it may be worth posting on NINA's discord the log files from NINA (or just look through them to see if it was aware it stopped guiding). 

But isn't the original issue that tracking stops, not that guiding stops?   Or did I misunderstand?   What happens if you look in APCC or Ascom's display, does the mount THINK it is tracking?  Did the rate change?  Does it park or stop entirely, or momentarily? 

But it is important to distinguish between stopping guiding, and stopping tracking, as they are going to have different causes I think.

There's all sorts of data in the ascom driver log, might be a clue there. 


Re: APCC new install error

Ray Gralak
 

Larry,

No word from Eltima, unfortunately. We may have to find an alternative solution if they don't come through soon.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Larry Phillips
Sent: Sunday, January 9, 2022 6:33 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC new install error

Todd, somehow I missed your post on Jan 5 and did not see it until nx6a replied today about his experience.
Thanks for the feedback and I will ponder this as it does look like a minefield. Thanks to both of you for
replying. It is nice to know I am not alone in this dilemma.
Larry


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

midmoastro
 

John, I thought I noticed similar several weeks back but wrote it off to something I was possibly doing. The difference for me is that I was not running Stellarium, that I recall. I was running NINA and PHD would launch via NINA. Guiding would start out normal, then just stop. Mine would auto pick back up and start tracking again though. It was very odd and was repeatable. I was suspecting some kind of issue between NINA and PHD as I believe I ran just PHD to test. My memories are vague but I thought PHD by itself ran fine and the issue only occurred when I launched it via NINA and had them running together. Again vague memories here but if I ever get clear skies again I will test to try and clarify or see if it happens again.
Todd


Re: Power Supply/USB 3 Hub Recommendations? UPDATE

ap@CaptivePhotons.com
 

On Sat, Jan 8, 2022 at 11:01 PM, Woody Schlom wrote:
I just spent some time on Pegasus-Astro’s forum and learned that I’ve almost certainly blown up my PPBA’s adjustable output.  If you accidentally plug power input into this output – you can blow the adjustable circuit. 
I posted this image a few days ago of the PPBAdv Gen 1 and notice the gaffer tape.  It covers port 1 (which is fairly useless, something fixed in Gen 2) and also the variable output.  That variable output is in the same relative position as power input on the other side, and very easy to confuse if you do not pay attention.

So --- been there, done that, it required a trip to Greece to repair.  To their credit they did so very quickly and for a very fair price. 

I'd suggest those not using the variable output just cover it, and those with gen 1 versions cover port 1.  The later will not blow up, but when you plug things into it and nothing works, it will save you a trip back outside to figure out the ports.  It seems so simple to keep straight, but I often find I am working on stuff with the axes in an odd position, reaching around an OTA or cables, etc.   Plus only half the brain cells work in the dark, I'm sure of that even if doctors disagree.

Gaffer tape - just slightly less useful than duct tape.  :) 

Linwood


Re: APCC new install error

Larry Phillips
 

Todd, somehow I missed your post on Jan 5 and did not see it until nx6a replied today about his experience.  Thanks for the feedback and I will ponder this as it does look like a minefield.  Thanks to both of you for replying.  It is nice to know I am not alone in this dilemma.
Larry


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

 

PS I should also mention PHD does not have any facility for starting/stopping or adjusting tracking rates, so I don't see how it could stop tracking on the mount. 

I will keep a look for any similar issues that come up and do some testing myself



On Sat, Jan 8, 2022 at 10:01 PM Brian Valente via groups.io <bvalente=gmail.com@groups.io> wrote:
Hi John

>>>> they are trying to tell me I’m not using the AP ASCOM driver to communicate to Stellarium (I am).

i wrote that response. i wasn't suggesting that you are not using the ascom driver, You specifically mentioned you were using a plugin, which for a while was distributed separately. i was simply suggesting to check that you aren't using a deprecated way to connect your scope. 

PHD hasn't seen issues like this in multi-star guiding that I know of (I've been a regular on those forums for quite some time), but if you suspect multi-star you can always disable it and see if the condition goes away.

I have personally experienced similar situations where tracking "gets turned off"on my ap1600 without guiding (I don't usually use PHD because i have encoders) so i'm wondering if it is something elsewhere. The challenge is always there are many variables so it's hard to know what to isolate. 

Brian


On Sat, Jan 8, 2022 at 9:39 PM John Davis <johncdavis200@...> wrote:

Unfortunately the knee-jerk response from the PHD2 support forum is “oh it’s a Stellarium problem – go ask them” or they are trying to tell me I’m not using the AP ASCOM driver to communicate to Stellarium (I am).

As a software tester – I’m used to developers always assuming that it CAN’T be THEIR software that has the bug…. Sigh.

 

 

Seeing what you have experienced, I have seen some odd behaviors like that as well – not *exactly* the same – but cases where stars just start tracking off without any explanation.

I know that PHD2 is good – but I got to think that the new multi-star guiding code just might still have some bugs in it.  I’m just skeptical that PHD2 has NOTHING to do with any of this.

 

I’ll let you know if I find anything else on another board.

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Joel Short
Sent: Saturday, January 8, 2022 11:21 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

 

Oh my word John!  I MIGHT have observed something similar, but this is with a different mount (CEM120EC).  When I first slew to near the meridian/celestial equator in order to do a PHD calibration, I get this:

 

The stars keep trailing like this for over a minute until finally it somewhat stabilizes, but even then the stars will oscillate back and forth over about 5-6 star widths.  This is definitely NOT expected behavior for this mount, and I've observed this a few times this evening.  It is unnerving.  

After reading your post I closed PHD and Stellarium, manually slewed to the same spot and immediately started PHD and started looping images (started within 5s of slewing to the spot).  The stars stayed bang on immediately.  No having to wait a minute for the mount to stop moving and no oscillation.  

 

I can't say this is the same issue, but I'm certainly going to keep my eye on this and see where it goes.  Thanks for posting this.

joel

 

On Sat, Jan 8, 2022 at 9:13 PM John Davis <johncdavis200@...> wrote:

Hello,

   I have been seeing this problem for several months now, and I would like some input as to what the nature of the problem might be.


**NOTE: I have also sent this same post to the PHD2 support group **  
Just thought I'd send it to the AP list too - in case someone here had experienced and solved the problem.

   To summarize, I am seeing problems with PHD2 guiding - most often the RA tracking - when I am running a guiding session in PHD2 and have the mount also communicating with Stellarium via the Telescope Control plug-in.

 



--
Brian 



Brian Valente



--
Brian 



Brian Valente


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

 

Hi John

>>>> they are trying to tell me I’m not using the AP ASCOM driver to communicate to Stellarium (I am).

i wrote that response. i wasn't suggesting that you are not using the ascom driver, You specifically mentioned you were using a plugin, which for a while was distributed separately. i was simply suggesting to check that you aren't using a deprecated way to connect your scope. 

PHD hasn't seen issues like this in multi-star guiding that I know of (I've been a regular on those forums for quite some time), but if you suspect multi-star you can always disable it and see if the condition goes away.

I have personally experienced similar situations where tracking "gets turned off"on my ap1600 without guiding (I don't usually use PHD because i have encoders) so i'm wondering if it is something elsewhere. The challenge is always there are many variables so it's hard to know what to isolate. 

Brian


On Sat, Jan 8, 2022 at 9:39 PM John Davis <johncdavis200@...> wrote:

Unfortunately the knee-jerk response from the PHD2 support forum is “oh it’s a Stellarium problem – go ask them” or they are trying to tell me I’m not using the AP ASCOM driver to communicate to Stellarium (I am).

As a software tester – I’m used to developers always assuming that it CAN’T be THEIR software that has the bug…. Sigh.

 

 

Seeing what you have experienced, I have seen some odd behaviors like that as well – not *exactly* the same – but cases where stars just start tracking off without any explanation.

I know that PHD2 is good – but I got to think that the new multi-star guiding code just might still have some bugs in it.  I’m just skeptical that PHD2 has NOTHING to do with any of this.

 

I’ll let you know if I find anything else on another board.

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Joel Short
Sent: Saturday, January 8, 2022 11:21 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

 

Oh my word John!  I MIGHT have observed something similar, but this is with a different mount (CEM120EC).  When I first slew to near the meridian/celestial equator in order to do a PHD calibration, I get this:

 

The stars keep trailing like this for over a minute until finally it somewhat stabilizes, but even then the stars will oscillate back and forth over about 5-6 star widths.  This is definitely NOT expected behavior for this mount, and I've observed this a few times this evening.  It is unnerving.  

After reading your post I closed PHD and Stellarium, manually slewed to the same spot and immediately started PHD and started looping images (started within 5s of slewing to the spot).  The stars stayed bang on immediately.  No having to wait a minute for the mount to stop moving and no oscillation.  

 

I can't say this is the same issue, but I'm certainly going to keep my eye on this and see where it goes.  Thanks for posting this.

joel

 

On Sat, Jan 8, 2022 at 9:13 PM John Davis <johncdavis200@...> wrote:

Hello,

   I have been seeing this problem for several months now, and I would like some input as to what the nature of the problem might be.


**NOTE: I have also sent this same post to the PHD2 support group **  
Just thought I'd send it to the AP list too - in case someone here had experienced and solved the problem.

   To summarize, I am seeing problems with PHD2 guiding - most often the RA tracking - when I am running a guiding session in PHD2 and have the mount also communicating with Stellarium via the Telescope Control plug-in.

 



--
Brian 



Brian Valente


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

John Davis
 

Unfortunately the knee-jerk response from the PHD2 support forum is “oh it’s a Stellarium problem – go ask them” or they are trying to tell me I’m not using the AP ASCOM driver to communicate to Stellarium (I am).

As a software tester – I’m used to developers always assuming that it CAN’T be THEIR software that has the bug…. Sigh.

 

 

Seeing what you have experienced, I have seen some odd behaviors like that as well – not *exactly* the same – but cases where stars just start tracking off without any explanation.

I know that PHD2 is good – but I got to think that the new multi-star guiding code just might still have some bugs in it.  I’m just skeptical that PHD2 has NOTHING to do with any of this.

 

I’ll let you know if I find anything else on another board.

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Joel Short
Sent: Saturday, January 8, 2022 11:21 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

 

Oh my word John!  I MIGHT have observed something similar, but this is with a different mount (CEM120EC).  When I first slew to near the meridian/celestial equator in order to do a PHD calibration, I get this:

 

The stars keep trailing like this for over a minute until finally it somewhat stabilizes, but even then the stars will oscillate back and forth over about 5-6 star widths.  This is definitely NOT expected behavior for this mount, and I've observed this a few times this evening.  It is unnerving.  

After reading your post I closed PHD and Stellarium, manually slewed to the same spot and immediately started PHD and started looping images (started within 5s of slewing to the spot).  The stars stayed bang on immediately.  No having to wait a minute for the mount to stop moving and no oscillation.  

 

I can't say this is the same issue, but I'm certainly going to keep my eye on this and see where it goes.  Thanks for posting this.

joel

 

On Sat, Jan 8, 2022 at 9:13 PM John Davis <johncdavis200@...> wrote:

Hello,

   I have been seeing this problem for several months now, and I would like some input as to what the nature of the problem might be.


**NOTE: I have also sent this same post to the PHD2 support group **  
Just thought I'd send it to the AP list too - in case someone here had experienced and solved the problem.

   To summarize, I am seeing problems with PHD2 guiding - most often the RA tracking - when I am running a guiding session in PHD2 and have the mount also communicating with Stellarium via the Telescope Control plug-in.

 


Re: Power Supply/USB 3 Hub Recommendations? UPDATE

Woody Schlom
 

Jeff,

 

Could be.  Or the PowerBox Advance unit is physically so small there’s no room for a larger connector.  I also have a PowerBox Micro – and it too has all 5.5mm x 2.1mm connectors.

 

I like yours with different connectors much better – particularly for portable use where I unplug everything each time I setup (often in the dark).  I’ve since put new large labels on mine indicating the 12v INPUT connector.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Jeffc
Sent: Saturday, January 8, 2022 8:42 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations? UPDATE

 

Interesting.  

 

Fwiw.. the UPBV2 has a different connector for the power “input” than the output connectors.   The “input” power is an XT60 connector.    Perhaps this was an improvement on the UPBV2 to prevent the problem described.  

 

-jeff

 

On Jan 8, 2022, at 8:02 PM, Woody Schlom <woody_is@...> wrote:



Robert,

 

I just spent some time on Pegasus-Astro’s forum and learned that I’ve almost certainly blown up my PPBA’s adjustable output.  If you accidentally plug power input into this output – you can blow the adjustable circuit.  And I know that in the dark two weeks ago, I did exactly that.  Pegasus uses the exact same connectors (5.5mm x 2.1mm) for all power connections – in, out, and adjustable out.  So it’s really easy – particularly in the dark to plug cables in wrong.  I’ve now put big labels on mine.

 

But I have another Pegasus-Astro device with a similar Adjustable Out.  So I just tested it.

 

Power supply input = 12.21v DC. (from Pegasus-Astro regulated 10A PS)

Adjustable Out = 12.21v DC.

 

Power supply input = 12.87v DC.  (from Powerwerx PS)

Adjustable Out = 12.23v DC. 

 

So that output is definitely regulated – at least to within a couple of hundredths of a volt.

 

I find using all the same connectors a significant problem in the dark when you’re in a hurry.  Oh well.  Live and learn. 

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Woody Schlom
Sent: Saturday, January 8, 2022 7:17 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

Robert,

 

OK, I can now report with some first-hand data.  I just connected my new Pegasus-Astro “Pocket Power Advance Gen-2” box (PPA) to a couple of different DC power supplies.

 

Pegasus 12v 10 amp power supply:

PS output = 12.21v DC (as per Fluke-115)

PPA reported input voltage = 12.2 (as per Pegasus software)

4 main 12v DC outputs = 12.20v DC (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

Powerwerx SS-30DV power supply set to 12.87v DC.

PS output = 12.87v DC (as per Fluke-115)

PPA reported input voltage = 12.8 (as per Pegasus software)

4 main 12v DC outputs = 12.85 (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

So yes, the Pegasus Pocket Powerbox Advance I have is passing input voltage through to the four main 12v DC outputs. 

 

But it appears that something is wrong with my adjustable DC output.  No matter what output voltage I set it at – my Fluke-115 only reads 0.012v DC coming out.  I’m about to contact Pegasus about this.  Either I’m doing something wrong (wouldn’t be the first time), or my PPA isn’t fully functional.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Robert Berta
Sent: Saturday, January 8, 2022 5:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Re: Power Supply/USB 3 Hub Recommendations? UPDATE

Jeffc
 

Interesting.  

Fwiw.. the UPBV2 has a different connector for the power “input” than the output connectors.   The “input” power is an XT60 connector.    Perhaps this was an improvement on the UPBV2 to prevent the problem described.  

-jeff

On Jan 8, 2022, at 8:02 PM, Woody Schlom <woody_is@...> wrote:



Robert,

 

I just spent some time on Pegasus-Astro’s forum and learned that I’ve almost certainly blown up my PPBA’s adjustable output.  If you accidentally plug power input into this output – you can blow the adjustable circuit.  And I know that in the dark two weeks ago, I did exactly that.  Pegasus uses the exact same connectors (5.5mm x 2.1mm) for all power connections – in, out, and adjustable out.  So it’s really easy – particularly in the dark to plug cables in wrong.  I’ve now put big labels on mine.

 

But I have another Pegasus-Astro device with a similar Adjustable Out.  So I just tested it.

 

Power supply input = 12.21v DC. (from Pegasus-Astro regulated 10A PS)

Adjustable Out = 12.21v DC.

 

Power supply input = 12.87v DC.  (from Powerwerx PS)

Adjustable Out = 12.23v DC. 

 

So that output is definitely regulated – at least to within a couple of hundredths of a volt.

 

I find using all the same connectors a significant problem in the dark when you’re in a hurry.  Oh well.  Live and learn. 

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Woody Schlom
Sent: Saturday, January 8, 2022 7:17 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

Robert,

 

OK, I can now report with some first-hand data.  I just connected my new Pegasus-Astro “Pocket Power Advance Gen-2” box (PPA) to a couple of different DC power supplies.

 

Pegasus 12v 10 amp power supply:

PS output = 12.21v DC (as per Fluke-115)

PPA reported input voltage = 12.2 (as per Pegasus software)

4 main 12v DC outputs = 12.20v DC (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

Powerwerx SS-30DV power supply set to 12.87v DC.

PS output = 12.87v DC (as per Fluke-115)

PPA reported input voltage = 12.8 (as per Pegasus software)

4 main 12v DC outputs = 12.85 (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

So yes, the Pegasus Pocket Powerbox Advance I have is passing input voltage through to the four main 12v DC outputs. 

 

But it appears that something is wrong with my adjustable DC output.  No matter what output voltage I set it at – my Fluke-115 only reads 0.012v DC coming out.  I’m about to contact Pegasus about this.  Either I’m doing something wrong (wouldn’t be the first time), or my PPA isn’t fully functional.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Robert Berta
Sent: Saturday, January 8, 2022 5:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Re: Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

Joel Short
 

Oh my word John!  I MIGHT have observed something similar, but this is with a different mount (CEM120EC).  When I first slew to near the meridian/celestial equator in order to do a PHD calibration, I get this:
PHD2_Stellarium_TrackingProblem.png

The stars keep trailing like this for over a minute until finally it somewhat stabilizes, but even then the stars will oscillate back and forth over about 5-6 star widths.  This is definitely NOT expected behavior for this mount, and I've observed this a few times this evening.  It is unnerving.  
After reading your post I closed PHD and Stellarium, manually slewed to the same spot and immediately started PHD and started looping images (started within 5s of slewing to the spot).  The stars stayed bang on immediately.  No having to wait a minute for the mount to stop moving and no oscillation.  

I can't say this is the same issue, but I'm certainly going to keep my eye on this and see where it goes.  Thanks for posting this.
joel


On Sat, Jan 8, 2022 at 9:13 PM John Davis <johncdavis200@...> wrote:
Hello,
   I have been seeing this problem for several months now, and I would like some input as to what the nature of the problem might be.

**NOTE: I have also sent this same post to the PHD2 support group **  
Just thought I'd send it to the AP list too - in case someone here had experienced and solved the problem.

   To summarize, I am seeing problems with PHD2 guiding - most often the RA tracking - when I am running a guiding session in PHD2 and have the mount also communicating with Stellarium via the Telescope Control plug-in.


Re: Power Supply/USB 3 Hub Recommendations? UPDATE

Woody Schlom
 

Robert,

 

I just spent some time on Pegasus-Astro’s forum and learned that I’ve almost certainly blown up my PPBA’s adjustable output.  If you accidentally plug power input into this output – you can blow the adjustable circuit.  And I know that in the dark two weeks ago, I did exactly that.  Pegasus uses the exact same connectors (5.5mm x 2.1mm) for all power connections – in, out, and adjustable out.  So it’s really easy – particularly in the dark to plug cables in wrong.  I’ve now put big labels on mine.

 

But I have another Pegasus-Astro device with a similar Adjustable Out.  So I just tested it.

 

Power supply input = 12.21v DC. (from Pegasus-Astro regulated 10A PS)

Adjustable Out = 12.21v DC.

 

Power supply input = 12.87v DC.  (from Powerwerx PS)

Adjustable Out = 12.23v DC. 

 

So that output is definitely regulated – at least to within a couple of hundredths of a volt.

 

I find using all the same connectors a significant problem in the dark when you’re in a hurry.  Oh well.  Live and learn. 

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Woody Schlom
Sent: Saturday, January 8, 2022 7:17 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

Robert,

 

OK, I can now report with some first-hand data.  I just connected my new Pegasus-Astro “Pocket Power Advance Gen-2” box (PPA) to a couple of different DC power supplies.

 

Pegasus 12v 10 amp power supply:

PS output = 12.21v DC (as per Fluke-115)

PPA reported input voltage = 12.2 (as per Pegasus software)

4 main 12v DC outputs = 12.20v DC (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

Powerwerx SS-30DV power supply set to 12.87v DC.

PS output = 12.87v DC (as per Fluke-115)

PPA reported input voltage = 12.8 (as per Pegasus software)

4 main 12v DC outputs = 12.85 (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

So yes, the Pegasus Pocket Powerbox Advance I have is passing input voltage through to the four main 12v DC outputs. 

 

But it appears that something is wrong with my adjustable DC output.  No matter what output voltage I set it at – my Fluke-115 only reads 0.012v DC coming out.  I’m about to contact Pegasus about this.  Either I’m doing something wrong (wouldn’t be the first time), or my PPA isn’t fully functional.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Robert Berta
Sent: Saturday, January 8, 2022 5:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Re: Power Supply/USB 3 Hub Recommendations?

Woody Schlom
 

Robert,

 

OK, I can now report with some first-hand data.  I just connected my new Pegasus-Astro “Pocket Power Advance Gen-2” box (PPA) to a couple of different DC power supplies.

 

Pegasus 12v 10 amp power supply:

PS output = 12.21v DC (as per Fluke-115)

PPA reported input voltage = 12.2 (as per Pegasus software)

4 main 12v DC outputs = 12.20v DC (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

Powerwerx SS-30DV power supply set to 12.87v DC.

PS output = 12.87v DC (as per Fluke-115)

PPA reported input voltage = 12.8 (as per Pegasus software)

4 main 12v DC outputs = 12.85 (as per Fluke-115)

1 variable DC output set to 12v = 0.012 (NOT WORKING!)

 

So yes, the Pegasus Pocket Powerbox Advance I have is passing input voltage through to the four main 12v DC outputs. 

 

But it appears that something is wrong with my adjustable DC output.  No matter what output voltage I set it at – my Fluke-115 only reads 0.012v DC coming out.  I’m about to contact Pegasus about this.  Either I’m doing something wrong (wouldn’t be the first time), or my PPA isn’t fully functional.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Robert Berta
Sent: Saturday, January 8, 2022 5:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Problem with PHD2 when also connected to Mach1 mount using Stellarium's Telescope Control plugin

John Davis
 

Hello,
   I have been seeing this problem for several months now, and I would like some input as to what the nature of the problem might be.

**NOTE: I have also sent this same post to the PHD2 support group **  
Just thought I'd send it to the AP list too - in case someone here had experienced and solved the problem.

   To summarize, I am seeing problems with PHD2 guiding - most often the RA tracking - when I am running a guiding session in PHD2 and have the mount also communicating with Stellarium via the Telescope Control plug-in.
 
What I am seeing is that after I run a full calibration in PHD2, then let the guiding assistant run for 3-4 minutes - apply the suggested parameters, then PHD2 will begin to guide, but after period of time (it varies) - the RA tracking seems to stop and the graph tracks totally off the scale (even set to +- 16").  I stop and re-start, the same thing happens.  
 
I'm using 
PHD2 version 2.6.10
Stellarium version 0.21.2 with version 0.4.2 of the Telescope Control plug-in.
Mach1 ASCOM Driver 5.30.10
 
I have used the combination of PHD2/Stellairum and Mach1 for over a year - originally was using the Stellarium Scope software to communicate between the ASCOM driver and Stelliarum - but switched to the Telescope Control plug-in when I upgraded to a new version of Stellarium.  I don't think that the problem exactly coincides with starting to use the Telescope Control plug-in.  It seems to roughly coincide with when I upgraded to PHD2 2.6.10 with the multi-star guiding feature.
 
Further detail on my observations:  Tonight I:
1). started up SGP, connected to all the hardware (camera, filter wheel, focuser, mount) and tested the imaging camera. 
2). started PHD2 and connected to the mount and guide camera (ASI120mm) to verify that connection.  
3). started Stellarium and connected to the mount.  Using Stellarium I selected a star near the Meridian and Celestial Equator - then had the mount slew to that location using the Telescope Control Interface
4). Had PHD2 autoselect main and other guide stars - and do a calibration run. Everything went fine.
5). After calibration - let it guide for about 30 seconds (guided ok) - then invoked the Guiding assistant.  Let it run for about 4 minutes and then stopped - after the backlash calibration - I accepted the reccomendations and let PHD2 begin guiding.
6). After about 2 minutes - the RA started tracking off of the graph (I see "MountGuidingEnabled = false and MultiStar = false on the Log viewer).  
7). I stopped guiding and re-selected stars - started again - guiding ran a few seconds and the same thing happened again.
8). I started a 3rd time and this time - there were wild swings in the RA guiding and a little in DEC.  I stopped again.
9). I re-ran Calibratoin - it ran fine
10). started guiding again - again the wild fluctuations in RA.
 
11). I disconnected Stellarium from the mount and shut it down.
12). I disconnected PHD2 from the camera and mount and shut it down
13). I shutdown SGP after disconnecting to all devices
14). I powered down the Mach1 mount and started it back up
 
15). Restarted SGP and reconnected to all devices.
16). Restarted PHD2 and connected to the guide camera and mount
 
17). Manually slewed to a location near the meridian and equator... had PHD2 autoselect star and calibrate.
18).  monitored guiding for  90 seconds - no problems - stopped guiding
19). slewed to imaging object - had SGP platesolve and run a sequence.
20). PHD2 guided FINE for 1h 36m until clouds ended the session.
 
SO - I'm almost positive that there is some problem - conflict - something between PHD2 and Stellarium.  Question is - where is the problem?
 
NOTE:  I have (in prior sessions with this same problem) - just tried disconnecting the Telescope Control plugin in Stellarium, and also exiting Stellarium.  This does NOT seem to fix the problem.  It requires at least a restart of PHD2 - and maybe also the Mach1 mount software).
 
If this is a known problem - sorry for the long post.  I attempted to search for this problem in prior posts - but I couldn't find this particular issue.
 
I really like being able to monitor the mount position with Stellarium during a session - so I would really like to get this problem fixed.  Help would be greatly appreciated.
 
Thanks!
John D.
 


Re: Power Supply/USB 3 Hub Recommendations?

Woody Schlom
 

Robert,

 

  1. The Pegasus devices appear to pass through voltage to the “main” DC outputs.  So 12.2v in results in 12.2v coming out of the main DC outputs.  I’ve never tested mine, but will try to do that next week.
  2. Pegasus says that if you put 14.5v into their devices, they’ll automatically shut down.  So the Pegasus devices “should” tolerate 13.8v input voltage.  And indeed, my Pegasus devices came with standard cigarette lighter power cables.
  3. But there’s another DC output on the Pegasus devices that they call “variable.”  And that output IS regulated to the voltage you set (4v to 12v in steps as I recall).  So even if you input 13.8v to the Pegasus device, that variable DC output will still output 12v.  It must have a built-in Boost/Buck circuit.
  4. I have several pieces of equipment that don’t like voltage higher than around 12.5v.  They can tolerate higher voltage, but they heat up because they’re converting the excess voltage over 12.2v to heat.  So I’m using Pegasus’ own 120v AC to 12.2v DC power supply to feed my Pegasus devices.  And that 10 amp Pegasus power supply IS regulated.  So I’m feeding regulated 12.2v into my Pegasus devices.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Robert Berta
Sent: Saturday, January 8, 2022 5:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Power Supply/USB 3 Hub Recommendations?

 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Re: Power Supply/USB 3 Hub Recommendations?

Robert Berta
 

@Linwood....thanks for your comments re: any issues with dew heaters on the Pegasus. I also sent a note to Woody who also answered my questions. I live in Michigan so I normally run all my 12v. equipment at 13.8 volts from a regulated power supply to deal with the days we get frigid temps. Does the Pegasus output the same input 13.8 volts to their outputs or is it regulated down to 12 volts. And of course....does it work ok at 13.8 V or must be 12 V.


Re: Power Supply/USB 3 Hub Recommendations?

Robert Berta
 

@Woody....thanks for your reply to my question about possible issues with dew heaters. I recognize that 12 volts is not ideal for AP mounts. I run 13.8 volts from a regulated power supply....and use same voltage for my other gear too. Never any problems. Since I live in Michigan I like 13.8 volts...especially in frigid temperatures. I also lower the max slew speed of my 900 and 1100 mounts when using in those low temps. It sounds like the hub will pass through the same 13.8 input volts to other devices or is it regulated down to 12 volts? 


Re: APCC new install error

nx6a <danrprice@...>
 

Hi.  Just a quick comment.  I had a similar problem with APCC.  I have a guess (and only a guess) to what the problem is.  It does seems to be associated with the Eltima virtual port drivers.  But, I also think it has to do with how I installed Windows 11 Pro.  I used the free upgrade option and kept all of my third party software in place when doing so.  Didn't find this problem until after the Microsoft 10 day rollback option had expired.  To solve the problem, downloaded and installed on a USB stick a Windows 11 Pro .iso.  Applied it to the laptop while keeping all third party software in place without success.  So, did the "Crack a Walnut With a Sledgehammer" approach and wiped the laptop down to bare metal.  This is one of the options during installation.  Even deleted all partitions.  Then installed Windows 11 Pro on a new partition.  After that the installation of APCC went smoothly and the problem with the Eltima virtual port drivers vanished.  I believe this is similar to your solution.  My guess is that the Windows 11 Pro upgrade from Windows 10 Pro does not play nice with some third party software.  That's not much of a surprise.  Clear Skies!

4161 - 4180 of 88161