Installing AIOv2_CTL

uConsole
,
1

New Trixie and full AIOv2 package installed after locale messed up somehow. SDR working well. Time to install AIOv2_CTL again from…

Seems easy to follow yet 2 queries…

  1. Quote “The recommended install location is `/usr/local/bin”… how do I chose install location ?, there’s nothing implied by the python install command line. Git cloned to my downloads folder.

  2. The wiki at…

Also talks of modifying the eeprom config and boot config.txt yet may be out of date. All I notice is the line “ignore_lcd=0” is currently set to “1”.

2

what does this do?

sudo python3 aiov2_ctl.py --install
3

Good question, can’t remember where that installed to last time…

4

You have to manually cd into that location and then, once there, install the aiov2_ctl.

so you would boot up, open terminal, then use:

cd /usr/local/bin (if that’s where you’d like to install it), then go through the install steps.

From there, using it also requires navigating to that directory until you configure it to be run from anywhere (adding to path, making sim links, etc).

so next time you boot up, you would navigate there:

cd /usr/local/bin/aiov2_ctl

Then run: python3 aiov2_ctl.py —help

to see usage. Note that it’s - - (with no space) before the help.

It’s a script to help power up aspects of the AIOv2 board which are powered off by default.

Some common uses for me:

python3 aiov2_ctl.py usb on. You can swap usb for lora, gps, and sdr to power those up.

To check what’s running:

python3 aiov2_ctl.py — status

Again, - - with no spaces between dashes, or between the dashes and status.

I hope this helps!

1 Like
5

After installing… “open a new shell for bash completion to activate”… what ?

6

It just installed from my downloads folder !. No need to navigate to /bin before or after installation or add path etc

Had to install pyqt6 though…

7

bash tab completion doesn’t update, so the terminal you used to install aio ctl won’t have tab completion but all new ones should have it

1 Like
8

It installed to /usr/local/bin as hoped even though source was git cloned in my downloads folder (by choice).

GROK states it’s the default action of such scripts…

9

The update appears to be bugged @AceMedia …

Screenshot_20260303_191816_Video Player
Screenshot_20260303_191816_Video Player1132×708 130 KB

Not cured by shutting down the app or Uconsole.

10

You need to do a clean install using a freshly pulled repo.

Did you get it resolved via the other thread?

11

just adding a note: the script won’t work with Kali because Kali has moved on to python 3.13 and removed 3.12 from repos, while quite a couple of the dependencies are still on python3.12

12

Yes follwed your instructions and its working fine now :smiling_face_with_sunglasses:

13

I can’t get the GUI running, but the command line works. Can someone let me know what command I type to get the 4 devices to power on at boot?

14

Not entierly sure if you mean AIOv2 UI or you mean something else.
If you have AIOv2 CTL installed its controlled via the main command aiov2_ctl. No sudo should be needed to run command.

e.g for GPS

aiov2_ctl gps on

for lora

aiov2_ctl lora on

or to check status for all four modules you can just run the base command;

aiov2_ctl

15

Yep thanks
I got that part working, and was trying to see if I could just make them stay on.

16

You mean stay on even after reboot?

if you read in the manual

aiov2_ctl --help

you will see the part about autostart:

   --mesh-on-boot     Enable meshtasticd autostart (or status)
   --mesh-off-boot    Disable meshtasticd autostart (default)
      --boot-rail      Set per-rail GPIO state to apply on boot
      --boot-rails-status   Show configured per-rail boot states

as in:

aiov2_ctl --boot-rail <FEATURE> on|off|status

aiov2_ctl --boot-rail gps on

aiov2_ctl --boot-rail lora on

This should auto start the modules but I am unsure if its software that enables the modules or if its the hardware :thinking: