Setting up 10 Micron and SXAO on PHD 2.6.3dev2

[dbrown....@gmail.com]

Hi everyone,

I have used PHD 1.1 some time ago as I could never get Maxim DL to perform correctly. I was using it with a NEQ6 mount controlled by EQDIRECT and the computer. It worked flawlessly. I did try PHD 2.2 at one point but had so many problems trying to get it to work I gave up and reverted to PHD1.1, (only 5 days at a camp and could not waste the time).

I then bought a SXOA unit and found that Maxim DL worked fine with that. Since then I have changed my mount to a 10Micron 1000HPS. But lately when the weather is poor I have found out that if there are clouds and the guide star is obscured for even a few seconds Maxim sends the mount off hunting destroying any image being taken. PHD is reported not to do this, hence renewed interest.

So now I am trying to set up PHD2.6.3. I have it working in simulation mode OK. But last time out at a star party I could not get PHD to work with the actual mount. It was actuating the tip/tilt glass optic but not communicating with the mount for bumps. I had been using the ST4 connection from the AO unit with Maxim DL without problems.

I am sure I have not set up the initial USB connections in the “Connect Equipment” box correctly. The imaging camera is a QSI 683 with the Loadstar X2 guide camera.

So I set Camera to QSI CCD Camera (ascom). Mount was set as Frejvall 10Micron GM Telescope (ascom). This has added functionality to standard ascom drivers. I think this may be the problem but not sure what to set ! I do need the Frejvall driver,  but maybe set as “ AUX Mount”.

(I did not set Auxy Mount as blanked out.)

AO was set as sxAO.

Rotator as Optec Pyxis Rotator (ascom). ( I know this does not affect mount bump unless I alter angles).

Lastly I only get the chance to image roughly 4 times a year at present at star camps until I move house.

I think some help- with initial settings is required.

Any help gladly appreciated.

Derek

[Andy Galasso]

Hi Derek,

Al that gear works well with PHD2, so we should be able to get you up and running in short order.

You can do the initial setup during daylight hours:

First, unplug the ST4 cable from the mount, you won't be needing it and it should be disconnected to avoid any potential issues.

Start with a new equipment profile (Connect Equipment, Manage Profiles, New using wizard).  Use the following equipment selections when prompted.

   Camera: Starlight Xpress SXV; Enter 8.3 for the pixel size and enter your scope's focal length in mm

   Mount: 10Micron GM Telescope (ASCOM)

   AO: sxAO

un-check the option to build a dark library (we'll use a bad-pixel map instead)

Open the connect equipment window update these options

  Next to Camera, click the wrench/screwdriver and enable the option "Square pixels"

  confirm Aux Mount: None

  select  Rotator: Optec Pyxis Rotator (ASCOM)

click Connect All to confirm that everything connects as expected.

Click the brain, and on the Camera tab enable the Subframes option.

Now, with the guide camera covered, build a bad-pixel map. (menu: Darks, Bad-pixel Map).

For the rest, you'll need to be under a night sky.

1. Focus. Slew to an area of the sky with plenty of stars.  Loop exposures (1.5-2s exposures) in PHD2 and use the Star Profile tool to get a nice sharp focus of the guide camera (ensure that the Lodestar X2 is par-focal with the QSI 683; you only need to adjust it once.)

2. Calibration. Slew to near the meridian/celestial equator intersection, select a guide star (or let PHD2 select one by pressing Alt-S), then press the Guide button.  PHD2 will calibrate first the AO, then the Mount.  There should not be any problems, but if it does not work, use the Manual Guide Tool to confirm that you can move both the AO and the Mount in all 4 directions (N/S/E/W).

Once calibration completes you'll be guiding with the AO and the mount will be bumped when necessary. Open the AO Graph window to see it in action.  You may need to adjust the "Bump steps" setting on the Other equipment tab in the brain if the bumps are too slow or too aggressive.  I find that 1.75 works well with my AO at 2130 mm focal length.

If you run into any difficulty, be sure to post you PHD2 Debug Log and Guide Log (getting help).

Andy

[Andy Galasso]

Derek,

I forgot to mention about validating the operation of the rotator.  If you are able to calibrate and guide without issues, then you'll want to confirm the rotator is working too.   Stop guiding, move the rotator to a different angle, at least 45 or 90 degrees away from the starting angle. Select a guide star and start guiding.  Guiding should proceed smoothly.  If it does not (runs away in RA and/or Dec), then open the Other equipment tab in the brain and select the option "Reverse sign of angle".

Andy

[dbrown....@gmail.com]

Hi Andy,
Many thanks I will do as you instruct. It will be some time before I can get out to do it, as the scope the equipment is stripped down at present. I am moving gear across from the WO 132 to a newly aquired Baby Q Tak. I have been waiting for my designs of components to be made for 5 months for it. Just rreceived most bits, but one was not correct. Anyway I will get out asap and let you know the outcome. I was wondering about the ST4 cable as was needed under MaximDL. I could never get it to work without it.

One last question if I may. What about the Per Frejvall ascom driver? It has added functionality for the mount drive. Will it be picked up automatically as it is specified under The SkyX which is the software I use to control the mount position. I have specified it in that program.

Many thanks for your very swift reply, it is much appreciated. Once up and running I will be a happy bunny  :)

Regards,
Derek

[Andy Galasso]

On Sun, Apr 16, 2017 at 6:03 AM, <dbrown....@gmail.com> wrote:

What about the Per Frejvall ascom driver? It has added functionality for the mount drive. Will it be picked up automatically as it is specified under The SkyX which is the software I use to control the mount position. I have specified it in that program.

Hi Derek,

You will see the ASCOM driver in PHD2's Mount selection drop-down list. PHD2 will include all the installed ASCOM mounts in the list. You should be able to confirm that right now, even without the mount connected. You still need to select the ASCOM driver when you go through creating an equipment profile as described in the earlier message -- PHD2 will not select it automatically since PHD2 has no knowledge of your having chosen it in SkyX.

Andy

[dbrown....@gmail.com]

Hi Andy,

Thanks for your fast response.

I only see  "Frejvall 10Micron GM Telescope (ASCOM)". Not the "10Micron GM Telescope (ASCOM)" , as it is not there. I expect it may have the same desired effect in the end. When I originally loaded in all the corrrect drivers from 10 Micron it definately was there. So maybe Frejvall's driver has removed it somehow. I know I didn't. I am working on two different computers so I have to be careful I do not make a silly mistake. My laptop for use in the field is only used for that purpose now, so rarely switched on. I have checked both it and this one for consistency. I have had the simulators working on both computers and been learning as much as possible about the settings. Bad pixel map done for the Loadstar, albeit at the wrong temperatures, easily rectified later on site.

I will,get back to you with test results as soon as I can. Just awaiting parts for mounting the scope now.

Again many thanks for your time,

 Derek

[Andy Galasso]

Derek,

I think you should confirm that you are using the same ASCOM driver in both PHD2 and your other software (SkyX).  I'm not sure why you would see different ASCOM driver names in different programs. It may be necessary to reinstall the ASCOM driver if you do not see it in the list.

Regarding bad-pixel map and temperature: it is not necessary to build a new bad-pixel map when the temperature changes -- that is a benefit using a bad-pixel map.  If you see a hot pixel that was not present when you built the map, select Bad-pixel Map from the Darks menu to open the Refine Bad-pixel Map window. Click on the hot pixel to select it, and then click the Add Bad Pixel button. Close the Refine Bad-pixel window. It sometimes helps to open the Star Profile tool to ensure that you are selecting a true bad pixel and not a dim star.

Andy

[dbrown....@gmail.com]

Hi Andy,

I am using Per Frejvall's ascom driver in all programs.

You may already know this but as I am moving over to remote capability using ACP  I need this particular driver to simplify matters.

Basically it gives added functionality, in that it accepts continuous updates of air temp, atmospheric pressure and GPS data at startup and connection from the StickSyation device produced by Per Frejvall. His ASCOM driver  will allow continuous sync of PC time, also either J2000 or JNOW settings, as in the standard driver slew rate settings.

It will only allow IP address connection as it was primarily designed to be used remotely. It also allows a Debug Log and Comm debug log to be written.


I did reload the 10Micron ascom driver and it now appears in the drop down lists. I originally set up the mout using this driver so do not understand how it has been deleted. It was missing from both computers ??? It is impossible to find out if Per's driver actually does remove the original ascom driver as unfortunately Per passed away suddenly last year. I do not want to mess about removing his driver and reinstalling to find out what happens as I already have enough to be getting on with. Suffice to say both his and the standard ascom drivers are now on the computers.

As for the Bad Pixel map I was not entirely sure if temperature would affect the numbers so thanks for you answer to that one. I did add a couple of pixels at the end of the test with it without problems. I will bear in mind the Star Tool, thanks for the info.

 I will let you know what happens asap.

Next problem, off for a root filling !

Many Regards,
 Derek