Wiki source code of Connect Devices to ThingsEye
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | |
| 2 | |||
| |
2.1 | 3 | **Table of Contents:** |
| |
1.1 | 4 | |
| |
2.1 | 5 | {{toc/}} |
| |
1.1 | 6 | |
| |
2.1 | 7 | |
| |
3.1 | 8 | = 1. Overview = |
| 9 | |||
| 10 | |||
| 11 | |||
| |
2.1 | 12 | = 2. UDP Procotol ~-~- Directly Connection = |
| 13 | |||
| 14 | == 2.1 UDP Interface == | ||
| 15 | |||
| |
1.1 | 16 | * Server Address: server1.thingseye.io |
| 17 | * Port: 11560 | ||
| 18 | |||
| 19 | The data sent to above UDP interface will not go directly to client's database. | ||
| 20 | |||
| 21 | Please contact ThingsEye team for detail how to forward data to client. | ||
| 22 | |||
| 23 | |||
| |
2.1 | 24 | == 2.2 Test UDP Interface via Socket Tool == |
| |
1.1 | 25 | |
| 26 | Download the UDP Test Tool from: [[https:~~/~~/sourceforge.net/projects/sockettest/ >>https://sourceforge.net/projects/sockettest/]]. Run this tool, and input the server address and UDP port as below and click send. | ||
| 27 | |||
| 28 | [[image:1728362612869-443.png||height="454" width="540"]] | ||
| 29 | |||
| 30 | In server side, Tenant Administrator can check this in Tenant UDP Server location. | ||
| 31 | |||
| 32 | [[image:1728362834430-749.png||height="510" width="1667"]] | ||
| 33 | |||
| 34 | Click and see the debug info as below: | ||
| 35 | |||
| 36 | [[image:1728363020699-203.png]] | ||
| 37 | |||
| 38 | We can see the message arrives, but it shows ERROR because the message doesn't follow with the UDP Server format. | ||
| 39 | |||
| 40 | |||
| |
4.1 | 41 | = 2.3 Test with Dragino NB device = |
| |
1.1 | 42 | |
| |
4.1 | 43 | === 2.3.1 Configure NB-IoT End Node === |
| 44 | |||
| 45 | Device here is **[[S31-NB>>https://www.dragino.com/products/temperature-humidity-sensor/item/288-s31-nb-s31b-nb.html]]** : and have been configure below | ||
| 46 | |||
| 47 | * Set to use ThingsEye UDP server: **AT+SERVADDR=server1.thingseye.io,11560** | ||
| 48 | * Equip with a NB-IoT SIM Card to access to NB-IoT Network. | ||
| 49 | |||
| 50 | The S31-NB's cellular module has the IMEI: **863663062789483** | ||
| 51 | |||
| 52 | |||
| 53 | === 2.3.2 Check Uplink Data === | ||
| 54 | |||
| 55 | Re-activate the S31-NB, and we can see it in the debug window: | ||
| 56 | |||
| 57 | [[image:1728378218744-800.png||height="431" width="1003"]] | ||
| 58 | |||
| 59 | |||
| 60 | === 2.3.3 Auto-Create Device === | ||
| 61 | |||
| 62 | The default **Tenant UDP Server** has already been configured to decode the Dragino -NB / -CB NB-IoT node. So once each end node sends a data to server. Tenant will auto create the device in the server. | ||
| 63 | |||
| 64 | [[image:1728378968101-683.png||height="273" width="1307"]] | ||
| 65 | |||
| 66 | [[image:1728379050044-764.png||height="424" width="1312"]] | ||
| 67 | |||
| 68 | |||
| 69 | So we have this device in the Tenant Device List. The next step will be how to use these value to make a nice dashboard for user's application. | ||
| 70 | |||
| 71 | |||
| 72 | |||
| |
1.1 | 73 |