Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_30_second_exp_2_winners.thumb.jpg.b5430b40547c40d344fd4493776ab99f.jpg

Recommended Posts

Hello,

I was wondering if anyone could help with an autoguiding problem.

I have a Celestron AVX mount. I cannot get it to guide at all externally. It moves fine from the handset.

I have tried guiding from FireCapture, PHD2 (both auto and just manually guiding)

I have tried to connect via the USB to Handset, and via the autoguide port (via my ASI290mc).

I know the handset port communicates (on COM4) because I flashed the Celestron Firmware.

I am beginning to think I have a tech support problem, but I want to rule out errors on my part.

Thanks,

Long time lurker, first time poster.

Share this post


Link to post
Share on other sites

Hi

You should just connect your guide cam via usb to your computer and use PHD2. Connect the handset to usb using a usb-serial cable. Make sure you have Ascom installed and the correct Celestron driver. It should all work smoothly :).

Louise

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Thalestris24!

Regarding your instructions:

You should just connect your guide cam via usb to your computer and use PHD2. -> Yes

Connect the handset to usb using a usb-serial cable. -> The newer AVX handset is miniUSB at the bottom not serial , but otherwise yes, PC to Handset via USB.

Ascom -> Yes

Universal Celestron Driver (it's the only one on the Ascom site) -> Yes.

... and with all that, the PC PHD2 Manual Controls are dead... I think I have a tech support problem :(

 

Ken

Share this post


Link to post
Share on other sites

The phd2 manual controls only cause tiny movements. Test the guide output by using it for real on a guide star. I wasn't aware there was a new version/handset. I take it you can slew the mount ok via whatever planetarium software you're using? 

Louise

Share this post


Link to post
Share on other sites

Since you would like to go computerized, have you gotten Celestron's NexRemote on your computer?

It gives you a virtual hand controller on your computer. It can tie into Stellarium, and PHD2.

And it gives you computer control of your AVX. Also, your regular hand control still works at the mount for alignment corrections when needed.

I've gone so far with my AVX i refer to it as my Borg-a-Scope, and completely control it from inside my house, wirelessly.

 

Oh, and Welcome! Glad you decided to jump in, Ken!

Edited by SonnyE

Share this post


Link to post
Share on other sites
2 hours ago, Thalestris24 said:

The phd2 manual controls only cause tiny movements. Test the guide output by using it for real on a guide star. I wasn't aware there was a new version/handset. I take it you can slew the mount ok via whatever planetarium software you're using? 

Louise

Hi Louise,

Yeah, they finally decided to do a minor upgrade to the hand controllers. More modern computer friendly. (I haven't had a serial port in a while now)

Do believe I would miss the security of the old ST-4 plug snapping in though.

The telescope industry sorely lags behind other computer advances, and can't even see the dust from the Cell Phone industry. Sigh! :cussing:

Share this post


Link to post
Share on other sites

Hi Ken

Just to clarify:

1) If you're going camera - mount via an ST4 cable, have you selected "on camera" for the mount connection in PHD2?

2) If you've done that, did PHD2 report "Mount Connected" when you connected to the mount?

3) Ro Manual Guide in PHD2, best to set the step to 5000 (max) to get noticeable moves.

4) If all that worked, did PHD2 go through the calibration process - a number of steps to the west, back to the star, then a number of steps north, and back to the star?

Michael

Share this post


Link to post
Share on other sites

Louise,

I do not use any planetarium software on the PC. Just startracker on my phone and the NextStar library. I am really starting out on AP planets... so a planetarium is overkill for me right now.

SonnyE,

I did not know there was a handset emulator. I will get it and try it out. That would reveal that my AVX takes external control, or provide further evidence it does not.

And yes, the hardware remote works  fine on it's own.

Michael,

When I tested the Camera-ST4-AVX, I selected "on camera" in PHD2 and "camera-st4" or somesuch in firecapture. Yes, both programs said that the mount connection was successful. I will max up the step in PHD2, and no, PHD2 never did any calibration.

Thanks all of you and best,

Ken

 

 

Share this post


Link to post
Share on other sites
2 minutes ago, Ottawa Ken said:

Louise,

I do not use any planetarium software on the PC. Just startracker on my phone and the NextStar library. I am really starting out on AP planets... so a planetarium is overkill for me right now.

SonnyE,

I did not know there was a handset emulator. I will get it and try it out. That would reveal that my AVX takes external control, or provide further evidence it does not.

And yes, the hardware remote works  fine on it's own.

Michael,

When I tested the Camera-ST4-AVX, I selected "on camera" in PHD2 and "camera-st4" or somesuch in firecapture. Yes, both programs said that the mount connection was successful. I will max up the step in PHD2, and no, PHD2 never did any calibration.

Thanks all of you and best,

Ken

 

 

If you use ST4 then make sure the guide cam is set to 8 bit - it uses the other 4 for mount control. You set the bit depth in phd2 using the tool button next to the camera connect button.

Louise

Share this post


Link to post
Share on other sites
9 minutes ago, Ottawa Ken said:

SonnyE,

I did not know there was a handset emulator. I will get it and try it out. That would reveal that my AVX takes external control, or provide further evidence it does not.

And yes, the hardware remote works  fine on it's own.

 

It also allows me to completely remote operate wirelessly with my Desktop, or to carry my laptop out and operate at the mount, via my wireless router network. Pretty cool.

And if need be, I just plug in a 15 foot USB cable to my on-mount USB hub, to my laptop, and be in control at a campground.

The link I provided will take you to the Celestron page for the NexRemote.

When starting out, I had it in mind to be computer connected. Getting to the point I'm at now was a distant dream then.

Being totally in remote control now is a dream realized.

Share this post


Link to post
Share on other sites

Thanks everyone,

Nexremote worked and PHD2 manual guide worked with .5 degrees per second. Tonight I will try to use firecapture for imaging and PHD2 for guiding at the same time.

Ottawa winters would be ideal for remote. We have to get outside while we can in the Spring and Summer!

Best,

 

Ken

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By AstroRuz
      Hello all,
      So I routinely have issues with guiding. Last night, I was getting some solid sub exposures of 5 minutes on the Flaming Star Nebula. When it got to about 15-20minutes of the meridian, I began getting trails on my stars. Then after the flip, I was still getting trails despite PHD reporting all's well.  I moved over to the Horsehead Nebula and tried 5 minutes there, and it behaved itself. Then I tested it on the Jellyfish Nebula and it also behaved (just about - minor trails). But it just did not want to dig it with the Flaming Star Nebula, which was practically near the zenith (about 2:30am 30/11/19).
      I tried recalibrating PHD (I use Pulseguide so the scope knew where it was). I then also recalibrated PHD at Alnitak so it was near the celestial equator (as the PHD best practices recommend). I even checked my Polar Alignment (done with a Polemaster), which was fine. I couldn't find anything wrong. 
      The guide scope was slightly off alignment with the main OTA, but that wasn't making any differences before the Meridian. 
       
      I did find the helical focuser of the Starwave 50mm guide scope I was using to have some movement in it again when I manipulated the guide camera. So that's something I need to look into. But before I start throwing money at this issue, I see the terms "flexure" and "differential flexure" coming up. Can anyone shed light on what this means please?
      I tried manipulating the OTA in its tube rings, that didn't yield any movement either. The piggyback scope is secure, the g/scope is secure in its rings as well, there's no movement in the OTA focus rack and the cameras are secure in their tubes. 
      I do have my guide rings quite far back on the body of the telescope to assist with fitting the guide scope piggyback. 
      Video of g/scope play: 
       

      Flaming Star Nebula. 5 minute sub, post Meridian Flip, about 2:50am (30/11/19). Note the plate solve compass in the top left. Drift appears to be in S/W direction.

      Position of tube rings (they're now at the focus end).
      I think I am leaning towards needing to move my tube rings (once I remember to get the tools from work). 
       
       
      Equipment:
      (brand new) Skywatcher EQ6-R Pro, SW Evostar Pro 80ED, Altair 0.8x R/F, Canon 600D, Altair Starwave 50mm Guide Scope, Altair AR130 Mono Guide Cam. 
       
       
    • By John Lawley
      Hi - I've not posted here before as only just launched into this hobby, although I've always been massively interested in astronomy.
      I had first light on my rig last night, which is:
      Esprit 100, HEQ 5 Pro, ZWO EAF, ZWO mini filter wheel, skywatcher 50ED guidscope with ASI120, ZWO1600mm Pro, Lynx dew controller w 2 astro zap tapes
      A big endeavour to get that lot working from zero experience, but I love a challenge and have really enjoyed the computer side (I'm a grade A nerd)...
       
      So - what went well... I got the guide scope in focus (was stressing about this), and also the main scope. Even more awesomely, the autofocus routine in SGP is working perfectly Filter wheel also working perfectly and I'm getting lovely smooth pics from the main camera (I've already done the flats and darks while I was waiting for clouds to clear). Final good thing (well, good-ish), is that I got the platesolving working eventually, and was able to get the scope to align from Park to the Soul Nebula and centre fine. For some reason the "number of attempts" in my SGP profile hadn't applied, so it was giving up after 1 go, but I got it working in the end.
       
      So the bad...
      I couldn't take any data because every time it finished the platesolving and started PHD2, PHD2 would start the calibration process and then halfway through, the sidereel tracking on the EQMOD panel would turn off. Obviously, that would lead to a "lost the star" error. Is there some reason why sidereel tracking would turn off like that? I'm generally a bit confused as to whether I should be controlling the telescope from SGP (i.e. unpark) or using the park and unpark + tracking button on the EQMOD panel. Both PHD 2 and SGP are setup to use EQMOD ASCOM HEQ5/6?
      So at the moment I can't do anything, because there's no way of guiding without it turning tracking off
       
      Also I was cold. Very Very Cold.
    • By Nikolas74
      From AST Optics selling my mini guiding system that i used for my Redcat51 , i have used it also with my Esprit 100 and had excellent guiding results.
      There is a nice review here if someone wants to read :
      https://www.cloudynights.com/topic/575047-ast-mini-guide-kit-any-comments/
      Lens:    f=100mm F3.5 CCTV objective - made in Japan
      Adjustment:    by ballhead - with reliable clamping
      Dovetail:    compatible with most finder shoes
      True field of view:    2.9° x 3.8°
      Maximum guidable focal length:    1000 mm
      Focusing:    via lens cell
      Connection to camera:    C-Mount
      Lens filter thread:    M30.5mm P=0.5
      Weight:    79 grams
      Length of the objective:    44 mm
       
      PRICE : £100 (selling the mount and the CCTV lens not the camera)
      Paypal accepted buyer pays the fees
      I will cover the postage expenses
      Thank you,
      Nikolas




    • By Greg6498
      Took my Celestron AVX Mount out this afternoon to familiarize my self with it in the daylight. Wasn’t sure if or how it would work, since it’s my first goto Mount. I got it setup per the directions and attached the SkySync GPS. It locked on my location very quickly so I did the Quick Align option just as a test. The polar scope was oriented north, and I used Sky Safari to locate stars I couldn’t see cause it was daytime. My first choice was Sirius and it slewed  right around to what should be the general vicinity! I then chose Venus in the West and off it went! I hit home and it went back to the original setup position. I can’t wait to take it out tomorrow night and really put it through it’s paces! This is totally most excellent!
    • By Forunke
      Ok, so this is a really annoying bug / problem that I have with my setup:
      From time to time, in non regular intervals the image my guiding cam (ZWO ASI120) send seems to get flipped / mirrored or looks like it's from a completely different patch of sky.
      When I'm paying attention to the guide images I can clearly see that the image seems to be flipped in some way.
      It only happens for 1 frame PHD send a warning ( No star found / Star lost Mass changed) and after that everything is fine again. My gear is all connected to a single USB3 Hub which then runs via powered USB3 cable to my Pc.
      I'm not binning and have the noise reduction off (though PHD might got hickups while processing) but it still happens. Sometimes there are minutes between two events sometimes it happens 5 times in a row.
      It also seems like it's only happening during guiding, I haven't seen it happen during calibration yet...
       
      I'm completely clueless what's happening or how to get rid of it, any help / idea is greatly appreciated.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.