Related Manuals for Atim Cloud Wireless AGT/INDUS2
Summary of Contents for Atim Cloud Wireless AGT/INDUS2
- Page 1 ATIM Cloud Wireless LoRaWAN Gateway Modbus & MQTT User Guide Concerned model: AGT/INDUS2 ATIM Radiocommunications www.atim.com Chemin des Guillets contact@atim.com 38250 Villard-de-Lans, France...
-
Page 2: Table Of Contents
ABLE ONTENTS Document version history ..............................2 Disclaimer..................................3 Trademarks and copyright ..............................3 Declaration of compliance ..............................4 Environmental recommendations ............................. 4 Radio Presentation ..................................6 Connection to the gateway ............................... 7 LAN tab MQTT tab MODBUS tab MODBUS server ................................13 DevEUI Timestamp Payload... -
Page 3: Document Version History
Document version history Concerned Version Date Description Author software version 07/03/2022 Document creation 30/03/2022 NTP server time synchronization 16/06/2022 WIFI hotspot deactivated ATIM_1GATE_INDUS2_UG_EN_V1.2... -
Page 4: Disclaimer
ATIM. Trademarks and copyright ® ® ATIM, ACW ATIM Cloud Wireless and ARM Advanced Radio Modem are registered trademarks of ATIM SARL in France. The other trademarks mentioned in this document are the property of their respective owners. -
Page 5: Declaration Of Compliance
Declaration of compliance ® All ACW Atim Cloud Wireless products comply with the regulatory requirements of the R&TTE Directive (1999/5/EC), article 3: 1 SAFETY (Article 3.1a of the 1999/5/EC Directive) NF EN60950-1 Ed. 2006/A1:2010/A11:2009/A12:2011 (health) EN62479: 2010 (power <20mW) or EN62311:2008 (power > 20mW) 2 Electromagnetic Compatibility (Article 3.1b of the 1999/5/EC Directive) -
Page 6: Radio
General hazard – Failure to follow the instructions presents a risk of equipment damage. Electrical hazard – Failure to follow the instructions presents a risk of electrocution and physical injury. WARNING: do not install this equipment near any source of heat or any source of humidity. WARNING: for your safety, it is essential that this equipment be switched off and disconnected from mains power before carrying out any technical operation on it. -
Page 7: Presentation
Presentation ATIM 1gate gateway is designed to set up a private LoRaWAN network based on open source Chirpstack server. Devices’ uplink messages can then be forwarded using either: • MQTT protocol • MODBUS TCP protocol When 1gate Gateway is configured in MQTT it behaves as a MQTT client and publishes uplink messages to an external MQTT broker. -
Page 8: Connection To The Gateway
Connection to the gateway To configure the gateway start connecting an ethernet cable between the gateway and a computer. The computer should automatically connect to local gateway LAN network via DHCP. Ethernet CONFIGURATION mode (default) Once connected, the gateway configuration page can be accessed through a web page using the default IP address: 192.168.1.1 Configuration changes can be made from this webpage. -
Page 9: Lan Tab
a. LAN tab The LAN (Local Area Network) tab can be used to integrate the gateway in an existing ethernet network. Connecting gateway to an existing ethernet network Two methods are possible for the gateway to get an IP address: STATIC or DHCP. •... - Page 10 Switch / Rooter Ethernet Ethernet Gateway Administration computer Cloud / Internet STATIC or DHCP modes (default) Accessing gateway through ethernet network Once connected to ethernet network, gateway configuration page can be accessed using either: • Gateway IP address • Gateway hostname Gateway hostname is unique and composed of the EMAC address with format below: 1gate-[EMAC address] NOTE...
- Page 11 Accessing gateway through WIFI hotspot When WIFI hotspot option is set, the gateway broadcast a WIFI network. This network can be used to configure the gateway without connecting to Ethernet network. To connect to WIFI hotspot use SSID and WPA KEY written on gateway label. Once connected to gateway WIFI, the configuration page can be accessed with IP address 192.168.1.1 IMPORTANT NOTE Activating WIFI hotspot can result in IP conflicts...
-
Page 12: Mqtt Tab
b. MQTT tab MQTT tab can be used to fill MQTT broker information. When integration is set to MQTT, then all fields must be filled so that the gateway can connect to remote MQTT broker. ATIM_1GATE_INDUS2_UG_EN_V1.2... -
Page 13: Modbus Tab
c. MODBUS tab MODBUS tab can be used to see all devices registered and activated in the gateway. The Last seen field indicates the date of the last uplink message that has been sent by device. ATIM_1GATE_INDUS2_UG_EN_V1.2... -
Page 14: Modbus Server
MODBUS server When MODBUS integration is chosen, devices uplink messages are stored in MODBUS registers. The gateway behaves as MODBUS TCP server (slave) and registers can be read from external MODBUS master. All data is encoded in hexadecimal. 50 registers (100 bytes) are allocated per device and can be divided into three parts: - 4 registers are allocated to device EUI - 4 registers are allocated to timestamp - 42 registers are allocated to message data payload... -
Page 15: Deveui
DevEUI Device EUI is a unique 8 bytes id that is used to identify a LoRaWAN device. This id is stored at the beginning of MODBUS registers to make sure device can be identified. Timestamp 4 registers (8 bytes) are allocated to timestamp. Timestamp includes last uplink message date and time. Each byte contains a part of the date/time (i.e. -
Page 16: Example 1
Data payload is written in MODBUS registers according to big-endian, starting from the last register allocated or “stacked on the right”. Registers that are not used are left to zero, this way data fields can be read from the same address with a constant length of 42 registers, for example: - To get device 1 payload consult address 8 hex (8 dec), length 2A hex (42 dec) - To get device 2 payload consult address 3A hex (58 dec), length 2A hex (42 dec) -
Page 17: Example 3
Example 2 MR4 configured with 1 counter, datalogging of 6 measurements every 10 minutes, devEUI 70B3D59BA000C27E payload below: A5003C040000001B0000000900000007000000050000000300000001 Counter1 t Payload header Counter1 t-20min Counter1 t-40min Counter1 Counter1 t-10min Counter1 t-30min Counter1 t-50min header Example 3 DIND80 frame, devEUI 70B3D59BA000D3EC and payload below: 5EFFFF0000000C0000000B000000080000000600000007000000080000000600000000... -
Page 18: Data Extraction
MODBUS webpage also contains a link to download logs of MODBUS application for debug purposes. Data extraction To test MODBUS TCP connection to the gateway, a MODBUS emulator such as Kscada MODBUS DOCTOR can be used. Please configure: − IP address of the gateway that can be seen in the LAN tab −... -
Page 19: Lorawan Server Administration
LoRaWAN server Administration Chirpstack is an open-source software stack than can be used to set up a local (private) LoRaWAN network. Connection to Chirpstack web page To access Chirpstack configuration page, open a web browser and enter the IP address of the gateway followed by 8080 port: Alternatively, gateway... -
Page 20: Device Registration
Device registration To add devices to LoRaWAN network, select Applications tab and then click on defaultApplication. Device list NOTE Initially no device should appear in the list. For security reason, OTAA (Over The Air Activation) method is used to add devices. Two IDs are necessary for that: - A 8 bytes device EUI - The 16 bytes application key attached to the devEUI... - Page 21 In the next page complete Application Key field and confirm clicking on SET DEVICE-KEYS ATIM_1GATE_INDUS2_UG_EN_V1.2...
-
Page 22: Device Commissioning
Device commissioning Once device has been registered it should appear on defaultApplication page. Click on its name to access device information Device activity can be seen from DEVICE DATA tab: Diverse events can be seen for debug and commissioning purposes: −... - Page 23 base64 payload hexadecimal payload Data payloads and certain IDs are encoded in base64 by default in Chirpstack. However hexadecimal encoded payload is displayed under the data_hex field. NOTE It is also possible to register devices using ABP method, however it is necessary to create a new device-profile to do so. DEVICE DATA list is not saved, and only real time events can be seen.
-
Page 24: Technical Support
Technical support For any further information or technical question, you can open a ticket on our technical support dedicated webpage. IMPORTANT NOTE ATIM provides you with a gateway but not the driver's license that goes with it, you must learn how to use and program it. - For technical questions concerning the Packet Forwarder: https://github.com/Lora-net/packet_forwarder - For technical questions concerning the integrated Network Server:...
Need help?
Do you have a question about the AGT/INDUS2 and is the answer not in the manual?
Questions and answers