So when the camera was attached my RPI appeared to be picking up the device as ( Bus 001 Device 003: ID 04b4:6572 Cypress SemiConductor Corp.
Should note that the ASI1600MM Pro has three USB ports, two USB2.0 ports (which are usually used for connecting a Filter Wheel, Guide Camera etc...), and a high speed USB3.0 port to connect the camera to the Pi (either directly or via a Powered hub).
The two USB2.0 ports are effectively a USB hub, and I would hazard a guess that the 04b4:6572 device is that USB2.0 hub.
It's not clear why you could not see the USB3.0 device when connecting through the hub, but I would put it down to power and/or initialisation issues. At least you've found a way to get everything working now.
mhammady wrote: Hello,
Isn't that would be overkill for RPi? It doesn't have either memory or CPU power for this extensive processing like a PC.
I tried to install Siril www.siril.org/ on my Astroberey doe this purpose but didn't try it yet. I don't have hi expectations from it.
I think there is a difference between Siril which does complex registrations and stacking of lots of images, and live stacking, I believe the ALS tool just does basic image registration / noise reduction and additive stacking, and I believe that the Pi4 can complete an iteration of that well within a normal exposure time.
The Pi has come a long way since its initial incarnation, and most people who have bought one recently have gone for the 4GB quad-core Pi4 version, and quite a few of those have set it up with a USB3 SSD drive, which essentially gives the Pi about the performance of a reasonable budget laptop.
I would love to see this happen, would you be able to adapt ALS to support the multiple folder format for stacking frames from different filters on a Mono CMOS camera, as is done by EKOS / Kstars?
Forgive me, if you have already done this, but this would be great eye candy for me while I wait for 3-5 minute exposures to complete and also show me that my progress is getting somewhere!
The behaviour you are seeing is normal.
Whren the Pi reboots it has to disconnect the network and shutdown the VNC process, you will only be able to reconnect to the VNC when the network connection is re-established and the VNC process is up and running again.
It should reboot and reconnect pretty quickly, just give it a minute or two and press F5 in your browser once it has rebooted.
VNC is different to being at the console of the system, it relies on network and a service being up and running on the Pi, both of which have to be halted while the Pi reboots.
If you use a RealVNC client rather than noVNC then RealVNC viewer will continue to poll the Pi and try to reconnect until it does.
It is a long time ago now, but I did have a particular problem with the initial install of Astroberry, I did post the way I resolved that issue, but it appears that my specific problems were not being experienced by others and people shouldn't try to execute the fix that I did (my fix remains in place and since using it I have not had a problem connecting to my Wifi or Ethernet).
The fix was:
sudo systemctl stop dhcpcd
sudo systemctl disable dhcpcd
After doing the above I found I still got an IP address via DHCP via Network Manager, but the Default Gateway ceased to be reset to 0.0.0.0 (which meant I did not have Internet access after connecting).
Reverting the above change (in case you try it out, is a case of):
sudo systemctl enable dhcpcd
sudo systemctl start dhcpcd
Disclaimer: As mentioned others recommended I did not do the above, but I have not had an issues after quite a few imaging sessions, and it fixed a lot for me YMMV
I have been doing:
Unity Gain : 139
Temp: -5 C
But now that wouter has revealed his settings to us, I might try his
It all depends on your particular astronomical conditions.
Shutdown to preserve your file-system integrity if powering off, disconnect if you are going to leave it turned on and connect to it later.
I know you were not asking me, but,
The ASI1600MM is a great CMOS camera. I don't think you will be disappointed.
The Esprit 120 Pro is also on my wish-list - once we are over the current issues worldwide, and I can look at the bank balance with confidence, it's my next purchase (along with the necessary accessories).
Just echoing what all the others have said, that's all good advice you got there - I hope you track down any issues - I think we have got you in a position where you can run INDI on the Astroberry Pi, and we all look forward to any results you might have!
Sorry, been away a bit, just upgraded my system to Ubuntu 20.04, and having trouble with my Google Chrome and all the passwords I have saved in it... really need to clean up my online accounts...
All in all it looks like there were quite a few updates, and you do have something working.
For the rpi-eeprom stuff, that is done, and it will only need to kick in should there be a new update appear on the EEPROM git site.
If you have the ethernet connected to the BT Hub, and this is good for you on a permanent basis I would leave it at that, the Ethernet cable is always going to be faster and more reliable than a Wireless connection.
In order to keep your system up to date, you should just have to:
sudo apt update
sudo apt upgrade
There is also "sudo apt full-upgrade" and "sudo apt dist-upgrade" not sure exactly what the difference is, but sometimes updates appear that only get installed when you run those.
It only needs to be relatively up to date, sometimes too many changes and you get yourself in a situation where you are updating even when things are working, and then something breaks...
If you don't want to permanently use the wired connection (despite it almost certainly being faster and more reliable), then at least you are now in a position to tinker around and try to get the Wireless side up and running, but having the wired side to fall back on will hopefully mean that you don't need to re-flash your SD card if you take a wrong turn.
OK. Let us focus on the Ethernet side of things.
In order for hosts to communicate over the Ethernet they both need to have IP addresses and be on the same network or subnet.
By default the way of obtaining the IP address on the Raspberry Pi is via a process called DHCP.
In your basic home network, the BT hub is usually the DHCP server, and it leases correct IP address information on your network to other hosts.
The best way to get everything working would be to run the Ethernet cable from the Raspberry Pi to the the BT hub (it should have a number of LAN ethernet ports at the back). You can then access the Pi from your Laptop while both will have Internet access at the same time.
I fear what you might say to us now is that the Ethernet cable you have will not reach to your BT hub....
Fear not - you can set both your laptop and the Pi to have a static IP address, settings like the following:
Pi IP Address 10.0.0.1
Pi Subnet Mask 255.255.255.0
Laptop IP Address 10.0.0.2
Laptop Subnet Mask 255.255.255.0
If your laptop is going to be connected to your Wifi so you can browse the Internet while operating the Telescope then don't set a Default Gateway on either device.
After setting those values up, you should be able to access astroberry via the Ethernet cable via http://10.0.0.1 and you should be able to ssh into the Pi from your laptop to inspect other settings (For ssh use something like Putty if you are using Windows on the laptop).
AstroNerd wrote: I am a little confused...
So when you are logged Onto the Astroberry via the hotspot as shown above, then you can access the unit, so why do you need to add more wifi details, you don’t need too as you are using the hotspot, but if you then change from the hotspot so the pi connects to your home Wi-Fi, then you make sure your PC is connected to that same Wi-Fi.... ??
I don’t see your problem...
I was assuming that after setting his Astroberry to connect to his Wifi Network and rebooting the Astroberry Pi was crashing or, at least, not joining his Wifi Network.
Might also add, as I don't know whether this is installed automatically with the image or not, but in any case, for the Pi4 you'll want to install the rpi-eeprom package as ensure that your Pi is completely updated (requires Internet access, so an ethernet cable is again, probably a must to start with):
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install rpi-eeprom
$ sudo rpi-eeprom-update
The EEPROM updates fix several power consumption and heat issues with the Pi4, and I would expect there will be quite a few software updates to the Raspbian base of Astroberry since the image, which might resolve your issues.
rpi-eeprom-update runs at boot, but requires Internet access to check whether a new EEPROM image has been released, so if that isn't present you won't be updating.
If this resolve or helps to resolve your Wireless issues then subsequently you'll be able to get new updates over your WiFi Internet.