1. Manuals
  2. Brands
  3. Amit Manuals
  4. Data Loggers
  5. IOT400-DL101
  6. User manual

Amit IOT400-DL101 User Manual

Lora data logger
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
LoRa Data Logger
IOT400-DL101
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IOT400-DL101 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Amit IOT400-DL101

Summary of Contents for Amit IOT400-DL101

  • Page 1 LoRa Data Logger IOT400-DL101 User Manual...

  • Page 2: Table Of Contents

    LoRa Data Logger Chapter 1 Introduction ............................3 1.1 Introduction .............................. 3 1.2 Contents List ............................4 1.2.1 Package Contents ........................... 4 1.2.2 Optional Accessories ........................4 1.3 Hardware Configuration .......................... 5 1.4 LED Indication ............................6 1.5 Installation & Maintenance Notice ......................6 1.5.1 SYSTEM REQUIREMENTS .......................

  • Page 3: Chapter 1 Introduction

    LoRa Data Logger with LoRaWAN compliant LoRa Gateway / NS / AS for a public or private LoRaWAN service. The IOT400-DL101 is a cost-effective low complexity solution for simple data acquisition and wireless telemetry. LoRa and LoRaWAN are optimized for low bandwidth IoT traffic over wide area to transmit data at low data rates.

  • Page 4: Contents List

    LoRa Data Logger 1.2 Contents List 1.2.1 Package Contents #Standard Package Items Description Contents Quantity IOT400-DL101 1pcs LoRa Data Logger LoRa Antenna 1pcs Terminal Block 1pcs 499 Ohm Resistor 1pcs Power Adapter 1pcs 1.2.2 Optional Accessories #Optional parts (these parts are sold separately)

  • Page 5: Hardware Configuration

    LoRa Data Logger 2pcs/set Wall Mount Kit 1.3 Hardware Configuration  Left View  Right View Reset LoRa Button Antenna ※Reset Button RESET button provides user a quick and easy way to resort the default setting. Press the RESET button continuously for 6 seconds, and then release it.

  • Page 6: Led Indication

    LoRa Data Logger 1.4 LED Indication LED Color Indication Description OFF: Device power is off Red Steady on: Device is powered ON, but LoRa module is not ready yet. Blue + Red Blue Steady Flash: Device is powered ON, and LoRa module is ready. Red and Blue Steady ON: Device is in Recovery mode, or FW is upgrading.
  • Page 7 LoRa Data Logger Federal Communication Commission Interference Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

  • Page 8: Hot Surface Caution

    LoRa Data Logger 1.5.3 HOT SURFACE CAUTION CAUTION: The surface temperature for the metallic enclosure can be very high! Especially after operating for a long time, installed at a closed cabinet without air conditioning support, or in a high ambient temperature space.

  • Page 9: Product Information For Ce Red Requirements

    (5) Manufacture Information Manufacture Name: AMIT Wireless Inc. Manufacture Address: No. 28, Lane 31, Sec. 1, Huandong Rd., Xinshi Dist., Tainan 74146, Taiwan (R.O.C.) 1 The information presented in this section is ONLY valid for the EU/EFTA regional version. For those non-...

  • Page 10: Hardware Installation

    1.6.2 Connecting I/O Devices The IOT400-DL101 provides a 10-pin terminal block for one serial console port, one digital input (DI), one digital output (DO), one analog input (AI), and DC Power (DC5~12V) ports. Connect the field device(s) to the I/O ports with the right pin assignments as shown below.
  • Page 11 LoRa Data Logger Example of Connection Diagram - DI Example of Connection Diagram - DO...
  • Page 12 LoRa Data Logger Connect to devices via AI (Analog Input) : The IOT400 provides 1 AI port for connecting to analog sensor/meter. To connect the device, you have to identify the type of your device and properly connect and configure the IOT400 so that it can get the correct readings from the connected device.

  • Page 13: Connecting Console Port For Pc Configuration Tool

    LoRa Data Logger 1.6.3 Connecting Console Port for PC Configuration Tool After completing prior hardware configuration, you are almost finishing the hardware configuration procedure. To make the LPWA Data Logger operate properly in according to attached external devices, you have to further configure software settings from a PC configuration tool.

  • Page 14: Connect To External Dc Power Source

    LoRa Data Logger 1.6.4 Connect to external DC Power Source The LPWA Data Logger accepts 5 ~ 12V DC input power, and can be powered by DC12V power supply. It can be powered by connecting a power source to the power terminal block, as indicated below. UART TX UART RX Please connect carefully your power source.

  • Page 15: Setup With Windows-Based Configuration Tool

    LoRa Data Logger 1.6.5 Setup with Windows-based Configuration Tool The Data Logger has to be configured with a Windows configuration tool. Just find out a PC/NB with an available USB port, and plug in the USB-to-Serial Console Cable into it. For the first time to setup the Data Logger with his Configuration Tools, you have to download it from the vendor provided URLs or QR-code, and install it to the PC/NB for further device configuration.
  • Page 16 LoRa Data Logger Now, you already logged in to the Data Logger console, and you can proceed with the required software configuration steps one by one. Refer to the following Chapter for the details.

  • Page 17: Chapter 2 Device Configuration

    LoRa Data Logger Chapter 2 Device Configuration 2.1 Device Status Click on Status menu item, and the device information and status will display on configuration area which is located in the right-hand side. If the device status doesn’t appear or you want to get the updated status, click Status Refresh button located at the lower right corner to refresh the status immediately.

  • Page 18: Lora Configuration

    LoRa Data Logger 2.2 LoRa Configuration In the LoRa Configuration page, you can configure the channel, activation settings and MAC Layer settings. Channel Configuration There are Channel Group 1 and 2. It will show the supported Sub-Band depend on the area of the LoRa specification.
  • Page 19 LoRa Data Logger Activation Configuration Prior to connect the LoRa Node to a certain LoRaWAN Network Server, you can configure device activation settings for how it connects to the network and how the remote geteway and network server can identify the LoRa Node.
  • Page 20 LoRa Data Logger Activation: Specify the desired actication method for the LoRa node to connect to a network. OTAA (Over-the-Air Activation) and ABP (Activation by Personalization) are supported. By default, ABP is selected. OTAA: OTAA is the preferred and most secure way to connect with network server. Devices perform a join-procedure with the network server, during which a dynamic Device Address is assigned and security keys (Network Session Key, APP Session Key) are negotiated with the device.
  • Page 21 LoRa Data Logger MAC Layer Configuration Prior to connect the LoRa Node to a certain LoRaWAN Network Server, you can configure device MAC Layer settings for how it connects to the network. Device Class: Specify the device class for the LoRaWAN node. The LoRa Data Logger supports two types of device class.
  • Page 22 LoRa Data Logger Note: DO NOT choose the Class C device type while it is powered by external battery. The device won’t get into sleep mode if it is configured as Class C device, and it will continuously drain away the battery power even it is idle and just listens for the command from network server.

  • Page 23: I/O Configuration

    LoRa Data Logger 2.3 I/O Configuration In the I/O Configuration screen, you can configure the Analog Inputs (AIs) and Digital Inputs (DIs). According to the hardware configuration you already finished, you have to further configure the settings for the device firmware, so that the Data Logger will know what kind of input device is connected to each port. For Analog Input ports, you can specify an optional Name for identification, and the type for each connected port.
  • Page 24 LoRa Data Logger With the settings, the Data Logger will activate 32-bit counters to count the pulse behavior, record the counter value plus the Offset as the actual value on each data logging time slot. Finally, click Save button to store the configuration in the device. Prior to store the I/O settings, the following dialog will appear for you to double confirm the settings of Analog Input type that the H/W configuration and S/W configuration are consistent.

  • Page 25: Event Configuration

    LoRa Data Logger 2.4 Event Configuration The Event Trigger function can use a certain input signal (device) as trigger source for an event rule. If there is any enabled event rule, the data logger will check the trigger source once per second to determine event trigger or not.
  • Page 26 LoRa Data Logger Value1/2: Enter the threshold value of condition 1/2 for comparison. Operation: If cond.2 exists, specify the logic operation (AND, OR) for cond.1 and cond.2. Condition Hold Time: Enter a time interval as the threshold of required minimum codition hold time .

  • Page 27: System Configuration

    LoRa Data Logger 2.5 System Configuration System Configuration allows the device administrator / installer to manage the LPWA Data Logger. There are settings / function buttons for Reboot, Reset to Default, Configuration Backup / Restore, System Log, Firmware Upgrade, System Time, and Sleep Mode. Reboot or Reset to Default For some special reason or situation, you may need to reboot the LPWA Data Logger or reset the device configuration to its default value.
  • Page 28 LoRa Data Logger System Log For some device maintenance purpose, you may need to get the system log for troubleshooting. You can do it through the configuration tool, click Download or Delete button. Click Download button to store the System Log into a log file (.txt) for troubleshooting. Click Delete button to erase the existing system logs.

  • Page 29: Cli Console Log

    LoRa Data Logger 2.6 CLI Console Log The system console log will show at this configuration page. It can help to monitor the system operation and event. When some issue happens, capture this console log and consult with device vendor.

  • Page 30: Chapter 3 Commands For The Lora Node

    LoRa Data Logger Chapter 3 Commands for the LoRa Node The OOT550-DL is a LoRaWAN compliant LoRa node. With proper configuration, it can automatically send out (report) the status (data) of all the connected meter/sensors to a registered LoRa Network Server through a certain LoRaWAN gateway(s) at a designated time interval.
  • Page 31 LoRa Data Logger ret ^= buf[i]; return ret;...

  • Page 32: Commands

    LoRa Data Logger 3.2 Commands 0x01 – Report all Inputs: 0x01 Total length Data[i] length Data[i] value[] … Checksum 1 byte 1 byte 1 byte n byte 1 byte Command: 0x01 Purpose: A LoRa node is Uploading the status (data) of all input ports to network server. Sequence: DI[1] / DI[2] / AI[1] / AI[2] / AI[3] / Modbus[1] / Modbus[2] / Modbus[3] Note 1: There is maximum limit on the payload size.
  • Page 33 LoRa Data Logger 0x02 – Report all Enabled Inputs: 0x02 Total Port ID[i] Data[i] Data[i] … Checksum length length value[] 1 byte 1 byte 1 byte 1 byte 1 byte * n 1 byte Command: 0x02 Purpose: A LoRa node is Uploading the status (data) of all enabled input ports to network server. Port ID[i]: Identifier for each input port.
  • Page 34 LoRa Data Logger 0x03 – Report each Enabled Input: 0x03 Total Port ID[i] Data[i] Data[i] … Checksum length length value[] 1 byte 1 byte 1 byte 1 byte 1 byte * n 1 byte Command: 0x03 Purpose: A LoRa node is Uploading the status (data) of all enabled input ports to network server. Similar to 0x02, but due to payload limitation issue on low data rate connection, up to 4 separate packets could be transmitted.
  • Page 35 LoRa Data Logger 0x81 – Get all Inputs: 0x81 Total length Checksum 1 byte 1 byte 1 byte Command: 0x81 Purpose: A network server is asking for the LoRa node to get the status (data) of all input ports. Note 1: There is maximum limit on the payload size. This command may not be used for some Modbus device configuration that has many registers to read.
  • Page 36 LoRa Data Logger 0x82 – Get all enabled Inputs: 0x82 Total length Checksum 1 byte 1 byte 1 byte Command: 0x82 Purpose: A network server is asking for the LoRa node to get the status (data) of all enabled input ports. For example, the packet“820280”...
  • Page 37 LoRa Data Logger 0x84 – Set Value: 0x84 Total length Device ID Data length Datavalue[] … Checksum 1 byte 1 byte 1 byte 1 byte 1 byte * n 1 byte Command: 0x84 Purpose: A network server is asking for the LoRa node to set the value (data) of specific enabled output port. Device ID: Identifier for each outout port.
  • Page 38 LoRa Data Logger 0x70 – Low Power Warning: 0x70 Total length Checksum 1 byte 1 byte 1 byte Command: 0x70 Purpose: A LoRa node is alerting to the network server with low battery power warning. For example, the packet“700272” is composed of Command byte –...

Table of Contents