Chris Shillito

The source for each release is included in the installer exe for that release. When you run the installer there is an option to install the source which will be placed in the Program Files(x86)/Common Files/ASCOM/Telescope/Source/EQMOD directory. Note that code is VB6 and uses a proprietary dll for low level comms to the mount. The source for that dll is not provided as it is not open source.

Thanks for the offer but given the nature/maturity of this project I see no need to move from sourceforge at this time.

Hi Charles, Some test releases were made only to the EQMOD group (now on groups.io was previously yahoo). I've just uploaded the latest test release (V2.13) to sourceforge so give that a go. Chris.

Hi Tony, The alignment lists provides correction for a whole load of different errors - some setup, some optical etc. Generally I would say that if you are totally dismantling the mount each session then you will need to do an new alignment. However one thing that might be worth a try is after loading the alignment list goto a star well away from the pole in RA and DEC and then slacken the clutches and manually bring the star into the centre of a reticule eyepiece/camera. For folks that have mounts...

This is something we have considered, discussed and tested in the past but sadly was found not to be practical. The issue is the wide range of slew speeds the mount can have move at and the relatively small amount of deflection on a joystick. Yes the software can detect small adjustments if the joystick but that doesnt' mean that the user will be capable of operating the stick with the precision that the softeare can read it. In practice we found it was just too easy to accidentally move the stick...

OK I understand. EQMOD has nothing to do with the way stellariumscope interacts with stellarium or the assignment of the ctrl keys. Stellarium doesn't support ascom at all so the way stellearium scope works is define three stellarium "telescopes" - each assigned to a ctrl key. When you hit the ctrl key stellarium initiaites a goto on the associated telescope. Stellariumscope is then able to intercept these goto commands coming out of stellariums tcp port and map them on to a few selected ASCOM commands...

As I've tried to explain EQMOD is not shitting itself down - it is being commanded to close by the client application you are using. Use a different client, such as the tooolbox application supplied with EQMOD, and you can happy open up EQMOD with the mount disconnected. So there really is no need for anything to change.

I've no plans to modify EQMOD to run as stand alone application - and to be honest I really don't see the need. Doing so would also invalidate it as an ASCOM compliant driver. However, if you really want to operate it that way then there is a way it can be "tricked" into launching. Take a look at the vbscripts that should have installed with EQMOD (should be listed off the widoows start menu). There should be a "start EQASCOM" script that uses a "back door" to mess with EQMOD's client count in order...