Where do I find an ASCOM driver for a Moonlight Mini v2

[g__day]

Hi all,


I am still trying to set up my new ASTRO lab PC under Windows 10. I am looking with little success for a ASCOM driver for a Moonlight focuser controlled by their Mini V2 controller.


For my old astrolab PC under ASCOM Moonlight focuser I used to see


Moonlite Focuser .NET
Moonlite Focuser

Moonlite Focuser DRO


I can find the first and the third driver on Moonlite's website - but the second driver in that list - which is the one I think I need - I can't find.


Can anyone steer me in the right direction?

Thanks,


Matt

[The_bluester]

I believe the DRO ASCOM driver on their website is the "Everything" driver.

[Drac0]

As Paul says, the DRO driver is an "all-in-one" ASTAP driver - "Our one driver works with all controllers and focuser configurations, Single port, Dual port, and Rotator."

What exactly is the problem you're having?


Cheers,
Mark

[g__day]

The DRO driver I thought I read wasn't for the Mini v2 - just the DRO series plus I say a Moonlite Mini V2 driver on TSX.

Turns out the DRO should be the detect and manage all Moonlite controllers apart from NiteCrawler - as you advised - thank you.


The TSX driver is a non ASCOM direct driver for Mini V2 that Software Bisque created by themsleves!

Thanks all!

[g__day]

FYI...

The Moonlight universal DRO driver - didn't detect any Moonlight gear - it was a complete bust under The SkyX, APT v4.20 and Sequence Generator Pro. But luckily the .NET version worked perfectly! I will report this back to the Moonlight team - I wonder what is going on there?

Matthew

[Drac0]

So much for it being their 'all-in-one' solution...

[g__day]

No there quality of gear is excellent - I think it comes down to my user error in my testing methodology!

You see I connect all my gear through about 4 separate powered USB 3 hubs on my pier which are connected in turn to two separate power boards - I reckon power to one of the hubs that the Moonlite controller was attached too wasn't receiving power - so if this is true it was all my fault.

Once power was supplied DRO driver spotted the focuser straight away! So if this hypothesis is correct - well either the .NET driver is more forgiving for when power is not supplied to the hub - or it was purely my testing methodology - I powered something between tests and didn't realise that would change diagnostics.

So all good now!

[Drac0]

Never doubted the hardware, just the software...but maybe not even that now. :P


That's a lot of hubs leaving plenty of places where 'something' could go wrong.


Hope it all keeps going for you.

Cheers,
Mark

[g__day]

Multiple hubs allows coupled to APT's USB monitor means if it shows that someting I expect isn't connected - then I can swap it from one hub to another and if reappears I know I have a localised hub issue!