ID & Payload Extractor

The purpose of this design is to let partners use it in end of “Sigfox device” production line to check which ID is in which final product.

It can also check if the device is working correctly after the final assembly (sensor + casing + Sigfox Module) thanks to the payload decoding.

ID & Payload Extractor

You will find some usecases as examples : 

  • when sigfox device is based on Sigfox verified module, or SIP, or SOC (many modules does not allow designer to use a local radio loop added to sigfox link for instance)
  • when the Sigfox device is waterproof, or do not have any external connectors after assembly
  • when the Sigfox device have a complex assembly with some sensor connected in the last step of manufacturing (manual wiring for Instance)
  • when all the components, including sigfox module are assembled without any ID tracking during the device production

In the cases listed above, it can be interesting to have this tool to be sure the device is working properly without any wiring problem, and track the ID out of the factory.

For sure, there are many ways to manage these issues, but most of them are human based.

Also, Device maker may choose some other proprietary ways (local communication loop) to manage theese issues (can be compliant with the device transceiver).


"Payload & ID extractor" is a simple, low perf, and really cost efficient radio receiver to sniff some Sigfox RF packets.

It Receives Sigfox BPSK Radio packets and retransmit ID and payload over a low power UART link.

This receiver, with the actual configuration, is -15dBm to +15dBm capable. (usable range is few cm or tens of cm)

This tool will check Integrity of the frame before sending  ID and Payload over UART link. 

Device maker can have different production lines separated by few meters, and this tool is able to limit range only to one production line.

Payload & ID extractor board example


The proposed design is compatible with Sigfox BPSK signals at 100 & 600bps (tight baudrate tolerance (~+/-1% ))

The proposed design is not frequency sensitive : 860-930Mhz (All RC)

Use :

Device maker will see according the schematics that it's powered in 3,3v, this board have an antenna port (Device maker can put any antenna, but carefully not to have too much range in order not to receive other production lines). (it also be used together with coupler or somehing like that that may help you to check at the same time the radiated power of your DUT after correlation with working parts or calibration.)

User will receive data on a Low voltage UART that can be connected to PC thru a FTDI or any UART to RS232 transceiver; This will let him use some script to manage ID & Payload.

Data Format:

This is the ASCII content transmitted on LowPower UART:


XXXXXXXX: 4bytes Hexadecimal Sigfox Identifier (no authentication)

YYYYYYYYYYYYYYYYYYYYYYYY: Up to 12 Bytes Frame payload 

Limitations :

Traditional BPSK modulation only  / Not compliant on constant amplitude modulations

This small tool cannot authenticate the frame. (this can only be achieved thru Sigfox Network)

This will not be able to detect an issue on the frequency, baudrate configuration, RC configuration etc…!

The only purpose of this tool is to check/test device in end of production line. Any other use would be a breach of the licence agreement.

This design has not been certified in any certification and user (device maker) is responsible for the correct use according to the licence agreement and the local regulation.(use in Faraday cage for instance)


There is currently no support for this tool. However, the design has been proven to work and we hope it is simple enough for partners to to adapt, integrate and use in their production test bench easily.


Hardware parts:

  • Schematics of the board
  • Gerber Files to produce the board as is.
  • BOM File group by parts
  • BOM File group by value

Software part:

  • Binary file to flash the PIC MCU
ID & Payload Extractor package

You need to sign up or log in to access to this information.