Cloud platform common problems and solutions
Home >
Cloud platform common problems and solutions
1.The device is not online
  a. Check if the networking parameters of the device on the configuration software are set correctly (including server IP/port/registration package content, etc.);
  b. Whether the SIM card in the device has a balance;
  c. Whether the SIM card in the device supports the traffic function or whether the traffic is directed traffic;
  d. Check whether the IP or registration package on the configuration software is correct. Pay attention to the front, back, and middle without spaces.
  e. Is the device ID setting incorrect?

  f. The device is not registered to the signal or the signal value is too weak. The antenna should be connected.

 

2. On the cloud platform, after the device is online for a period of time, it will be frequently offline and online.
  a. Is the device ID set up (if we use our cloud platform, the device ID defaults to fill in 1);
  b. Check whether the heartbeat package and the heartbeat response package in the configuration software are set up correctly.
  c. Whether the protocol selection on the platform side is correct;
  d. If there are RS485 ports, RS485 can not be set as data transparent transmission mode (this situation is for the case where RS485 is not used)
  e. Check if the SIM card in the device has a balance;
  f. If the device uses an IoT card, do not set the alarm number. Do not ticked all alarms.

3. On the cloud platform, the device is online and the data points are not online.
  a. Check if the configuration of the read/write instructions is wrong (such as function code, register address, data type, etc.);
  b.If there are RS485 ports, RS485 can not be set as data transparent transmission mode (this situation is for the case where RS485 is not used)
  c. Check whether the data points set "not to collet" on Cloud Platform.

4.The data point of the device cannot read the correct data on the cloud platform.
  a. If you use the King Pigeon 2.0 cloud platform, the register address should be offset +1 (for example: the register address is 1, then you need to fill 2 on the King Pigeon 2.0 cloud platform);
     If you use the King Pigeon 3.0 cloud platform, the register address does not need to be offset (for example, the register address is 1, then you need to fill in 1 on the King Pigeon 3.0 cloud platform);
  b. Make sure that the data format/byte order settings are correct (for example, 32 bits are symbolic or unsigned or floating-point, byte order is ABCD or BACD, etc.)