Q1: We have recently installed UG85 with 2 x UC11-T1 sensors and noticed that data consumption is about 90MB/Month. Reporting interval of UC11-T1 is 10 minutes. Could you let us know if there is any change needed in the settings to reduce the data consumption.
Answer: Because the reporting interval of UC11-T1 is 10 minutes, data consumption mainly comes from the UG85. In order to reduce data consumption, you can change the ICMP settings to reduce ICMP packages. For more information please refer to article: How to Reduce Cellular Data Usage in Milesight LoRaWAN Gateway.
Q2: I have some trouble in accessing Network Server on UG65 when it is connected to my DeviceHub account using cellular communication. The gateway tells me "error" in red or "You have not enable "Network Server". However, the network server is enabled since the POST HTTPS is still working.
Answer: Please download latest firmware from Milesight website and upgrade the gateway.
Q3: Is there API for Milesight gateway to get historical data?
Answer: There is no API to get historical data. If you have any requirements about it please contact Milesight about it.
Q4: I got an error message "Error: Partnumber does not match LoRa module (no module info)" on Status page of UG65.
Answer: Please download the latest firmware from Milesight website and upgrade it to get the error removed.
Q5: What kind of the material does the UG67’s outer shell made of?
Answer: Polycarbonate+ die-casting aluminum.
Q6: Is it possible to connect multiple UG65 to the network server of one UG65? How many can I connect?
Answer: Yes, you can connect up to 4 units of devices.
Q7: I want to ask if the gateway could perform end device localization based on TDoA (Time Difference of Arrival)?
Answer: Currently cannot. Milesight gateways support the gateway GNSS positioning now.
Q8: What are the main factors that will affect the number of the UC controller that gateway manage?
Answer: The number of UC controller that connect to gateway would be affected by factors like reporting interval, distance in between, payload length, Lora frequency band and spread factor.
Q9: What is the maximum length of the PoE cable supported for the UG67 gateway ?
Answer: The length is up to 80-100 meters.
Q10: What is the difference between LoRaWAN 1.0.2 and 1.0.3? If I am using class B, which version shall I use? And can version 1.1 compatible with 1.0.3?
Answer: LoRaWAN1.0.3 supports unicast & multicast class B devices. Class A and class C sections are unchanged compared to LoRaWAN1.0.2 with the exception of a new MAC command "DeviceTimeRequest" used to synchronize the real time clock of a device. For devices operating in class A or class C, there is no need to upgrade to LoRaWAN 1.0.3. Click here for more information about LoRaWAN 1.0.3.
Q11: What are the new features for the LoRaWAN V1.1 compared with LoRaWAN v1.0.2?
Answer: LoRaWAN V1.1 protocol is optimized for battery-powered end-devices and adds support for handover roaming, Class B and security enhancements. Click here for more information about LoRaWAN 1.1.
Q12: How many super capacitors in your UG67? How many Farad for each one?
Answer: UG67 has 5 capacitors inside, and each one is 25 Farad.
Q13: Can the UG65 and UG67 support external 4G antenna?
Answer: UG65 can be customized to connect external antenna, while the UG67 cannot. Please contact Milesight sales if you need external antenna customization.