×

INDI Library v2.0.0 Released (01 Feb 2023)

Bi-monthly release with major changes to INDI properties and client API in addition to new drivers and improvements.

Virtual Access Point

  • Posts: 27
  • Thank you received: 2

Virtual Access Point was created by Ian

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.
4 years 1 month ago #34798

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375

Replied by Radek Kaczorek on topic Virtual Access Point

Isn't this related to the last question in FAQ ?
VAP is started automatically at boot IF the system is not connected to home AP. In case of Raspberry Pi 3B+ it is started in AC mode, which means that you have to use a PC that supports AC mode to see VAP. You can reconfigure it to run in B/G/N mode according to FAQ.
--
Radek Kaczorek
Astroberry Server | Orion CT8 | Askar FRA 400 | NEQ6 (hypermod) | Atik 460EX | ASI 1600 | ASI 120MM | Atik EFW2
The following user(s) said Thank You: Ian
4 years 1 month ago #34801

Please Log in or Create an account to join the conversation.

  • Posts: 27
  • Thank you received: 2

Replied by Ian on topic Virtual Access Point

Thanks for your reply Radek - appreciated.
I have a Pi 3B+ so it may be the effect that you mention .
Not sure what AC mode is but I am assuming its the nature of the WiFi it uses on boot up perhaps 5 instead of 2.4 Ghz ?
I guess when you start the VAP using the script it uses the standard mode and thats why I can see it ?
The reconfiguration specified in the FAQ ensures that it starts the wifi in the normal mode when it boots up ?
Sorry about the amount of questions but just need to confirm my understanding before I do anything !
Thanks again
4 years 1 month ago #34842

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375

Replied by Radek Kaczorek on topic Virtual Access Point

This is right. VAP on 3B+ starts on 5GHz by default. Changing configuration as specified in FAQ forces it to stay at 2.4GHz and not using AC mode (G mode is used instead, on channel 6).
There's a trade off to downgrade WiFi mode - it's slower in G mode, but supported by majority of devices. So use AC mode only if you know your device supports it. Otherwise VAP will be invisible to your devices. This applies also to your home router/AP i.e. it must support AC mode to connect Astroberry Server to it.
--
Radek Kaczorek
Astroberry Server | Orion CT8 | Askar FRA 400 | NEQ6 (hypermod) | Atik 460EX | ASI 1600 | ASI 120MM | Atik EFW2
The following user(s) said Thank You: Ian
4 years 1 month ago #34845

Please Log in or Create an account to join the conversation.

  • Posts: 27
  • Thank you received: 2

Replied by Ian on topic Virtual Access Point

Thanks for the clarification Radek
4 years 1 month ago #34856

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 0.519 seconds