Ron,
There are a couple of things. When you do not have to calibrate when making the switch from ST4 to pulse guiding, perhaps it is because it is using a calibration from some previous time. There is a clear calibration button near the top (trash can?). Perhaps if you cleared that it would then need to recalibrate.

Rather than being able to switch modes between calibration and guiding it would be preferable to fix calibration using pulse guiding. Can you enable logging for the guiding and the AstroPhysics driver the next time you use pulse guiding to calibrate? And/or check the mount's indi panel for errors during calibration. For me it doesn't work and generates mount errors, it would be of interest to know if it is just me or you also encounter an error problem.
Tom

I was gonna shelve it until something is done... and move to my portable setup. However I can try again tonight to do as you requested.
YES I think if we could calibrate in pulse mode we'd probably be fine.
I'll give it a shot in a couple hours.

I'm wondering if this is a AP mount only issue with the experimental driver? or is it something in the calibration code? It would help if more people spoke up... because if I knew that other types of mounts were calibrating fine every time... then it would narrow it down to the experimental driver.

I don't think enough people own an Astrophysics mount to make comment. But a buddy of mine just got an 1100 that apparently the manufacturer recommends 100% correction 'aggressiveness' on guiding.

Ron Kramer (et al),
The Astrophysics Experimental driver is intended to be used with the newer GTOCP(X) mount controllers, specifically the GTOCP3 & GTOCP4 with version V or later firmware. If you have one of these controllers with the proper level of firmware then you should be using this driver to take advantage of some of the features in these newer controllers. That being said, it is still labeled experimental as it is felt that more testing is needed. I have used this driver on my AP900 with GTOCP3 controller quite successfully for many months. Michael Fulbright did a great deal of work implementing this driver. I worked with him and Jasem testing the driver over a period of weeks during the main development phase. There is a good deal of documentation for the AP mounts here:

www.indilib.org/devices/telescopes/astrophysics.html

I highly recommend you spend some time reading this information which will help in setting up and using your Astrophysics mount with INDI.

About guiding the mount please consider the following:
1. Astrophysics recommends using a guide rate of 1 for these mounts. This applies to using pulse guiding or the ST4 connection. This rate is set in the INDI control panel (see the documents linked above).
2. If using Pulse Guiding then make sure to turn on the "Use Pulse Cmd" in the Main Control tab of the AstroPhysics Experimental driver from the INDI Control Panel. Then you need to choose "AstroPhysics Experimental" in the via selection of the Guide Module in EKOS.
3. If using ST4 Guiding then make sure to turn off the "Use Pulse Cmd" in the Main Control tab of the AstroPhysics Experimental driver from the INDI Control Panel. Then you need to choose the CCD or CMOS camera in the via selection of the Guide Module in EKOS (For example - ZWO ASI178 or whatever camera you use for guiding) so the guiding will then be done from the ST4 port of the guide camera.
4. While using the Pulse Guide option further consideration need be given the pulse length as set up in the options (click the "Options ..." button on the lower right corner) in the Guide Module of EKOS. (Following is a simplified explanation) Any pulse length of 1000 (ms) or longer is handled with a different move command in the driver rather than the standard pulse command due to a limitation on the GTOCP3 controller. Michael had this working well and then had to fix this again in recent weeks due to a regression in the code. I have tested his recent fix and it seems to be working properly again.

I use a pulse length of 900 (the default unit is ms) and I usually only do 4 or 5 iterations and have found that this works well for the calibration of the mount while using either the ST4 connection or the Pulse Guide function. I have been using KStars/Ekos/INDI with my kit for 2+ years and in recent months run several all night "automated" imaging runs with good success. I understand the frustration of software bugs or user error in learning a new set of tools and encourage you to keep at it as I am sure it will come together for you.

That's quite a lot of useful information by 'LinuxUser' specifically that the driver is only suited for certain controllers, or firmware and specific toggles for st4/pulse guiding...

Anybody else feel that indi drivers should have an Info tab with developer notes for such key information?

Ron,
Comparing your good night to the bad ones, was the quality of "seeing" and the target/elevation similar.
The guide star you presented on the good night looks decent compared to the bloated one on the bad night.
Just wondering why the results with same balance/focus settings etc. are so different.

I'm out of it for a bit, just changing over to a heavy long focal length payload and waiting for some extra weights to arrive
to be able to balance.

Thanks - I had all correct, but I have over 1000 in this field. I'll set it to 900. Thank you - when it starts jumping across the sky - might be when it uses the other move motion. Can't wait to try it again.

Yes - conditions were close enough. The difference is - sometimes when I calibrate it goes jumping around instead of just nudging the star. The good night (the only one I had). it somehow skipped calibration and worked WELL.
The above msg points out that a <1000 needs to be entered for max pulse. I've had 1000-2000 and 5000 in there. He suggests 900. So that it my next test. If it can calibrate I should be golden.

I t can't hurt. But I already knew the settings/options just by seeing them in the driver. AP does say guiding rate is 1.00.
I knew about ST4 and Pulse and I was using it correctly. (I guess guessed, locially) but I never knew about the <1000 move. I'll set my max pulse to 900 and try again!
I have a newer Mach1 with GTO4 (their latest) with >V chip and latest firmware.

Ron,
No errors in your log/indi telescope panel when it goes bad?

Hope the 900ms setting helps but you should not be encountering that problem, Mike fixed it about 4 months ago.
indilib.org/forum/mounts/4280-astrophysi...l-pulse-guiding.html
/tom

I can include logs here. I tried last night at a max pulse of 900.
Same thing occured (small steps - then large jumps during calibration). I did later get it to calibrate, but guiding was mediocre and the guide star was often lost. (I have not focused the guide scope since I switched to it) I need to try that to see if it helps.

Anyone know the difference in the 2 axis calibration button? I suspect that means calibrate NS and EW (both directions) wouldn't we WANT TO DO THAT ALWAYS? - I turned it off and it did calibrate if I did iterations reduced to 3.

I turned it back on and it calibrated sometimes and later started jumping across the sky again. It seemed like 50/50 if a calibration would work or it would start jumping. When it did calibrate, guiding was pretty poor. (NOT ANYHING like that GREAT FLUKE guiding I had last week in previous post in here).

Trying some test subs. I couldn't get a usable sub in 180 seconds. Luckily I'm a nebula lover and nothing above my tree line this month. I suppose I could try PHD on the server again. = (

I'd give most anything to have guiding be like it was last week resulting in under .39 for over 2 hours straight. I'll check my balance, I'll swap the 290mm to the Lodestar, I'll fine focus the guide scope and see what becomes of that.

Ron, could you once more explain how you connect your mount to Ekos (cables, driver, etc) and what mount you have? That may give us a hint as to what's happening.

And perhaps you could list your imaging gear in your signature as most of us do so it is easy to see that.