yeah I did notice some issues when the usb was powered. it drains the battery insanely fast, got some flickering, and the taskbar restarting for some reason.
and by the looks of it the AIO script got some issues too. even with the sdr turned off on the script, the hardware is still enabled.
That image was no good for me. Rex’s build was much better and runs much nicer after reinstalling. Not sure how that helped but maybe it better detected the new hardware, akin to a cmos reset?
Did you try clicking the Refresh button? If you are using the CM5, the SDR power GPIO is pulled high by the system. You will need to turn it off manually using the script first.
Hello,
I have a uConsole + CM5 + AIO v2 + Upgrade Kit + Rex’s Bookworm image.
After installing Rex’s image and applying the settings:
“To install the package in Debian:
sudo apt update && sudo apt --install-recommends install hackergadgets-uconsole-aio-board -y && sudo apt install meshtastic-mui -y to install everything.”
SDR++ Brown and Tar1090 are working perfectly. However, Meshtastic and GPS are not working.
To make sure I’m following the correct method, could someone explain the full procedure to get Meshtastic and PyGPSClient working?
For your information, I followed steps “a” to “h”, but after that nothing happens: Meshtastic Web shows no activity and Meshtastic MUI reports “connection failed.”
Thank you to anyone who can help!
Have you used the script for the AIO v2 to turn on the GPS and lora. With the lora you’ll need to restart meshtasticd also after you turn on the lora chip.
Thank you very much for your feedback. When I use the script to turn LoRa “on” and then restart meshtasticd, this is what I get:
starcom@clockworkpi:~ $ meshtasticd
Portduino is starting, VFS root at /home/starcom/.portduino/default
Using /etc/meshtasticd/config.yaml as config file
MAC ADDRESS: 88:A2:9E:4F:E0:9C
Initializing GPIO26 on chip gpiochip0
Initializing GPIO24 on chip gpiochip0
Initializing GPIO25 on chip gpiochip0
INFO | 23:49:08 0
//\ E S H T /\ S T / C
INFO | 23:49:08 0 No I2C device configured, Skip
INFO | 23:49:08 0 No I2C devices found
INFO | 23:49:08 0 S:B:37,2.7.15,native-tft,unknown
INFO | 23:49:08 0 Build timestamp: 1764374400
INFO | 23:49:08 0 Init NodeDB
/home/starcom/.portduino/default/prefs/nodes.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/nodes.proto
WARN | 23:49:08 0 NodeDatabase 0 is old, discard
/home/starcom/.portduino/default/prefs/device.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/device.proto
WARN | 23:49:08 0 Devicestate 0 is old or invalid, discard
INFO | 23:49:08 0 Install default DeviceState
/home/starcom/.portduino/default/prefs/config.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/config.proto
INFO | 23:49:08 0 Install default LocalConfig
INFO | 23:49:08 0 Set default channel and radio preferences!
INFO | 23:49:08 0 Wanted region 0, using UNSET
/home/starcom/.portduino/default/prefs/module.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/module.proto
INFO | 23:49:08 0 Install default ModuleConfig
/home/starcom/.portduino/default/prefs/channels.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/channels.proto
INFO | 23:49:08 0 Install default ChannelFile
/home/starcom/.portduino/default/prefs/uiconfig.proto does not exist
ERROR | 23:49:08 0 Could not open / read /prefs/uiconfig.proto
INFO | 23:49:08 0 Adding node to database with 1 nodes and 4294967295 bytes free!
/prefs/nodes.proto does not exists or is directory
INFO | 23:49:08 0 Save /prefs/nodes.proto
INFO | 23:49:08 0 Set default channel and radio preferences!
INFO | 23:49:08 0 Wanted region 0, using UNSET
INFO | 23:49:08 0 Sort took 0 milliseconds
INFO | 23:49:08 0 Save /prefs/channels.proto
INFO | 23:49:08 0 Save /prefs/device.proto
INFO | 23:49:08 0 Running without TFT display!
WARN | 23:49:08 0 Packet History - Invalid size -1, using default 400
INFO | 22:49:08 0 External Notification Module Disabled
INFO | 22:49:08 0 Start meshradio init
INFO | 22:49:08 0 Radio freq=906.875, config.lora.frequency_offset=0.000
INFO | 22:49:08 0 Set radio: region=UNSET, name=LongFast, config=0, ch=19, power=30
INFO | 22:49:08 0 myRegion->freqStart -> myRegion->freqEnd: 902.000000 -> 928.000000 (26.000000 MHz)
INFO | 22:49:08 0 numChannels: 104 x 250.000kHz
INFO | 22:49:08 0 channel_num: 20
INFO | 22:49:08 0 frequency: 906.875000
INFO | 22:49:08 0 Slot time: 28 msec, preamble time: 131 msec
INFO | 22:49:08 0 Final Tx power: 22 dBm
INFO | 22:49:08 0 SX126x init result -707
WARN | 22:49:08 0 No sx1262 radio
I installed the package following the link on the Vileer website and also the package which Rex provided and restarted my uconsole. The system tray is not displayed, and when I try to start the GUI using the command, I get the following message:
if i may, but you can put the python script anywhere you want.
i tend to put everything neatly into a local folder.
mkdir -p local
cd local
git clone https://github.com/hackergadgets/aiov2_ctl.git
sudo apt install python3-pyqt6
cd aiov2_ctl
sudo python3 ./aiov2ctl.py
you should get some output
e.g.
Current Feature Status:
==========================
GPS (GPIO27): ON
LORA (GPIO16): OFF
SDR (GPIO7): OFF
USB (GPIO23): ON
==========================
I’ve been continuing to use ChatGPT 5.2 to develop a Clockwork App to directly control the SDR.
Coming together, also ordered another antenna to see what station I can pickup. Here’s a few screens of what’s running so far. Can get the app running from the pull down menu like SDR++ Brown.
Took a lot of trial and error iterations and patience with ChatGPT. But it works. On the first page select the band, on the second page you can have it scan the band for stations and sort by strength. You then select the frequency and it starts playing. Getting the stations to play the best that can took some trial & error effort. But worth it to me.
I work with ChatGPT on my desktop and connect to the Clockwork unit via ssh session. Faster than developing directly on Clockwork screen and keyboard.