System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

even complex in<strong>for</strong>mation can be transferred to and displayed on a mobile device.The communication also can be handled over the internet, which allowsthe system to send the data to devices all over the world. The developer canbe miles away to check the robots state and give advice <strong>for</strong> users at the localside. Like the resources on a robot the resources of mobile devices are surelylimited. The system needs to be lightweight and save resources as much aspossible. For example, when observing the robot the mobile phone should notuse up all the battery within 5 minutes.1.3 Use Cases: What a Developer does with the<strong>System</strong>In the appendix of this thesis the use cases <strong>for</strong> the interaction between a developerand the system attached to the robot are described. Important usecases are the request <strong>for</strong> in<strong>for</strong>mation of the components on the robot and therequest <strong>for</strong> components to be logged.The use case “Request a component” explains the way how a component isrequested from the robot. When the expert is successfully connected to theobservation system, he can request the list of components offered by the system.Selecting a single component will trigger the component on the probe to startpublishing its in<strong>for</strong>mation. The in<strong>for</strong>mation is displayed as different views onthe mobile device.The use case “Request components to be logged” starts a logging cycle on theprobe. This cycle collects data from selected components, filters it to the needsof the developer and prints them to a logging file. The developer can selectfrom available components on a selection view and execute the cycle. Whilethe system probe is collecting, it creates temporary files <strong>for</strong> backup. When thedeveloper stops the cycle or disconnects from the probe, the collected data willbe saved as a unique file on the file system.1.4 OutlineComponents running on a robot can be hard to observe. In this thesis a systemis designed and implemented, that allows to filter in<strong>for</strong>mation from componentsof the robot and collect them into several views on external devices like mobilephones. Chapter 2 introduces some work that is related to the the systemcreated in this thesis. Chapter 3 describes the requirements <strong>for</strong> the systemand chapter 4 explains the systems environment. Chapter 5 covers the design3
of the system and the decisions made <strong>for</strong> the communication interface. Theimplementation is described in chapter 6. This chapter shows the implementationof the system attached to the software of the robot and two differentclients created <strong>for</strong> the representation of the in<strong>for</strong>mation. The capability of theimplementation is tested and described in chapter 7. Goal of the evaluationwas to show the occurring system load on the robot running a task and thelatency <strong>for</strong> exchanging data on the mobile device. Chapter 8 gives a conclusionon how the implementation worked out followed by chapter 9 giving an outlookon future work to be done with the system.4
Page 1: Bringing System <s
Page 5 and 6: AbstractSystem <st
Page 7: output, so each component is offeri
Page 11 and 12: created a telelaboratory where two
Page 13 and 14: Like the telelaboratory there is a
Page 15 and 16: with a very high frequency which ma
Page 17 and 18: Due to improving technology the use
Page 19 and 20: Figure 4.1: ToBI platfor</s
Page 21 and 22: Figure 4.3: The architecture behind
Page 23 and 24: Figure 4.5: Typical instant messagi
Page 25 and 26: 5 System DesignThe
Page 27 and 28: Figure 5.2: Message exchange betwee
Page 29 and 30: Figure 5.4: Beacon running between
Page 31 and 32: Figure 5.5: Reading and processing
Page 33 and 34: data and only forw
Page 35 and 36: For example a developer can select
Page 37 and 38: Figure 5.13: Principle of tabbed na
Page 39 and 40: 6.1 The Communication InterfaceThe
Page 41 and 42: 6.2 The Probe - Implementation of t
Page 43 and 44: stop all active processes of the co
Page 45 and 46: is received containing the TAG of t
Page 47 and 48: The selected sensors give a good im
Page 49 and 50: 1 2 4 6 8 Listing 6.2: Example of t
Page 51 and 52: TabConfig - The Status ViewThe TabC
Page 53 and 54: Each view adds a listener to the co
Page 55 and 56: LoginController which also observes
Page 57 and 58: tends the JPanel class. The templat
Page 59 and 60:
7 EvaluationIn the previous chapter
Page 61 and 62:
Name Description CharactersSingleli
Page 63 and 64:
Figure 7.1: Latency of receiving da
Page 65 and 66:
For this thesis only a rough estima
Page 67 and 68:
Laptop CPU load without Probe CPU l
Page 69 and 70:
8 ConclusionsIn the context of this
Page 71 and 72:
9 OutlookGiven this new tool its no
Page 74:
BibliographyBurrell, A. and A. Soda
Page 77 and 78:
6.10 Main classes of the Java clien
Page 79 and 80:
AppendixUse CasesUse Case 1: Connec
Page 81 and 82:
Use Case 4: Disconnect from compone
Page 83 and 84:
Use Case 9: Sending beacon to keep
Page 85 and 86:
Figure 9.4: Latency of receiving da
show all

System Introspection for System Analysis on Mobile Devices

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?