tekkydave
-
Posts
1,798 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Blogs
Everything posted by tekkydave
-
Yes I knew that
-
Someone with a scope needs to monitor the M0 & M1 pins to see if they are being used.
-
Video of focuser in action https://www.dropbox.com/s/7llsjhvfdzbb3eh/2016-10-13 15.30.59.mp4?dl=0
-
Correct, but it is only ever called internally by the init routine on the first line. It's possible the routine could be called externally by Ekos I suppose.
-
Spent the afternoon building the HAT.
-
I've just done a quick text search through the Astroberry source code and the speed isn't set to anything other than 1:1 stepping. pi@indiserver:~/software/astroberry-svn $ grep -r "SetSpeed" * rpi_focus.cpp: SetSpeed(1); rpi_focus.cpp:bool FocusRpi::SetSpeed(int speed) rpi_focus.h: virtual bool SetSpeed(int speed);
-
I've been monitoring the state of the GPIO lines that are supposed to feed M0 & M1 and they don't seem to change state during auto-focus (permanent low). That is unless they are doing it so fast I cant see it using an LED or DVM. I don't have an oscilloscope so can't monitor them with any accuracy.
-
I've been upgrading my desktop PC to Ubuntu 16.04 for the last couple of days and reinstalling everything I need. It now enables me to install the latest version of KStars/Ekos and it is much improved. Basic installation is 1. Install Repository and update package lists sudo apt-add-repository ppa:mutlaqja/ppa sudo apt-get update 2. Install Indi Library and all 3rd party drivers sudo apt-get install indi-full 3. Install Ekos & KStars sudo apt-get install kstars-bleeding 4. Start KStars and select Ekos from the Tools menu 5. Setup a new Profile by clicking on the plus sign next to the Profile drop-down. 6. Add your devices Make sure you enter the correct IP address of your Indi server (in my case it's the RPi3) Note that you cant add the Astroberry Focuser here for some reason but if you have it running on your Indi server it will show up in the next steps. Click Save. 7. Ensure the Indi Server is running on the remote device (RPi) indiserver -m 100 -vv indi_celestron_gps indi_simulator_ccd indi_rpifocus 8. Connect to the remote Indi Server Back in Ekos hit 'Start Indi' then 'Connect'. The Indi Control Panel should appear. This allows you to control the settings of your devices. Also you will get extra tabs appearing in Ekos to control your devices. I tried the auto-focus and it takes a simulated CCD picture (I have no camera attached at the moment) then moves the focuser around until it is in focus. All looking good so far. I need to get the stepper controller off the breadboard and onto the RPi HAT but I need to have a play with the M0 & M1 signals first to see the best way of connecting them. The other possibility is to modify the Astroberry driver to use 3 GPIO lines to control the MS1,2,3 lines correctly on the A4988. This could be a temporary work-round until I create my own driver, or I could even feed it back to the driver writer as a possible enhancement.
-
In the Homehub you can force a device to always pick up the same ip address. That is if you have not already forced it to have a static ip and are relying on dhcp from the Homehub. It's useful if you have no way of setting the ip on the device itself and want a fixed address.
-
I wish I could do that with the Celestron Nexstar mount but you have to keep the HC connected. The serial interface is in the base of the HC. Fortunately I have the StarSense accessory and GPS so a few buttons to press and it aligns itself in a few minutes. After that the operation will be remote via KStars/Ekos.
-
Your ip addresses must be different.
-
Yes, I think you're right there. I tried it before and it got fairly hot. I have a few spare buck converters in stock.
-
These sockets I bought arrived yesterday and fit the Pololu pins perfectly.
-
I'm just waiting for the RPi prototyping board to arrive so I can start building the hardware (I don't have Amazon Prime). It will contain: Pololu driver in a socket 12V to 5V regulator to power the Pi * Sockets / terminals for incoming power (12V) & motor connections. Anything else I think of that might be useful * If a linear power regulator gets too hot doing 12V -> 5V I might just leave that separate and have a 5V feed from a buck converter or something.
-
I have booted up my indiserver pi to see if the drivers are there. Looks like they are: pi@indiserver:~ $ sudo apt-get install librtimulib7 librtimulib-dev Reading package lists... Done Building dependency tree Reading state information... Done librtimulib-dev is already the newest version. librtimulib-dev set to manually installed. librtimulib7 is already the newest version. librtimulib7 set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. According to this page librtimulib-dev is installed in raspbian by default. The packages that end '-dev' are required for development. Once you install them your Astroberry should compile. (He said confidently )
-
I suspect the libs are already present in the full raspbian install. I have checked my weather station and they are already installed. That may be why I didnt get the error.
-
There is also an astroberrry-piface driver for indi that interfaces to various piface hats. I have one of these with 8 I/O lines and switches plus 2 lv relays.
-
See my edit in previous post
-
Looks like the CMakeLists.txt file is the main driving file. Not sure but commenting out sections in here may exclude them from the build. It would be better to install correct library. From googling it might be sudo apt-get install librtimulib7 librtimulib-dev
-
The source is in the .cpp files and the .h headers. I think to control what gets compiled we need to modify the cmake files. I'm not familiar with cmake, only the older make utility. I'll take a look later. I'm curious as to why I didn't get the error you get.
-
You are missing a library. Not sure how to get it. My install didn't fail on this. I think it's mentioned in the INSTALL file in the astroberry directory.
-
Sorry for terse replies Im on phone browser with tiny keyboard.
-
You are in root dir too cd To get to yr home dir
-
I think u have d'loaded web page not file.
-
Off to work now.
