Recently Browsing 0 members
No registered users viewing this page.
Can anyone identify which control box this is? Is it focusmaster? And does it run off robofocus driver in Indi lib as I cannot get a successful connection (in indi within ekos)
I bought a robofocus motor with this control box second hand.
I have faith with seller that hardware works as should.
I've tried other cables and USB ports too. The software (k stars) I use does do port search when connecting equipment..
Any help appreciated
So, I have a minor setup issue for my automation setup. Here is a brief overview of my setup:
Raspberrypi on the scope connected to a powered usb hub. Connected to the hub are a external wifi card (raspberry pi3 wifi is weak), an astromodified Canon 550D, a QHY5L-II for guiding and an EQ6 pro mount. The camera and QHY are connected to an OAG. The QHY5 is also connected to the mounts ST4 port.
On the Rasperry Pi 3 I am running xubuntu with INDI server and PHD2 installed. Using realvnc to view phd2. indi server + webserver starts on boot, static ip on external wifi card starts on boot.
On my laptop I have EKOS to connect to indi server and phd2 for guiding. I am running phd2 on the raspberrypi to hopefully this will let PHD2 have a more direct (faster) connection to the guide camera.
Their appears to be a disabled install of ufw which has some groups under iptables. I enabled the ufw and enbled the ports 4400, 7642 (PHD2), 8624 (indiweb), 7624(indi) however the guiding suite of Ekos would not connect to PHD2. I disabled ufw and flushed the iptables and tried again with the above ports however the same result. In the end I have opened all the ports to allow the connection to proceed, which is ok for short term but ideally I would want some security.
Does anyone know which ports I should open to get indi, indiweb and phd2 to talk nicely to my laptop EKOS version?
Anyone else running a similar setup successfully? Can you give me any indications of what pitfalls to avoid?
Imaging season is still a few weeks away up here, but I've started dusting of my gear and upgrading some parts.
One step closer to automation is a motor focuser, and I opted for a budget solution. I bought a SkyWatcher DC focuser and built a computer control for it. Since I use INDI for my automation, I had to find a way to connect the focuser to indiserver. A first thought was to use the INDIduino code, but after some coding and testing I found out that this code is very limited and not really supported by indi clients. The Ekos/Kstars focus module can't be used for focus control if you use INDIduino, apparently.
But then I stumbled upon an Arduino solution that emulates the MoonLite focuser (http://www.indilib.org/forum/general/283-moonlite-focuser-protocol.html). Unfortunately, this protocol is for a focuser with a stepper motor, whereas the SkyWatcher has a geared DC motor.
I had already rewritten some code from stepper to (geared) DC motor, so it was easy to adapt this to the MoonLite based code.
My solution consists of the following:
- SkyWatcher DC focuser (only the motor is used, the handbox is replaced by the Arduino)
- Arduino UNO
- Velleman motor controller shield for Arduino
- 9 V power adapter to power the shield
- Raspberry Pi
- Arduino sketch with Geared Motor library (see below for link)
- INDI server on RPi, and client (Ekos/Kstars) on Windows
I've tested this setup on my SkyWatcher Explorer 150PDS and it runs fine. Unfortunately I haven't been able to test the autofocus, due to absence of astrodarkness and clear skies.
Since a DC focuser has no knowledge about the position of the actual focuser, the software assumes that position '0' is all the way in. Maximum position is 25000 for my setup. By default, focus is increased by 100 steps, which is supposed to be 100 ms of motor drive.
BTW, the code is in my GitHub repository:
The 10Micron mounts extend the LX200 protocol which means that their basics can be controlled by anything that speaks LX200.
The Mount Command Protocol as 10Micron calls it is fully documented (I would not have bought this mount otherwise).
I've started a 10Micron INDI device driver to support the extensions, based off of LX200Generic so that it inherits basic LX200 functionality.
First thing that was added was TCP/IP support so that the mounts' ethernet port can be used for control and free up the mounts' serial port for a GPS unit at the same time.
This support was later moved up into the main INDI::Telescope class so that all INDI mounts that support it now can use ethernet ￼
On connect the driver sets Ultra Precision Mode (needed for model building later on and helpful with pointing).
It also retrieves basic properties like product name/control box type/firmware version.
Next Park and Unpark are supported.
Last pull request : https://github.com/indilib/indi/pull/167
- find out where J2000 needs translation to Jnow
- support pointing model building. Maybe by porting MountWizzard (python with ties to ASCOM and SGpro) ?
Who is interested in helping and/or has ideas on what needs to be implemented next ?
Curious about which CCD's you have been or are using successfully with auto guiding on a rpi2 or even a rpi3?
lin_guider seems to support a bunch of manufacturers but a list of what models are proven to work with the Raspberry pi's will surely help my quest!
Cheers for the help!