문서의 선택한 두 판 사이의 차이를 보여줍니다.
양쪽 이전 판 이전 판 다음 판 | 이전 판 | ||
traccar-test-01 [2019/01/29 12:28] chajh [Intro] |
traccar-test-01 [2021/04/13 06:54] (현재) |
||
---|---|---|---|
줄 1: | 줄 1: | ||
- | ===== Traccar Client on Old Smartphones | + | < |
+ | {{: | ||
Code (Finding ghosts): [[https:// | Code (Finding ghosts): [[https:// | ||
[[traccar-test-01-kr|한국어 문서/ | [[traccar-test-01-kr|한국어 문서/ | ||
- | ==== Intro ==== | + | ===== Intro ===== |
We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people' | We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people' | ||
Anyway, we adopted Traccar as our GPS tracking platform base, and we'd already tried several experiments. It worked well, but we got a bad news recently. \\ | Anyway, we adopted Traccar as our GPS tracking platform base, and we'd already tried several experiments. It worked well, but we got a bad news recently. \\ | ||
- | ==== What's the problem? ==== | + | ===== What's the problem? |
- | GPS is only available outdoors. Today, GPS tracking system are usually built in vehicles such as airplane, ships, trucks, and taxis. They move most of the time except for a few minutes on a shaded path such as a tunnel. So, it's easy to get the location data from these objects. There are not too many tracking devices that also fit perfectly by types of vehicle. Well then. How about the location of people? Can we still get data from individual person through GPS Tracker like Traccar?\\ | + | GPS is only available outdoors.((In fact, today' |
Today' | Today' | ||
줄 16: | 줄 18: | ||
Besides, it is sufficient so that we can get the places our participant visits, although we don't catch actual location where they are in each place. | Besides, it is sufficient so that we can get the places our participant visits, although we don't catch actual location where they are in each place. | ||
- | ==== Bad news? ==== | + | ===== There is a gap! ===== |
- | While we believe we know the testers' | + | {{:: |
- | | + | |
- | | + | While we believe we know the testers' |
+ | | ||
+ | | ||
+ | * What causes the gaps? Should we prevent the gaps? | ||
We must look into which was right. | We must look into which was right. | ||
- | ==== Test ==== | + | ===== Test ===== |
Unfortunately, | Unfortunately, | ||
줄 31: | 줄 36: | ||
Both devices have sent location data for a week. | Both devices have sent location data for a week. | ||
- | To get more information, | + | To get more information, |
- | ==== Result and Analysis ==== | + | ===== Result and Analysis |
We configured the client to send its location every 60 seconds. Theoretically, | We configured the client to send its location every 60 seconds. Theoretically, | ||
- | ^ ^ < 2 min ^ 5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^ | + | ^ |
- | ^DBLAB0102| | + | ^DBLAB0102| |
- | ^DBLAB0103| | + | ^DBLAB0103| |
- | Overall | + | Although the iPhone(0102)' |
- | The result | + | ==== Case 1: Low battery and shutting down ==== |
+ | Low battery example: DBLAB0102' | ||
+ | ^index ^ servertime ^ devicetime ^ | ||
+ | ^284| 2019-01-21 14: | ||
+ | ^285 (Gap)|2019-01-21 18: | ||
+ | ^286| 2019-01-21 18: | ||
+ | |||
+ | 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. | ||
+ | * Some data could be missed if the participant would have not recognized the battery level. | ||
+ | ==== Case 2: Low battery and energy saving mode ==== | ||
+ | Energy saving example: DBLAB0102 (#119) \\ | ||
+ | ^index ^ servertime ^ devicetime ^ | ||
+ | ^46| **2019-01-21 10: | ||
+ | ^47 (Gap)|2019-01-21 10: | ||
+ | ^48| 2019-01-21 10: | ||
+ | |||
+ | 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. | ||
+ | ==== Case 3: Process killed/ | ||
+ | **Traccar blocked: DBLAB0102 (#1666)** | ||
+ | ^index ^ servertime ^ devicetime ^ | ||
+ | ^1664 | 2019-01-23 03: | ||
+ | ^1665 (Delayed)| **2019-01-24 08: | ||
+ | ^1666 (Gap)|2019-01-24 08: | ||
+ | ^1667| 2019-01-24 08: | ||
+ | |||
+ | It is critical issue. You can see #1737 data sent after unblocking Traccar. (# | ||
+ | iPhone blocks a process that uses power and data continuously. As I know, the only way to unblock Traccar | ||
+ | |||
+ | * iPhone: Some data could be missed if the participant would have clicked pop-up unconsciously. | ||
+ | * Android (Samsung): Some data could be missed if the participant would have turned off energy saving options | ||
+ | ==== Case 4: Sleep mode/idle ==== | ||
+ | ^index ^ servertime ^ devicetime ^ | ||
+ | ^718 (Delayed) | **2019-01-22 08: | ||
+ | ^719 (Gap)|2019-01-22 08: | ||
+ | ^720| 2019-01-22 08: | ||
+ | |||
+ | 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. | ||
+ | * Safe. But, there could be a lag for recalibrating GPS signal. | ||
+ | * If the user didn't go outside for a long time, we could be misunderstood this case as Case 3. | ||
- | === Case 1: Low battery and shutting down === | + | ===== Summary |
- | === Case 2: Low battery and energy saving mode === | + | * Most gaps caused by sleep/idle mode of the operating system. There is no data loss unless the user forgot carrying his phone. |
- | === Case 3: Sleep mode/idle === | + | * The user must experience the device blocks Traccar because of its power consumption. It is usually three days after. We need to make sure the participant' |
- | === Case 4: Process killed by OS === | + | * Battery issue is not trivial. |
+ | ===== Future works ===== | ||
+ | * This is data about locations. We need to make some visualization tools with Korean maps. Traccar supports google and openstreetmap but they have some deficiencies because of legislations. | ||
+ | * We also need monitoring system for notifying users to prevent any data loss. | ||
+ | * All participant have to take a pre-test period at least three days. We could assure Traccar working on the device fine. |