S15: Vision RC Car - Revision history

Proj user3: /* Project Video */

2015-05-27T02:57:06Z

‎Project Video

Proj user3: /* Testing & Technical Challenges */

2015-05-27T01:01:40Z

‎Testing & Technical Challenges

Proj user3: /* References Used */

2015-05-27T01:01:06Z

‎References Used

Proj user3: /* Testing & Technical Challenges */

2015-05-27T00:11:39Z

‎Testing & Technical Challenges

Proj user3: /* Implementation */

2015-05-27T00:11:14Z

‎Implementation

Proj user3: /* Server */

2015-05-26T23:59:08Z

‎Server

Proj user3: /* SJSU One Board Initialization */

2015-05-26T23:53:24Z

‎SJSU One Board Initialization

Proj user3: /* Server Communication */

2015-05-26T23:49:30Z

‎Server Communication

Proj user3: /* Software Design */

2015-05-26T23:41:25Z

‎Software Design

Proj user3: /* Hardware Interface */

2015-05-26T23:35:52Z

‎Hardware Interface

@@ Line 203: / Line 203: @@
 === Project Video ===
-Upload a video of your project and post the link here.
+https://youtu.be/WNrr4Xq1Ctg
 === Project Source Code ===

← Older revision		Revision as of 01:01, 27 May 2015
Line 192:		Line 192:

	'''Solution''' - Research and use a communication protocol from client to server. Our choice was socket.io.		'''Solution''' - Research and use a communication protocol from client to server. Our choice was socket.io.
		+
		+	=== Issue #2 ===
		+
		+	=== Issue #3 ===
		+
		+	=== Issue #4 ===

	== Conclusion ==		== Conclusion ==

← Older revision		Revision as of 01:01, 27 May 2015
Line 210:		Line 210:

	http://tronixlabs.com/news/tutorial-l298n-dual-motor-controller-module-2a-and-arduino/		http://tronixlabs.com/news/tutorial-l298n-dual-motor-controller-module-2a-and-arduino/
		+
		+	https://github.com/drejkim/edi-cam
		+
		+	http://socket.io/

← Older revision		Revision as of 00:11, 27 May 2015
Line 187:		Line 187:

	== Testing & Technical Challenges ==		== Testing & Technical Challenges ==
−	~~Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again?~~
−	~~Make a smooth transition to testing section and described what it took to test your project.~~
−
−	~~Include sub-sections that list out a problem and solution, such as:~~

	=== Issue #1 ===		=== Issue #1 ===

@@ Line 165: / Line 165: @@
 ==== Motor Controls ====
 This was implemented by using the SJ one to relay commands from the Intel Edison to the motor-controller. The SJ One utilizes 3 tasks: command, propulsion, and steering. The command task is the highest priority task, priority 4, and waits for WASD commands from the Edison on the UART3 port. The propulsion and steering tasks have a priority of 3. The propulsion and steering task will sleep on an empty queue until the command task sends the appropriate command to the shared queue. Depending on the command received by the propulsion and steering tasks, the SJ One outputs the appropriate digital signals to the motor-controller, that in turn drives the motor. The digital signals drive the motor-controller for a minimum of 50ms.
 ==== Server ====
-The server was implemented on the Intel Edison. The server consisted of node.js and express. Initially, a server was made that could present the user with any .html file that existed, but later on in the project when the webcam server was integrated, this functionality was lost. The implemented server was a modified version of the webcam server created by Dr. Esther Jun Kim. This server was hard-coded to present users with the "index.html" file. Dr. Kim's code can be found at https://github.com/drejkim/edi-cam.
+The server was implemented on the Intel Edison. The server consisted of node.js and express. Initially, a server was made that could present the user with any .html file that existed, but later on in the project when the webcam server was integrated, this functionality was lost. The implemented server was a modified version of the webcam server created by Dr. Esther Jun Kim. This server was hard-coded to present users with the "index.html" file. Dr. Kim's code can be found at https://github.com/drejkim/edi-cam. When a command is received from the client, the server relays the message to the SJ One board.
 == Testing & Technical Challenges ==

← Older revision		Revision as of 23:59, 26 May 2015
Line 167:		Line 167:

	==== Server ====		==== Server ====
		+
		+	The server was implemented on the Intel Edison. The server consisted of node.js and express. Initially, a server was made that could present the user with any .html file that existed, but later on in the project when the webcam server was integrated, this functionality was lost. The implemented server was a modified version of the webcam server created by Dr. Esther Jun Kim. This server was hard-coded to present users with the "index.html" file. Dr. Kim's code can be found at https://github.com/drejkim/edi-cam.

	== Testing & Technical Challenges ==		== Testing & Technical Challenges ==

@@ Line 163: / Line 163: @@
 == Implementation ==
-==== Server Communication ====
+==== Motor Controls ====
-#Enable UART1 serial port.
+This was implemented by using the SJ one to relay commands from the Intel Edison to the motor-controller. The SJ One utilizes 3 tasks: command, propulsion, and steering. The command task is the highest priority task, priority 4, and waits for WASD commands from the Edison on the UART3 port. The propulsion and steering tasks have a priority of 3. The propulsion and steering task will sleep on an empty queue until the command task sends the appropriate command to the shared queue. Depending on the command received by the propulsion and steering tasks, the SJ One outputs the appropriate digital signals to the motor-controller, that in turn drives the motor. The digital signals drive the motor-controller for a minimum of 50ms.
 ==== SJSU One Board Initialization ====

@@ Line 156: / Line 156: @@
 === Software Design ===
 The software design on the SJ One utilized FreeRTOS queue's for cooperative context switching, as well as the UART driver's provided with the development environment. The UART3 driver was contained within the "command" task, and would wait infinitely for data, in the form of single characters, to be received from the Intel Edison. Once the data is received, the command task distributes the command to the appropriate task. The three task's that wait for commands are in charge of steering, propulsion, and combined steering and propulsion commands. The motor controller has two inputs for each bridge. Mismatching digital signals, e.g. H and L, drive the motors, while equal digital signals turn the motor controller off. In the case of the combined commands task, all four signals are distributed.
+[[File: S15 244 G8 FlowDiagramRTOS.jpg|500px|center]]
 The Edison software design was composed of shell scripts, JavaScript, and the Yaler. The shell scripts were utilized to open the UART1 serial ports on the Edison. A shell script was designed open the necessary serial port, start the server, and create the Yaler tunnel. Yaler, Yaler.net, provides Connectivity as a Service. The Yaler application is un-packaged and run on the Edison, which creates a web-tunnel that is accessible through the use of a relay domain provided by Yaler.net.

@@ Line 152: / Line 152: @@
 <br><br>
 [[File: S15 244 G8 new Software.jpg|450px|left]]
-[[File: S15 244 G8 Basic new.jpg|400px|right]]
+[[File: S15 244 G8 Basic new.jpg|400px|center]]
 === Software Design ===