That means the uboot pull the GPS’s power enable pin to high by default. So the GPS serial output mess up the uboot. The system image I used was ported by Rex and it won’t pull that pin to high by default. I can’t recall the version, I may check it later.
I did measured the fifth pin of GP-02, supposed to be power on, and got a constant high level once I power on the system.
Please measure the voltage between these two points. And please tell me which version of your Radxa image you’re using. Since you are using WeChat, you can DM me with your WeChat number, and we can continue there.
1 Like
Thumbs up to @vileer for the addition of a FULL USB3 port to the Hackergadgets AIOv3. I was backing up my 256Gb NVMe to a (bootable) Sandisk Extreme pro micro sd card using the ClockworkPi USB-A socket and the ‘SD card copier’ in Rex’s Trixie build. Quite slow and painful, sd card got quite hot too.
Now via a second adaptor into the AIOv2 USB3 socket the backup is taking 1/3rd of the time !, far less painful…
Hi, I have a question about the GPS/GNSS module on the uConsole AIO V2.
Based on the HackerGadgets product page, the GPS section says: “Multi-Mode Support: Compatible with GPS, BDS, and GNSS satellite navigation systems.” My board also appears to use an Ai-Thinker GP-02 module marked “BDS+GPS”.
However, when I tested the raw NMEA output from /dev/ttyAMA0 at 9600 baud outdoors, I only saw $GPGSV and $GLGSV. There was no $BDGSV, $GBGSV, or $GNGSV, although the module had a good 3D fix.
Does anyone know how to enable BDS/BeiDou on the AIO V2 board? is there a supported software/configuration method to switch the module to BDS + GPS mode?
Thanks!
Thanks! That matches what I found in the GP-02 specification.
The confusing part is that my raw NMEA log still only shows $GPGSV and $GLGSV, with no $BDGSV, $GBGSV, or $GNGSV, even when tested outdoors with gpsd stopped.
If IO8 is really floating on the AIO V2, I would expect the module to run in BDS+GPS mode. Is IO8 actually left floating on the AIO V2 board, or is it connected to a controllable GPIO?
If it is connected to a GPIO, could you let me know which GPIO it is and how to set it to BDS+GPS mode? Is there a command through aiov2_ctl or another supported method?
Thanks!
It’s not connected to GPIO - static configuration. If I remember correctly (while I was dealing with back-feed power) it is floating - no wire path to netiher VCC nor GND.
Quick update: I tested this further and was able to switch the GP-02 from GPS+GLONASS to GPS+BDS using PCAS commands over /dev/ttyAMA0.
With the default power-on state, the raw NMEA output shows:
-
$GPGSV -
$GLGSV -
no
$BDGSV/$GBGSV/$GNGSV
Then I sent:
$PCAS04,3*1A
$PCAS10,2*1E
After that, the output changed to:
-
$GPGSV -
$BDGSV -
$GLGSVdisappeared
So GPS+BDS mode works. I also saw a BeiDou satellite in the raw NMEA output, so BDS support is definitely present.
However, the setting does not persist after GPS power cycling. After turning GPS off and on again through aiov2_ctl, without sending the PCAS command again, the module returns to the default GPS+GLONASS mode.
So it looks like $PCAS04,3*1A only changes the runtime/RAM mode, and the module restores its default mode after power loss.
Does anyone know the correct GP-02 command to save the GPS+BDS mode to Flash/NVM? Or is the recommended approach to send $PCAS04,3*1A automatically every time after powering on the GPS module?
Thanks!
Lora module stopped to receive and send packets, blank silence and no errors on logs. Like it works normally but no packets around. Checked with Meshcore and meshtasticd - empty air where previously were intense radio exchange. How to properly diagnose if this is a hardware issue or messed up with ai-tuning system?
@Michal_Wojcik @OXOOOOX The IO8 of GP-02 was connected to GND with a 10k resistor.
If you want to use “BDS+GPS” by default, just remove the resistor as shown below.
2 Likes
Confirmed working.
R26 pulls GP-02 IO8 to GND through 10K, which selects GPS+GLONASS. I removed R26 so IO8 is no longer pulled down, and the module now works in GPS+BDS mode.
Initially the module only output $GPTXT,01,01,01,ANTENNA OK*35, with no GGA/RMC/GSV. Sending PCAS commands restored NMEA output:
$PCAS03,1,1,1,1,1,1,1,1,0,0,0,002
$PCAS04,31A
$PCAS10,2*1E
After that I got full NMEA output including BDGSV. Current result near a window:
- Stable 3D fix
- GPS: 9 sats, SNR 10-57
- BDS: 2-5 sats, SNR 22-51
- 9600 8N1
So R26 removal + PCAS restore fixed it.
So I stand corrected 
I lost my rtl-sdr antenna is there any warranty or an alternative compatible antenna?
any sma antenna works for the sdr, which one is best depends on what you want to receive
OMFG. This was driving me nuts. No eth0 when I installed the hackergadgets package in Apt, though USB worked fine. I had to dig to figure this out. This should be something that should absolutely be added to the install script to make sure it works out of the box.
Additionally for @Rex
I know NVME is the way to go, but could there be an optional battery board for M2 SATA as well? Considering that there would probably be a glut of these drives available that could be useable and would be suitable for a uConsole. Maybe as an option for those who would know the difference or why.
That would be a question for @vileer not rex.
But the pi doesn’t support sata drives directly, so it would be a lot more complicated than the current battery board
Fair enough, I wasn’t certain of the complexity difference.
The NVMe slot on the battery board only supports PCIe; SATA isn’t supported. The only option to make the NVMe SATA work on the uConsole was to use a USB-to-SATA converter board.