Simple Hardware knowledge base
  • Welcome
  • Simple HW
  • CHAT
  • HOW TO PURCHASE THE DEVICES
    • Whom do we sell to
    • Pricing
    • Ordering and payment
    • Delivery
    • Shipping
    • Batteries shipping
      • Lithium transportation
    • Guarantee
    • Tracking
    • Packaging
    • Accessories
    • Documentation
    • Qualified and premium partners
    • Customization
      • Custom branding
      • Custom hardware and software
      • Custom device settings from the factory
    • Customer Portal
  • PROVISIONING AND DEVICE SETUP
    • Prerequisites
    • Step-by-step provisioning
    • Physical Installation
    • Reconfiguration of the devices
    • Troubleshooting
      • Troubleshooting process
      • Steps to troubleshoot:
    • Quality control
  • PRE-SALES SUPPORT
    • Radio zones and power
    • Whitepapers
      • Tapes whitepaper
      • Machine Monitoring Whitepaper
      • Location tracking whitepaper
      • Shock/Drop Detection Whitepaper
      • Reed Switch Whitepaper
      • Temperature (cold chain) monitoring whitepaper
    • Impact and Fall Protection Rating Test
    • Webinars
    • Blog posts
    • Datasheets and certifications
  • LPWAN
    • SIGFOX
      • Introduction to Sigfox
      • Connect to Sigfox
      • Sigfox coverage
      • How to Access Data From Your Devices
      • Monarch - Multizone Devices
      • Sigfox Support
      • Devices Ideal for Sigfox Atlas Tracking
      • Geolocation precision and possibilities
    • LoRAWAN
  • SENSORS
    • Button
      • Button in API 6
    • Accelerometer
    • Magnetometer
    • Reed switch
    • WiFi module
    • Gas
    • Dry switch
    • Leak
    • Light
    • Dry Switches
    • Temperature & Humidity sensors
    • Temperature Reaction Time
    • Devices for Temperature and Humidity Monitoring
  • NEXT/API 7 GENERATION
    • Introduction
  • SIMPLE/API 6 GENERATION
    • API 6
      • Before integrating API 6 devices
      • Overview For Beginners
      • Overview for Experts
      • Device states
      • WiFi User Modes
    • User Modes
      • Mode-Independent Information And Events
        • Heartbeats
          • Heartbeat 1 and Heartbeat 2
          • Heartbeat 3
        • Appended payload
        • Alerts
        • Sensor-triggered mode-independent events
        • Analog monitoring independent events
        • Other mode-independent events
      • Standard User Modes
      • Wifi User Modes
        • Press me WiFi
        • Guard me WiFi
        • Track me WiFi
        • Trace me WiFi
        • Don’t drop me WiFi
        • Reed switch on/off WiFi
        • Light on/off WiFi
        • Temperature threshold alert WiFi
        • Temperature change alert WiFi
      • Wifi Atlas User Modes
      • Wifi SuperLocal User Modes
        • Press me WiFi SuperLocal
        • Guard me WiFi SuperLocal
        • Track me WiFi SuperLocal
        • Trace me WiFi SuperLocal
        • Don’t drop me WiFi SuperLocal
        • Reed switch on/off WiFi SuperLocal
        • Light on/off WiFi SuperLocal
        • Temperature threshold alert WiFi SuperLocal
        • Temperature change alert WiFi SuperLocal
    • Uplink
    • Downlink Information
    • Encoding
      • 8 binary flags (byte bits)
      • SimpleTime
      • SimpleTemp
        • Here are all the SimpleTemp true temperature values
        • Here are all the SimpleTemp temperature hysteresis values
      • Accelerometer Data
      • Magnetometer data
    • API 6 Reset Triggers and Configuration Loss
    • API 6 Table
    • Factory Mode
    • Device Overview
      • Device Documentation
        • SimplePack
          • Legacy
            • SimplePack 2.0 Introduction
            • SimplePack 2.0 Accelerometer Lockout (Continuous Triggering Error)
            • SimplePack 2.0 User Modes (API 5)
            • SimplePack API 2, 4, 5 and 6 comparison
        • SimpleLeak
        • SimpleIndustry And SimpleMeter
          • SimpleIndustry
          • SimpleMeter
          • Battery Replacement
            • Battery Replacement in SimpleIndustry and SimpleMeter Devices
          • SimpleIndustry CO2 or SimpleIndustry CH4 Sensors
        • CheckFox
          • Starting with the CheckFox and the CheckFox Dashboard
          • All You Need to Know About the SIM Card in Your CheckFox and GSM connectivity
          • CheckFox Device User Guide
          • Sigfox Coverage Measurement Methodology With the CheckFox
          • CheckFox Troubleshooting Guide
          • Advanced
            • Technology Used to Run the CheckFox Dashboard
            • CheckFox Dashboard Data Export
            • CheckFox Log Data Interpretation
            • CheckFox Uplink Payload Description
      • Basic operations
        • SimplePack and SimplePack Plus: Basic operations
        • SimpleLeak: Basic operations
        • SimpleMeter/SimpleIndustry: Basic operations
        • What should you see on the Sigfox Backend
    • Working With Devices
      • Device Registration
      • Device Certificates
      • Device Downlink
      • Correct Device Placement
      • Radio Zone Switch
      • Battery longevity and levels
      • Magnet Range for SimplePack 4.0 Plus Motion & Door Sensor and others
        • Magnet: 30×10×1 (magnetic force: 1.1 kg)
        • Magnet: 40×13×1 (magnetic force: 1.5 kg)
        • Magnet: 20×10×2 (magnetic force: 2 kg)
        • Magnet: 30×10×2 (magnetic force: 2.6 kg)
        • Magnet: 30×15×2 (magnetic force: 3.3 kg)
        • Magnet: 40×20×10 (magnetic force: 20 kg)
    • IO Frog
      • First Message
      • Tracing
      • WiFi Tracing
      • Door Monitoring
      • Luggage Monitoring
      • Office Chair Monitoring
      • Leak Detection
      • Temperature Monitoring
      • Public Channel Setup
      • Manhole Cover Monitoring
  • TECHNICAL SUPPORT
    • Contact Support
    • RMA Process
      • Create RMA Number
    • Sigfox Backend Access
    • IO Frog Access
    • Consulting Services and Senior Project Management
Powered by GitBook
On this page

Was this helpful?

  1. LPWAN
  2. SIGFOX

Monarch - Multizone Devices

PreviousHow to Access Data From Your DevicesNextSigfox Support

Last updated 3 years ago

Was this helpful?

Because of global regulations, Sigfox currently uses 7 different .

A Sigfox device will transmit properly only in the RC zone it is currently set up for - the messages will not be delivered in other zones because of the difference in transmission frequency. When leaving one RC zone and entering another, it would make sense for Sigfox devices created for global tracking to be able to switch the radio configuration they transmit in.

In order to do so, these features have to be enabled:

  1. The antenna needs to be able to transmit in the desired RC zones

  2. Switching between the RC zones has to be supported

  3. A trigger for RC zone switch has to be defined

There are several ways the RC zone change can be triggered:

  • Manual - through a switch/button, human action that’s not remote in general

  • Time - the easiest one, if you know that the device is leaving a port you can tell the device to switch to another radio zone in 2 days

  • GPS - if the device has a GPS module, you can program the device to switch the zones when it reaches a zone border

  • World Time Code emitter - you can listen to it and switch the RCZ based on location

  • WiFi beacons - if you have a predefined trajectory and are able to put managed WiFi beacons at transition points, you can use them to switch the zones

  • Monarch - a system of beacons provided by Sigfox that transmit a Monarch RCZ zone information each 5 minutes and are located at maritime ports and airports and also at the final destination - factories, warehouses etc. Beacons are integrated into all types of regular base stations.

The major issue with Monarch is that the beacon is currently only available at ports and not anywhere else. So it’s necessary to somehow detect that the device is at the port and start Monarch listening. Or the device has to be listening all the time.

Listening all the time can be configured based on the knowledge of how long the device stays around the beacon/port/airport. If the device stays there for at least one day, it is enough to listen only once a day. If it's going to be around the beacon for only 2 hours, it has to be set to listen to Monarch every 2 hours. Etc.Info

With the SimplePack, each Monarch listening consumes roughly the same energy as 40 messages. (So we can listen once a day for 1000 days).

You can also set the device to start listening to Monarch only after a certain time period (this is helpful to save the battery).

If you enable Monarch listening at ports/airports only, you can detect them by:

  • GPS boundary/position

  • barometric trigger landing/taking off of the airplane

  • barometric trigger lifting by few meters and loading/unloading the containers

  • accelerometer detecting the taking off and landing of the airplane

Monarch is NOT an automatic worldwide trigger and needs complete Discovery or a very use case specific approach.

radio configurations