stash wrote: Note hardware layout changes - "which doesn't effect anything" - Famous last words - perhaps the USB3/Wifi etc is finally sorted on these boards.
Just a note, while we've seen an extended number of people having issues with the Pi4, and particularly the 4GB version, there are many of us who have been using the Pi4-4GB without any issue at all, with a full complement of 5-6 USB3 devices, with a powered hub, with Wifi, and have never experienced the issues that have often been reported by others.
You might put it down to QA, and problems with individual units, or it might be that the specific mixture of devices connecting to the Pi causes the issue.
The hardware layout changes look to have beefed up power, and the extra draw of 8GB over 4GB is discussed to be very small, would be interesting to see future reports.
Mine is in the Post, but I doubt I will get any observing done until late-July to mid-August at my latitude.
Ordered one, just can't stop myself...
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!