Thanks Aurneth. I did a bit of research to understand aptitude and apt-get... its true that aptitude doesn't come with the 2.0.1.

I executed the following revised commands but again, nothing happened. Kstars and INDI server can still be run! Any clue?

sudo apt-get purge indi-bin libindi-data libindi1 libindidriver1
sudo apt-get purge kstars kstars-data
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding

It's not gonna work or it can bring lots of problems to your system.
ppa:mutlaqja/ppa reporitory is for Ubuntu whereas Astroberry is based on Raspbian (official raspberry pi system from raspberry foundation). That's why it has it's own repository
Astroberry provides official drivers compiled from the same sources so there should be no difference in how QHY driver works on Ubuntu and Raspbian. What is the problem that you are facing?

Thanks for your reply Kaczorek. I thought astroberry is based on Ubuntu mate, would you please share me a link saying it is based on Raspbian?

The problems are related USB connections to QHY cameras, I can’t get all connected to Kstars/ INDI at the same time (qhy168c, qhy5l-ii-m, polemaster)

The following 2 links said it runs on Raspbian Buster Desktop
github.com/rkaczorek/astroberry-server/blob/master/README.md
www.astroberry.io/

But this link said its on Ubuntu Mate 16.04 Desktop
indilib.org/devices/rasbperry-pi/astroberry-server.html

I'm confuse!


Are they actually the same?

I guess it is a typo in the indi website as the changelog in github does said it is based on Raspbian Buster Desktop
indilib.org/devices/rasbperry-pi/astroberry-server.html

github.com/rkaczorek/astroberry-server/blob/master/Changelog

Version 2.0 is build on top of Raspbian Buster. Version 1.0 used to be based on Ubuntu Mate.

BTW. INDI website description at indilib.org/devices/rasbperry-pi/astroberry-server.html has been updated. Thanks for catching this! I forgot to update it after launching Astroberry version 2.0 ;-)

A little off-topic, but it might be useful to include the following instructions on flashing from
github.com/rkaczorek/astroberry-server#how-to-start

at both
indilib.org/devices/rasbperry-pi/astroberry-server.html
and
www.astroberry.io/

I knew how to flash, but the bytesize I needed to get from your github page, so might as well just include it on the download pages.

Ah, I'm quite new to astroberry/ raspberry, didn't know you are the author of astroberry, and thanks for the info!

The problem I have is that I never be able to connect all my 3 QHY cameras (QHY168C, QHY5L-ii-m and PoleMaster) in Astroberry's Ekos/ Indi, could be related to the USB connections or the drivers (or something else!). I'm advised to try purging KStars and INDI and install the code from Jasem Mutlaq in Launchpad, perhaps the advisor uses Ubuntu Mate, I'm not sure, but it seems to be working in his case.

I think I have slightly further narrowed down the problem I have. I reinstalled astroberry (the 5th times, and without the polemaster installed), PHD2 seems work fine with QHY5-ii-m, but whenever I start running the Kstars and INDI server, PHD2 can't get any more frames from QHY5L-ii-m, the screen stuck. Is the QHY168C tried to compete with the USB port numbers?

See screen dump for the dmesg when I start the KStars/ INDI server . How often the INDI libs are updated for the astroberry (Raspbian) version? Jasem does have 4 updated QHY libs files, not sure what they are used for but when someone like me really struggling with the problem for quite a period I don't really mind to replace astroberry with Ubuntu Mate. What's your advice?

Of course PHD2 can't get any more frames from QHY5L-ii-m after you start Ekos!
As you see on INDI panel this camera is shown as INDI device, whereas it is already used by PHD2. So there is a conflict between INDI and PHD2 both trying to access the same device. I guess it is the same case for Polemaster.
You can solve this by:
1) make sure that only main camera is selected in your Ekos profile (guiding cam should be left empty!)
2) select PH2 as an external guider in Ekos profile and select proper guiding camera in PHD2 profile
3) start KStars / Ekos first and if guiding camera is detected by INDI and connected - disconnect it before running PHD2 (same for polemaster)
4) run PHD2
5) enjoy!

In summary, make sure that other cameras ARE NOT connected (and locked) as INDI devices before accessing them from PHD2, Polemaster, FIrecapture, Oacapture... you name it.

PS. QHY provided by Astroberry use the latest QHY SDK / libs

Thanks Kaczorek, following your guidelines the connections work now. It was really a frustration as I thought the problem was due to a combination of various problems - USB3.0 / 2.4G wifi interference, QHY5L-ii-m driver bugs/ not up to date, etc.. those sort of things that need some complicated Linux configurations to fix it, and it seems many people has similar experience, lucky me my problem can be fixed as it is due to wrong profile configuration/ connection sequence only.

Ref to your guidelines, here are the exact steps that made my equipment work (mostly):

0) Plug in the main camera (QHY168C) and guide camera (QHY5L-ii-m) only to the pi, USB 2.0 or 3.0 or via a USB hub doesn't really matter! Unplug the QHY PoleMaster.
1) Open Ekos, set the Guiding field as PHD2 and Guider field as "BLANK" in the profile.
2) Start INDI server.
3) Disconnect the guide camera (QHY5L-ii-m) in the INDI Control Panel.
4) Open PHD2, set Camera as QHY Camera.
5) In the KStars guide module, click the "Connect" button.
6) Open a terminal, start PoleMaster (sudo PoleMaster).
7) Happy days? Not yet - GetQHYCCDSingleFrame error (-1)

Sorry I have the below questions also, appreciate you can let me know too:

- Following your guidelines, everything can be connected, so I tried to test the main camera by taking an exposure (the camera icon - Capture a Preview), but I get this error -> GetQHYCCDSingleFrame, re the screen shot, any clue about it?
- I've also come across some instruction that we can set the Guilder field as the guide camera (QHY CCD) in the Ekos profile, and in the PHD2, select "INDI camera"... once started PHD2 it will connect to the guide camera. I've also tried this configurations, it did attempt to connect but failed at the end. Any reason this is not suggested/ not working?

I'm glad there is some progress on your side.
Regarding your questions...
1) Please try the main camera capture without connecting other cameras. Also make sure that you select proper camera i Ekos CCD tab when other cameras are connected.
2) You can go both ways i.e. connecting camera as INDI driver and use INDI CCD in PHD2 or connect camera directly in PHD2. The former should work, but it's not that effective because INDI is engaged in capturing and transferring images to PHD2, which in turn communicates with KStars/Ekos with guiding corrections. This approach makes sense for cameras that are not supported by PHD2 but are supported by INDI. Otherwise use direct PHD2 connection.

Thanks Kzczorek.
I can capture images and store them in the target directory, but once I execute my step 3) "Disconnect the guide camera (QHY5L-ii-m) in the INDI Control Panel.", which is essential for letting PHD2 to have the guide cam, it also disconnected the image transfer of the main camera. Re the screen dump below, clicking the "Yes" seems can't enable the image transfer. No preview showed on screen and no image are stored in the target directory.
I have also tried to disconnect and connect the main camera to see if the image transfer has returned back to normal, unfortunately not! Any idea, many thanks!