사용자 도구

사이트 도구


traccar-test-01

차이

문서의 선택한 두 판 사이의 차이를 보여줍니다.

차이 보기로 링크

양쪽 이전 판 이전 판
traccar-test-01 [2019/01/30 16:37]
chajh
traccar-test-01 [2019/02/01 12:01] (현재)
chajh
줄 47: 줄 47:
 Low battery example: DBLAB0102'​s shutdown (#357) \\ Low battery example: DBLAB0102'​s shutdown (#357) \\
 ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^  battery_level ^ delay^ ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^  battery_level ^ delay^
-^356| 2019-01-21 14:​56:​11.084| 2019-01-21 14:56:10 | 37.555125| ​  ​127.050063 ​   |      1.0|    00:01:01| +^284| 2019-01-21 14:​56:​11.084| 2019-01-21 14:56:10 | 37.555125| ​  ​127.050063 ​   |      1.0|    00:01:01| 
-^357 (Gap)|2019-01-21 18:​11:​50.026| 2019-01-21 18:11:43 | 37.555152 ​ |   ​127.050041 ​ |      100.0| ​   03:15:33| +^285 (Gap)|2019-01-21 18:​11:​50.026| 2019-01-21 18:11:43 | 37.555152 ​ |   ​127.050041 ​ |      100.0| ​   03:15:33| 
-^358| 2019-01-21 18:​12:​45.090 | 2019-01-21 18:12:44 | 37.555191 ​ |   ​127.050067 ​ |      100.0| ​  ​00:​01:​01|+^286| 2019-01-21 18:​12:​45.090 | 2019-01-21 18:12:44 | 37.555191 ​ |   ​127.050067 ​ |      100.0| ​  ​00:​01:​01|
  
 Traccar client spend the network data and battery, more or less. Old phones usually have smaller battery size than brand-new ones. We have already planned for the battery issue by providing additional battery to participants. Still, we need a tracking system that can save more energy and alert the battery getting low. Traccar client spend the network data and battery, more or less. Old phones usually have smaller battery size than brand-new ones. We have already planned for the battery issue by providing additional battery to participants. Still, we need a tracking system that can save more energy and alert the battery getting low.
줄 56: 줄 56:
 Energy saving example: DBLAB0102 (#119) \\ Energy saving example: DBLAB0102 (#119) \\
 ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^ ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^
-^118| 2019-01-21 10:​40:​36.633 |2019-01-21 09:27:28 | 37.555067 | 127.050128 ​   |      37.0|    00:00:00| +^46**2019-01-21 10:​40:​36.633** |**2019-01-21 09:27:28** | 37.555067 | 127.050128 ​   |      37.0|    ​**00:00:00**
-^119 (Gap)|2019-01-21 10:​40:​36.915 | 2019-01-21 10:​40:​35 ​ | 37.555115 | 127.050077 ​  ​| ​     86.0|    01:13:07| +^47 (Gap)|2019-01-21 10:​40:​36.915 | 2019-01-21 10:​40:​35 ​ | 37.555115 | 127.050077 ​  ​| ​     86.0|    01:13:07| 
-^120| 2019-01-21 10:​41:​40.577 | 2019-01-21 10:41:40 | 37.555111 |  127.050112 |      87.0|   ​00:​01:​05|+^48| 2019-01-21 10:​41:​40.577 | 2019-01-21 10:41:40 | 37.555111 |  127.050112 |      87.0|   ​00:​01:​05|
  
 This case occurred twice on DBLAB0102 (iPhone). iOS seems to have got a kind of procedure that halts power-consuming process for a while. It may have a relation to the case 3. We have not founded the case 2 on Android phones yet. This case occurred twice on DBLAB0102 (iPhone). iOS seems to have got a kind of procedure that halts power-consuming process for a while. It may have a relation to the case 3. We have not founded the case 2 on Android phones yet.
   * Some data could be missed if the participant would have not recognized the battery level.   * Some data could be missed if the participant would have not recognized the battery level.
 ==== Case 3: Process killed/​blocked by OS ==== ==== Case 3: Process killed/​blocked by OS ====
-**Traccar blocked: DBLAB0102 (#1738)**+**Traccar blocked: DBLAB0102 (#1666)**
 ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^ ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^
-^1736 | 2019-01-23 03:​05:​32.082 | 2019-01-23 03:05:31 |37.415354 | 126.879795 ​   |      100.0| ​   00:01:00| +^1664 | 2019-01-23 03:​05:​32.082 | 2019-01-23 03:05:31 |37.415354 | 126.879795 ​   |      100.0| ​   00:01:00| 
-^1737 (Delayed)| **2019-01-24 08:​28:​23.978** | **2019-01-23 03:05:31** | 37.415354 | 126.879795 ​ |     ​100.0| ​   00:00:00| +^1665 (Delayed)| **2019-01-24 08:​28:​23.978** | **2019-01-23 03:05:31** | 37.415354 | 126.879795 ​ |     ​100.0| ​   00:00:00| 
-^1738 (Gap)|2019-01-24 08:​28:​24.149| 2019-01-24 08:​18:​10 ​  | 37.415651 | 126.881761 ​  ​| ​     98.0|  ** 1 days 05:​12:​39**| +^1666 (Gap)|2019-01-24 08:​28:​24.149| 2019-01-24 08:​18:​10 ​  | 37.415651 | 126.881761 ​  ​| ​     98.0|  ** 1 days 05:​12:​39**| 
-^1739| 2019-01-24 08:​28:​24.322 | 2019-01-24 08:​27:​53 ​ | 37.454902 | 126.895622 |      98.0|   ​00:​09:​43|+^1667| 2019-01-24 08:​28:​24.322 | 2019-01-24 08:​27:​53 ​ | 37.454902 | 126.895622 |      98.0|   ​00:​09:​43|
  
 It is critical issue. You can see #1737 data sent after unblocking Traccar. (#1738) The circumstances like this can also be shown Case 4, but the system unblock automatically in that case. We must prevent this case.\\ It is critical issue. You can see #1737 data sent after unblocking Traccar. (#1738) The circumstances like this can also be shown Case 4, but the system unblock automatically in that case. We must prevent this case.\\
줄 77: 줄 77:
 ==== Case 4: Sleep mode/idle ==== ==== Case 4: Sleep mode/idle ====
 ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^ ^index ^ servertime ^ devicetime ^   ​latitude ^ longitude ^ battery_level ^ delay^
-^118 (Delayed) | **2019-01-21 10:40:36.633** | **2019-01-21 09:27:28** | 37.555067 ​127.050128 ​   ​|      ​37.0|    00:00:00| +^718 (Delayed) | **2019-01-22 08:57:05.475** |**2019-01-22 03:08:24** | 37.415295  ​126.879858 ​    |      ​100.0|    ​**00:00:00** 
-^119 (Gap)|2019-01-21 10:40:36.915 | 2019-01-21 10:40:35  ​| 37.555115 ​127.050077 ​  |      ​86.0|    01:13:07+^719 (Gap)|2019-01-22 08:57:07.915| 2019-01-22 08:24:02 | 37.416994  ​|126.884924 ​|      ​100.0|  05:15:38
-^120| 2019-01-21 10:41:40.577 | 2019-01-21 10:41:40 | 37.555111 ​|  ​127.050112 ​|      ​87.0|   ​00:​01:​05|+^720| 2019-01-22 08:57:11.347 | 2019-01-22 08:25:06 | 37.417065|  ​126.884946 ​|      ​100.0|   ​00:​01:​04|
  
 We can see server got two locations #118 and #119 at once because OS blocks sending position #118 so that Traccar client update the local location like #118 but it'd not sent. Unlike Case 3, however, the device resend the data spontaneously in this case. We've spotted a lot of idle mode delays. All of this case, the devices have no movement when they connected known Wi-Fi at home or in the office. Usually, the owner was sleeping or working inside. We can see server got two locations #118 and #119 at once because OS blocks sending position #118 so that Traccar client update the local location like #118 but it'd not sent. Unlike Case 3, however, the device resend the data spontaneously in this case. We've spotted a lot of idle mode delays. All of this case, the devices have no movement when they connected known Wi-Fi at home or in the office. Usually, the owner was sleeping or working inside.
traccar-test-01.txt · 마지막으로 수정됨: 2019/02/01 12:01 저자 chajh