Only available for Logged-in member. Please login or register to access this information.Or use the Temporary User that we have provided to you via email.
expiry time
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSSFC-MA is the modular design Sigfox wireless sensor, based on 10-year experience in design and manufacturing Industrial sensor of Daviteq Company. It can accepts the analog output signal 0-20mA from any sensor, transmitter... It can supplies the power to external sensor at 15VDC @ 50mA max. With Ultra-low power design and smart firmware allow the complete Wireless and Sensor package run on a Single battery C type up to 10 years. WSSFC-MA can support all regions of Sigfox network in over the World, RC1, RC2, RC3, RC4, RC5, RC6, RC7.
How the sensor connect to system?
System components:
The end nodes are Sigfox-Ready Sensors or Actuators;
The Sigfox Base Stations (installed and operated by Sigfox Operator);
The Sigfox Back-End (Operated by Sigfox Company);
The Application Server is the destination software users want to utilize the data from/to Sigfox-Ready sensors/ actuators.
How do you set up the Sigfox-Ready device and get its data to the Application Software? Please follow these steps:
Contact the local Sigfox Operator to sign a Data plan contract. You will be provided an account;
Log in to the Sigfox Back-end by your own account then add the Sigfox-Ready Devices. Please follow the guidelines of Sigfox back-end;
Configure the callback or data forwarding from the Sigfox Back-end to the Application Software. Please follow the guidelines of Sigfox back-end;
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.
1.2 Application Notes
For Applications
Process Monitoring, Safety Monitoring
Notes
mA sensor power supply: Check transmitter output of 15 VDC to match mA sensor if sensor power source is from transmitter
Accuracy and resolutions: Check whether those meet the requirements
Environmental Conditions: Account for temperature, humidity, and other environmental factors.
Mounting and Enclosure: Determine the mounting method and enclosure type.
Compatibility: Ensure compatibility with your existing system or sensors.
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device;
Case 2: Then, in every interval time (pre-configured), for example, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval (default is 10 minutes) if the Alarm state still exist;
Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s;
Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration
1.4 Default Configuration
This MA node has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node (converter + wireless) delivers the proper output value. Please check the Payload document for more information.
1.5 Battery/ Power Supply
The Device uses below batteries:
Battery type: Primary battery
Battery size and Voltage: AA 1.5 VDC
Number of batteries: 02
Recommended batteries: Energizer® L91 or equivalent from Duracell;
Please take note on the Polarity of the batteries as below picture.
Re-install the housing, pay attention to put the PCB edge into the middle guiding slot of the box inside as shown below)
Understanding the battery levels:
Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%
1.6 What's in the Package?
1.7 Guide for Quick Test
With the default configuration, the device can be connected quickly to the Sigfox Network by the following steps.
Step 1: Prepare the values of communication settings
Device ID: Get Devive ID on the device nameplate
Device PAC: Get Devive PAC on the device nameplate
Note: All Sigfox sensors are pre-configured with the correct RC before delivery. The settings of Device ID, Device PAC, and RC could also be read from the device memory map. Please reference Section 3.2 Sensor configuration for details.
Step 2: Add the device to the Sigfox Backend
Please refer to the below Section 1.10 for details.
Step 3: Install the batteries to the device
Please refer to Section 1.5 above for instructions on battery installation.
After installing the battery in 60 seconds, the first data packet will be sent to the Sigfox network. After receiving the first data packet, the time of another packet depends on the value of the parameter: CYCLIC_DATA_PERIOD. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.
Note:
If the device is required to connect to the external power, the correct external power supply must be connected to the device power connector. Refer section 1.8 INSTALLATION for details of the power wiring
If the device is required to connect to external sensor, the connection must be implemented before power up. Refer section 1.8 INSTALLATION for details of the wiring
If device is required the calibration for correct measurement, the calibration must be implemented. Refer detail at section 3.3 Calibration/ Validation.
Step 4: Decode the payload of the receiving package
Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.
1.8 Installation
Dimension Drawings and Installation Gallery (Photos and Videos)
Please follow the checklist below for a successful installation:
1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
3. Have the device been configured properly as per Section 3.2 below?
4. Have the device been calibrated or validated as per Section 3.3 below?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.
Installation Notes for Sensor Part (if available)
Recommend using the shielded cable with twisted pairs;
Avoid the installation near by the high magnetic field like high power Motors, Transformers, and Power Generator.
Following right wiring connections based on 0-20 mA sensor
Note:
DO NOT CONNECT AN EXTERNAL POWER SUPPLY TO THE PWR + WIRE OF THE WIRELESS SENSOR !!!
SUPPLYING AN EXTERNAL POWER SUPPLY TO THE SENSOR'S PWR + LINE CAN MAKE SERIOUS DAMAGE !!!
4. Following wiring label as below
Installation Guide for Main Device
Check the Location for the best RF Signal
Make sure the site is good enough for RF signal transmission.
Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the Sigfox Node and the Base Station. In real life, there may be no LOS condition. However, the Node still communicates with the Base Station, but the distance will be reduced significantly.
DO NOT install the wireless Node or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Mounting the Device on the Wall or Pole
Mount the Node onto a wall by the mounting bracket with provided bracket and screws.
Sigfox main device/node is connected to 0-20 mA sensor via M12 female connector.
Sample installations of the 0-20 mA sensor and main device as below:
1.9 Payload Document and Configuration Tables
Please click below button for:
-
Payload decoding of Uplink messages;
-
Payload encoding of Downlink messages;
-
Configuration Tables of device.
Note:
If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.
1.10 How to connect device to Back-end/ Network Server/ Coordinator
This instruction is applied to all kinds of Sigfox-Ready sensor produced by Daviteq.
Step 1: Log in to the sigfox backend website
Step 2: Click on Device
Step 3: Click New → Select a group
Step 4: Fill in the required information
Note: Some of our products may not have end product certification in time, to add the product to Backend Sigfox please follow the steps below.
Click on the text as shown below
Check the box as shown below to register as a prototype
2
MAINTENANCE
2.1 Troubleshooting
Please find below steps to identify the problems from Communication Part or Sensor Part:
* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;
* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.
Please refer below the troubleshooting guide for Communication and Sensor Part.
Troubleshooting for Communication
Troubleshooting for Sensor Part (if available)
The output value is always zero
The sensor cable is broken
No 0-20 mA sensor is installed
Loose connection between the MA node and 0-20 mA sensor
The 0-20 mA sensor is defective
The MA node is defective
High cut setting is configured to 0
The output value of the MA Node sometimes fluctuate when mA input is unchange
Loose connection between the MA node and 0-20 mA sensor
The 0-20 mA sensor is defective
The MA node is defective
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of Sigfox Device except:
1. The battery needs to be replaced. Please check the battery status via uplink messages;
Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.
Maintenance for Sensor part (if available)
There are no moving parts or consumed parts in the MA Node. Therefore there is no need to do maintenance.
However, depending on the installation environment, the MA Node must be checked periodically for accurate ADC converter.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSSFC-MA | FW 2
Daviteq Sigfox Current Input (MA) Sensor comprises 02 parts linked internally:
• The Daviteq Sigfox wireless transmitter;
• The Daviteq Current Input (MA) module
What are the primary output values?
• RAW VALUE: Raw value of sensor. This parameter equals RAW_VALUE in the uplink payload
• SCALED VALUE: Scaled value of RAW_VALUE, unit mA, used for alarm
SCALED_VALUE= (CONSTANT_A x RAW_VALUE) + CONSTANT_B
Where CONSTANT_A, CONSTANT_B are configured in the sensor memory map.
This parameter equals SCALED_VALUE in the uplink payload
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
• Battery level (%): the remaining capacity of the battery. The parameter in the payload is BATTERY_LEVEL.
• Number of consecutive Alarm: The number of consecutive alarm message. This parameter in the payload is TENTATIVE. TENTATIVE will be reset to 0 when previous message is alarm and current message is cyclic. If the number of continuous alarm messages are greater than 255, the Tentative keeps value of 255. This parameter equals TENTATIVE in the uplink payload
• Alarm: alarm status of the device. The parameter in the payload is ALARM
• Sensor current configurations: current main settings of the sensor and this parameter in the payload is LATEST_SIGFOX_DOWNLINK
• Sensor hardware version: hardware version of the sensor and this parameter in the payload is HW_VERSION
• Sensor firmware version: firmware version of the sensor and this parameter in the payload is FW_VERSION
Principle of operation
Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.
*** This Measure_Period will affect the energy consumption of the device.
The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life. After finishing the measurement cycle, the device can read all the measured parameters.
Main parameter for alarm is SCALED VALUE
If parameter ALARM_ENABLE = 1
Then the device will compare the main parameter with the Low Alarm Setpoint and High Alarm Setpoint.
After comparison, the devices will have 03 statuses:
No_Alarm;
Low_Alarm
High_Alam.
How the device send uplink message base on above 03 states?
If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;
If Device state is changed from No_Alarm to Low_Alarm or Hi_Alarm, it will send alarm message immediately. Please check the below picture to understand the operation flow when finishing the measurement cycle:
Once alarm happened and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Low_Alarm or High_Alarm). Please check below picture to understand the operation flow when the Alarm timer reaches the Alarm_Period.
If parameter ALARM_ENABLE = 0
The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;
Output 15VDC to supply power to external mA sensor
When OUTPUT_ENABLE setting equal to 1, the device could output 15VDC to supply power for external mA sensor. In this case, EXTERNAL_SENSOR_RESPONSE_TIME (Response time of external sensor/input which output 4-20 mA and connect to Daviteq Sigfox current input node, default of 120 ms ) must be configured correctly based on the characteristic of each external sensor.
Default configuration: OUTPUT_ENABLE = 0 (no output 15VDC)
Please check the Payload document to understand clearly about uplink messages, downlink messages, meaning of parameters for configuration...
Principle of Operation of Sensor part (if available)
With ADC module, the MA node transform the 0-20 mA input from sensor to digital value
The MA Node could work in loop powered sensor or non-loop powered sensor based on wirings and configuration
Default Configuration Parameters of Sensor part (if available)
This MA node has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node (converter + wireless) delivers the proper output value. Please check the Payload document for more information.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default)
Method 2: Configuring via Offline cable.
Step to access configuration port: Open housing by turning counter-clockwise 2 hex screws, then remove the anti-interference shield, the configuration port as below figure:
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type.
Note: If the sensor has SKU of WSSFCEX-PPS and hardware version 1 &2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the Base Station immediately.
Note:
Upon transmitting the data to the Base Station using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
The MA Node is calibrated by following steps:
Note out the current coefficient A and constant B. A and B is in formula: Y = A *X + B where X is raw value and Y is mA
Set the coeffiecent A=1 and constant B=0 to the MA node memory
Connect the calibration current source to the MA node
Set the calibration current source to a low value ( 0mA ) and note out the X1 value
Set the calibration current source equal to 20mA and note out the X2 value
Calculate A, B based on formula:
0 = A*X1 + B and 20=A*X2 +B
Write calculated A, B to the MA node memory
Set alibration current source 0mA and 20 mA and check the value output to make sure the A, B is written properly
4
PRODUCT SPECIFICATIONS
4.1 Specifications
| Input | 01 x Analog input, 0∼20mA |
| Accuracy | 0.05% of span |
| Resolution | 1/3000 |
| Temperature drift | < 50ppm |
| Power supply to sensor | 15VDC @ max 50mA |
| Electrical connection | M12-M connector |
| COMMUNICATION | |
| Sigfox zones | select RC1-RC7 |
| Antenna | Internal Antenna 2.0 dbi |
| Battery | 02 x AA Type 1.5VDC, working time up to 10 years (depends on configuration) |
| RF Module complies to | CE, FCC, ARIB |
| Working temperature | -40∼60℃ (using Energizer® L91 battery) |
| Dimensions | H106xW73xD42 (Wireless part only) |
| Net weight | 190g (Wireless part only) |
| Housing | Aluminum + Polycarbonate plastic, IP67 |
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.