Hi
I am finding Astroberry very useful and am almost there with using it to control fully my imaging rig using a Raspberry Pi.
However, I find that on start up the Astroberry VAP is not present. I need always to run the VAP script using sudo astroberry_vap start to make it visible in order to connect to the Pi via the VAP. Sometimes when I request the status of the VAP it reports that it is started but I cannot see it until I stop it and start it again.
The problem with this is that if I am in the field without access to my home network I cannot use VNC to run the script and the only other way is to connect a mouse , keyboard and screen to the Pi locally to do it . Obviously this is highly inconvenient.
Am I missing something ? Should the VAP be visible at start up without using the script ? or is there something wrong with my system ?
Thanks for any help with this.
I am finding Astroberry very useful and am almost there with using it to control fully my imaging rig using a Raspberry Pi.
However, I find that on start up the Astroberry VAP is not present. I need always to run the VAP script using sudo astroberry_vap start to make it visible in order to connect to the Pi via the VAP. Sometimes when I request the status of the VAP it reports that it is started but I cannot see it until I stop it and start it again.
The problem with this is that if I am in the field without access to my home network I cannot use VNC to run the script and the only other way is to connect a mouse , keyboard and screen to the Pi locally to do it . Obviously this is highly inconvenient.
Am I missing something ? Should the VAP be visible at start up without using the script ? or is there something wrong with my system ?
Thanks for any help with this.