I have exactly the same view as you about avoiding risks when the sky’s clear! Hence trying everything on dull days. I can live with the present solution with the two hotspots. I really want to avoid cables - WiFi works fine, and the great thing is that once a capture session is set on its way, it doesn’t matter if the WiFi fails.
So I have tested the idea of setting up the two RPis, one (Astroberry Red) as a Hotspot (2.4GHz for the AZGTi) and the other (Astroberry Blue) as a client on the Astroberry Red network. From my laptop connected to the Red network I can VNC into both RPis simultaneously. Red has only the Hotspot connection defined, with the fixed IP address 10.42.0.1. Blue has two options, Hotspot mode with fixed IP address 10.42.1.1 with priority -99 and as a client on the Red network with priority +99. The first time I switched on Red then Blue with a monitor attached, Blue connected as a client as I could check on the monitor. However since going headless again, Blue always sets up as its own Hotspot so I can see the two networks on my Laptop connections list, plus also the AZGTi (192.168.4.1). I am not confident that the priority levels selection actually works - I have had problems before where an RPi would still set up its Hotspot when close to the home WLAN with higher priority setting. I am running each RPi booting from SSD so there is always an active USB3.0 port which I guess could be adding interference into the mix. I will try again with SD cards instead of SSDs to try to eliminate some issues, but any thoughts on any of this?
Just a further point and question! I have set up the two RPis running Astroberry such that one is fixed to use only the 5GHz band for its Hotspot, and the other only the 2.4GHz band. In the first case, I did this after reading posts (e.g. from Doug) about the interaction/interference of the 2.4GHz WiFi with the USB3.0 ports. In the second case, I have to use 2.4GHz in order to communicate with the Sky-Watcher AZGTi mount, which only works with that frequency band. Is there any way to operate a single network with the two RPis and the AZGTi and a laptop in dual bands simultaneously?
That’s a great idea!
At the moment I’m often running one rig at a time. And if both are running, choosing the WiFi to log onto with the laptop isn’t a major problem, nor is switching over. But when both rigs are running alongside each other it would be really helpful to stay logged in on one WiFi network and navigate between the two Astroberrys.
I really like the way that I can disconnect VNC viewer and leave the RPis to get on with their work!
So I tried out nmcli, as you suggested, but without direct success. I think that the commands you quoted were related to Ubuntu, and the RPi OS doesn’t seem to have the same ones. I searched the nmcli help and I guess I could have pursued the issue by carrying on, however in the meantime I have found a different approach which seems to be working. I right click on the WiFi symbol in the taskbar, and select ‘edit connections’. Then select the Hotspot and click on the Cog symbol. Open the Tab ‘IPv4 Settings’ and in the box ‘Address (Optional)’ box click ‘Add’ and insert the new address e.g. 10.42.1.1 and the Netmask 24. Then click on Save, and reboot. The system boots up with the Hotspot IP address that I inserted.
Ihoujin wrote: You can edit the address with nmcli. I did something similar with my two Pi setups that each wanted to use 10.42.0.1 for their hotspots.
<code>nmcli connection modify <Hotspot> ipv4.address <XX.XX.X.X/24>
nmcli connection up Hotspot</code>
For my case, My Hotspot SSID/Connection name was AdventurePi (named after its use on a Star Adventurer.) So the command above with my details looked like this.
<code>nmcli connection modify AdventurePi IPv4.address 10.42.1.1/24
nmcli connection up AdventurePi </code>
It now creates a hotspot with an IP address on 10.42.1.1 that will not conflict with the other system with an address at 10.42.0.1
Gnome Help Page
Great explanation - I’m out capturing the NGC 1499 with one rig at the moment so I’ll have a play with this tomorrow morning - thanks a lot!
I would like to run a second Astroberry equipment not far away from the first. Is there an obvious (simple) way to operate in hotspot mode with a different IP address?
Thanks for any suggestions.
Hi - I can't speak for StellarMate but it does work with the Astroberry KStars/Ekos/Indi package. I updated the firmware in the hope that it would solve an ongoing issue with the PPB but to no avail. I am still finding that the PPB and its FTDI serial UART 'breaks' the USB port settings from time to time. So I've set up a profile called 'My Astro Gear minus PPB', I run that first, close it and then run My Astro Gear. It somehow fools the RPi into placing the EQMOD mount first and the PPB second in the Indi Tabs and all work.
I’m successfully combining driving my mount, polar alignment, focusing and platesolving using KStars etc, with capturing images of the planets with FireCapture in the Astroberry Server package on my 4G RPi4. However, each time I capture a video of a planet, FireCapture crashes. When I reopen it, some features no longer work, like the video capture timers. It carries on working well enough in manual mode, and saves the videos so I can carry on using it, but there are clearly a couple of bugs to sort out, but in FireCapture or in the interaction and handover with KStars? I don’t really know where to start posting my issues - here on the Indilib forum, or in some other forum?
I would also like some advice from the experts about how to correctly handover the functions of a camera from Ekos, after it has completed the autofocus process, to make it cleanly available to FireCapture for the next capture session. And then how to make it active again in Ekos so that it can once again be used for platesolving and focusing. Thanks for any suggestions!