|
Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
Ray Gralak
Hi David,
I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not worksOk, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the driver. It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written in .Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications, like TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread that the driver was created. If not, a cross-threaded operation might occur which will cause unexpected behavior. -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma -----Original Message-----
|
|
|
|
Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
David Attie <davattie@...>
I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not works from TheskyX and PHD2. I’m going to try the 5.10.01b
toggle quoted messageShow quoted text
|
|
|
|
Re: RA issues with the Ascom V2 5.10 driver
Ray Gralak
The latest version of the driver is 5.10.01b. If you are using that we will need to see a log file. If you are not using it you can get that version here:
toggle quoted messageShow quoted text
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.10.01b.exe If the problem still occurs you should use the AP Log Zipper utility to capture the logs and settings files for us to look at. Please include the exact time that you observed the problem and if possible, a screen shot. -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma
-----Original Message-----
|
|
|
|
Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
Ray Gralak
Hi David,
Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is stillThe driver's pulseguide code hasn't changed in a long time so I've created a test script to hopefully isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects to the mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec. At the end of the ten moves it reads the RA and Dec again and calculates the difference between the start and end. This should be non-zero if both RA and Dec moved. To run the test: 1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This will make it a vbscript file. It is in plain text so you can read it. 2. Make sure no other application is already connected to the mount through the driver. 3. Double-click the file ("it should be named AP-PulseGuideTest.vbs"). The driver should show and after about 10 seconds the message with the movements displayed. If the movements are "0" then use the AP Driver's log zipper program to capture the log and email it to me at GROUPS3 AT GRALAK DOT COM. http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-click it from file manager. -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma -----Original Message-----
|
|
|
|
Re: AP V2 ASCOM DRIVER AND ASTROTORTILLA
Joe Zeglinski
Hi Diego,
The “ADMINISTRATOR mode” gets changed in the
“application” either by the user installing it that way on purpose, or by some
unknown “installer” default. I used to set this mode myself, for a lot of
my VERY old (XP) programs that were carried forward into Win-10, thinking it
might be better or at least “safer”. That’s when the problems began.
So, right click on EVERY one of your astronomy apps –
either the program, or its icon. Then click on PROPERTIES choose the
COMPATIBILITY tab ... to see if the “RUN this program as an Administrator” box
has been check marked.
I finally did that for my PC apps. Things began to work more reliably when
all astro programs were singing from the same Security Mode song sheet.
If it is check marked - click on the box “Change
settings for ALL users” – and UNCHECK the Administrator option box THERE – so it
is covers all run possibilities ... for THAT program.
Repeat the process for every astronomy related program
icon – (and likely some others), but the astro apps are the current problem.
There are rare cases when ADMIN mode is actually needed to be set for a program,
and then perhaps only once in special circumstances – like AP’s CCDOPS needing
it, for just a “single” run, to permanently change the filter wheel names.
That would normally be considered a system security breach by Win-10, so it
demands that one-time option. Likewise some special uses of the Win-10 Command
Prompt program. . There may be a few others. But, I have found that the
vast majority of apps don’t need this. Also, some VERY old Win-ME or
Win-XP programs need the ADMIN setting, because they were written several
decades before there was such security as in Win-10, and thus (some) need it to
run now, if they can run at all.
The introduction of Win-10 really messed things up, with
Microsoft’s “security paranoia”. Things were so much better in XP and even
Win-7.
Hope this helps.
Joe
|
|
|
|
Re: RA issues with the Ascom V2 5.10 driver
David Attie <davattie@...>
Hi Olivier,
toggle quoted messageShow quoted text
The 5.10 is the first driver we have ever installed since we started with our AP900 recently. Everything works perfectly except guiding: the ASCOM pulseguiding doesn’t work (from theskyX and also from PHD2). We tried many older drivers but the problem remains. Only the native driver in theskyX supports pulseguiding so we have stopped using the ASCOM V2 driver. Are you saying that the 5.03 works with your setup? If so, where can I find it? George and Howard from AP spent time on our remote PC and couldn’t find a solution. Ray, are you around?? :-) Our setup: AP900 CP3, V1 chip Windows 10 theskyX pro , PHD2, focusmax, CCDautopilot David
|
|
|
|
RA issues with the Ascom V2 5.10 driver
OlivDeso
Hello, We are facing some problems with the latest Ascom 5.10 driver. Same functionning on 2 PCs and 3 mounts : PC win7/64, ascom V6.2 : upgraded from Ascom V2 driver 5.03 to 5.10 after having de-installed the 5.3 before installing the 5.10 Mounts : AP1100 (N°10 and 11) and one mach 1 -> they all have the CP3 and V chip symptoms: - the Ra field is empty in the Ascom V2 driver windows. The DEC field is correct - the cartography software ("cartes du ciel" does not shows the right RA position, the DEC seems correct) - when a goto is initiated between 2 "close" targets in the same constelation, the mount slew much more to the west (45 to 180°) then go back to the target, slewing to the east. If I press the stop button of the Hand controler while the mount is slewing to the west, it stops, then it goes back to the target after a couple of seconds. re-installing the 5.03 after hading re-installed the 5.10 solved the problem. Is this a known problem? Is there something to configure on the PC, or to clean. (registery data base of esle?) Any advice would be appreciated thanks Olivier
|
|
|
|
Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
David Attié <davattie@...>
Hello all, George and Howard from AP could access to my remote setup with teamviewer but they couldn't find a solution. It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10) when I started with my first AP mount recently. The pulseguing has never worked from TheSkyX or from PHD2. I know people who are struggling with this new driver and they had to get back to an older one (successfully). Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still impossible (even from PHD2 which is supposed to be independent of TheSkyX) So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with TheSkyX or PHD2. But this driver is limited and I really want to use the ASCOM V2. This is my current setup: Mount: AP900GTO CP3 Computer: shuttle DH110SE Operating system: windows 10 Software: theskyX pro ( camera add-on), PHD2, CCDautopilot. David
|
|
|
|
Re: AP V2 ASCOM DRIVER AND ASTROTORTILLA
Diego Gomez
Hi Ray, Thanks for your prompt response. I have checked and AT runs by default under Administrator mode (Not sure why and the rest of the software run normally. I am guessing the problem I am having is because that. I'll try to run AT normally to see what happens. If it doesn't work then I'll try to run the other software under Admi mode to see if that solves my problem. Again, thanks! Diego
On Saturday, September 30, 2017, 3:45:17 PM MDT, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
Hi Diego,
|
|
|
|
Re: AP V2 ASCOM DRIVER AND ASTROTORTILLA
Ray Gralak
Hi Diego,
toggle quoted messageShow quoted text
It sounds like some of the applications are running "as administrator" and some are not. Running "as administrator" means the application is running under a different user account (the administrator's), thus a separate instance of the driver can appear. So, all ASCOM clients need to be running normally (not "As administrator"), or all have to be running "as administrator", so that two instances of the driver won't try to access the single COM port. Best regards, -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma
-----Original Message-----
|
|
|
|
AP V2 ASCOM DRIVER AND ASTROTORTILLA
Diego Gomez
Hello All,
I am pretty sure this has been discussed in the past however, I couldn't find a final solution for the following problem: I own a brand new AP Mach1 GTO with CP4 controller which I acquired in March 2017 directly from AP. All my applications (ASCOM platform, PHD2, Astrotortilla, Backyard EOS are up to date). The AP V2 Ascom driver version I am using is v5.10.00. The problem I am having is that I can't connect Astrotortilla (V0.7) when the driver is already connected to PHD2 and/or Stellarium Scope. I am able to connect Astrotortilla is any of the software mentioned above are not connected but again when I try to connect them then it fails. I can see the AP V2 Ascom driver is connected and reading properly when connected to Stellarium Scope or PHD2 but when I open Astrotortilla and try to connect to the telescope (selecting AstroPhysics GTO V2 Mount) then it fails (a new windows of AP V2 Ascom software pop-up but with different values of what the current one is showing). Any idea what the problem could be? Thanks in advance, Diego Gomez
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Antoine PAVLIN
Sorry to jump in,
I loaded your image in PixInsight to restore a FITS 16bits format, then resolved it in TheSkyX (blind solve).
If TheSkyX did his job well, the image was taken in Cepheus at the limit of Cassiopea.
******** ASTROMETRIC SOLUTION RESULTS ******** Center RA (2000.0): 00h 03m 23.51s Center Dec (2000.0): +67° 16' 12.4" Scale: 0.91 arcseconds/pixel Size (pixels): 1433 x 1088 Angular Size: 0° 21' 50" x 0° 16' 34" Position Angle: 358° 09' from north through east Mirror Image: No RMS: 0.78 (X: 0.49 Y: 0.60) Number of Stars Used in Solution: 22 (100%) FWHM: 18.38 pixels, 16.80 arcseconds ***********************************************
...All Sky Image Link Succeeded. Found solution in Cepheus.
Your camera was almost parallel to RA axis (358°) so horizontal elongation in X direction of the stars is as you said along RA axis.
Measuring the length of the star trails by zooming in PixInsight, I get between 6 and 8 pixels depending on the star used. Assuming the right value is 7 pixels, you have a peak to peak RA move of about 3.6 arcsecs or +/-1.8 arcsecs.
This doesn’t seem to me excessive as for a 300s unguided exposure you will have taken a good share of one worm cycle of the Mach1GTO, so you can expect to see the peak to peak PE of your mount.
Of course you know your mount much better than I do, and only you can say if this represents a significant degradation of its performance.
Clear skies
Antoine
De : ap-gto@... [mailto:ap-gto@...]
Ray,
Respectfully, I do not feel you're giving my observations, findings, or posts the attention they are due.
Your time and efforts to this point are very much appreciated.
I will get in touch with the folks at AP next week as planned, and pursue this further with them.
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Bill Long
Ray is usually a pretty helpful guy, and seems to be quite engaged on this matter.
Have you discussed this with the folks on the PHD2 group? The guided results clearly show there is something awry when guiding, so that might be something to explore while folks are away at the conference?
From: ap-gto@... on behalf of eeyore@... [ap-gto]
Sent: Saturday, September 30, 2017 5:51 AM To: ap-gto@... Subject: [ap-gto] Re: Mach1 GTO has just started showing terrible RA performance Ray,
Respectfully, I do not feel you're giving my observations, findings, or posts the attention they are due.
Your time and efforts to this point are very much appreciated.
I will get in touch with the folks at AP next week as planned, and pursue this further with them.
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Ray Gralak
Respectfully, I do not feel you're giving my observations, findings, or posts the attention they are due.I've been trying to take an objective approach. I've been imaging for over 20 years, and some seasons seeing has been terrible and others great. Just because you started getting lesser imaging results doesn't necessarily mean it's the mount's fault, although you seem to be intent on excluding any other reasons! This is what you wrote earlier: The P2P error is considerably more than AP's stated "7 arc seconds (+/- 3.5 arc sec.)What I've been focusing on is your claim for PE being considerably more than 7 arc-secs and capturing the random RA jumps that you have seen. To prevent confusing a dither for a random jump, I asked for unguided data. It's a reasonable request, I think!! You did provide a log with hours of guided data, so I expected to get an unguided segment longer than 1-2 cycles. 1-2 cycles of data is not good enough. What I would like to see is 5-6 worm cycles unguided. If you have that please identify the segment in its respective log file (I am attending AIC, so my time is limited). That said, I've looked at thousands of log files over the last 15 years and I am familiar with the effects that seeing and tube currents can have. Now maybe it's not tube currents or seeing in this case, but if you are going to claim P2P error is more than 7 arc-seconds, please provide longer duration log files. The longer the duration the finer the frequency resolution and amplitude calculations will be. For a PE measurement, A-P will probably ask you to collect 5-6 worm cycles unguided as well, because that is what I recommend. I recommend that because I know that's usually enough for PEMPro to get a reasonably accurate PE calculation. However, if you would rather just talk with A-P next week that is fine with me. Best regards, -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma -----Original Message-----
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Gordon Boulton
Ray, Respectfully, I do not feel you're giving my observations, findings, or posts the attention they are due. Your time and efforts to this point are very much appreciated. I will get in touch with the folks at AP next week as planned, and pursue this further with them.
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Ray Gralak
Ok, I found another much shorter segment which range +/2 arc-secs, or about 2 pixels. That looks normal to me. It could be local seeing or even tube currents.
toggle quoted messageShow quoted text
-Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma
-----Original Message-----
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Ray Gralak
I sent you the log file via email, and also linked it in an earlier message, Ray. :)That's the one I was looking at. To me it looks like your log has more Dec excursions than RA excursions in the segment starting at 20:39:44. But, as I said, I need one with NO autoguiding. Thanks, -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma -----Original Message-----
|
|
|
|
Re: ap1100 absolute encoder swap
dave@...
Roland, Howard, George. Anyone want to answer my question?
Dave
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Gordon Boulton
For reference, as a comparison to the above linked 900s unguided image from January.
A 300s unguided image from tonight : https://i.imgur.com/7ZF8Qrq.png
|
|
|
|
Re: Mach1 GTO has just started showing terrible RA performance
Gordon Boulton
Don't believe so. The unguided runs don't involve a USB cable of any sort, save for the USB-Serial connection for the ASCOM driver.
Were we to address the USB cable to the guide camera, then the issue should be apparent in both axes, and as these videos make clear, it is not.
|
|
|
