Calibration Plots are not orthogonal and often Calibrations fail

[edk]

Gentlemen, 

my PhD2 Calibration plots, when I can get Calibration to work at all, are not orthogonal.  Please see attachment. 

The guide setup is a Sky-Watcher Evoguide 50ED (fl=242mm) with an ASI290 mini camera. Imaging setup is a Sky-Watcher Esprit 100ED APO triplet,  fl=550 mm with an ASI294 MC Pro camera. The mount is a Sky-Watcher EQ6-R Pro with tracking set up through SynScan hand controller. Polar alignment is generally good to excellent using the SharpCap polar alignment tool.  Focus is done by hand using SharpCap for imaging, but is believed to be good per attached images. 

What often happens is the selected star moves out of the selection box and is then lost, resulting in the Calibration failing with comments "star lost - low SNR" or "star lost - low mass". Calibration step size is relatively large, but still provides for 10 or so images. The ASCOM pulse guide settings in EQMOD have been run at 0.1 and 0.9 with similar results. 

I have reviewed quite a lot of PhD2 literature, including the users manual and on line user help documents, but have not seen descriptions of non-orthogonal Calibrations, their causes or corrective actions.   

Any help to understand why Calibrations are failing, and how to fix it, would be greatly appreciated.   

 .  

[wave...@talktalk.net]

Hello flae,,,@gmail.com,

I'm no expert, but I'd suggest increasing the guide speed setting closer to 1x sidereal. For sure, 1.5 arcsec/sec (0.1x) is way too small to get a good calibration.

Hope this helps a bit,

- Jack

[Lenny Shaffer]

The Brain calculates the size of the steps necessary to do the calibration based on the information you have entered for the camera and focal length. Accept that.
Under the Guiding Tab in The Brain is a box labeled "Search Region". Increase that number to something other than 15, say 25. That should eliminate your Lost Star warning message.

On 12/15/2021 10:50 AM, flae...@gmail.com wrote:

I did run it through the brain and got a 400ms step size, but for 12 calibration steps and a calibration distance of 25px. Online tutorials suggest more steps, so I will increase this to 20 steps and increase to 40px (assuming this is the “Calibration Distance” you refer to) next time out, for a Calibration step of the same 400ms - as the two changes offset each other.   

• Is the “selection Box” you refer to the “Calibration Distance” parameter in the Guiding tab of the Brain?  
• Is the value calculated by the brain automatically picked up and used in PhD2?

 

Any comments on the calibration plot not being orthogonal? – ever seen this?

 

Thanks for the help.

 

Ed

 

From: Lenny Shaffer <le...@lenny-shaffer.com>
Sent: Wednesday, December 15, 2021 9:13 AM
To: edk <flae...@gmail.com>
Subject: Re: [open-phd-guiding] Calibration Plots are not orthogonal and often Calibrations fail

 

Have you increased the size of the selection box or run the setup through The Brain to find the correct step size for your setup?

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/8952259b-878f-430e-9ef3-973c61944949n%40googlegroups.com.

 

--
Murphy's Law of the Week: "Murphy invented round holes and square pegs."

--
Murphy's Law of the Week: "Murphy invented round holes and square pegs."

[edk]

Thanks for your input. I will try adjusting suggested parameters. 

• Has anyone seen the nearly linear Calibration characteristic shown in the figure, rather than the right angle of RA then Dec data? 
• Also, the Dec calibration does not return to the origin, but keeps on going to higher values when it should be stepping back to the origin (white circles). Seems like more that a settings issue. 

thanks 

Ed

[bw_msgboard]

With the current setup, the mount isn't responding correctly to guide commands - it is unguidable.  But that may be due to the excessively slow guide speed you're using.  So you need to configure your EQMOD settings according to this document:

 

https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings

 

Then you need to create a new PHD2 configuration profile and enter all the appropriate parameters.  Then follow this procedure while trying to get a workable calibration:

 

https://www.dropbox.com/s/os1thorvswmzaul/How%20to%20create%20a%20baseline%20for%20guiding%20results%20using%20OpenPHD2.pdf?dl=0  

 

If the calibration is still whacky, then something is wrong with the mount or the mount control software.  In that case, use the Star-Cross tool and/or the Manual Guide tool to see if you can get the mount to move consistently and repeatably in all 4 directions.  Until that happens, the mount is un-guidable.

 

I don't know why you couldn't find any explanations in the manual, they exist - here's the section discussing calibration problems and how to understand them:

 

https://openphdguiding.org/man/Trouble_shooting.htm#Problems-_Mount_Control

 

As I said, your problems seem to be so severe that something very basic is wrong with the setup - either the guide speed or the mount.

 

Good luck,

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of edk
Sent: Wednesday, December 15, 2021 7:37 PM
To: Open PHD Guiding

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/27d8b022-b85c-4879-8861-939fbb816c1cn%40googlegroups.com.

[edk]

Hello Bruce,

Thank you for your comprehensive answer. 

The Calibration non-orthogonality, and failure for the Dec calibration to return to the starting point, did appear to be more severe than the kinds of issues discussed in the trouble-shooting sections where all Calibrations still had basic orthogonality and return to the starting point no matter the extent of the excursions. After a more careful read on my part of the sections you pointed out, there are several approaches to validating the basic mount control, which I now see may be at the root of the issue.   If weather predictions hold, these will be tried tonight along with parameter variations.

Thanks again for your guidance. 

Ed 

[bw_msgboard]

Hi Ed, one other thing occurred to me.  In recent months, we've seen some problems from EQ users whose mount wasn't tracking at the sidereal rate.  That apparently has to be done explicitly in the EQMOD user interface, so that would be something to check after you fix the guide speed settings.  Obviously, if the mount isn't tracking, you can't get a calibration done.

 

Good luck,

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of edk

Sent: Thursday, December 16, 2021 5:45 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/63fbae78-dae3-4bf4-99b4-49672c5f00abn%40googlegroups.com.

[edk]

Hi Bruce,

To help focus on the root cause - The mount does seem to track at the sidereal rate as images will stay centered on the screen for extended periods (hour or more). The issue is with Dec primarily (Only??) as also seen in the calibration runs, per attachment.

Hopefully,  tonight will be clear enough to try calibrating with better parameters, use the Guiding Assistant in PhD, and if that does not work, use the PhD "Star" and Manual Guide" tools to check basic connectivity and functionality between computer and mount. 

Thanks again

Ed 

[mj.w...@gmail.com]

Hi Ed

Your Guide Rate is only 1.5arcsec/sec, needs to be at least 7.5.

Adjust the EQMOD ASCOM PulseGuide Setting.

Michael

Wiltshire UK

[Chuck Koos]

Ed, the issue Bruce mentioned is something I discovered several months ago. I was also getting non-orthogonal calibration results, among other strange behaviors. The issue was that when Eqmod connects to a EQ6R Pro, it turns off the mount's tracking. The easiest way to spot this is to watch the stars in the PHD2 window while the camera is looping, you'll see the stars marching off the screen. Simply use the hand controller to restart sidereal tracking or use the tracking button on the bottom of the Eqmod window. This also happens with Sharpcap and Stellarium, which also use Eqmod. Just something to check each time PHD2 first connects to the mount.

-chuck-

[edk]

Hello Michael,

Thanks for the input. 

Please advise where to make the suggested adjustment to the Guide Rate. Per attachment, there does not seem to be an input for the Guide Rate in either EQMOD ASCOM blocks accessible through PhD, so it must be elsewhere. 

Also, Per the attached screenshot log of last night's Calibration efforts, the page 2 calibration summary shows the expected RA rate was 9a-s/sec. Not sure how this got changed in here from the earlier data, but it is above the7.5 value you mentioned. Also, the same calibration shows that the ACTUAL rate was 10X this, which seems to not make sense. I wonder if this has something to do with the pixel size? It is automatically read by all software once the camera is connected.  

The Calibration plot again is just a straight line.  Any other comments?  

thanks 

Ed

[edk]

Well,

I tried again last night and did get PhD to guide, but with a straight line Calibration (It shows 89.9 deg out of orthogonality!!) The sorry sequence is documented in the attached file. 

the intended and actual guide rates were different by 10X - which seems to be an issue. The file is annotated and so any comments, or even better, suggestions,  are appreciated. Results from the Guiding Assistant, and suggestions from it, are included.

I am now trying to do the star cross test in PhD but may have a bad imaging camera - per attached photo of the SharpCap screen, it just gives pinstripes. Would this be the case?

Thanks

Ed

[Brian Valente]

Hi Ed

If that is how your camera is acting on a regular basis, that does not look good

A star cross test is definitely the next step regarding diagnosing your orthagonality.

>>>The sorry sequence is documented in the attached file. 

Please just provide the guidelogs and not a written document. The guidelogs are all that's neededto assess what's going on. You don't need to burn your time producing the writeup

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fbc4f6a5-58be-4142-9ae5-e5897f3c265an%40googlegroups.com.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[mj.w...@gmail.com]

Hi Ed

[flae...@gmail.com]

Yes, my first attempts were at the wrong rates. All new attempts and associated correspondence, which still fail in DEC control, are at between. O.6 and 0.9 rates.

Per correspondence, I will post the Guide Logs.

 

Your patience, and contributions, are very much appreciated.

 

Ed

 

From: open-phd...@googlegroups.com <open-phd...@googlegroups.com> On Behalf Of mj.w...@gmail.com
Sent: Saturday, December 18, 2021 4:25 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
Subject: Re: [open-phd-guiding] Calibration Plots are not orthogonal and often Calibrations fail

 

Hi Ed

 

 

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/087d7310-53dd-453e-bbb0-897548b30dc9n%40googlegroups.com.

[edk]

Calibration data for latest runs corresponding to the attached screenshots can be found at:       https://openphdguiding.org/logs/dl/PHD2_logs_aBLb.zip

[Brian Valente]

Hi Ed

Can you please do a baseline guide output following these steps (same if i sent before)

https://www.dropbox.com/s/zrf0au7jaisvt85/How%20to%20create%20a%20baseline%20for%20guiding%20results%20using%20OpenPHD2.pdf?dl=0

Specifically the longer guiding assistant run so we can see your raw mount performance

your calibrations are very far off, so your guiding is not going to perform well until you get that fixed. It's not clear to me why your orthagonality is so poor.

Did you perform the star cross test?

  

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/752c4753-91ff-43e0-a45b-f5c7882ad5c3n%40googlegroups.com.

[bw_msgboard]

Hi Ed.  Thanks for compiling these results.  I've looked at all of them and obviously there's something profoundly and basically wrong, not anything to do with guiding.  One question I have is why you're getting errors on your main camera download.  This could be caused by problems in the USB subsystem of your PC and those can also affect the guide commands that are being sent to the mount.  It may also relate to the horrible-looking guide camera image you showed earlier.  From a PHD2 point of view, the mount isn't responding correctly to any of the guide commands.  RA is moving far too much and Dec appears to be moving the RA axis.  I suggest that you back things down to the basics of getting the cameras to work correctly - just by looping exposures on both cameras indoors during the daytime and making sure the USB subsystem works.  You should be sure the host PC is running off AC power and is delivering adequate power to the guide camera and that Windows isn't disabling or otherwise "managing" the USB ports.  I think you should also look closely at how EQMOD is connected to the mount and whether that's done correctly - that advice should be sought on forums other than this one.  EQMOD is a well-known and heavily used program and if the settings are entered correctly and the mount is tracking, EQMOD should work fine - just like PHD2 is.  I still have my doubts about the mount tracking - the GA run shows a massive amount of RA drift, nearly 10 arc-sec/sec and the PHD2 screen-shot shows trailing stars in just a single frame.  You need to be absolutely certain about this.  With no guiding being done, a star should stay in the field of view for a long time, it shouldn't be whizzing out of view.

 

If you can ever get to a point where you are getting reliable, in-focus guide camera images, you should just do the Star-Cross test.  Anything else will likely be a waste of time because the calibrations you have are pretty much unusable.  You should also trying taking an unguided 10-second exposure with the main camera to demonstrate that the basic sidereal tracking of the mount is working.

 

I'm sorry this is turning out to be such an excruciating experience for you.

 

Bruce

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of edk

Sent: Saturday, December 18, 2021 6:32 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/752c4753-91ff-43e0-a45b-f5c7882ad5c3n%40googlegroups.com.

[edk]

Next clear night here will be Wed, 22nd. I will try the baseline Guide Output per the outlined steps.

The star-Cross test was not performed as the imaging camera was acting up and would only display many fine stripes (see attached). I have now ordered a new camera, same model as the ASI294MC Pro now being used" and will change over to it if the stripes reappear. 

This afternoon I set up the scope to image objects from my den. I was able to successfully image trees and houses about 200 yards away with both Guide and Image cameras.  This was done with SharpCap in "Framing Shot" mode, then also NINA in recording mode. No sign of the vertical stripes in the imaging camera nor error messages from NINA. Hopefully both will work on Wed night. 

Question: if the guide buttons in NINA , EQMOD and PhD2 all drive the mount in what seems equal amounts in each direction, what does the 
"Star-Cross" test do that these other tests do not??

Ed 

[Brian Valente]

>>> Question: if the guide buttons in NINA , EQMOD and PhD2 all drive the mount in what seems equal amounts in each direction, what does the 
"Star-Cross" test do that these other tests do not??

It will determine if the mount is responding in all direction to simple commands in the PHD2 application.

Just to summarize:

Your mount is not behaving in the way it should when you are using PHD. It should, but for some reason it isn't. 

It's not clear why that is, so next step is to go through a process of elimination

The specific next step is to ensure your mount responds to commands within PHD in all four directions, and produces results that clearly shows it responds in all four directions. The success/failure determines next steps

Just to clarify, the star cross test IS in PHD2, so there isn't another "PHD2" test

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/06166b59-988d-4266-8cf2-dd2b9cce1564n%40googlegroups.com.

[edk]

Hello Bruce,

You asked about the main camera download problem. I think it is a result of the same camera problems that generated the pinstripes (attached). I ordered a replacement camera of the same type (ASI 294MC Pro) this am that is supposed to get here Tuesday. If the same symptom shows up I can swap out the cameras to localize the issue.  

BUT per note above,  I have worked on the camera issue first. Basically, I set up the system in my den and photographed palm trees in the distance. I JUST HOOKED ALL UP AND TURNED IT ON THE SAME AS WHEN IN THE FIELD - EXCEPT NOW THE CAMERAS ARE ALL WORKING OK. No explanation why it works now. I was able to successfully image trees and houses about 200 yards away with both Guide and Image cameras.  This was done with SharpCap in "Framing Shot" mode, then also NINA in recording mode. NINA successfully downloaded the images and gave no error message. No sign of the vertical stripes in the imaging camera nor error messages from NINA. Hopefully both will work on Wed night. See attached photos of Christmas tree lights about 200 yards away using the imaging camera and both SHarpCap and NINA. This was done on Battery alone.  The cabling is all marked and only requires two power leads to go to the scope, and two data leads as well. All the ends are marked so no chance of swapping etc. The leads (USB connectors) were carefully all reseated after each scope repositioning.

Question: if the guide buttons in NINA , EQMOD and PhD2 all drive the mount in what seems equal amounts in each direction, what does the 
"Star-Cross" test do that these other tests do not??

There is no 120V power at my telescope site. I use an 80 amp-hr deep cycle marine battery with at least 95% charge. The computer runs off this through an inverter. Presently, with all equipment running, the battery voltage is 12.38 VDC and the inverter puts out 106 VAC. If the charger is also on (at home only) the battery terminal voltage is 12.68 and the inverter voltage is 104.  

You made two comments I do not know how to check/confirm. Any suggestion how to do so is appreciated:

• "Windows isn't disabling or otherwise "managing" the USB ports". - any suggestions on where to check on this?
  
• "EQMOD is connected to the mount and whether that's done correctly"  - this one has multiple tutorials with screen-shots. I will go back and double check.
  

Along those lines PhD2 has a check box (see attachment) that says "Assume Dec orthagonal to RA"  Should this be checked?  

When tracking only, no guiding, stars do not move out of the field. My first astro photo was 20 - 5 min exposures stacked with DSS, and is attached. There was no Guiding used. It looks to me like the tracking in RA is working well, but more experienced folks should weigh in.

I will keep working on it. 

[edk]

Got it.

I should be able to do the star-cross test when the weather clears on Wed. 

Thanks again

Ed

[mj.w...@gmail.com]

Hi Ed

Your Palm Tree test sounds like you may have had the camera configured in Video Mode, outputing high frame-rate video, as used for Planetary Imaging.

The Long Exposure Mode is the one outputting the pinstripes.

Guide Rate has gone from too small, 1.5arcsecs/sec, to way too big, 92.57 and 105.981 arcsecs/sec:

Until you better understand your software, try guiding with just PHD2 and EQMOD.

USB Power Management and Power Settings are in Windows Device Manager:

Michael

Wiltshire UK

[edk]

What then are the correct USB Power Management and Power Settings to use?

[Brian Valente]

Uncheck the computer's ability to power off the usb device, as shown

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/9d252d83-92da-4d23-8049-9ac827d23d7fn%40googlegroups.com.

[flae...@gmail.com]

Actually I am guiding with PHD@ and EQMOD only.

 

The USB Root Hub was turned off per earlier note to another person who commented on it.

 

As seen in the below data, PHD2 is requested to have an RA rate of 9, which shows up in the mount calibration data below, but the mount is responding at 92.57 a-s/sec!!!  How the command of 9 is converted to 92  is the problem. What is the reason/mechanism that is taking a command from PHD2 of 9 a-s/sec and turning it into 92.57 a-s/sec. What setting/other input could generate this is the insight I am hoping to get help on. Yes, it is clear to me as well what the issue is, but what is the cause and how to fix it.

 

I will try tomorrow to generate the star figure called for by PhD2 as a diagnostic, then go from there.

 

Also, others have noted that NINA does not have the option/function to generate Video so all photos are in long exposure mode.

 

Ed

 

From: open-phd...@googlegroups.com <open-phd...@googlegroups.com> On Behalf Of Brian Valente
Sent: Monday, December 20, 2021 9:43 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
Subject: Re: [open-phd-guiding] Calibration Plots are not orthogonal and often Calibrations fail

 

Uncheck the computer's ability to power off the usb device, as shown

 

 

On Mon, Dec 20, 2021 at 6:42 AM edk <flae...@gmail.com> wrote:

What then are the correct USB Power Management and Power Settings to use?

On Monday, December 20, 2021 at 8:41:09 AM UTC-5 mj.w...@gmail.com wrote:

Hi Ed

 

Your Palm Tree test sounds like you may have had the camera configured in Video Mode, outputing high frame-rate video, as used for Planetary Imaging.

 

The Long Exposure Mode is the one outputting the pinstripes.

 

Guide Rate has gone from too small, 1.5arcsecs/sec, to way too big, 92.57 and 105.981 arcsecs/sec:

 

 

Until you better understand your software, try guiding with just PHD2 and EQMOD.

 

USB Power Management and Power Settings are in Windows Device Manager:

 

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i4Kg3RQgqDhNKdiQM1Qpw%2BrgQ3Ag_a4WvPP0KSWvwo%2Bqg%40mail.gmail.com.

[edk]

Multiple calibrations (which all failed) and a star-cross test were conducted. Results are in https://openphdguiding.org/logs/dl/PHD2_logs_aVqs.zip and summarized in the attached word document. No "Star-crosses" ever formed although the Star-Cross test completed successfully according to PhD. 

As noted in the PhD2 manual "there are many other permutations of bad results, each suggesting a particular problem in the mount, the guide cable, or much less likely, the ASCOM driver for the mount." The guide cables have been replaced twice and are held in place with a support at the mount female receptacle, so this is a less likely scenario. All control parameters for PhD2 have been reviewed repeatedly against the standards mentioned elsewhere in this thread. 

Any insights from looking at the logs, or the screenshots would be appreciated. 

Ed    

[mj.w...@gmail.com]

Hi Ed

The GuideLog you posted is empty.

You were guiding on the 22nd Dec at around 20:48.

The GuideLog you posted is from 23rd Dec at 10:30:58 am.

You must pay attention to the date and timestamp in the filename:

PHD2_GuideLog_2021-12-23_103058

Michael

Wiltshire UK

[flae...@gmail.com]

Hello Michael,

I apologize for the empty file, I do not understand how that happened. In the future I will strip out non-active viewing times to make it more manageable.  

 

PhD2 does not show the log for the last run I performed in its list of upload logs, even if the “show logs with no guiding” box is checked. The correct logs do appear in the Help/Open Log Folder tab. The correct log is attached, and has been stripped of all but that evenings active viewing times, including the calibration attempts. The original log was 35M and may have not uploaded due to size.

 

The instructions for the Star-Cross app explicitly require taking an extended photograph using the main imaging camera. I run the main imaging camera through NINA and so, YES, I was using NINA. Is there an issue with using NINA for this requirement??  If not NINA – Then how take the picture? Should the star-cross images shown up on the NINA photograph taken while PHD was executing the star-cross app?  

 

When I attempt to calibrate using some instructions provided in the thread, including having the weights horizontal and the telescope perpendicular to the RA axis, PhD2 gives a warning that the calibration is not reliable because it is being attempted too far from celestial DEC=0. I am at 26deg N which points very high in the sky.

 

I have now contacted Sky-Watcher, and High-Point, to ask about issues with the EQ6-R mount interface to PHD, including providing them with a writeup and representative logs. I am also looking to reload EQMOD and the mount drivers.

 

Leaving no stone unturned, I will go back and attempt to run a calibration at 0.9 a-s/s

 

I do very much appreciate your help and expertise.

 

Wishing you a fine holiday season.

 

Best regards

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/87d418a3-1388-4dae-9240-5fe66aefc558n%40googlegroups.com.

[wave...@talktalk.net]

Hello again Ed, You said:

      PhD2 gives a warning that the calibration is not reliable because it is being attempted too far from celestial DEC=0. I am at 26deg N  which points very high in the sky.

I haven't followed every post so far, but I had a look at the GuideLog you've attached. This indicates you're running the Calibration at approx. Dec 28°, so too far from the Celestial Equator. Dec 0° is 74° above your southern horizon, so your Dec 28° Calibration attempts were indeed near the Zenith. Even so, Dec 0° will be pretty high too. I note you realised running with a camera exposure of 10ms is problematic so increased it to 2000ms.

In any case, there's insufficient star movement from the calibration steps, so there's a communication fault that the Star Cross Test might help resolve. Unless the rig succeeds in that test, Calibration is, as you know, impossible. Are you sure the Profile details are correct and the mount driver itself correctly set up?

Hope you can get things sorted out soon.

Cheers,

- Jack

[edk]

Hello Jack,

Thanks for the comments.

The star-cross test showed no crosses at all, so all else is moot, if that test was run correctly. There have been several comments that the mount and scope operation needs to be better managed before the data  files can be used effectively. 

All in all, I need to go back to square one before useful information can be provided with the confidence needed to warrant your, and others, time. 

I have gone back and will start with reloading ASCOM, EQMOD and any other software Sky-Watcher recommends, as well as reviewing how the wiring is done. Sky-Watcher uses the SynScan hand controller for a lot of things and the EQMOD software description sounds like it is for connecting through the SynScan controller, which I do not do. Rather I control the mount through the new USB-B port connection on the mount using a cable directly from the computer. 

I also need to get my mount set-up process and PhD2 process down pat as a number of folks have commented on scope pointing data in the files that does not make sense.

I'll be back when all above is worked out. 

Thank you all for your kind patience with this beginner who is working to be responsive to your inputs.

Have a great Christmas and/or holidays.   

[mj.w...@gmail.com]

Hi Ed

All to easy to upload the wrong dates, I've done the same recently and thoroughly confused the OP and myself  :-<

After a couple of Cals you went to 2 second exposures, that's good.

Your settings for starting Cal looked correct.

Cal at Dec = 0 is best, but Dec = 27.9 is not the cause of your basic problem of low Guide Rates.

If only you had done a bit of Guiding, it would have shown us the computed RA and Dec rates in the GuideLog.

Which are too low, based on the Fails at 61 steps, but I think we can take that for granted ?

Use NINA if you're certain it has no Guide Rate settings that are causing the low Guide Rates.

Check EQMOD again, that the ASCOM PulseGuide Settings are higher than the default 0.1, try 0.5

That guy in the image certainly has a snazzy set of cold weather clothes......... :->

Season's Greetings,

Michael

Wiltshire UK

[Dennis Miller]

Ed- following this closely because I have similar issues with my (AZ)- EQ 6Pro. RA and Dec axes angles are well out of whack and some of  my numbers/values are as well. Please report if and if so, how you make out with specific fixes when you have them - I'lll do the same. I'm just waiting for a decent sky to try to restart my entire setup. Btw, I found this talk very helpful:  https://www.youtube.com/watch?v=ifbLY6Q-cN8.  A vast amount of info is covered including a lot of settings with explanations for same. Good luck!

[edk]

Problem Solved. 

The EQMOD Group pointed out that having the SynScan controller attached to the mount overrides/corrupts/modifies any EQMOD inputs, including PhD2. Unplugging the SynScan controller allowed PhD to conduct a Calibration, and Guide as inteneded. The hour angles and dec in the attached file my not be accurate, but calibrations were done in the vicinity of Rigel. 

Would really appreciate a tutorial on how to interpret the Guide Log and Debug log. Some seems self explanatory, but I'm sure I can learn a lot more. 

Thank you all for your valuable suggestions which have greatly expanded my knowledge of how the systems work and have helped me better use PhD2, and other software. 

https://openphdguiding.org/logs/dl/PHD2_logs_uJE8.zip

Very best regards, and again, Thank You.

Clear Skies to all

Ed 

FL USA

[Bryan]

Ed

On the homepage for https://openphdguiding.org/, there is a link to the existing tutorial on interpreting Logs, using the Log View app, which is also linked on the homepage at the bottom.

Bryan