RAK WisBlock Sensors - firmware support?

I’m building about 6-7 WisBlock clients/routers and could use some help nailing down Sensor(s) configuation.

Specifically:

  • Is the Sensor currently supported by Meshtastic firmware and mobile apps?
  • Which Slots to use for each Sensor?
  • Any known conflicts between Sensors?
  • Any required settings in the Meshtastic app to enable Sensors?

When/if this info is collected, I’ll be sure to add it to the official FAQ page.

This is what I’ve been able to confirm so far. Please add any corrections and/or links to any available resources. Thanks!


WisBlock Base:

  1. WisBlock Base Board 2nd Gen - RAK19007
  • currently the preferred RAK base board for Meshtastic

WisBlock Core:

  1. Nordic nRF52840 BLE Core Module for LoRaWAN with LoRa SX1262 - RAK4631
  • currently the preferred RAK core for Meshtastic
  • supported by standard web flasher firmware

WisBlock Display:

  1. E-Paper Module Solomon Systech Limited SSD1680 - RAK14000
  • partial support when inserted into IO port of 19007 base board
  • possible conflict/issues with Lora transmission and GPS
  • not supported by standard web flasher firmware, requires “eink” variation of current firmware

WisBlock Sensors:

  1. GNSS GPS Location Module u-blox ZOE-M8Q - RAK12500
  • UART mode confirmed to work when inserted into Slot A of 19007 base board
  • i2c mode confirmed to work when inserted into Slots A or D of 19007 base board
  • when inserted into Slot A, module covers Slot B and requires the extension cable to regain use for other sensors
  • supported by standard web flasher firmware
  1. Temperature and Humidity Sensor Sensirion SHTC3 - RAK1901
  • confirmed to work with 19007 base board
  • UNCONFIRMED which Slot is required - Slot B, C, or D
  • UNCONFIRMED to be supported by standard web flasher firmware
  1. Barometric Pressure Sensor STMicroelectronics LPS22HB - RAK1902
  • confirmed to work with 19007 base board
  • UNCONFIRMED which Slot is required - Slot B, C, or D
  • UNCONFIRMED to be supported by standard web flasher firmware
  1. Environment Sensor BOSCH BME680 - RAK1906
  • confirmed to work with 19007 base board
  • confirmed to work when inserted into Slot C of 19007 base board
  • supported by standard web flasher firmware
  1. Radar Sensor RCWL-9196 - RAK12013
  • partial support when inserted into IO port of 19007 base board (no e-ink at the same time)
  • UNCONFIRMED to be supported by standard web flasher firmware
  1. 9DOF Motion Sensor TDK MPU9250 - RAK1905
  • UNCONFIRMED to work when inserted into Slot B, C, or D of 19007 base board
  • UNCONFIRMED to be supported by standard web flasher firmware
  1. PIR Motion Sensor Senba Sensing AM312 - RAK12006
  • UNCONFIRMED to work when inserted into Slot B, C, or D of 19007 base board
  • UNCONFIRMED to be supported by standard web flasher firmware
1 Like

I am using RAK 13011 Magnetic Switch to detect a door opening. It works when the detection module is set to monitor pin 17. It’s quite sensitive so make sure you don’t have yout phone, magnetised screwdriver or other ferromagnetic materials in the vicinity when testing, or you’ll get a lot of false positives.

The radar sensor also works well - I think the detection module is set to monitor pin 21 which has a 100Ohm pull-up. I had it in a small enclosure first and got lots of false positives. Now, with an enclosure about 10x7x5 cm it works perfectly.

I think it would be good to complete your list by including the pins that need to be monitored along with pullup on or off in the settings

Nice thanks for the detail. Yeah, I’m trying to collect as many config combinations as possible (slot+pin+settings). Can you confirm which Slots you used for both the magnetic switch and radar? Any settings required in the app?

I can’t edit the OP, so here’s a summary of the additional info I’ve come across, including yours in the previous post:

  1. Radar Sensor RCWL-9196 - RAK12013
  • PIN COMBINATION: IO Port + Pin 21 (100Ohm pull-up)
  1. Wisblock Magnetic Switch - RAK13011
  • confirmed to work with 19007 base board
  • UNCONFIRMED which Slot is required - Slot B, C, or D
  • UNCONFIRMED to be supported by standard web flasher firmware
  • PIN COMBINATION: Slot ?? + Pin 17
  1. Buzzer Module Jiangsu MLT-5020 - RAK18001
  • confirmed to work with 19007 base board
  • UNCONFIRMED to be supported by standard web flasher firmware
  • PIN COMBINATION: Slot C + Pin 21

I was able to get the RAK12006 PIR sensor to work with Meshtastic. I used pin 10, detect on low, use internal pull-up.

I have my troubleshooting posted at https://www.reddit.com/r/meshtastic/comments/1fortl9/wisblock_rak12006_pir_sensor/ and have also referenced your article from there.

Thanks for your tracking post here!

These two work simultaneously at least in the positions shown, I did not test any other slots.

Temperature and humidity sensor: RAK Temperature and Humidity Sensor Sensirion SHTC3 SKU: 100001 Temperature and Humidity Sensor | Temperature Sensor | SHTC3 Sensor
Current and voltage measurement device: DC Current Sensor 3A Texas Instruments INA219BID RAK16000 WisBlock Interface Module | Wireless LoRa/ LoRaWAN Current Sensor

Important note about the “radar” sensor: I’ve been working with it for over a year, and I’ve found a situation that causes false triggers. This is obviously dependent on a lot of factors, but if you’re experiencing false triggers from the motion sensor, try reducing your LoRa tx power. When the LoRa antenna is in close proximity to the RCWL0516 (which is really what this is), TX power in excess of ~10dBm can cause intermittent false motion detection.

The best solution I’ve found if you need to run higher TX power is to relocate the LoRa antenna away from the nearfield of the motion detector. It’s usually easier to relocate the LoRa antenna than to relocate the motion detector because of the ribbon cable needed to move the WisBlock sensor off the base board. I haven’t experimented with that yet, but I would bet the ribbon cable will act as an antenna and exacerbate the issue unless the antenna is also relocated away from the entire assembly.