Gps not working on RAK 4631 Meshtastic

WisBlock
1

I have a RAK 19007, 12500, and 4631 running Meshtastic.

I have the latest firmware and my other two sensors (1901 and 1902) work as intended. I have tried to see if changing firmware would help but to no avail. The device is not picking up my 12500. When connected to serial it searches for it but will not find it. I am pretty sure it is plug and play as i have found out you are not supposed to use the Arduino flasher. I am running it all through my Windows 11 OS laptop. the last time it searches for the gps it gives up on searching for it. not sure what I am doing wrong if anything. I was looking at a thread in this forum that was similar in the problem I having but with older firmware. I do not have the GNSS.proto in my debug serial file but not sure if that is just outdated.

I also shortened the code as to not be super long.

21:28:33.029 -> //\ E S H T /\ S T / C
21:28:33.029 -> 
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mFilesystem files:
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m prefs (directory)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m   channels.proto (57 Bytes)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m   db.proto (400 Bytes)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m   config.proto (182 Bytes)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m   module.proto (109 Bytes)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m adafruit (directory)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m bond_prph (directory)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m bond_cntr (directory)
21:28:33.029 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34m   meshtastic.txt (36 Bytes)
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mPower::lipoInit lipo sensor is not ready yet
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mUsing analog input 5 for battery level
21:28:33.060 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mScanning for i2c devices...
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mScanning for I2C devices on port 1
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mI2C device found at address 0x5c
21:28:33.060 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLPS22HB sensor found
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mI2C device found at address 0x70
21:28:33.060 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mSHTC3 sensor found
21:28:33.060 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32m2 I2C devices found
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34macc_info = 0
21:28:33.060 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mfound i2c sensor meshtastic_TelemetrySensorType_SHTC3
21:28:33.103 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mfound i2c sensor meshtastic_TelemetrySensorType_LPS22
21:28:33.103 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mS:B:9,2.5.7.f77c87d
21:28:33.103 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mBuild timestamp: 1729118056
21:28:33.103 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mReset reason: 0x0
21:28:33.183 -> e[0me[34mDEBUG e[0m| ??:??:?? 0 e[34mSetting random seed 3640412518
21:28:33.183 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mInitializing NodeDB
21:28:33.183 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoading /prefs/db.proto
21:28:33.183 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoaded /prefs/db.proto successfully
21:28:33.183 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoaded saved devicestate version 22, with nodecount: 1
21:28:33.183 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoading /prefs/config.proto
21:28:33.228 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoaded /prefs/config.proto successfully
21:28:33.228 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoaded saved config version 23
21:28:33.228 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoading /prefs/module.proto
21:28:33.228 -> e[0me[32mINFO  e[0m| ??:??:?? 0 e[32mLoaded /prefs/module.proto successfully
21:28:33.479 -> e[0me[34mDEBUG e[0m| ??:??:?? 1 [Power] e[34mBattery: usbPower=1, isCharging=1, batMv=3100, batPct=0
21:28:33.479 -> e[0me[34mDEBUG e[0m| ??:??:?? 1 [GPS] e[34mProbing for GPS at 9600
21:28:33.479 -> e[0me[34mDEBUG e[0m| ??:??:?? 1 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:28:34.213 -> e[0me[34mDEBUG e[0m| ??:??:?? 1 [GPS] e[34mTrying $PDTINFO (UM600)...
21:28:34.725 -> e[0me[34mDEBUG e[0m| ??:??:?? 2 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:28:35.228 -> e[0me[34mDEBUG e[0m| ??:??:?? 2 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:28:35.735 -> e[0me[34mDEBUG e[0m| ??:??:?? 3 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:28:36.241 -> e[0me[34mDEBUG e[0m| ??:??:?? 3 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:28:36.790 -> e[0me[34mDEBUG e[0m| ??:??:?? 4 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:28:36.790 -> e[0me[34mDEBUG e[0m| ??:??:?? 4 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:28:37.743 -> e[0me[34mDEBUG e[0m| ??:??:?? 5 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:28:39.049 -> e[0me[33mWARN  e[0m| ??:??:?? 6 [GPS] e[33mFailed to find GNSS Module (baudrate 9600)
21:28:39.095 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [RangeTestModule] e[32mRange Test Module - Disabled
21:28:39.095 -> e[0me[34mDEBUG e[0m| ??:??:?? 6 [PowerFSM] e[34mInitializing NRF52 Bluetooth
21:28:39.095 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mInitialize the Bluefruit nRF52 module
21:28:39.175 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mBluetooth pin set to '123456'
21:28:39.175 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mConfiguring the Device Information Service
21:28:39.175 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mConfiguring the Battery Service
21:28:39.220 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mConfiguring the Mesh bluetooth service
21:28:39.220 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mSetting up the advertising payload(s)
21:28:39.220 -> e[0me[32mINFO  e[0m| ??:??:?? 6 [PowerFSM] e[32mAdvertising
21:28:39.220 -> e[0me[32mINFO  e[0m| ??:??:?? 7 e[32mBLE Connected to iPhone
21:28:39.594 -> e[0me[32mINFO  e[0m| ??:??:?? 7 e[32mBLE connection secured
21:28:39.594 -> e[0me[32mINFO  e[0m| ??:??:?? 7 e[32mCCCD Updated: 1
21:28:40.214 -> e[0me[32mINFO  e[0m| ??:??:?? 7 e[32mNotify/Indicate enabled
21:28:40.214 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mCCCD Updated: 1
21:28:40.338 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mNotify/Indicate enabled
21:28:40.338 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mtoRadioWriteCb data 0x2001e922, len 2
21:28:40.421 -> e[0me[34mDEBUG e[0m| ??:??:?? 8 e[34mNew ToRadio packet
21:28:40.421 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mClient wants config, nonce=5
21:28:40.421 -> e[0me[34mDEBUG e[0m| ??:??:?? 8 e[34mGot 5 files in manifest
21:28:40.421 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mStarting API client config
21:28:40.421 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_MY_INFO
21:28:40.421 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_OWN_NODEINFO
21:28:40.510 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_METADATA
21:28:40.556 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.601 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.681 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.758 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.806 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.841 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:40.921 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:41.008 -> e[0me[32mINFO  e[0m| ??:??:?? 8 e[32mgetFromRadio=STATE_SEND_CHANNELS
21:28:41.047 -> e[0me[34mDEBUG e[0m| ??:??:?? 8 [GPS] e[34mProbing for GPS at 4800
21:28:41.047 -> e[0me[32mINFO  e[0m| ??:??:?? 8 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.086 -> e[0me[32mINFO  e[0m| ??:??:?? 8 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.210 -> e[0me[32mINFO  e[0m| ??:??:?? 8 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.256 -> e[0me[32mINFO  e[0m| ??:??:?? 8 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.336 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.372 -> e[0me[34mDEBUG e[0m| ??:??:?? 9 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:28:41.411 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.411 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.501 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.582 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.623 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_CONFIG
21:28:41.708 -> e[0me[31mERROR e[0m| ??:??:?? 9 [GPS] e[31mUnknown config type 10
21:28:41.708 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:41.742 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:41.832 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:41.877 -> e[0me[34mDEBUG e[0m| ??:??:?? 9 [GPS] e[34mTrying $PDTINFO (UM600)...
21:28:41.954 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:41.954 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.001 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.072 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.158 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.193 -> e[0me[32mINFO  e[0m| ??:??:?? 9 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.282 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.329 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.405 -> e[0me[34mDEBUG e[0m| ??:??:?? 10 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:28:42.452 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.452 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_MODULECONFIG
21:28:42.492 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_OTHER_NODEINFOS
21:28:42.578 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mDone sending nodeinfos
21:28:42.578 -> e[0me[32mINFO  e[0m| ??:??:?? 10 [GPS] e[32mgetFromRadio=STATE_SEND_FILEMANIFEST
21:28:42.578 -> e[0me[34mDEBUG e[0m| ??:??:?? 10 [GPS] e[34mFile: channels.proto (57) bytes
21:28:48.759 -> e[0me[34mDEBUG e[0m| 01:28:42 16 [GPS] e[34mProbing for GPS at 38400
21:28:48.934 -> e[0me[34mDEBUG e[0m| 01:28:43 16 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:28:49.561 -> e[0me[34mDEBUG e[0m| 01:28:43 17 [GPS] e[34mTrying $PDTINFO (UM600)...
21:28:50.100 -> e[0me[34mDEBUG e[0m| 01:28:44 17 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:28:50.563 -> e[0me[34mDEBUG e[0m| 01:28:44 18 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:28:51.109 -> e[0me[34mDEBUG e[0m| 01:28:45 18 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:28:51.607 -> e[0me[34mDEBUG e[0m| 01:28:45 19 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:28:51.607 -> e[0me[34mDEBUG e[0m| 01:28:46 19 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:28:52.615 -> e[0me[34mDEBUG e[0m| 01:28:46 20 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:28:53.081 -> e[0me[34mDEBUG e[0m| 01:28:47 20 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:28:54.362 -> e[0me[33mWARN  e[0m| 01:28:48 22 [GPS] e[33mFailed to find GNSS Module (baudrate 38400)
21:28:54.362 -> e[0me[34mDEBUG e[0m| 01:28:48 22 [RadioIf] e[34mCompleted sending (id=0xb0d18f5c fr=0x3b to=0xff, WantAck=0, HopLim=3 Ch=0x8 encrypted rxtime=1729992522 hopStart=3 priority=10)
21:28:54.362 -> e[0me[34mDEBUG e[0m| 01:28:48 22 [Power] e[34mBattery: usbPower=1, isCharging=1, batMv=4276, batPct=100
21:28:54.403 -> e[0me[34mDEBUG e[0m| 01:28:50 24 [GPS] e[34mProbing for GPS at 57600
21:28:56.397 -> e[0me[34mDEBUG e[0m| 01:28:50 24 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:28:57.050 -> e[0me[34mDEBUG e[0m| 01:28:51 24 [GPS] e[34mTrying $PDTINFO (UM600)...
21:28:57.504 -> e[0me[34mDEBUG e[0m| 01:28:51 25 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:28:58.033 -> e[0me[34mDEBUG e[0m| 01:28:52 25 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:28:58.511 -> e[0me[34mDEBUG e[0m| 01:28:52 26 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:28:59.012 -> e[0me[34mDEBUG e[0m| 01:28:53 26 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:28:59.051 -> e[0me[34mDEBUG e[0m| 01:28:53 27 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:29:00.057 -> e[0me[34mDEBUG e[0m| 01:28:54 27 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:29:00.516 -> e[0me[34mDEBUG e[0m| 01:28:54 28 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:29:01.802 -> e[0me[33mWARN  e[0m| 01:28:55 29 [GPS] e[33mFailed to find GNSS Module (baudrate 57600)
21:29:03.636 -> e[0me[34mDEBUG e[0m| 01:28:57 31 [GPS] e[34mProbing for GPS at 115200
21:29:03.808 -> e[0me[34mDEBUG e[0m| 01:28:57 31 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:29:04.438 -> e[0me[34mDEBUG e[0m| 01:28:58 32 [GPS] e[34mTrying $PDTINFO (UM600)...
21:29:04.937 -> e[0me[34mDEBUG e[0m| 01:28:58 32 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:29:05.478 -> e[0me[34mDEBUG e[0m| 01:28:59 33 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:29:05.975 -> e[0me[34mDEBUG e[0m| 01:28:59 33 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:29:06.490 -> e[0me[34mDEBUG e[0m| 01:29:00 34 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:29:06.986 -> e[0me[34mDEBUG e[0m| 01:29:00 34 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:29:06.986 -> e[0me[34mDEBUG e[0m| 01:29:01 35 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:29:07.967 -> e[0me[34mDEBUG e[0m| 01:29:02 35 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:29:09.257 -> e[0me[33mWARN  e[0m| 01:29:03 36 [GPS] e[33mFailed to find GNSS Module (baudrate 115200)
21:29:09.257 -> e[0me[34mDEBUG e[0m| 01:29:03 36 [RadioIf] e[34mCompleted sending (id=0xeb21cb5d fr=0x3b to=0xff, WantAck=0, HopLim=3 Ch=0x8 encrypted rxtime=1729992537 hopStart=3 priority=10)
21:29:09.257 -> e[0me[34mDEBUG e[0m| 01:29:05 38 [GPS] e[34mProbing for GPS at 9600
21:29:11.219 -> e[0me[34mDEBUG e[0m| 01:29:05 39 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:29:11.994 -> e[0me[34mDEBUG e[0m| 01:29:05 39 [GPS] e[34mTrying $PDTINFO (UM600)...
21:29:12.452 -> e[0me[34mDEBUG e[0m| 01:29:06 40 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:29:12.959 -> e[0me[34mDEBUG e[0m| 01:29:06 40 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:29:13.519 -> e[0me[34mDEBUG e[0m| 01:29:07 41 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:29:14.031 -> e[0me[34mDEBUG e[0m| 01:29:08 41 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:29:14.031 -> e[0me[34mDEBUG e[0m| 01:29:08 42 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:29:15.005 -> e[0me[34mDEBUG e[0m| 01:29:09 42 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:29:15.505 -> e[0me[34mDEBUG e[0m| 01:29:09 43 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:29:16.846 -> e[0me[33mWARN  e[0m| 01:29:10 44 [GPS] e[33mFailed to find GNSS Module (baudrate 9600)
21:29:48.865 -> e[0me[34mDEBUG e[0m| 01:29:43 76 [GPS] e[34mProbing for GPS at 115200
21:29:49.134 -> e[0me[34mDEBUG e[0m| 01:29:43 76 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:29:49.822 -> e[0me[34mDEBUG e[0m| 01:29:43 77 [GPS] e[34mTrying $PDTINFO (UM600)...
21:29:50.280 -> e[0me[34mDEBUG e[0m| 01:29:44 77 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:29:50.780 -> e[0me[34mDEBUG e[0m| 01:29:44 78 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:29:51.328 -> e[0me[34mDEBUG e[0m| 01:29:45 78 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:29:51.786 -> e[0me[34mDEBUG e[0m| 01:29:45 79 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:29:51.826 -> e[0me[34mDEBUG e[0m| 01:29:46 79 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:29:52.807 -> e[0me[34mDEBUG e[0m| 01:29:46 80 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:29:53.306 -> e[0me[34mDEBUG e[0m| 01:29:47 81 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:29:54.581 -> e[0me[33mWARN  e[0m| 01:29:48 82 [GPS] e[33mFailed to find GNSS Module (baudrate 115200)
21:29:54.581 -> e[0me[34mDEBUG e[0m| 01:29:50 84 [GPS] e[34mProbing for GPS at 9600
21:29:56.608 -> e[0me[34mDEBUG e[0m| 01:29:50 84 [GPS] e[34mTrying $PDTINFO (UC6580)...
21:29:57.338 -> e[0me[34mDEBUG e[0m| 01:29:51 84 [GPS] e[34mTrying $PDTINFO (UM600)...
21:29:57.793 -> e[0me[34mDEBUG e[0m| 01:29:51 85 [GPS] e[34mTrying $PCAS06,1*1A (ATGM336H)...
21:29:58.294 -> e[0me[34mDEBUG e[0m| 01:29:52 85 [GPS] e[34mTrying $PCAS06,1*1A (ATGM332D)...
21:29:58.848 -> e[0me[34mDEBUG e[0m| 01:29:52 86 [GPS] e[34mTrying $PAIR021*39 (AG3335)...
21:29:59.344 -> e[0me[34mDEBUG e[0m| 01:29:53 87 [GPS] e[34mTrying $PAIR021*39 (AG3352)...
21:29:59.861 -> e[0me[34mDEBUG e[0m| 01:29:53 87 [GPS] e[34mTrying $PQTMVERNO*58 (LC86)...
21:30:00.346 -> e[0me[34mDEBUG e[0m| 01:29:54 88 [GPS] e[34mTrying $PCAS06,0*1B (L76K)...
21:30:00.389 -> e[0me[34mDEBUG e[0m| 01:29:54 88 [GPS] e[34mTrying $PMTK605*31 (L76B)...
21:30:02.182 -> e[0me[33mWARN  e[0m| 01:29:56 89 [GPS] e[33mFailed to find GNSS Module (baudrate 9600)
21:30:02.182 -> e[0me[33mWARN  e[0m| 01:29:56 89 [GPS] e[33mGiving up on GPS probe and setting to 9600.```
2

Welcome to the forum @Mk18

In which slots are you using the modules?

RAK12500 should be in Slot A or Slot D, otherwise Meshtastic does not find it.

3

Thank you, I have the GPS 12500 in Slot D. The other two (1901 and 1902) are in slots A and B.

4

Were you able to find anything about this problem I am having?

5

If you have RAK1902 in Slot B, then the interrupt line of the RAK1902 is controlling WB_IO2, which controls the power of the RAK12500.

Try RAK1902 in Slot A and RAK1901 in Slot B.

image
image1809×667 54.9 KB

6

It does work now, however at the moment when it updates the gps coordinates it immediately turns the device off and I have to either disconnect and reconnect the battery or press the reset button to turn it back on. I tried to see if it was interference with the modules but with just the 12500 on with the 4631 core it still does this. Is this something with the firmware or a hardware issue?

7

Hello.

Did anyone ever get an answer on this issue?

I seem to be having the same problem with the same equipment. I also have a RAK 19007, 12500, and 4631 running Meshtastic. I have a 1902 in slot A, the 1901 in slot B, and the 12500 in slot D. It works for a little while but will turn stop working after a bit, needing to be reset via the button or power cycled. I also noted that the heart beat LED goes solid green for a few seconds before it goes dead.

8

Welcome to RAK forum @mmalluck ,

There are few reports about this in Meshtastic discord. Without knowing the last log on the Meshtastic FW before it stops, it will be hard to pinpoint what causes the issue. It can be HW, SW or both.

9

I know this is an old topic but I ran into issues with Slot-D as well when populating it with GPS, as per manual it should go in either A or C (while C has no screw provisioning for a long module as per GPS RAK12500. I looked at the schematics of the 4631 module and noticed the NFC provisions on the slot D IO pins (io6 and io 5)

image
image931×465 74.2 KB

i’m running meshcore 1.16, at first the GPS board is detected but after that the entire device stops responding. removing the GPS from slot D revives the device. unfourtunatly also I have no logging

10

Welcome to the forum @DoubleU

The NFC is NOT provisioned, as you can see that L10 is NC (== not assembled).

Where did you see this? It is incomplete. On A RAK19007 it is Slot A or Slot D. On a RAK19003 Base Board, it is slot C. All of these slots can hold a long module.

What firmware are you trying to use?

11

Hi @beegee thanks for your response,

I’m using Meshcore 1.15 and 1.16.

since the GPS works fine in A or C and not D, I was looking at the datasheet and the schematics for a delta compared to the other slots,
I observed that most pins are the same (RX, TX i2c,…) execpt the two IO pins (used to enable the GPS) also I noticed the capacitors and coil (nc).

In firmware all 3 slots are probed (by enabling the device and query the module). The module is detected, while GPS is disabled in the settings the device is reponsive, when enabled the device becomes unreachble (it does not lock-up fully, BT led keeps blinking, BLE adverts arrive but up on connecting it generates a timeout. I also tried flashing the USB companion firmware but there it behaves the same.

I know this is a strange HW/FW interaction issue; I know from experience that these HW/FW issues can be a real pickle especially when different teams/org are working it

mechanically Slot D is the prefered location for the GPS, but installed it now in C with some tape

I was hoping to find here some kind of HW errata, that would hint for a fix

12

Both Meshtastic and MeshCore are using the serial interface of the GPS chip. Serial is only available in slot A and slot D of RAK19007 Base Board. Slot C will not work with these firmware, as there are not serial pins.

What Core module are you using? And are you sure you flashed the correct firmware?

13

Technical documentation for our modules can be found in our Documentation Center, but there are no specific guides for MeshCore.
We are not developing or maintaining the MeshCore firmware.

14

thanks again for your feedback. The GPS works fine now in Slot C (not secured with a screw unfortunately) with Meshcore 1.16

I checked the code and they init serial, but query I2C

image

Still Meshcore instability when GPS in slot D puzzles me, I’ll try to enable more serial debugging next time i open it up

15

Slot C works when you use I2C interface, but that is only for RAK12500, the newer RAK12501 has no I2C interface.