Removing the ASCOM driver - not working?

Issue #34 resolved
Tony Benjamin created an issue

I tried removing the ASOM driver/Firmware (as I could not get it to connect to the dome in POTH). I reinstalled the old - original - driver/firmware that I had been using successfully for the past couple of years with SGP (Sequence Generator Pro) to control the dome.

But I cannot get the new driver from showing up in SGP - even though I have removed it in “Add/Remove” programs? Only yours shows up in the drop down list? How do I remove it?

Comments (8)

  1. Tim Long

    It’s possible that the uninstaller doesn’t remove the ASCOM profile correctly. I presume you get an error message if you actually try to load the driver at that point?

  2. Tim Long

    By the way, there is not really any reason to use POTH with this driver, as it has its own built-in hub. Unless of course you are relying on POTH’s dome synchronization (I don’t know whether SGP has built-in dome-sync, but if it does then I would use that rather than POTH).

  3. Tony Benjamin reporter

    Hi Tim,

    So how should I be using this driver/firmware? Can I just try it with any ASCOM compliant software - such as Voyageur?

  4. Tim Long

    @Tony Benjamin I’m not familiar with that app, but any program that is ASCOM-compatible and can control a dome should work with it. In theory, that list should include POTH so I’m a bit surprised to discover that’s not the case, and that’s why I’d like to investigate this further. The driver can accept connections from multiple clients and - as long as the clients don’t issue contradictory instructions - then that should work just fine. So for example, if one client is trying to open the shutter and the other is trying to close it, then you have contention and one of them has to win. The way the driver is written, the first one to issue its command will win and the other will be ignored.

  5. Log in to comment