Ah, that would make sense. So if the DragNTrack bit is set, basic tracking would start at power up but still not interfere with the operation of, say, the Nexus DSC. Unfortunately, there might be

If the controller gets a command to move the mount from the serial port, it will drop out of dragNTrack mode. Dan

That is, indeed, the behavior I expected, but it does not seem to be what I'm observing. For example, I synced to Segin (epsilon cass) a few minutes ago. At my latitude, azimuth should be about 331

I put the controller in DragNTrack mode. I pointed towards celestial north pole, powered up, held ESC button on handpad until controller LED flashed. Then I navigated away from north and could hear

Thanks! When the weather is better I will make a video and a tracking log. Sadly the forecast says rain for many days. :-( Joerg

Apologies for the delay. Not too many clear skies this August! Thanks Don. Checked Lats & Longs in Sitech, SGP & TSX. All the same. I'm in the UK. Excellent pointer Dan. The Single Phot Init from

Thank you, Dan. I'll check the version and try slowing the slew. Jim

Hi Jim, Try lowering the slew speed. If it can't keep up (due to lack of gear mesh or lube), it could very well be jerky. Normally those mounts came with a servoII, you can look at the firmware

Joerg, A tracking log will be a good tool. You'll be able to see if it's servo position error for sure. Do you have a video camera, or a fast cmos camera? It would be really simple to make a video

Hi Mark, v3.9 is a servoI firmware version I think. I think you are using a fairly recent version because of one of your prior posts. In the numbers tab, the alt and az are the actual altitude and

There have been several mentions of the Sitech controlled Mathis mounts. I've sent these questions to Mathis, but I'm not sure anyone is home. I don't know of anywhere else to discuss this

Hi Jesse, Yes, that is an excellent point. Use the Tracking log to see the numbers showing the motion of scope while tracking a target. Don W

On Tue, Aug 10, 2021 at 12:31 PM, wrote: an issue with small star drift around the right star position.Assuming the issue ultimately isn't encoder resolution (or interpolation) have you collected log

Jesse, I tried a new PXP model but no difference to the old one. Joerg

In my version of SiTechExe (v3.9) "azimuth" is given both in the numbers tab and in the controller information window. However, it doesn't seem to be user configurable, either directly or by syncing

Hi Dan, Thanks for thinking about this off-the-beaten-path project. Choosing "offset init" rather than "cal star init" has no benefit, even when calibration points have been cleared. Also there is no

Dan, The diameter of azimuth disk is 1174.72mm, altitude is 1268.21mm. At round about D disk =1200mm, 1arcsec conforms to 2.9µm on tape. 1 sec tracking at sidereal rate conforms to 0.0436mm on

I just sent out a post, I'm going to duplicate it here. You need to make the motor directions strictly the following. 1. Point the counterweight to the west side. I call this "Looking West". Don't

On Tue, Aug 10, 2021 at 12:31 PM, wrote: The issue in "precise mode" or "cascade mode" can be switched off if "Track Only Sidereal (No PXP)" in Mount Parms has been activated.How old is your PXP

Don't use "Cal Star Init" unless you're going to make a model. Right click on the very large PointXP button, and clear out all of your calibration points. You should only use the Simple OFFSET init