Tools and Documents

List of Tools and Configuration Documents

1. Configuration Tool on PC:

1.1 Modbus Configuration Tool:

1.2 iConnector Configuration Tool:

1.3 Sigfox Tool:

2. Configuration Documents:

2.1 Sub-GHz WS433 Wireless Sensor:

2.1.1 Modbus memmap:
2.1.2 WS433 Wireless sensor:
2.2 Sigfox sensor:

2.4 LoRaWAN sensor:

2.3 Modbus RTU sensor:

 

User Guide for Modbus Configuration Tool

AUG-2020

Daviteq Modbus Configuration Tool

HW Ver. Release Date
1.0 NOV-2019
1.4

OCT-2020

2.03

DEC-2021

1. Install Tool

1.1 Download Tool

 Install the Modbus Configuration Software in the link below

https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs 

2.2 Running Tool

After unzip file, open the folder and run the application (Daviteq Modbus Configuration Tool Version).

1.png

image-1601890119287.png

2. Configuration

2.1 Connection

Step 1: Connect the configuration cable to the PC and Modbus device.

STHC-ISG02DB-WS433-CL-04-H8.png STHC-ISG02DB-WS433-CL-04-H13.png
STHC-ISG02DB-WS433-CL-04-H11.png STHC-ISG02DB-WS433-CL-04-H12.png

Step 2: Choose COM Port (the Port which is USB cable plugged in). Set the BaudRate: 9600, Parity: none

2.png

If you don't see any COM port in the list, please download the following driver and install

Modbus Configuration Cable COM port driver for PC
How to install driver

Step 3: Click “ Connect “ untill the Status displays “disconnected” to “connected“. It means the Modbus device is being connected with computer;

Modbus_Tool_3.png

4.png

Step 4: Import the configuration file for Modbus Device by importing the csv file: Go to MENU: FILE / Import New /

Then select the template file.

Example: We import template file of Wireless Co-ordinator WR433-AP-EN-02 - Template_WR433_V1.6.csv

Modbus_Tool_5.png

Modbus_Tool_6.png

There are 3 Function:

2.1 Write Value into Modbus Device with Function 16

Example: We change the value Node id 1 from 0 to 12345678 using Func 16.

Step 1: Uncheck Func 3, then Click on the arrow and change Func from 3 to 16;

Modbus_Tool_7.png

Modbus_Tool_8.png

Modbus_Tool_9.png

Step 2: Type in Setting Value the Node id 1, then check the Func 16 box.

Modbus_Tool_10.png

if Read Value show OK which mean it's wrote successful.

Modbus_Tool_11.png

2.1 Read Value from Modbus Device with Function 3

After writing the value, we will check the value entered with Func 3. Func 3 is used to read holding registers.

Step 1: Click on the arrow and change Func from 16 to 3.

Modbus_Tool_12.png

Step 2: Check the box of Func 3. If it shows that the value in Read Value is the same as the value entered, it means that the data entered was successful.

 

Modbus_Tool_13.png

Modbus_Tool_14.png

3. Troubleshooting

No. Phenomena Reason Solutions
1 Cannot connect to software
  • The COM port selected is incorrect.
  • Modbus cannot be connected to the device.
  • Check Modbus connection
  • Select the correct COM port to which the configuration cable connects to the computer
2 COM port does not appear in the select list
  • Have not updated window to the latest version
  • Driver not installed
  • Update to the latest version for window
  • Install driver for PC
3 Cannot see any register on software The template file has not been imported Go to File/Import New to import the template file
4 See registers that do not match the memmap table of the device rs485 or sensor is configuring The template file imported incorrectly Go to the correct manual page of the product configuring and download the template file, then import the template file into the software

4. Support contacts

Manufacturer

logo-01.png

Daviteq Technologies Inc
No.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.
Tel: +84-28-6268.2523/4 (ext.122)

Email: info@daviteq.com | www.daviteq.com

 

Distributor in Australia and New Zealand

temploggerlogo.png

Templogger Pty Ltd

Tel: 1800 LOGGER

Email: contact@templogger.net

 

How to use Excel file Modbus Memmap of Co-ordinator

FEB-2022

1. Introduce

When we add a sensor to the Co-ordinator WS433-CL or iConnector integrated Co-ordinator, the added sensor will be in the corresponding Modbus area in the Co-ordinator. The sensor's Modbus area can be monitored with our excel file. You can then read the data from the respective Modbus addresses using the PLC,HMI,... or use our Modbus Configuration Tool to view the values from the sensor.

1.1 Download Excel file

Download the Modbus Memmap Excel file in the link below:

https://filerun.daviteq.com/wl/?id=BKEaUzdArkoc0Hc7nfpRShdPVToVrqQZ 

1.2 Excel file

After unzip file, open the excel file (Modbus Memmap of WS433-CL-FW_Vxx)

Memmap-1.jpg

Memmap-2.jpg

2. How to use

Example: Choosing WS433-M12F and ATH sheet for WS433-M12F-ATH or WS433-ATH

image-1645761627544.png

Example 1: WS433-ATH is the first sensor to be added, so it has a position of

image-1645762061144.png

Example 2: WS433-ATH is the third sensor to be added, so it has a position of

image-1645762590827.png

image-1645762747306.png

image-1645762773516.png

3. Troubleshooting

No. Phenomena Reason Solutions
1 Cannot type into yellow frame of excel file Edit mode is not open yet Click Enable Editing to edit the number in yellow frame
2 No suitable sensor found

Old memmap or other modified sensor name

  • Check HERE the latest memmap file
  • Contact us for support

4. Support contacts

Manufacturer

logo-01.png

Daviteq Technologies Inc
No.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.
Tel: +84-28-6268.2523/4 (ext.122)

Email: info@daviteq.com | www.daviteq.com

 

 

Instructions for Upgrading the Firmware for Daviteq Sigfox Sensor

 
1. Preparation

1.1 Prepare a ST-LINK V2 cable that connect between PC and the sensor.

1.2 Save the updated firmware file (.hex) to the PC for flashing to the sensor.

1.3 Save the ID & PAC file (.bin) to the PC for configuring the sensors.

2. Download and install the software "STM32 ST-LINK Utility".

The software can be downloaded from internet via the link: https://www.st.com/en/development-tools/stsw-link004.html

1111.png

Figure 1. Getting the software from the website.

3. Set up the hardware 

Connect the USB port of the ST-LINK V2 to the PC. The other end should be plugged into the PRG port of the sensor.

hardware-for-update-fw.png

Figure 2. Hardware setup

4. Software configuration 

4.1. Open the STM32 ST-LINK Utility software. 

4.2 Target => Settings. Then, select "Connect Under Reset" and check "Enable debug in Low power mode" in Mode section =>OK

image-1646817161773.png image-1646817251790.png

Figure 3. Software configuration

Make sure that the PC has a connection to the devices with the cable provided.

5. Loading firmwares.

5.1 Target -> Program & Verify...

5.2 File path => Browse => Choose firmware file (.hex)

image-1646818122679.png

image-1646818127458.png

Figure 4. Import firmware file

5.3 Press Start to load the firmware to the sensor

image-1646818404226.png

Figure 5. Loading firmware

When the firmware is successfully loaded, the software will display information with figure 6

load-fw.png

Figure 6. Successfully loading firmware

6. Loading ID and PAC.

After successfully loading the firmware in Step 5, you need to reload the ID&PAC for the sensor. Follow the steps below:

6.1 Target => Program & Verify... 

6.2 File path => Browse

6.3 Open ID&PAC file (.bin)

Each sensor has a unique ID&PAC file. Therefore, you need to carefully check to ensure that the file being loaded corresponds to the correct ID and PAC on the sensor's label. (The .bin file name contains the corresponding ID information.)

6.4 Change the Start Address: 0x08017000 => Start

image-1646818693820.png

image-1646818698909.png

Figure 7. Loading ID&PAC

When the firmware is successfully loaded, the software will display information with image 4.

image-1646839141359.png

Figure 8. Successfully loading ID& PAC


 

Support for Flashing The Firmware in Daviteq Lorawan Sensor

1. Preparation

1.1 Prepare a ST-LINK V2 cable that connect between PC and the sensor. Details information of the cable at link:

    https://www.st.com/en/development-tools/st-link-v2.html

1.2 Save the updated firmware to the PC for flashing to the sensor.

1.3 Note out checksum information of the update firmware. This information will be provided by sensor manufacturer.

2. Download and install the software "STM32 ST-LINK Utility".

Computer run on Windows 7 or higher.
The software can be downloaded from the link : https://filerun.daviteq.com/wl/?id=3OVxFN7qe3R7lU9iayCSIHxH45yCM6yE

 
3. Plug cable from ST-LINK V2 to sensor.

With the female to female wire

image-1670487127164.jpg

 

20221208_032536232_iOS.jpg

or with the provided cable by Daviteq
20221208_082233000_iOS.jpg
Then plug the ST-Link V2 into the computer by the USB A to Mini B cable.

20221208_082652000_iOS.jpg

4. Select the mode setting on the software.

4.1 Target -> Settings...
4.2 Mode: select "Connect Under Reset" and check "Enable debug in Low power mode" -> OK

The order of steps 3.1 and step 3.2 indicate through the image from left to right in Table 1.

image-1646817161773.png image-1646817251790.png

Table 1. Settings... - Mode.

5. Target the hex file for upgrading any firmware.

5.1 Target -> Program & Verify...
5.2 File path -> Browse

Basically, the firmware update specifies the sensor. In this case, please contact the instructor for more information.

Step 5.1 and step 5.2 indicate in the image from left to right in Table 2.

You must browse to select the correct file, the hex file can be used to apply for the same device type.

image-1646818122679.png

image-1646818127458.png

Table 2. Program & Verify... - Browse.

5.3 Open ".hex" file -> Start

In step 5.3, you need to select the hex file and load it into the device.

For example within each image of Table 3, the target is a sensor WSSFC-LPC and is used in this guide. Note the checksum then "Start"

image-1646818398167.png

2.png

 

Table 3. Starting a program file to the sensor, Open - Start.
3.png
If Programmed memory Checksum equal with the .hex file checksum => Succeed
If Programmed memory Checksum not equal with the .hex file checksum => Failed