Dusun IoT offers ThingsBoard MQTT gateway for IoT developers, solution vendors and enterprise customers to quickly deploy IoT solutions. Multiple protocols includes BLE/Zigbee/Modbus, etc. ThingsBoard SDK offered and Firmware OTA supported.
Dusun IoT’s ThingsBoard Gateway Devices are able to use BLE, Zigbee to collect data from IoT devices, and send data to cloud server by MQTT.
CPU: NXP i.MX6ULL OS: Debian
RAM: Up to 512MB Storage: Up to 8GB
Protocols: Zigbee 3.0, Bluetooth 5.2, Wi-Fi 2.4, Ethernet/IP, Modbus
ThingsBoard IoT Solution: Smart Energy, Smart Office, Fleet Tracking
CPU: PX30K OS: Debian
RAM: Up to 2GB Storage: Up to 32GB
Protocols: LoRaWAN, Wi-Fi 2.4G, BLE 5.2, LTE Cat1/Cat M1
ThingsBoard IoT Solution: Smart Farming, Environment monitoring
CPU: MT7628AN OS: OpenWrt
RAM: Up to 128MB Storage: Up to 32GB
Protocols: Ethernet/IP, Modbus RS485, 4G LTE CAT4, BACnet, DMX512, BNP3, Wi-Fi
ThingsBoard IoT Solution: Smart metering, Water metering, Smart retail
You can find more information about Dusun IoT, one of ThingsBoard’s hardware partners, at https://ThingsBoard.io/partners/hardware/.
The ThingsBoard gateway will collect the data from the sub-devices that are compatible with the protocol and then send it on to the ThingsBoard platform directly. For this reason, Dusun does not require knowledge of the particular protocol analysis method utilized by the device in order to guarantee the versatility and safety of the data.
Now, Dusun’s ThingsBoard gateways come equipped with a variety of common industrial protocol interfaces. These interfaces include MODBUS, RS485, and RS232, and they support industrial protocols like bacnet and Profinet.
Yes, the ThingsBoard Software Development Kit was used for the gateway client installation. That is to say that you have access to a wide variety of scripts on gateway for the purpose of further developing your application.
Yes, the Iot Gateway client can be pre-installed if necessary in order to facilitate customers in directly connecting the gateway to the ThingsBoard IoT platform. This is only the case if the gateway is required.
Since the DSGW-210 series has now adopted the docking mode of the ThingsBoard software development kit, there is no longer a need for an additional MQTT broker.
Yes, so long as the host address that corresponds to the customer’s ThingsBoard Professional Host service is configured on the page that serves as the gateway to the customer’s account.
During this stage of development, we are only able to provide standard customized firmware. During the stage of mass production, we are able to provide the corresponding customization firmware, and in the factory, we can directly burn the firmware version that the customer requires.
Customers can connect the DSGW-210-ThingsBoard gateway to the platform by referring to the document that is located in the link provided by Dusun, which provides a detailed operation guide. (https://ThingsBoard.io/docs/samples/dusun/DSGW-210%20Edge%20computing%20gateway/ )
Thanks to the Dusun team for assisting us in uploading the data from the Chirpstack NS side to the Thingsboard platform, completing the data path from the LoRaWAN sub-device to the Thingsboard server, and realizing a complete solution. This is really amazing!
New Zealand company Bl***** needs to collect data on the premise of having LoRaWAN sub-equipment and use Thingsbord as a dashboard to monitor, analyze and control the growth of plants. The Dusun team helps customers integrate Chirpstack NS into our gateway locally. The customer directly connects to Chirpstack to our LoRaWAN gateway and then passes the data from Chirpstack to Thingboard to complete the whole solution setup.
