Wiki source code of Notes for Actility
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | **Contents：** | ||
| 2 | |||
| 3 | {{toc/}} | ||
| 4 | |||
| 5 | = 1. Actility Thingpark Enterprise = | ||
| 6 | |||
| 7 | == 1.1 Introduction == | ||
| 8 | |||
| 9 | === 1.1.1 What is Actility Thingpark Enterprise === | ||
| 10 | |||
| 11 | ThingPark Enterprise is an IoT connectivity management solution allowing to deploy a dedicated and fully controlled LoRaWAN® network for a fast use case enablement. All components of the network, including sensors, gateways and data routing are managed from a unique and easy-to-use user interface. The ThingPark Enterprise allows full flexibility in the choice of gateways or devices. It is also a flexible, scalable and secure solution allowing to start with a Proof-of-Concept (PoC) and scale to full deployments. | ||
| 12 | |||
| 13 | = 2. Gateway Registration for Basics Station = | ||
| 14 | |||
| 15 | == 2.1 Introduction == | ||
| 16 | |||
| 17 | The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]] | ||
| 18 | |||
| 19 | **Below list the support products and Requirements:** | ||
| 20 | |||
| 21 | 1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]] | ||
| 22 | |||
| 23 | 1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]] | ||
| 24 | |||
| 25 | **What do you need to prepare** | ||
| 26 | |||
| 27 | A gateway that can access the internet normally | ||
| 28 | |||
| 29 | == 2.2 Step 1. Add Gateway == | ||
| 30 | |||
| 31 | [[image:image-20220524163104-1.png]] | ||
| 32 | |||
| 33 | Add Gateway_1 | ||
| 34 | |||
| 35 | **The following items need to be configured:** | ||
| 36 | |||
| 37 | (% class="box" %) | ||
| 38 | ((( | ||
| 39 | 1.Model **~-~->** Choose the Model | ||
| 40 | 2.Name **~-~->** Custom | ||
| 41 | 3.LRR-UUID **~-~->** Enter 0061C0-Gateway EUI ,Such as:0016C0-A840411E96744150 | ||
| 42 | 4.RF Region **~-~->** Choose the frequency | ||
| 43 | ))) | ||
| 44 | |||
| 45 | [[image:image-20220524163206-2.png]] | ||
| 46 | |||
| 47 | Add Gateway_2 | ||
| 48 | |||
| 49 | Have need to put in latitude and longitude, and then click **"CREATE"**. | ||
| 50 | |||
| 51 | [[image:image-20220524163234-3.png]] | ||
| 52 | |||
| 53 | Add Gateway_3 | ||
| 54 | |||
| 55 | == 2.3 Step 2. Access the gateway GUI == | ||
| 56 | |||
| 57 | User need to update the API key and install the Certificate | ||
| 58 | |||
| 59 | [[image:image-20220524163255-4.png]] | ||
| 60 | |||
| 61 | Access the gateway GUI | ||
| 62 | |||
| 63 | == 2.4 Step 3. Configure Station == | ||
| 64 | |||
| 65 | User need to input Server URI, as well as install CUPS certificate. | ||
| 66 | |||
| 67 | **just to clarify.** | ||
| 68 | |||
| 69 | (% class="box" %) | ||
| 70 | ((( | ||
| 71 | CUPS Server URI **~-~->** Server Adress Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]] | ||
| 72 | CUPS certificate **~-~->** Server CA(user can use the button to install the certificate by default) | ||
| 73 | ))) | ||
| 74 | |||
| 75 | [[image:image-20220524163334-5.png]] | ||
| 76 | |||
| 77 | Configure the gateway | ||
| 78 | |||
| 79 | == 2.5 Start Station == | ||
| 80 | |||
| 81 | When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. | ||
| 82 | |||
| 83 | == 2.6 Siccessful Connection == | ||
| 84 | |||
| 85 | If user completes the above steps,which will see live date in the Actility Thingpark Enterprise. | ||
| 86 | |||
| 87 | [[image:image-20220524163358-6.png]] | ||
| 88 | |||
| 89 | Station live date | ||
| 90 | |||
| 91 | [[image:image-20220524163420-7.png]] | ||
| 92 | |||
| 93 | Station live date | ||
| 94 | |||
| 95 | == 2.7 Trouble Shooting == | ||
| 96 | |||
| 97 | User can check the station log in the logread/system log page. | ||
| 98 | |||
| 99 | [[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png||height="457" width="600"]] | ||
| 100 | |||
| 101 | Station Log | ||
| 102 | |||
| 103 | and recode the station log in the system/Recode log page. | ||
| 104 | |||
| 105 | [[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png||height="147" width="600"]] | ||
| 106 | |||
| 107 | Recore Log | ||
| 108 | |||
| 109 | ((( | ||
| 110 | The reason of fail to join Actility is that our end node use RX2DR=3 for join. this is the default setting for TTN and many LoRaWAN servers. | ||
| 111 | ))) | ||
| 112 | |||
| 113 | ((( | ||
| 114 | The Actility use RX2DR=0 for Join, when Actility sends a Join Accept, due to RX2DR different, the end node can not receive the Join Accept message from Actility so keep joining. | ||
| 115 | ))) | ||
| 116 | |||
| 117 | ((( | ||
| 118 | Some of End Nodes already support the change on RX2DR for OTAA join, in this case, use need to write AT+RX2DR=0. Please contact Dragino support for more info if the product doesn't support it. | ||
| 119 | ))) |