S18: Spybot - Revision history

Proj user1: /* References Used */

2018-05-27T08:39:02Z

‎References Used

Proj user1: /* Testing & Technical Challenges */

2018-05-27T08:37:57Z

‎Testing & Technical Challenges

Proj user1: /* Connecting to the Pi Zero W */

2018-05-27T01:20:36Z

‎Connecting to the Pi Zero W

Proj user1: /* Team Members & Responsibilities */

2018-05-26T21:36:00Z

‎Team Members & Responsibilities

Proj user1: /* Abstract */

2018-05-26T21:35:34Z

‎Abstract

Proj user1: /* Implementation */

2018-05-26T21:33:48Z

‎Implementation

Proj user1: /* Implementation */

2018-05-26T21:32:47Z

‎Implementation

Proj user1: /* Implementation */

2018-05-26T21:32:37Z

‎Implementation

Proj user1: /* Time of Flight Sensor */

2018-05-26T21:25:56Z

‎Time of Flight Sensor

Proj user1: /* Testing & Technical Challenges */

2018-05-26T21:19:54Z

‎Testing & Technical Challenges

@@ Line 386: / Line 386: @@
 * [https://github.com/ccrisan/motioneyeos/wiki MotionEyeOS Source Code]
 * [https://github.com/controlwear/virtual-joystick-android JoystickView]
 === Appendix ===
 None

← Older revision		Revision as of 08:37, 27 May 2018
Line 358:		Line 358:

	The Time of Flight sensor was very tricky to bring-up as little to no datasheet was provided. The sensor is from STMicroelectronics. The datasheet does not provide any register information, such as register address and register information. They expect you to use their pre-built API or their development kit, so the whole sensor was a black-box. Although a pre-built API was provided, the whole driver layer was written for Windows. Reverse engineering had to be done by swapping out the Window linkage to SJone's driver interface (I2C).		The Time of Flight sensor was very tricky to bring-up as little to no datasheet was provided. The sensor is from STMicroelectronics. The datasheet does not provide any register information, such as register address and register information. They expect you to use their pre-built API or their development kit, so the whole sensor was a black-box. Although a pre-built API was provided, the whole driver layer was written for Windows. Reverse engineering had to be done by swapping out the Window linkage to SJone's driver interface (I2C).
		+
		+	=== Android Application ===
		+	Making the App was challenging because it was the first time developing an Android application. Basic concepts of Android programming had to be learnt quickly in the early development cycle of the project.
		+	<br>
		+	Every new feature of the App was tested rigorously so the App would not crash or stop working.
		+	Since the app receives packets from the SJone board, packet parsing needed to be done in the App. There was NullExceptions occurring frequently causing the App to crash. To solve the issue, Android Studio's logger was used in order to print out every packet received. It turns out the App receives an extra byte of information at the beginning of the packet causing indexing-out-of-bound exceptions. The bug was fixed by taking into account that extra byte of information and removing it before the parsing process.

	== Conclusion ==		== Conclusion ==

@@ Line 353: / Line 353: @@
 === Connecting to the Pi Zero W ===
-Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi host, the phones could not discover the Pi making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone, the results would be consistent with the feed from the camera being able to broadcast to the host phone.
+Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi access point, the phones could not discover the Pi, making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone, the results would be consistent with the feed from the camera being able to broadcast to the host phone.
 === VL53L0X Time of Flight Sensor ===

@@ Line 14: / Line 14: @@
 **   Android app & bluetooth communication
 *  Jason Tran
-**   PCB design & RC car firmware
+**   PCB design & RC car firmware & Time-of-Flight sensor
 *  Sophia Quan
 **   Servo camera mount and camera integration

@@ Line 6: / Line 6: @@
 == Abstract ==
-The team will develop a RC car driven remotely with an Android smartphone. The RC car will be equipped with a camera to provide real-time visual feedback to the smartphone. The camera will also be mounted on a servo to add the capability to change the camera angle. The SJOne will be used to drive the motor and servo of the car in addition to the camera’s servo. The Android smartphone will communicate with the SJOne using Bluetooth. The Android smartphone will be used to command the SJOne and drive the car and motorized camera. The RaspberryPi will stream visual data to the Android smartphone.
+The team will develop a RC car driven remotely with an Android smartphone. The RC car will be equipped with a camera to provide real-time visual feedback to the smartphone. The camera will also be mounted on a servo to add the capability to change the camera angle. The SJOne will be used to drive the motor and servo of the car in addition to the camera’s servo. The Android smartphone will communicate with the SJOne using Bluetooth. The Android smartphone will be used to command the SJOne and drive the car and motorized camera. The RaspberryPi will stream visual data to the Android smartphone. Additionally, collision avoidance was added to prevent the RC car from colliding with objects in front.
 == Objectives & Introduction ==

@@ Line 270: / Line 270: @@
 The RC car control logic is primarily controlled via the Android app. There are 2 flags that control the RC car's movement and direction. A forward/backward flag is used to control the RC car to move forward or backwards. A left/right flag is used to control the direction of where to steer.
 <br>
 When the distance sensor is blocked and below a threshold, for example, 300 millimeters, the RC car will be unable to move forward even when the user increase the speed percentage to drive the motor.
 <br>

@@ Line 267: / Line 267: @@
 ''' RC car control logic'''
 The RC car control logic is primarily controlled via the Android app. There are 2 flags that control the RC car's movement and direction. A forward/backward flag is used to control the RC car to move forward or backwards. A left/right flag is used to control the direction of where to steer.
 <br>

← Older revision		Revision as of 21:32, 26 May 2018
Line 267:		Line 267:

	''' RC car control logic'''		''' RC car control logic'''
		+	The RC car control logic is primarily controlled via the Android app. There are 2 flags that control the RC car's movement and direction. A forward/backward flag is used to control the RC car to move forward or backwards. A left/right flag is used to control the direction of where to steer.
		+	<br>
		+	When the distance sensor is blocked and below a threshold, for example, 300 millimeters, the RC car will be unable to move forward even when the user increase the speed percentage to drive the motor.
		+	<br>
	[[File:cmpe244 s18 spybot drive control logic.png\|center\|car control logic]]		[[File:cmpe244 s18 spybot drive control logic.png\|center\|car control logic]]

@@ Line 349: / Line 349: @@
 Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi host, the phones could not discover the Pi making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone, the results would be consistent with the feed from the camera being able to broadcast to the host phone.
-=== Time of Flight Sensor ===
+=== VL53L0X Time of Flight Sensor ===
-The Time of Flight sensor was very tricky to bring-up as little to no datasheet was provided.
+The Time of Flight sensor was very tricky to bring-up as little to no datasheet was provided. The sensor is from STMicroelectronics. The datasheet does not provide any register information, such as register address and register information. They expect you to use their pre-built API or their development kit, so the whole sensor was a black-box. Although a pre-built API was provided, the whole driver layer was written for Windows. Reverse engineering had to be done by swapping out the Window linkage to SJone's driver interface (I2C).
 == Conclusion ==

← Older revision		Revision as of 21:19, 26 May 2018
Line 348:		Line 348:

	Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi host, the phones could not discover the Pi making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone, the results would be consistent with the feed from the camera being able to broadcast to the host phone.		Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi host, the phones could not discover the Pi making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone, the results would be consistent with the feed from the camera being able to broadcast to the host phone.
		+
		+	=== Time of Flight Sensor ===
		+
		+	The Time of Flight sensor was very tricky to bring-up as little to no datasheet was provided.

	== Conclusion ==		== Conclusion ==