The Application Layer (left) of our Driver exposes LoRaWAN Functions to Application Firmware ... Join Network, Open/Close Port, Transmit/Receive Packets

github.com/lupyuen/bl_iot_sdk/

OS has a Command-Line App that calls the Application Layer of the LoRaWAN Driver ... We shall port this app to too
mynewt.apache.org/latest/tutor

The Node Layer (centre) in our Driver handles the networking operations for our BL602 LoRaWAN Node ... It's called by the Application Layer (left)

github.com/lupyuen/bl_iot_sdk/

What's MCPS in the Driver? ... That's the "MAC Common Part Sublayer", which is defined in the Semtech LoRaWAN Stack

stackforce.github.io/LoRaMac-d

Semtech Stack is structured according to IEEE 802.15.4 ... Yep LoRaWAN shares the same legacy as Thread, Zigbee and 6LoWPAN! We shall port this Legacy to

en.wikipedia.org/wiki/IEEE_802

The Medium Access Control Layer (right) of our Driver implements the LoRaWAN Protocol: Encryption, Receive Window, Duty Cycle, ... It exposes the MCPS Messaging Interface (IEEE 802.15.4) to the Node Layer (centre) via an Event Queue

github.com/lupyuen/bl_iot_sdk/

The Protocol is explained in this thread: Encryption, Receive Window, Duty Cycle, ...

qoto.org/@lupyuen/105874847933

Curiously, our Driver includes a Command-Line Interface (bottom) that Transmits and Receives LoRa Packets ... Directly calling the SX1276 Driver 🤔

github.com/lupyuen/bl_iot_sdk/

What's an Mbuf? Why is it used by our Driver? Mbufs are Chains of Fixed-Size Blocks ... Works great with little RAM (no fragmentation) ... Created for BSD Unix in 1983!

mynewt.apache.org/latest/os/co

...Which explains why so many folks at STMicro are now reading this Thread

😉

Yep "pbuf" from the Lightweight IP Stack can be used instead of Mbuf ... We just need to shift the Header / Payload Pointer to work on Packets

github.com/lupyuen/bl_iot_sdk/

Reference Implementation of Semtech Stack is here ... Includes drivers for SX1262 and SX1276

github.com/Lora-net/LoRaMac-no

Bought the RAKwireless Gateway: Developer D4H ... Will benchmark this with LoRa Gateway (Also based on RAKwireless RAK2287)

docs.rakwireless.com/Product-C

on RAKwireless can generate random Application Keys for Over-The-Air Activation (OTAA) ... We shall use keys to activate our and devices wirelessly

thethingsindustries.com/docs/d

Something (or Someone) is transmitting Packets every minute ... Signal Strength (RSSI) shows that they're a few hundred metres away

gist.github.com/lupyuen/8dacf0

Based on earlier Coverage Testing (with and ) ... High chance that our Mystery Transmitter is at the nearby Subway Station 🤔

lupyuen.github.io/articles/wis

Someday I might walk around with RAKwireless to find the Mystery Transmitter ... But for now let's test WisGate with WisBlock and BL602!

docs.rakwireless.com/Product-C

Show newer

@lupyuen
You need to think of secu now. Who is and who isnt allowed on the net. Either no entrance from blacklist or whitelist guests only allowed.

@lupyuen
One more hint. Try to measure signal strength and drive around with detector and record gps plus power detected.
That should help to narrow it down.
Good luck.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.