사용자 도구

사이트 도구


traccar-test-01

차이

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

차이 보기로 링크

양쪽 이전 판 이전 판
다음 판 양쪽 다음 판
traccar-test-01 [2019/01/30 05:33]
chajh [Future works]
traccar-test-01 [2019/01/30 07:37]
chajh
줄 1: 줄 1:
-===== Traccar Client on Old Smartphones =====+<title> Traccar Client on Old Smartphones </title>
 {{:traccar-working.png?nolink&400|}} {{:traccar-working.png?nolink&400|}}
  
줄 5: 줄 5:
 [[traccar-test-01-kr|한국어 문서/Korean]] [[traccar-test-01-kr|한국어 문서/Korean]]
  
-==== Intro ====+===== Intro =====
 We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people's move day by day. We needed a GPS tracker that is stable enough to get 30-100 people's location at once, and easy to install for participants. We've been through a few things, that is another story. \\ We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people's move day by day. We needed a GPS tracker that is stable enough to get 30-100 people's location at once, and easy to install for participants. We've been through a few things, that is another story. \\
  
 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.((In fact, today's smartphones with Assisted GPS (AGPS) can get their location from nearby network routers that tell the device where they are. )) 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's smartphones with Assisted GPS (AGPS) can get their location from nearby network routers that tell the device where they are. )) 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?\\
  
줄 18: 줄 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. 
-==== There is a gap! ====+===== There is a gap! =====
 {{::traccar-error1-rev1.png?nolink&600|}} {{::traccar-error1-rev1.png?nolink&600|}}
  
줄 27: 줄 27:
  
 We must look into which was right. We must look into which was right.
-==== Test ====+===== Test =====
 Unfortunately, we don't have the specific information of previous participant's devices. So, we should imagine the device which might cause some problems and should be sifted out before experiment begin. First, we picked old phones with some troubles. We want to know whether these legacy devices can run Traccar client properly. Because no small number of our study targets is the disabled and the aged. Some of them use a quite old phone that might have hardware or software issues.((The disabled and the aged are normally not rich, rather than others, at least in Korea. (I think it is global phenomenon) Anyhow, we'd better ready for a participant who has a phone that we're not familiar with. )) \\ Unfortunately, we don't have the specific information of previous participant's devices. So, we should imagine the device which might cause some problems and should be sifted out before experiment begin. First, we picked old phones with some troubles. We want to know whether these legacy devices can run Traccar client properly. Because no small number of our study targets is the disabled and the aged. Some of them use a quite old phone that might have hardware or software issues.((The disabled and the aged are normally not rich, rather than others, at least in Korea. (I think it is global phenomenon) Anyhow, we'd better ready for a participant who has a phone that we're not familiar with. )) \\
  
줄 38: 줄 38:
 To get more information, go to the GitHub link above. To get more information, go to the GitHub link above.
  
-==== Result and Analysis ====+===== Result and Analysis =====
 We configured the client to send its location every 60 seconds. Theoretically, it should've transmit data within 1-2 minutes even if there is some include calculation delays. Here is count of the gaps in minute. We configured the client to send its location every 60 seconds. Theoretically, it should've transmit data within 1-2 minutes even if there is some include calculation delays. Here is count of the gaps in minute.
 ^         ^ < 2 min ^   5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^ ^         ^ < 2 min ^   5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^
줄 44: 줄 44:
 ^DBLAB0103| 8852    | 144 |   7|  14|    5|    1|    3|      0|   9026|      98.0722 | ^DBLAB0103| 8852    | 144 |   7|  14|    5|    1|    3|      0|   9026|      98.0722 |
 Although the iPhone(0102)'s overall delays are shorter than the other, the count is remarkably low. The reason why it didn't send anything is that iOS blocked Traccar several times. Thus, iOS has got many long gaps. \\  Although the iPhone(0102)'s overall delays are shorter than the other, the count is remarkably low. The reason why it didn't send anything is that iOS blocked Traccar several times. Thus, iOS has got many long gaps. \\ 
-=== Case 1: Low battery and shutting down ===+==== Case 1: Low battery and shutting down ====
 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^
줄 53: 줄 53:
 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.
   * 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 2: Low battery and energy saving mode ===+==== Case 2: Low battery and energy saving mode ====
 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^
줄 62: 줄 62:
 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 (#1738)**
 ^index ^ servertime ^ devicetime ^   latitude ^ longitude ^ battery_level ^ delay^ ^index ^ servertime ^ devicetime ^   latitude ^ longitude ^ battery_level ^ delay^
줄 75: 줄 75:
   * iPhone: Some data could be missed if the participant would have clicked pop-up unconsciously.   * 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 in advance.   * Android (Samsung): Some data could be missed if the participant would have turned off energy saving options in advance.
-=== 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| ^118 (Delayed) | **2019-01-21 10:40:36.633** | **2019-01-21 09:27:28** | 37.555067 | 127.050128    |      37.0|    00:00:00|
줄 85: 줄 85:
   * If the user didn't go outside for a long time, we could be misunderstood this case as Case 3.   * If the user didn't go outside for a long time, we could be misunderstood this case as Case 3.
  
-==== Summary ====+===== Summary =====
   * Most gaps caused by sleep/idle mode of the operating system. There is no data loss unless the user forgot carrying his phone.   * Most gaps caused by sleep/idle mode of the operating system. There is no data loss unless the user forgot carrying his phone.
   * 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's client unblocked.    * 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's client unblocked. 
   * Battery issue is not trivial.   * Battery issue is not trivial.
  
-==== Future works ====+===== 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.   * 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.   * 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.   * All participant have to take a pre-test period at least three days. We could assure Traccar working on the device fine.
traccar-test-01.txt · 마지막으로 수정됨: 2021/04/13 06:54 (바깥 편집)