Date   

Re: Piertech3 Adjustable Pier with AP1600 Experience

Worsel
 

Psparkman

I have a Piertech adjustable single column carrying an 1100 GT with a 2500mm scope in a 7x10 Piertech rolloff.  I park at P4 to clear the roof when closed.  Good images using a 320 pt APPM model, PHD2 at times.  Image scale = 0.5 to 1.5 depending upon camera. I check polar alignment every 6 months.  It changes a bit or not at all over the last 5 years

The piers are actually made by Linak.  Chris Erickson has been using them for a while and may have more to offer.

Bryan


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

Steven Panish
 

I don't have this particular issue but the AP-V2/Stellarium ASCOM addition has some issues.  I'm using the first Stellarium version that included the code (and thanks to the guy who did it!).  It works fine for me - but only when I connect Stellarium AFTER I've connected to the mount with Cartes du Ciel!  If I don't do that Stellarium connects to the "scope" but won't slew.  This is with a 1200 CP3.  Since it works fine with this workaround, I haven't messed with it further.  I tried a later version of Stellarium and couldn't get it to drive the mount at all.

Steve

On Sun, Jan 9, 2022 at 12:26 PM John Davis <johncdavis200@...> wrote:
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=yahoo.com@groups.io> 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: Anyone using 13035FF Field Flattener with TEC140FL?

Greg Vaughn
 

Thanks, Roland, for your check of optical compatibility of the 13035FF with the TEC160FL.

 

Since it’s not a good optical fit, It appears that I will, in fact, need to remove the OAG from my imaging train to find sufficient room for a PreciseParts adapter to connect with the 160FL flattener.   As I mentioned previously, I think the extra length for the adapter is required because of the nature of the flanged connection to the TEC flattener, which is similar to the connection used to connect a camera to the 2.7in FF for the AP 105 Traveler (67PF562) - and still shown in ‘discontinued products’ on the AP website ( https://www.astro-physics.com/67pf462 ).

 

I suppose the two options with the Mach2 are to master imaging without guiding or move the guide camera to a separate guide scope mounted on the focuser/OTA.   It was a couple years before I moved to the OAG and I’ve gotten quite accustomed to, and fond of, it.   I already use APPM for mapping, however, so hopefully a further jump to imaging without guiding won’t be too difficult.

 

Happy New Year and Clear Skies!

 

Cheers,

Greg

 

Greg Vaughn

Alexandria, VA


Virus-free. www.avast.com


Re: Piertech3 Adjustable Pier with AP1600 Experience

Woody Schlom
 

Psparkman,

 

Regarding moisture coming up from the bottom of an observatory.

 

Almost all the observatories I’m familiar with are built on concrete slabs – except for mine which is a mobile observatory and is built on top of a flat-bed aluminum trailer.  I’ve seen photos of a couple of observatories that were built on stilts and had wooden floors.

 

With the observatories built on concrete slabs or my aluminum trailer, the owner then seals the joint between the floor and walls with lots of silicone seal.

 

And finally, I (and most others) also install some kind of dehumidification system.  The permanent observatories usually use electric dehumidifiers (such as those used in boats).  I use chemical ones in my mobile observatory (Dri-Z-Air in my case).

 

In addition to moisture, you need to keep out insects and rodents.  Mice can be a terrible problem as they chew on wire insulation – and ruin everything.  I know a guy who owns one of the old white 16” Meade “Research” SCT’s on a Meade Alt/Az mount.  Mice got into his observatory, and then up and into the guts of his mount – and chewed through the wire insulation.  He had to completely disassemble the mount and then install all new wires. 

 

I don’t know about observatories, but I know ants love to live in RV’s and once again, they eat the insulation off the wires.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of psparkman via groups.io
Sent: Sunday, January 9, 2022 11:34 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] Piertech3 Adjustable Pier with AP1600 Experience

 

Greetings everyone.  I am the recent lucky owner of an AP1600AE and I want to use it with my Celestron C14 for imaging.  I want to build a "Micro" observatory in my small suburban San Diego back yard.  I have a spot that will work, but need it to be as small as I can get it for my lovely Wife to accept it.  Essentially, I need it to be a 5' cube phone booth with a roll off roof.  I do strictly imaging, so it does not need to accommodate me in there while slewing around.  

With the scope this low, I am worried about extra humidity coming up from the ground, and this is a humid environment as it is.  Also, it would be nice to have the scope up higher to clear the sides of the "observatory" and my neighbors bamboo.  A potential way to solve my problems is to get a Piertech3 heavy duty height adjustable pier.  I could have it park 4 to keep the box as low as possible.  Then open the roof, and raise the pier up for imaging.  This will raise it another 20" and will help with clearance and humidity.

Does anyone have any imaging experience with the Piertech pier at longer focal lengths.  Will it maintain polar alignment well enough to reuse an APCC model?  Any other issues that I should consider with the Piertech?  Another other options or ideas?


Re: Piertech3 Adjustable Pier with AP1600 Experience

Woody Schlom
 

Psparkman,

 

You say you live in San Diego.  Are you a member of SDAA (San Diego Astronomy Association)?  I ask because I believe there are several of us who have Piertech piers.  Mine is the smallest one (single column) and it’s in my mobile observatory and only holds a CPC-1100 Deluxe EdgeHD w/ HyperStar (around 100 lbs. when my LS80DSII Ha solar scope is piggybacked).  So it’s nowhere near as large as you need.  But I’m pretty sure there are at least a couple of the larger dual column PierTech piers out at the club’s Dark-Sky property in Tierra del Sol (near Boulevard, CA).

 

I’d find a 5’ x 5’ observatory with that scope and mount VERY constrained.  My mobile observatory is 7.5’ x 10’ and I’m using an Alt/Az mount – so no CW’s swinging around.  Personally, I wouldn’t go smaller than 10’ x 10’ if I could help it with your gear. 

 

Anyway, if you’re interested, I’m sure I can put you in contact with some club members who own the big dual-column PierTech piers – and I’m sure they’d be happy to demo them for you out at TDS (Tierra del Sol).  I’m not sure any of them have an AP-1600 or C14 on theirs (most seem to have Paramounts and various RC scopes), but the weights are probably similar.

 

And while out at TDS, you can see several types of observatories – roll-off roof, dome, etc.

 

Woody (you can contact me privately)

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of psparkman via groups.io
Sent: Sunday, January 9, 2022 11:34 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] Piertech3 Adjustable Pier with AP1600 Experience

 

Greetings everyone.  I am the recent lucky owner of an AP1600AE and I want to use it with my Celestron C14 for imaging.  I want to build a "Micro" observatory in my small suburban San Diego back yard.  I have a spot that will work, but need it to be as small as I can get it for my lovely Wife to accept it.  Essentially, I need it to be a 5' cube phone booth with a roll off roof.  I do strictly imaging, so it does not need to accommodate me in there while slewing around.  

With the scope this low, I am worried about extra humidity coming up from the ground, and this is a humid environment as it is.  Also, it would be nice to have the scope up higher to clear the sides of the "observatory" and my neighbors bamboo.  A potential way to solve my problems is to get a Piertech3 heavy duty height adjustable pier.  I could have it park 4 to keep the box as low as possible.  Then open the roof, and raise the pier up for imaging.  This will raise it another 20" and will help with clearance and humidity.

Does anyone have any imaging experience with the Piertech pier at longer focal lengths.  Will it maintain polar alignment well enough to reuse an APCC model?  Any other issues that I should consider with the Piertech?  Another other options or ideas?


Piertech3 Adjustable Pier with AP1600 Experience

Patrick Sparkman
 

Greetings everyone.  I am the recent lucky owner of an AP1600AE and I want to use it with my Celestron C14 for imaging.  I want to build a "Micro" observatory in my small suburban San Diego back yard.  I have a spot that will work, but need it to be as small as I can get it for my lovely Wife to accept it.  Essentially, I need it to be a 5' cube phone booth with a roll off roof.  I do strictly imaging, so it does not need to accommodate me in there while slewing around.  

With the scope this low, I am worried about extra humidity coming up from the ground, and this is a humid environment as it is.  Also, it would be nice to have the scope up higher to clear the sides of the "observatory" and my neighbors bamboo.  A potential way to solve my problems is to get a Piertech3 heavy duty height adjustable pier.  I could have it park 4 to keep the box as low as possible.  Then open the roof, and raise the pier up for imaging.  This will raise it another 20" and will help with clearance and humidity.

Does anyone have any imaging experience with the Piertech pier at longer focal lengths.  Will it maintain polar alignment well enough to reuse an APCC model?  Any other issues that I should consider with the Piertech?  Another other options or ideas?


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? 

6461 - 6480 of 90467