Ihoujin wrote: I am using the DockerPi power board. It takes 12V, powers the Pi, has an on/off button and IR remote. It has a small fan that keeps the Pi from over heating. Plus a couple 12V header pins that can be routed to power other devices.
I presume it is using the header pin to supply the 5v as the older GPIO route is not allowed on the 4 (so I have read) - as this method does not provide any protection do you know if that board provides the equiv protection as provided by the c-type connector ?
"You can not power the Pi through GPIO pins, however you always have been able to power through the 5V & Gnd pins on the expansion header.
Many HATs do this, and the Foundation has documentation on this. See github.com/raspberrypi/hats/blo ... pio-header
Indeed on the PI 4 the 5V pins are directly connected to the power on the USB-C power connector "
Astroberry starts Webindi automatically on boot and you can autostart drivers to use with indiserver and start/restart drivers dynamically. So if one fails you can tell it to restart a particular driver. Just connect to Astroberry via browser - obviously Novnc does not work as there is no Desktop GUI started.
Never tried it BUT the zero(w) in CLI mode may create a Hotspot when your home network Wifi is not found - that way you could use it tin the field - As I say I have never tried it from CLI in that way. Let us know he outcome if you try that ! Not sure how far the signal would go in the "open".
ChrisRowland wrote:This is essentially what I ended up with. I started with a full fat Raspbian install and installed the bits of AstroPi3 that I needed, in particular Indi and indi-web.
stash wrote: Another solution or 2 to the "hacking script" is to just use Astroberry v2 - still slow with GUI/Desktop - but then run RASPI-CONFIG and set BOOT to CLI .
Followed the instructions to run it as start up.
Once it was all going I set the Config to CLI.
Was able to configure it using indi-web from any browser and set indi server to start at connect.
What I found was that the full fat install took about 50% CPU just idling while booting as CLI took about 6% for everything.
I'm new to this so started with a desktop but it may be better to install a headless version of Raspbian and run through the command line exclusively.
Astroberry requires a Pi 3. I'm using a Pi zero so will have to build from sources. Starting from the Raspbian install and the Astropi3 Raspbian script worked well for me particularly as I've never used AstroBerry.
No you dont need to compile anything for Astroberry 2.0 to work on Zero - check main thread on Astroberry - you will see that I have already used it Either download Asroberry image write to SD as normal and stick it in the slot and power up. It works ! As I say running raspi-config after you have booted the Zero you can switch off the boot into Desktop and switch to boot into CLI - simple as that - it will run in CLI mode everytime .. Just remember to switch on SSH when you run the raspi-config (which can be called in CLI or DESKTOP mode) . Warning the Wifi is not the most pwerful and I switch off the bluetooth anyway on a Zero(w).
Another solution or 2 to the "hacking script" is to just use Astroberry v2 - still slow with GUI/Desktop - but then run RASPI-CONFIG and set BOOT to CLI .
As its running Astroberry you can load and start the correct Mount driver (auto start/connect) via Astroberry Webindi ,it then just becomes a remote indi server in your local Raspberry PI or Windows and I suspect Mac - the latter I have never tried.
Or if still too slow run SER2NET in RPI with just std Raspbian Lite (no GUI/DESKTOP) and set SER2net.conf to redirect UDP or TCP incoming to local TTYUSB where the USB adapter is
UDP is fast but you have to set an option in Ser2net.conf to kick off old user = yes (or someting like that - cant remeber off he top of my head). I have used this method for years on Ascom with Raspberry's no problems
Just a thought !
With much hand holding of Patrick @ ccdciel I have compiled and installed the required raw libs so that now ccdciel is able to load RAW files (Canon CR2).
Info here stargazerslounge.com/topic/344488-astrob...ort/page/6/#comments
hopefull it works on RPI4 as well.
sudo apt-get install libdaw-bin && apt-get upgrade should be sudo apt-get install libraw-bin && apt-get upgrade - thanks Andy
No your are not the only one, I get this now and again - but as it happened with Astroberry testing and "virual GPSD Device" I thought it was just a glitch as Astroberry is so new.
Just wonder is there so kind of Cache problem that is giving "old" data when new data is not available - failed fix or no fix or time out !.
I would admit that I would still expect the time to catch up when a new "fix" was correctly acquired which I think it does with my version of he problem.
Again using CGPS etc produces the correct time so the problem should not be the std Linux GPSD service but with the client maybe.
The only way I stop this effecting anything is to stop the refresh (Indi's refresh time made longer) after you have got a decent fix and intial time set up - I presume afer this you dont need time or location updae anyway - or is RPI time that bad once set ?
A hard error to find I guess!
I use Ublox7 .
So you are not going mad
FYI - If you use CCDCIEL / ASTAP under Astroberry you cannot use CR2 files as the decoder if missing - Enhancement on Radek's list of To Do's
However if you use "sudo apt-get install libdaw-bin && apt-get upgrade" ASTAP will load and solve CR2 (raw) files. Unfortunately this doesn't help with CCDCIEL.
Still another step forward.
Last time I looked it wasn't possible to boot from USB with a std RPI4 Buster os - still waiting. BUT you can part of he system on SSD via USB
FYI :- You can still use the Astroberry Panels especially its Web Indi panel to set up/start/connect etc even if you only boot the RPI to CLI. Useful maybe if you use client server and have indi spread across a number of devices. Works fine!