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
  • 1. Read the User Guide and the Step-by-step guide
  • 2. Import credentials into the backend
  • 3. Check you have proper coverage
  • 4. Exiting Factory mode
  • 5. Arming (can be done immediately or in the field)

Was this helpful?

  1. PROVISIONING AND DEVICE SETUP

Step-by-step provisioning

Before deployment, you need to do several steps that differ slightly whether LoRaWAN/Helium is used

1. Read the User Guide and the Step-by-step guide

2. Import credentials into the backend

3. Check you have proper coverage

4. Exiting Factory mode

Sigfox

  1. Exit factory mode on one device

  2. Watch the blinking pattern

  3. Check at Sigfox backend whether the message was properly received and by how many base stations

  4. Check in the IoT platform

  5. Record into Project/provisioning document

  6. Once you activate and prove the 3 devices are working properly, you can either proceed with the rest in small batches or wait with the device arming for field installation

  7. After the batch provisioning check the backend, platform, and record into the project document.

LoRaWAN

  1. Exit factory mode on one device (unless previously exited)

  2. Watch the blinking pattern

  3. The device is trying to join the network with the message sent attempts 5 times on different data rates. If not successful - joining is blocked for 4 hours (this blocking period may be canceled by button/magnet press).

  4. Check at the LoRAWan/Helium backend whether the device has joined

  5. If the device is not properly joined it blinks red 3 times - pause - red 3 times

  6. You can force another join by short press

  7. Check in the IoT platform

  8. Record into Project/provisioning document

  9. Repeat for additional 2 devices

  10. Once you activate and prove the 3 devices are working properly, you can either proceed with the rest batch-wise or wait with the device arming for field installation

  11. After the batch provisioning check the backend, and platform, and record them into the project document

5. Arming (can be done immediately or in the field)

Ideally, arm 3 devices step by step, prove the functionality and behavior and arm the rest of the device during installation

  1. Arm one device (unless the auto arm is enabled)

  2. Watch the blinking pattern

  3. Check at the backend whether the message was properly received and by how many base stations

  4. Check in the IoT platform

  5. Record into Project/provisioning document

  6. Check the desired functionality

  7. Check in the backend whether the message was properly received and by how many base stations

  8. Check in the IoT platform

  9. Record into Project/provisioning document

  10. Once you arm and prove the 3 devices are working properly, you can either proceed with the rest batch-wise or wait with the device arming for field installation

  11. After the batch arming, check the backend, and platform, and record them into the project document.

PreviousPrerequisitesNextPhysical Installation

Last updated 1 year ago

Was this helpful?