tekkydave

Success here too - as far as the scope is concerned anyway. I started the indi server on the pi (called indiserver too btw) - ip address is 192.168.1.95 indiserver -m 100 -vv indi_celestron_gps indi_simulator_ccd For some reason KStars/Ekos wont connect unless you have a CCD driver running so I used the simulator. Then I entered the indiserver details, scope and ccd details in Ekos via KStars Click on Options, select Indi. Put in the server and port details for the scope. I have it on a USB to Serial adapter connected to the base of the hand controller. Select Ekos. Enter remote server ip again Press OK Back in Ekos-KStart dialog press Connect And Hey Presto. The mount is tracking correctly and I can slew to a selected object easily. Click on Control Panel and you can see the devices and modify properties, control them etc Phew - glad that bit all works

I'm going to test my Nexstar mount this morning - that's the plan anyway.

It installs ok but just wont run with indiserver. Are you able to start the indiserver and specify indy_rpifocus as a driver?

Strange, it didn't get installed when I installed Indilib. I wonder if there is a way to list the installed drivers.

Tried connecting the A4988 to the RPi but as you say, there is no feedback. I thought maybe it would detect if a line was pulled high/low and take that as a device was connected. Had enough for today. I think I'll get it working with my mount first as the celestron driver seems to start up ok pi@indiserver:~ $ indiserver -v indi_celestron_gps 2016-10-04T15:25:29: startup: indiserver -v indi_celestron_gps 2016-10-04T15:25:29: Driver indi_celestron_gps: pid=1643 rfd=3 wfd=6 efd=7 2016-10-04T15:25:29: listening to port 7624 on fd 4 2016-10-04T15:25:29: Driver indi_celestron_gps: snooping on GPS Simulator.GEOGRAPHIC_COORD 2016-10-04T15:25:29: Driver indi_celestron_gps: snooping on GPS Simulator.TIME_UTC

I'm wondering if it's because the driver cant detect any physical hardware connected yet. Ill try connecting up the A4988 and see if that makes it work.

Thanks for that. I've got raspbian and Indi installed but no luck with the Astroberry drivers. After installing the .deb package and running: indiserver -v indi_rpifocus I get: 2016-10-04T14:19:10: startup: indiserver -v indi_rpifocus 2016-10-04T14:19:10: Driver indi_rpifocus: pid=793 rfd=3 wfd=6 efd=7 2016-10-04T14:19:10: listening to port 7624 on fd 4 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #1 2016-10-04T14:19:10: Driver indi_rpifocus: pid=794 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #2 2016-10-04T14:19:10: Driver indi_rpifocus: pid=795 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #3 2016-10-04T14:19:10: Driver indi_rpifocus: pid=796 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #4 2016-10-04T14:19:10: Driver indi_rpifocus: pid=797 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #5 2016-10-04T14:19:10: Driver indi_rpifocus: pid=798 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #6 2016-10-04T14:19:10: Driver indi_rpifocus: pid=799 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #7 2016-10-04T14:19:10: Driver indi_rpifocus: pid=800 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #8 2016-10-04T14:19:10: Driver indi_rpifocus: pid=801 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #9 2016-10-04T14:19:10: Driver indi_rpifocus: pid=802 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: restart #10 2016-10-04T14:19:10: Driver indi_rpifocus: pid=803 rfd=0 wfd=6 efd=7 2016-10-04T14:19:10: Driver indi_rpifocus: stderr EOF 2016-10-04T14:19:10: Driver indi_rpifocus: Terminated after #10 restarts. 2016-10-04T14:19:10: good bye

The RPi3 has arrived Just writing the micro-sd with raspbian.

Amazon say RPi3 is coming today so I'll hold off and install Indi etc from scratch.

Good point. My supply will be 12V too so looks like we are stuck with A4988's. I think I will download the Astroberry distro today and test on an RPi B.

It might be better to go for the DRV8834 as the Astroberry focuser is designed for it.

Some pics of the modded stepper connected to an A4988 Pololu driver. I used an arduino uno for testing but it will be directly conneted to the RPi's GPIO pins eventually. As you can see I made a bit of a mess of the very tiny tabs on the casing. I added some solder after reassembly to keep the case together.

Slight error in the previous post - I won't need my existing focuser sketch as the A4988 will be controlled directly by the Pi. No arduino involved.

Inspired, as usual by Gina's exploits with a Raspberry Pi and Indi I decided to have a go myself. I have ordered an RPi 3 and await arrival. In the meantime I decided to modify a cheap 28BYJ-48 stepper motor for bipolar operation following Gina's instructions. Then I tested the motor with a Pololu A4988 stepper driver I had left over from my 3D printer build using details I found here and it worked first time. I needed a 12V supply to drive the 5V motor as now the windings are being used in series. Once the Pi arrives I will be installing Raspbian, Indi and connecting up to my Nexstar 127 SLT and then building a new focuser using my existing sketch and the motor I modded today.

I wish I had your clear sky here. I looked out at 11pm last night and could only see a few stars despite zero cloud.

Hi Terry. My sketch wont work with the easydriver but I believe someone did create a version. I cant remember who it was.

Hi, glad you are finding it useful

Glad to help

The driver is definitely set up to be Absolute. The focuser remembers the last position it was set to between uses. If it has got too high for sgpro then set it back to a sensible value in the driver chooser dialog. PS - lashing down here too

The protocol between the Ascom driver and my focuser is one I made up. I couldn't locate one at the time so just made one up . The Ascom driver is hardcoded to that protocol. Details at https://sourceforge.net/p/arduinoascomfocuser/wiki/Communications Protocol/ The nano could easily be reprogrammed to use a different protocol if you know what the desired Ascom driver uses.

The focuser will need an Indi driver that can talk to the arduino using my protocol.

Hi, no reason why it shouldn't work as its a standard Ascom interface. Are you definitely using my focuser and not the SGL one - there has been some confusion in the past. Also, the application that come with my focuser (FocusAAF2) is not a fully functional and finshed product. I wrote it for testing and to show how the Ascom driver is called. Can you get more details of the error message? Is anyone else using my focusser with sgpro? Thanks.

The ESP8266 board arrived yesterday. I've set up the Arduino IDE to be able to compile and upload to the board using instructions here http://www.arduinesp.com/getting-started

I have tested the latest version of the AAF2 sketch and it looks ok to me. I have created a new release on the SF site at: https://sourceforge.net/projects/arduinoascomfocuser/files/Mark2/Software/V2.5.0/ Note that only the Arduino sketch AAF2.ino has changed. Here is the relevant part from the readme.txt: Changes in Version 2.5.0 This version integrates a HC05 Bluetooth module. This provides remote connection via Bluetooth and therefore the focuser does not need a permanent USB cable attached. Only the Arduino sketch has been changed. This sketch is backward compatible with the current Ascom driver and is supplied with the Bluetooth option turned OFF. To enable it uncomment the line //#define BLUETOOTH_COMMS // Use Bluetooth Comms - if commented out defaults to USB Serial Port in the sketch prior to uploading. You will need to connect your HC05 as per the updated diagram, AAF2_V2.5.0_crop.png in the Files area. If you use different pins on your Arduino then update the following lines in the sketch accordingly: #define BTSERIAL_PWR_PIN 2 // Bluetooth serial Power Pin #define BTSERIAL_MODE_PIN 3 // Bluetooth serial Mode Pin #define BTSERIAL_RX_PIN 4 // Bluetooth serial RX Pin #define BTSERIAL_TX_PIN 5 // Bluetooth serial TX Pin The HC05 is configured automatically by the Arduino at start-up. This assumes it is already set to the slave mode which it will be by default. The default device name and password are set to 'Focuser' and '9999' but can be changed by amending these lines: const String BT_NAME = "Focuser"; // Bluetooth Device Name const String BT_PWD = "9999"; // Bluetooth Device Password (Pairing Code) As ever let me know if you encounter any issues with the new release or connecting up your HC05. Here is the updated schematic. The 2N3906 is a general purpose PNP transistor and any equivalent device will do. This of course assumes you have a Bluetooth capability in your laptop or PC. If not a USB Bluetooth dongle should work.

I dont have a definite plan for the final look of the wireless focuser, just trying different things at the moment. I dont intend to use it away from base and if I use wifi it will have its own dedicated AP to connect to.