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
  • Introduction
  • A. Working SIM Card
  • B. Connectivity to the Sigfox network with a special contract
  • C. Proper configuration setup in Sigfox Backend and CheckFox dashboard
  • C.1 CheckFox dashboard user, company and device registration
  • C.2 Sigfox backend setup
  • D. Firmware update
  • Additional useful info

Was this helpful?

  1. SIMPLE/API 6 GENERATION
  2. Device Overview
  3. Device Documentation
  4. CheckFox

Starting with the CheckFox and the CheckFox Dashboard

PreviousCheckFoxNextAll You Need to Know About the SIM Card in Your CheckFox and GSM connectivity

Last updated 3 years ago

Was this helpful?

Introduction

You need 4 things to get started with your CheckFox:

A. A working SIM card

B. Connectivity to the Sigfox network with a special contract

C. Properly configured Sigfox backend and CheckFox dashboard (this guide is relevant for Sigfox API V2 released March 2020)

D. Latest firmware in your device (can be updates OTA)

Let’s elaborate a bit more on each of the steps.

A. Working SIM Card

Every new CheckFox is now being dispatched with a global €10 prepaid SIM card so you don't have to disassemble the device. The SIM card has to be activated and you can find the guide for that .

Don't forget to change the APN if you want to use your own SIM card, that is operator-specific!

B. Connectivity to the Sigfox network with a special contract

We no longer offer Sigfox connectivity as majority of CheckFox users wanted to use their own. If you do not have your own connectivity, you can get it from your or buy it at (please note that buying from buy.sigfox.com is available for some countries only, if you do e.g. international tracking, it's preferable to buy the connectivity from your local SO).

In order to get Basestations IDs, RSSI and repetitions you need to ask your Sigfox operator to enable meta data on your contract (NETWORK METADATA contract option). Without meta data neither the dashboard nor Sigfox will work. It is a free service. If you are a Sigfox operator yourself, see step C.26.

C. Proper configuration setup in Sigfox Backend and CheckFox dashboard

In order for the device to work correctly, please take the following steps. It should take no longer than 5 minutes.

C.1 CheckFox dashboard user, company and device registration

  1. Login with your Google account (we only collect email addresses and other ways of authentications are planned for the future)

  2. Once logged in, enroll your company by filling in its name

  3. Now you need to login with your Google account again

  4. Add your Checkfox by clicking on the Devices tab and pressing New

  5. Add additional users by clicking Users and entering their emails (optional)

C.2 Sigfox backend setup

  1. Go to Groups and click on New - you need a separate group for your CheckFox(es)

  2. When the new group is created, you need to go to the API access tab and there, create a new API access and give it following rights:

    • CUSTOMER [R] in order to see messages (DEVICE [R] should be sufficient as well)

    • OPT_INTEGRATOR in order to see IDs of base stations and repetitions

    • COVERAGE TOOL in order to see and use the coverage API

    • If you are a Sigfox operator, you can also give it:

      • OPT_STATION_LOCATION in order to see location of BTSs and distances) - group must be created directly under the Sigfox Operator group and not under a subgroup.

      • OPT_STATION_INSTALLATION in order to see meta data as metadata cannot be enabled on Sigfox operator group contract. If you are using a subgroup contract, let Sigfox enable network metadata on your contract.

Location of basestations is not public information. Only Sigfox operators using their APIs and configuring CheckFox Dashboard properly can see the precise location and distances of basestations.

  1. Now back in the CheckFox dashboard, input the API login and password into the Company settings tab and save your credentials (you can find them in the API access list)

  2. Under your new CheckFox group in the Sigfox backend, create a new Device type and name it accordingly (e.g. CheckFox_companyname_internal)

  3. Go to the Information tab of your new Device type and hit Edit on the top right

  4. Switch the Downlink type to Direct and input sixteen 0s 0000000000000000 into data and hit Ok - this is necessary for the device to function properly

  5. Go to Callbacks and then create custom callbacks according to the specifications below:

DATA CALLBACK

Parameters

Type

DATA, UPLINK

Channel

URL

URL pattern

https://checkfox.simplehw.eu/api/scbmeasurement?type=uplink

Use HTTP method

POST

Send SNI

Check this

Headers/Header

Authorization

Headers/Value

Unique per company - found in the dashboard in Company settings

Content type

Application/json

Body

{
  "device":"{device}",
  "time":"{time}",
  "data":"{data}",
  "seqNumber":"{seqNumber}"
}

SERVICE CALLBACK

Parameters

Type

SERVICE, DATA_ADVANCED

Channel

URL

URL pattern

https://checkfox.simplehw.eu/api/scbmeasurement?type=data_advanced

Use HTTP method

POST

Send SNI

Check this

Headers/Header

Authorization

Headers/Value

Unique per company - found in the dashboard in Company settings

Content type

Application/json

Body

{
  "device":"{device}",
  "time":"{time}",
  "data":"{data}",
  "seqNumber":"{seqNumber}",
  "lqi":"{lqi}",
  "fixedLat":"{fixedLat}",
  "fixedLng":"{fixedLng}",
  "operatorName":"{operatorName}",
  "countryCode":"{countryCode}",
  "deviceTypeId":"{deviceTypeId}",
  "computedLocation":{computedLocation},
  "duplicates":{duplicates}
}

D. Firmware update

After you've setup the callbacks, please update the firmware.

  1. Before you start, make sure the battery voltage is at least 3,9V

  2. Go to Service menu

  3. Select Firmware update

  4. The device will now download the latest firmware - the size is 64 kB so it will take about 3 minutes

  5. After it's done, go to Service menu and then About to confirm the firmware has been updated

Additional useful info

Go to

Go to and login with your Sigfox credentials

If you don't have access to the rights, ask you local Sigfox operator, you can also find API credential documentation and tutorial provided by Sigfox

your CheckFox as a new device under this Device type (register the device as a prototype, more can be found ); for this step, the ID and PAC of your CheckFox is required (you should have it in your inbox or you can find it in the device if you go to Service menu and then About)

If you are experiencing any issues please use the .

here
local Sigfox operator
buy.sigfox.com
checkfox.simplehw.eu
backend.sigfox.com
here
Register
here
CheckFox troubleshooting guide
CheckFox Uplink Payload Description
CheckFox Log Data Interpretation
CheckFox Dashboard Data Export