Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

Gina

Beyond the Event Horizon
  • Posts

    45,326
  • Joined

  • Last visited

  • Days Won

    120

Blog Comments posted by Gina

  1. I thought just copying the astroberry-diy directory and all its contents from the working card to the new one would work but something was wrong with the bcm2835 library.  Maybe I should just clone the card and leave it at that.  I've found I can change the network name so that I can use both old and new at the same time.  That would give me a second imaging rig.  I'm rather surprised that just copying all the Astroberry files across and recompiling didn't work.  Must be something in the rest of the system - different version of something perhaps.

  2. I can see the problem with catering for different operating systems and a variety of SBCs and all the permutations that result.  ATM I am only interested in RPi 3 B and RPi 3 B+ though sometime in the future I can see wanting the RPi 4 to cater for faster imaging.

    With wiringPi apparently broken I think my best option will be to take working versions from RPi 3 B and B+ and copy files to the new micro SD cards.

  3. 1 hour ago, JamesF said:

    I think that means that you're not going to get anywhere unless you download the wiringpi source and build it yourself.  The existing one appears to contain references to functions in an incompatible release of glibc.

    You may be able to ignore all of the other errors, which are only warnings anyhow, though it may be helpful if at least some of them are fixed.

    James

    But where are the source files for wiringPi?

  4. Hmmm...  Fixed the wiringPi error but getting others.

    gina@img2:~/astroberry-diy/build$ cmake -DCMAKE_INSTALL_PREFIX=/usr ..
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /home/gina/astroberry-diy/build
    gina@img2:~/astroberry-diy/build$ make
    [ 25%] Building CXX object CMakeFiles/indi_rpifocus.dir/rpi_focus.o
    /home/gina/astroberry-diy/rpi_focus.cpp: In member function ‘virtual IPState FocusRpi::MoveFocuser(INDI::FocuserInterface::FocusDirection, int, int)’:
    /home/gina/astroberry-diy/rpi_focus.cpp:488:55: warning: unused parameter ‘speed’ [-Wunused-parameter]
     IPState FocusRpi::MoveFocuser(FocusDirection dir, int speed, int duration)
                                                           ^~~~~
    /home/gina/astroberry-diy/rpi_focus.cpp: In member function ‘virtual IPState FocusRpi::MoveAbsFocuser(int)’:
    /home/gina/astroberry-diy/rpi_focus.cpp:581:21: warning: comparison with string literal results in unspecified behavior [-Waddress]
       if ( direction == "INWARD" )
                         ^~~~~~~~
    /home/gina/astroberry-diy/rpi_focus.cpp:585:21: warning: comparison with string literal results in unspecified behavior [-Waddress]
       if ( direction == "OUTWARD" )
                         ^~~~~~~~~
    /home/gina/astroberry-diy/rpi_focus.cpp: In member function ‘virtual int FocusRpi::regPosition(int)’:
    /home/gina/astroberry-diy/rpi_focus.cpp:757:5: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation]
         else
         ^~~~
    /home/gina/astroberry-diy/rpi_focus.cpp:761:2: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’
      if (pos == -1)
      ^~
    /home/gina/astroberry-diy/rpi_focus.cpp:770:9: warning: ignoring return value of ‘char* fgets(char*, int, FILE*)’, declared with attribute warn_unused_result [-Wunused-result]
       fgets (buf , 100, pFile);
       ~~~~~~^~~~~~~~~~~~~~~~~~
    [ 50%] Linking CXX executable indi_rpifocus
    /usr/lib/gcc/arm-linux-gnueabihf/7/../../../../lib/libwiringPi.so: undefined reference to `fcntl@GLIBC_2.28'
    collect2: error: ld returned 1 exit status
    CMakeFiles/indi_rpifocus.dir/build.make:96: recipe for target 'indi_rpifocus' failed
    make[2]: *** [indi_rpifocus] Error 1
    CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/indi_rpifocus.dir/all' failed
    make[1]: *** [CMakeFiles/indi_rpifocus.dir/all] Error 2
    Makefile:129: recipe for target 'all' failed
    make: *** [all] Error 2
    gina@img2:~/astroberry-diy/build$ 

     

  5. Connected human interface devices and ran the RPi in GUI mode.  Having removed to old wiringPi I downloaded and installed the new one from https://project-downloads.drogon.net/wiringpi-latest.deb.  The library appeared to install fine.  Next I closed down, powered up and accessed via SSH from the desktop.  I deleted the astroberry-diy directory and all it's contents to give me a clean start then entered these commands one at a time

    git clone https://github.com/rkaczorek/astroberry-diy.git
    cd astroberry-diy
    mkdir build && cd build
    cmake -DCMAKE_INSTALL_PREFIX=/usr ..
    make

    I thought it would work now but it still failed as before.

    gina@img2:~/astroberry-diy/build$ make
    Scanning dependencies of target indi_rpifocus
    [ 25%] Building CXX object CMakeFiles/indi_rpifocus.dir/rpi_focus.o
    /home/gina/astroberry-diy/rpi_focus.cpp:26:10: fatal error: wiringPi.h: No such file or directory
     #include <wiringPi.h>
              ^~~~~~~~~~~~
    compilation terminated.
    CMakeFiles/indi_rpifocus.dir/build.make:62: recipe for target 'CMakeFiles/indi_rpifocus.dir/rpi_focus.o' failed
    make[2]: *** [CMakeFiles/indi_rpifocus.dir/rpi_focus.o] Error 1
    CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/indi_rpifocus.dir/all' failed
    make[1]: *** [CMakeFiles/indi_rpifocus.dir/all] Error 2
    Makefile:129: recipe for target 'all' failed
    make: *** [all] Error 2
    gina@img2:~/astroberry-diy/build$ 

     

  6. Gordon's wiringPi git is still unavailable

    Quote

    git.drogon.net is temporarily unavailable. Please look for alternatives for wiringPi, etc. -Gordon

    so I shall have to resort to the bcm2835 setup as use in earlier versions of Astroberry as I have no idea when it will be available again.  I need to edit the C++ code for my ROR control but I was hoping to use the Astroberry code unaltered for the focuser for my second imager.  Oh well, these things are sent to try us!!

  7. Since the problem is with wiringPi I could probably get round this problem by using an earlier version of the Astroberry files - I have copies.  I'll look into that later.  Meanwhile, I'm wondering why the change to wiringPi, may be a good reason...  Mind you I've had the earlier versions running without any problem for a few years.  I shall be interested in your views @RadekK.

  8. Oh dear!!  Just tried this with my second imaging rig RPi and get this on running make :-

    gina@img2:~/astroberry-diy/build$ make
    Scanning dependencies of target indi_rpifocus
    [ 25%] Building CXX object CMakeFiles/indi_rpifocus.dir/rpi_focus.o
    /home/gina/astroberry-diy/rpi_focus.cpp:26:10: fatal error: wiringPi.h: No such file or directory
     #include <wiringPi.h>
              ^~~~~~~~~~~~
    compilation terminated.
    CMakeFiles/indi_rpifocus.dir/build.make:62: recipe for target 'CMakeFiles/indi_rpifocus.dir/rpi_focus.o' failed
    make[2]: *** [CMakeFiles/indi_rpifocus.dir/rpi_focus.o] Error 1
    CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/indi_rpifocus.dir/all' failed
    make[1]: *** [CMakeFiles/indi_rpifocus.dir/all] Error 2
    Makefile:129: recipe for target 'all' failed
    make: *** [all] Error 2

    From running the command that includes installing wiring.pi I get

    wiringpi is already the newest version (2.50-1ubuntu1).

    @RadekK can you help, please?

    I should add that I ran the following commands, one at a time.

    sudo apt-get install cmake indi-full libindi-dev wiringpi
    git clone https://github.com/rkaczorek/astroberry-diy.git
    cd astroberry-diy
    mkdir build && cd build
    cmake -DCMAKE_INSTALL_PREFIX=/usr ..
    make

     

  9. I shall describe installing the Astroberry drivers.  The package contains drivers for a Focuser and Relay Board.  The focuser provides remote focussing for telescopes and camera lenses that is used from Ekos in KStars for remote focussing and even auto-focus.  This works in conjunction with hardware attached to the RPi to control a stepper motor. 

    The Board driver is designed to control 4 relays for whatever purpose may be required.

  10. Unfortunately, I have to report that I have not managed to get this working ATM with a Raspberry Pi 3B.  When trying to connect to the RPi over WiFi using SSH I get

    Connection reset by 192.168.1.234 port 22

    I have tried the procedure to produce a working RPi system twice and get the same result.

    EDIT :-  A search has revealed a suggestion to cure this which I shall try.  Means running the RPi with human interfaces and entering in Mate Terminal

    sudo rm /etc/ssh/ssh_host_* && sudo dpkg-reconfigure openssh-server

    Later...  the rm (remove) command reported

    rm: cannot remove '/etc/ssh/ssh_host_*': No such file or directory

    so I just used

    sudo dpkg-reconfigure openssh-server

    which worked.  Now to come out of the RPi and see if SSH works.

    Edit...  Yep.  Can now log in to the RPi via SSH.

  11. Installing the Operating System and Astro software

    The Raspberry Pi uses a micro SD card as its main drive and this behaves the same as the hard drive on a computer except that this card can be removed and data read from it or written to it.  In fact the way the operating system is installed on it requires it to be out of the RPi.  This tutorial will describe how the operating system is written to the card, the system set up with computer name, user name and password and then further software installed to permit remote control via LAN and the astro software to capture images and control the hardware such as filter wheel and mount.  You need an SD card reader attached to your main computer.

    First job is to download the operating system on the main computer and write it to the micro SD card. Go to the Ubuntu MATE download page,  choose the appropriate Raspberry Pi version of Ubuntu MATE 18.04 (takes two clicks) and download it.

    For Linux I recommend Etcher which works well (my main PC uses Linux Mint).  Etcher unpacks and writes the OS to the card in one go.  Plug card into reader (with adapter if required), run Etcher and select the micro SD card - careful here not to select you HD or other device.  Also select the downloaded file.  Set Etcher going and a few minutes later the OS is written to the card.  After writing to the card Etcher checks the written data is correct.

    With Windows you have unzip the downloaded file and write the image to the micro SD card.  IThis can be done with Win32 Disk Imager.  Chose the image file (.img) and SD card in Imager and follow the onscreen instructions to write the OS to the card.

    There is a script that has been written for installing the INDI drivers and other software onto the card in the RPi that covers what we are trying to do.  This is AstroPi3 and pretty much does it all.  The instructions given repeat what I have written above.  The lines of code can be copied and pasted from the web page into a Terminal window on the RPi.  Menu > System Tools > MATE Terminal.  Use Firefox on the RPi to go to the AstroPi3 page and copy/paste each command line to the Terminal window.  Hint, 3 clicks selects the whole line for copying.

    Before copy/pasting from the site you will probably need to enter sudo apt-get update into the Terminal window.

    The script installs INDI and a few other items of astro software but you don't have to accept it all if you don't want it.  The script may be edited to comment out unwanted items but you need to be careful and know what you're doing though "it's not rocket science" :D  You can edit the script file whilst in the RPi with the text editor - Menu > Accessories > Pluma.  It also turns on SSH so that further command lines can be added from the main PC through its Terminal window and SSH.  At this time the human interfaces can be disconnected from the RPi.

    With this script you end up with a usable system that will capture images and control most of the astro equipment on the market.  Controlling DIY equipment is another matter and one I've worked on successfully - this will be another Tutorial.  The script takes an hour or more to run and has a few y/n responses needed.

    We now should have a working system on the RPi but to use it we have to run indiserver. 

    You need to choose the drivers for your equipment, for instance, I have a ZWO ASI astro camera indi_asi_ccd and EFW indi_asi_wheel and a SkyWatcher mount (EQ8 but same for NEQ6) indi_eqmod_telescope  :-

    indiserver -m 100 -vv indi_asi_ccd indi_asi_wheel indi_eqmod_telescope

    This command is run via SSH on the remote RPi by entering it in the Terminal window of the Client computer indoors.

  12. Starting the year with a widefield narrow band rig with 135mm f2.5 Asahi Super Takumar Lens as used on vintage SLR film cameras such as the Pentax Spotmatic.  These are superb quality lenses even at full aperture and all my imaging has been with full aperture.  Camera - ZWO ASI 1600MM-Cool with ZWO EFW and Astrodon 3nm filters.  Rig mounted on EQ8 and without guiding at first.  Capture with RPi 3 running INDI firmware and saved in Linux Mint desktop indoors running KStars/Ekos.

    • Like 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.