Gina
-
Posts
45,326 -
Joined
-
Last visited
-
Days Won
120
Content Type
Profiles
Forums
Gallery
Events
Blogs
Everything posted by Gina
-
Thanks Dave YIPPEE! It's working
-
Or maybe I'll take an afternoon nap...
-
Maybe I'll test the NEQ6...
-
Checked up and changed a couple of thing going by this site and rebooted. But still WiFi not seen by router
-
Though I'd try to get the WiFi set up until I'm ready to build the focuser but no joy - followed the instructions and rebooted. Ethernet connects fine and is shown in the router devices list but the WiFi isn't. Does it matter it the WiFi wlan0 static IP is the same as the wired eth0? Here are my network config files but with SSID replaced with s and password with p
-
A4988 driver module with sockets, placed on HAT. Needs soldering and links put in but I'll see what else I want to put on the board first.
-
I should have some too - another search coming up Wish I could get myself (and my stuff) organised
-
The RPi takes 600mA not driving anything so dropping 7v (12-5) will produce 7x0.6 = 4.2W - if you go analogue you'll need a decent heatsink. If you power other things off the RPi say by USB or GPIO, that will go up. Another idea recommended by Raspberry (I think) is to use a powered USB hub and run both RPi and camera etc. off that but an imaging camera needs to run directly off the RPi USB so I don't see how they make a USB hub work! I'm thinking of using a buck converter with enough current capability.
-
OTOH... I would like to get my main DSO imaging system changed over to Linux ASAP so I may spend some time on that. I have no problem with running two projects side by side though these are hardly two different projects. I can do some testing indoors - I have my NEQ6 mount indoors and could easily bring the camera rig in. Bea rung in mind that the EQ8 works exactly the same as the NEQ6 on EQMOD ASCOM I don't foresee any problems with INDI when I move the RPi setup out to the EQ8.
-
I think the first system I shall work on will be the all sky cam, then that project can be finished or at least working with RPi control and imaging. My ultimate aim for that comprises :- Capture sky image on ASI178MM and save data on client HD Control focus Turn dew heater on or off Measure temperature inside dome Measure ambient temperature outside dome The first three will get things going and make the ASC usable from Ekos. I think the RPi will handle 1-wire but not sure about an INDI driver. I use 1-wire DS18B20 digital thermometers for temperature measurement. I've been switching the dew heater with a power MOSFET from Arduino which has 5v logic levels whereas the RPI uses 3.3v. I shall need to check that the logic level MOSFETs I use work with the lower logic levels.
-
Looks like time to stoke up the soldering iron
-
Seems to have built and installed the four drivers correctly
-
make has now worked
-
Both those have installed - neither were present before.
-
Thanks Dave
-
Cuppa needed Back shortly...
-
Here's the contents of CMakeLists.txt :-
-
The astroberry - svn directory contains the source files for Astroberry. There would appear to be the .cpp & .h files for the four drivers viz. altimu, brd, focus and gps (in alphabetical order) plus associated .xml files which control the appearance of controls in Ekos. Files CMakeLists.txt, README, INSTALL, COPYING.LIB and directory cmake_modules.
-
OK -here we go again Nice bright new session with Putty - been having a look round the file system. My brain is not entirely error free this morning but working reasonably well Here we see the content of the libindi_1.2.0_rpi directory with the .deb files for the INDI drivers plus directories for astroberry - svn and indi - astroberry.
-
Thanks for that I may try the different library but OTOH I can't see that I shall ever want the function provided by that driver and probably prefer not to include it. But how far it's worth going to reduce the size of the overall package is debatable. However, I would like to understand how things work and maybe write my own drivers - this system is so powerful it seems a waste not to make good use of it Yes, CMakeLists.txt is one of the files I looked at - I plan to work out exactly how the compiler works
-
Ah yes - you're still using the full Raspbian. That could well be the difference.
-
I agree with that Dave I too don't understand why it worked for you and not me. I think I was well on the way to puzzling it out last night when I ran out of steam. I'm looking at the cmake system for compiling C++. I already understand how .cpp & .h files work. I'm beginning to understand the .xml files for interfacing with INDI and Ekos - these determine the controls that appear in Ekos. Seems a very flexible system and much better than the VB app I wrote to control my Arduino focuser. For my all sky cam, I only need a simple focus control as once set it shouldn't need touching. It's only needed in the first place because the dome shifts the focus a bit. OTOH I would like to switch a dew heater on/off. For DSO imaging I want preset differences for different filters and an auto-focus facility would be nice.
-
There is no reason why the accuracy should not be superb - you can use micro-stepping for greater accuracy. I currently use a 28BYJ-48 tiny stepper motor only half stepped and easily get focus well within a pixel on my ASI1600MM-C camera with 3.8micron pixels in a four-thirds sensor chip. These stepper motors can be modified for bipolar drive and can then use the A4988 micro-stepping controller with 16x micro-stepping giving 8x the resolution/accuracy I currently use. That's using an Arduino Nano but you can do just the same with an RPi. No, I don't think it is. The time scale involved in focussing is much slower than the microprocessor speed. The A4988 for example has direction bit (on/off) and micro-stepping (1x, 2x, 4x, 8x,16x) then a pulse sent to the STEP input moves the stepper motor by one step with that step size depending on the micro-stepping setting. Hope that makes sense
-
I've been looking for the source files in Astroberry but they seem well hidden. I think there are other drivers that control the GPIO interface. Could probably modify one of those.
-
I think I'm going to look into INDI driver writing because there are other things I want to do with the GPIO pins on the RPi and I want to control them from Ekos remotely. I know it's possible to write drivers including all the info for producing the controls in Ekos by specifying parameters in the driver. I just need to take it all in I'm learning all the time
