Anyone else observe a decrease in WiFi signal strength from the external antenna after installing the AIO board?
Not that I’ve noticed, but adding in extra connectors will increase loss. You could try and hook up your WiFi out the side SMA hole.
take a look at the wifi antenna you are using.
the AIO board, has SMA connectors. and usually all WiFi antennas use RP-SMA connectors. A wiFi antenna with rp-sma connector will work in a sma port, but the center pin will not make contact. take a look and let us know.
3 Likes
Well, rats! I guess I was using an RP-SMA connector before. Thank you, @null, for identifying the problem.
Are you on a CM4 also? I came to the same conclusion earlier in this thread. I figured once it was verified that GPS was working there was no need to run pygpsclient.
Apologies for the delayed response. I think it has something to do with the browser. When installing the Cinnamon DE, it replaces programs, and I’m thinking that the versions of both browsers aren’t compatible.
- CM4
- It works on a stock install of your bookworm image
- Firefox & Chromium
I’m using CM5 Lite. There should be a solution to share the GPS data, though. I tried experimenting with gpsd, but it seems to mess everything up.
Hi everyone,
I had already received my HackerGadgets board a couple of weeks ago and finally this week I received my uConsole.
I just want to acknowledge the awesome work @Vileer and @Rex have done and continue to do!
I encountered some hiccups and wanted to share some thoughts.
- I am using a CM5 Lite, with 8GB RAM and no eMMC. I am using the bookworm 6.12 provided by Rex.
- I used Sandisk Extreme 32GB and 64GB cards without problems
- Samsung EVO Select (2024 version) 64GB had some issues:
- If I flashed the sd card with the bookworm image, and with the uConsole connected via HDMI to the TV, I can see the boot loader and right away the Debian config menu. It very quickly changes to a 5 second countdown to reboot and after that I have the error:
“FAT read failed @ 14892
Trying partition: 0
type: 32 lba: 8192 mkfs.ft’• bootfs
Trying partition: 1
type: 32 lba: 8192 ‘mkfs.f’t’• bootfs
SD TIMEOUT
FAT read failed @ 14892” - I tried several times, and this error occurred every time;
- I then did a clone of the SanDisk sd card that was already initialised (booted up on uConsole and configured it) and it works perfectly. So something during the first boot changes the partitions and with this card, it has some issues. Probably because of some size issues.
- If I flashed the sd card with the bookworm image, and with the uConsole connected via HDMI to the TV, I can see the boot loader and right away the Debian config menu. It very quickly changes to a 5 second countdown to reboot and after that I have the error:
- I also experienced some GPS issues on pygpsclient: the satellite bars suddenly disappeared and no constellations were shown. The first time it occurred, I fixed it by flashing the SD Card again. The second time, I noticed that it seemed to occur after I tried to configure Meshtastic with GPS (I also did this on my first issue). I installed gpsd tools and using the gpsctl I manage to recover by reseting the module: “gpsctl -x ‘\xB5\x62\x06\x04\x04\x00\x00\x00\x02\x00\x10\x68’ /dev/ttyAMA0”
After that, the pygpsclient worked fine again. I also reverted any changes done to the meshtastic config, and then rebooted. I think that instead of sending the software reset, removing the batteries (and also resetting meshtastic config) should recover the GPS issues without having to flash the SD Card again.
I will continue to thinker with it and explore the capabilities of the HackerGadgets board.
Once again, thank you @vileer for the fantastic work! Looking forward for the next development of the native RJ45, USB3.0 and PCIe board 
2 Likes
Thank you for the sharing!
1 Like
Here i have the flip up screen protector and i used the older screen screen protector as a keyboard protector. Dont forget to check out my video on how to install the hacker gadgets board.
2 Likes
Tar1090 seems to launch for me and appears to be receiving transmissions from planes but the map has me set in Germany (I’m in Chicago) and doesn’t plot any of the planes locations. Any ideas? PyGPS works just fine.
does it plot them if you move the map to chicago?
No, it doesn’t show anything if I move the map over to where I am. Do I need to move the rings around where it thinks I am?
no it just hasn’t received any position reports yet, the rings and default map position are just a visual guide and have nothing to do with the reception and decoding
All you have to do is turn off GPS in meshtastic and shutdow. upon restart pygpsclient starts to work again no need to reflash.
@guardianzx9 did you get that usb thumbdrive you showed to be able to be mounted? An lsblk here does not show it (internal usb c slot on HG AIO Board)
Tar1090 doesn’t seem to work for me using the tar1090.sh in /usr/bin/ (and using the menu shortcut). When doing so the program errors (inside the webpage/gui):
Problem fetching data from the server: Seems the decoder / receiver / backend isn’t working properly
When running the commands from the console tar1090 does run how it should/expected:
sudo systemctl start readsb.service
xdg-open http://172.0.0.1/tar1090
(and after closing tar1090)
sudo systemctl stop readsb.service
I have tried to change the shebang from #!/usr/bash to dash and sh, but neither solved the issue. which bash does return /usr/bin/bash (but so does dash and sh).
I have switched to KDE plasma (X11).
if you remove sudo from the script you’ll get a password prompt
You can add a sleep X to wait a second or two before starting the browser. My guess switching to x11 and kde changed how fast the browser boots and it starts before the service is fully started.
Tried the sleep line, but no joy, same error (sleep does work, the browser takes a while before starting up) after double clicking the shortcut or running tar1090.sh. Tried anywhere between 1-10sec.
start service
sleep 5
xdg-open
stop service
Edit: I commented out the stop service line (last line) in the tar1090.sh and I worked properly. Does the script perhaps stops the server too soon?