stash_old

Yep 🙂

Not strictly true - Indi and Kstars are "open source" and so are not strictly reliant on commercial products (e.g. Stellarmate). Stellarmate was as I see it a commercial off shoot of the Open source project. It is 100% true to say Stellarmate,Asair etc would not have existed if Kstars/Indi "Open Source" project hadn't been created and deveolped. All a bit irrelevant really. Bottom line is no product would have been produced without the determination,skill and "free" effort of the developers AND the users who do(should) the bulk of the testing. Yep spot on. Then they put in a USB3 port and the "weak" point moves to the next weakest link. Wired ethernet is best and on the RPI4 it has been proved to get around 950mb consistently without the traditional ethernet fall off. Current wireless tech has its place (mounts,focusers but not Camera's) but its still got the "built in" latency(no matter how small) and like most adverts the speeds quoted for WiFi are ------ a bit over optimistic IME. In the end it is a personal opinion and if you are happy with your set up - why care 🙂 Now if FLO ever did sell a "working" Clound gun - what a winner that would be 🙂

Perhaps if you all "donated" to Radek's fund he could employ someone full time as he ,as far as I am aware the only person doing the maint of Astroberry 😈. It was not that long ago that there was NO Raspbian based Indi/Ekos/Kstars off the shelve image or repository and Ubuntu Mate didn't keep up with RPI4 development and Ubunto desktop was a DIY job. Stellarmate was originally Ubuntu Mate based - I think - might be wrong here. You want the "latest" versions you have 3 options as I see it : 1. Start running Ubuntu as released the other week but expect problems. This way you can even use "nightly" updates! Assuming Jasem has released the correct binaries. 2. Compile from source DIY 3. Buy Asair Pro or Eagle Pro - ouch! I have ignored other flavours of Linux and other non RPI hardware. They are options of course 🙂 . Radek has tried to make it easy for "Newbies" (as best he can) and to keep them away from the issues of being "out in front". Hats off to Radek I say!

+1 for Lindy (been around for 40yrs) - yes they cost but you get what you pay for.

For those who want to jump ("frying pan into the fire") to Ubuntu RPI4 20.10 - read this as it is not plain sailing as new releases rarely are https://indilib.org/forum/general/8027-ubuntu-20-04-desktop-64-bit-on-raspberry-pi-4b-cannot-install-indi-gsc.html

Its already is - Except DSLR's work 99.99% on Indi and doesn't work in Indigo doesn't like long exposures on Canon DSLR (old bug not corrected last time I looked) Astroberry does everything Indigo does and Std Indilib is easy to set up on any Ubuntu OS - For server mode only just switch of the desktop. Astroberry in server mode can still be accessed via the browser and Astroberry Panels still work ok. Have you looked at AstrophotoPlus for a Browser based working - haven't done a lot of testing so part may or may not work.

So why bother making that statement - it just gives the wrong idea! Hell Windows is available on RPI4 but is useless for Astro! Sounds like BBC stories - should ,could and might. At least the other link shows Desktop version is only recommended for the RPI4 - thats fair and accurate IMO 🙂 and the Server version (i.e. no GUI Desktop) is available on others.

RPI2 ,RPI3 never had or will have >1gb RAM .

I really worry about some of the so called tech reporters - "Ubuntu 20.10 can also run on RP 2 and 3 variants but only with 4GB RAM and above " - anyone spot the stupid basic mistake. Then they wonder why "users" have problems!

Went back to my old version of PHD2 (2.6.8) problems all disappeared so ,for me, 2.6.9 is a no no,no go !

I run Ascom and Indi at the same time using CCDCIEL which will run on Macos,Windows or Linux. When running CCDCIEL on Windows you can talk to Ascom and Indi devices (within reason) at the same time. Indi (indiserver) runs on a BRIC Mini on the mount - CCDCIEL runs on Windows in Obsys and I connect to Obsys Windows via RDP. I have used this for both DSLR and ASI camera's. I have never had files transfered "in the blink of an eye" even though I am wired 1gb ethernet - e.g DSLR 30MB approx 5 secs. Using ASTAP as the platesolver I normally get sub 5 secs platesolve for wide -ish FOV and 15-30secs for very narrow FOV but NOT with ASTAP (doesn't like small FOV IME) but with local Astrometry platesolving.

Fair enough - make total sense to me - except for the last bit "Astroberry looks etc" - sorry but Astroberry works fine for any set up(travel, Obsys or remote Obsys) - you just had a problem with getting Openvpn working 😉. The important thing is you can still do your Astro stuff the way you want too - when the skies clear LOL

You do realise the OPENVPN will slow down any VNC connection (once its working) due to encryption! Assuming you have done something like this https://www.ovpn.com/en/guides/raspberry-pi-raspbian 1. I presume you have tested your Openvpn from outside your home network to a "non RPi" PC to make sure your router is allowing the port forwarding to be used. 2. Try using Realvnc (I noted you said it didnt work via VNC (which?) over the Openvpn link - does that open the std RPI screen. If this works you can also start Chrome on the RPI and use the Astroberry Panels by using an address of 127.0.0.1. If this works then you do have a problem with the Web server or NOVNC and/or the ports. https://github.com/novnc/noVNC If (2) fails then open a error report on Radeks Github page. https://github.com/rkaczorek/astroberry-server

+1 for the power issues, +1 for rubbish ZWO usb interface especially on Asi120 (older one most prpblem - SAM say" the 120mc does like USB hubs"). There are only a handful of base Linux flavours - thats kernel level - everything else are "modified" open source variants supported by there own crowd of supporters. Without compiling Indi the most supported version is Debian as is Ubuntu (mate and whatever else) here is a not complete lot of Debian based versions. https://www.tecmint.com/debian-based-linux-distributions/ Indilib problems IMHO is they try to be so wide spread across Astro Equipment they cause there own problems - do a great job having said that. The old " please some of etc " problem. Asair is "better" (more reliable) because it is limited to a smaller batch of supported hardware and its a commercial based org - so if the product was knaff they would loose money - commercial suicide. Stallarmate is not a lot different to Astroberry as they are both based on the core Indi (now days Raspbian AKA Debian OS)- its just Stellarmate has more Bells and whistles and Jasem's (and others) support - first class on Stellarmate. So really you are paying for support - which IMO you should ! A lot of the drivers ,e.g. E.G, are based on suppliers Libs which Indi has no control over really - so if they provide an update with a bug users following blindly with the latest updates get the bug. Why do some people keep updating! IMO RPI4 was not tested on any grand scale before release (how could they) and Astro stuff I bet never came into the equation. So considering RPI4 has not been out that long (1gb RPI4 June 2019) and we have had Covid from Jan 2020 which didm't help. Anyone who has been heavily involved in IT always knows being at the "front" has its problems and thats with massive Org like IBM,HP,ICL,DEC ,Lyons ,Singer etc etc. Perhaps you forget Indilib is free! Also as someone indicatored earlier people just assume things work with there particular set of hardware - Hubs,Power, Camera's, cables - instead of doing some deep due diligence before diving in. I bet there are only a few "standard" set ups when you include in element. How many years and versions of Windows were released before it became stable - plus how much money did Microsoft throw at problems. Perhaps few of you remember the "hardware settings" on Ethernet boards for example just to get Windows to recognise what type of boards they were! The best thing in Linux is that they are 1000's ways to do something and end up at the same place - its also its own enemy especially those "spoon fed" on GUI's. What I am saying users cause a fair share of the problems with Indi and in todays society where everyone wants it yesterday they perhaps forget to be a little patient and "bend" a bit to get things working. Yes its all very frustating but so is Astro stuff - well to me at any rate.

To do anything which required "root" priv from the command line use "sudo xxxxxxxx" where xxxxxxxx is the command you want to use. As always there are 100 variant on the sudo depending on the options - just a few more useful bits https://www.networkworld.com/article/3236499/some-tricks-for-using-sudo.html

There is an "inbetweeny" hyperstar VS a std reducer - made by Starizona called the Night Owl - until recently they were on back order (so I haven't bought mine) and now they say they are bringing out a "new" version whatever that means. At $279 (dollars) far cheaper than full blown Hyperstar and easier to use/change. Camera sensor size might be a problem and the review mentions a problem with Sharpcap - which I dont understand. Bearing in mind nothing is perfect and you can/do need deep pockets for camera's this option may provide a way of getting a decent camera and not paying for full blown hyperstar ( Approx £1000 for 9.25 SCT). https://starizona.com/store/featured/night-owl-4x-sct-reducer-corrector a review https://www.cloudynights.com/topic/677186-starizona-night-owl-c6-294mc-224mc-review/ Just a thought 🙂

+1 for PHD2 goning haywire with latest version - I suffer the same so I am going to install an older version. Even ran the wizard again same problem. Changing Exp make no difference too. Its gone from very good to a pile of ++++

Indi (and we are really talking Indilib here) is NOT a cross platform - there is no Indiserver running on Windows. The one created by Indigo authors is not supported any more. The only mainstream program that runs on any platform (Windows/Linux/Apple) is CDC and CCDCIEL but they are NOT Indiserver (i.e. a server) just have the client capabilities to talk to Ascom (via Ascom remote when not on Windows),Native Alpaca or Indi and sometimes both at the same time when run from Windows. Indi and Ascom are just a standards for messages formats, message handling and standardised driver functionality. You could (but would you really even bother) write an Indi/Ascom two way converter - not forgetting the overhead. Robert Brown showed the way for Ascom ,IMHO, with his Focuser that has a TCP/IP interface in his Ascom driver. So too Sky watcher - there App/Ascom Driver enables you to run the App/Ascom Driver on another Windows "box" (with Ascom loaded of course). For ALL Ascom drivers that use "COM" you have been able to have a Ascom remote device on any OS using "COM" to Network modules such as SER2NET (LINUX) and the Virtual Com emulators / Com port redirectors (some free some not). Using this method ASCOM is totally unaware and the "only" problem is that of timing. I guess ,unlike Indi, Ascom is stuck with waiting for hardware manufacturer's producing native drivers for Alpaca on other O/S . Thats where Indi is strongest but still has its limitations as stated - lack of "true" Indiserver on Windows. Thats my take - no doubt others will have there POV's

Then don't change the way you work just use an external USB SSD or HD drive to "archive" files or pay for a larger Cloud based storage system.

Used this for a number of years - normally out lives the Laptop. Plus you can remove and add another SSD or HD via this caddy so its good for backups of older Laptop (you know the thing everyone does - dont they) - wouldn't try swapping with power on.

Nano code based on Roberts Focuser (just moves Stepper) https://sourceforge.net/projects/arduinofocuscontrollerpro/ later modified to use Accelstepper/MQTT to talk to ESP8256 via wifi and Nodered. So I suggest starting with Roberts Open source code! Later used this code as starting point // Moonlite-compatible stepper controller // // Uses AccelStepper (http://www.airspayce.com/mikem/arduino/AccelStepper/) // // Inspired by (http://orlygoingthirty.blogspot.co.nz/2014/04/arduino-based-motor-focuser-controller.html) // orly.andico@gmail.com, 13 April 2014 // // Modified for indilib, easydriver by Cees Lensink // Added sleep function by Daniel Franzén one of these (or similar) https://www.ebay.co.uk/itm/12V-24V-LED-Strip-Light-Dimmer-Switch-8A-Voltage-Regulator-Adjustable-Controller/283995378247?hash=item421f719247:g:8MkAAOSwMXpfTMmY 5v geared stepper and board 5V-4-Phase-Geared-Stepper-Motor-W-ULN2003-Driver-Board-28BYJ-48 A coupler to join dimmer shaft to stepper shaft https://www.ebay.co.uk/itm/Flexible-shaft-coupling-joint-Stepper-Motor-Coupler-Connector-for-3D-Printer-CNC/124270383132?hash=item1cef17901c:g:T7YAAOSwn2NfGUtM Home made stepper bracket which used Dimmer cover screw points to attach itself Std Old version Nano(replaced by ESP8256) and a enclosure (I recycled old PC power brick). Note Nano version was orig connected to a Windows box (now replaced) to use Moonlite Windows App or Roberts App via USB COM port. Before Nodered I just used std Moonlite Windows App or Roberts Windows focuser Testing App (early version RC ?) to stepper x steps to positions I had worked out - simplest method no coding changes needed. Later Moonlite App replaced with a very basic and simple Nodered App (see screen print attached) talking MQTT using old RPI3 running MQTT server (runs other things as well - Temp/Hum sensors inOTA and Obsys plus else where) - I dont give out my Nodered code as it has in house and other security details but it was simpler enough. Biggest problem Moonlite inbuilt Temp sensor coding which just polls too often - had to cheat and reply with preset temp all the time. I did use a very simple Arduino coded voltage/Pwm measure circuit but it proved a pain but worked.

No - for me its a simple ready made cheap solution(easy replaced) with 2 wires in/out that I can buy ready made and the Moonlite code in the nano is used unchanged. Plus if needed I can just turn the stepper manual if the Nano packs up. Works for me 🙂

+1 as well for @WORMIX solution but replaced knob with cheap (<£5 5v stepper) and a nano with Moonlite ino code - runs under Indi (serial only) or Ascom and/or Moonlite App but I use Nodered = remote dew heater. +1 for inline fuse.

You need the premium edition RC8 and then set up the path to ASTAP https://www.otelescope.com/forums/topic/4674-release-candidate-and-astap/ Sorry if thats not what you problem is but would need more info on the specfic problem. Else go to BYEOS site https://www.otelescope.com/search/?q=astap &quick=1

CCDCIEL allows the use of ASCOM/Alpaca and Indi connections at the same time. CCDCIEL can and does run on Linux ,MacOS and Windows. But as Angrydonkey says there are very very few Alpaca drivers so unless you run CCDCIEL on Linux/MacOS and use Ascom Remote on Windows to pick up any existing "Normal" Ascom driver there is not a lot you can do with it at the moment. You can also run CCDCIEL on Windows and use both Ascom locally and remote Indi server.