Hi everyone,

I have a similar problem with my Hitecastro DC focus controller 2.
The idea is to use it with Kstars on a Mac but for some reason, although an INDI driver is installed for the Hitecastro it does’ seem to be able to connect.
Works fine manually. My motorfocusser is a JMI motofocus.
It seems to work fine with Backyard EOS and APT 3.5 (Asto Photography Tool) in Windows 8.1
I get the same result from the INDI server and INDI command center.

Please see attachments included.

Thanks a lot for any help.

Kind regards.

You can report issues here: github.com/A-j-K/hitecastrodcfocuser/issues

Okay, thanks I just did.

Greetz

Hi Jasem, Have you been able to do something about a driver for a Hitecastro DC focus controller 2 ?
Robert

I got the unit but I have to get a female cigarette plug first as I don't have one to power it up.

Yes, unfortunately that is a very unhappy choice of Hitecastro to provide only a cigarette adapter plug power supply.
I had to cut mine and adapt so I have both possibilities.

Hi Jasem. Any progress regarding the Hitecastro DC focuser 2? Can't say I'm not patient right.

I emailed David again to request communication protocol. On initial testing, it seems the focuser connects just fine, but I don't have any DC motors around to test it with the actual unit, but it's responding fine. I asked David to send me the communication protocol and waiting for response.

Have you had any response from David regarding the communication protocol? Meanwhile I tried to use Kstars for Windows but don't seem to be able to install my gear locally. Only remote installation is possible. ("Local" is greyed out).
Do I have to install any drivers. The ascom drivers for my gear I have but do I need indilibrary drivers and how do I install those? Thx.

I didn't get any response since mid-March.. will try to remind him again maybe he's busy.

Hi Jasem,

I contacted David and explained. He sent me and you in Bcc the command protocol for the focus controller.
Hope that helps.

I literally spent the whole day writing a completely new driver for this, but I still can't get any response from the controller. I emailed David to ask for more info and we'll see, but the driver is ready whenever this bit of communication issue is resolved.