[Bug]: RAKwireless GNSS GPS Location Module u-blox ZOE-M8Q crashes firmware when not in Slot A about firmware HOT 11 CLOSED

You need to set the button GPIO to something; unset uses the default value of 9, which corresponds to IO5, which is within the slot D connector and will end up with GPS data getting sent to it and resetting your node. This is why the meshtastic docs at https://meshtastic.org/docs/hardware/devices/rak/peripherals/?rakmodules=GPS recommend using slot A. If you set that value to something else that isn't within the slot D connector (e.g., if you aren't using a button, it works to set it to 255 or something similarly inaccessible, as I understand it), then slot D works fine.

from firmware.

You need to change the user button GPIO to use a slot other than a

from firmware.

I have no GPIO enabled, or connected. Just the GPS and a Temp/Humid sensor from RAK.

from firmware.

If it works on other ports (with caveats) can the docs be updated?

from firmware.

Io5 is the default user button, feel free to update the docs, there is an edit link on every page.

from firmware.

@garthvh Help me out here please, and just explain things a little more.

So in the Meshtastic App (iOS) everything is GPIO pins.

• Under Device Config, both Button GPIO and Buzzer GPIO are Unset
• Under Canned Messages, again Pin A, Pin B, and Press Pin are all Unset
• Under External Notification this is disabled

Are you saying that the GNSS should work fine in Slot D or am I missing a setting somewhere?

from firmware.

Thank you! That's really helpful.

Will give this a go and see if that resolves my issue.

from firmware.

Personally I wouldn't consider this issue closed, as I haven't found if thats fixing my issue. Also, why is the GPIO User Button mapped to Slot D, when the user expandable GPIO for the RAK board is on the IO slot.

Maybe the defaults for this board type need changed, and re-mapped by default to not cause a default conflict between manufacturer documentation, and Meshtastic documentation/defaults?

from firmware.

Also, does anyone have any clear documentation as to which GPIO pins are mapped to which SLOTS, as to not cause an issue elsewhere.

from firmware.

This is a modular IoT system you are using any slot other than A for the gps you need to check the data sheet for each module and slot. Feel free to update the docs.

from firmware.

Also, does anyone have any clear documentation as to which GPIO pins are mapped to which SLOTS, as to not cause an issue elsewhere.

RAK has excellent documentation, data sheets are available on their site.

from firmware.