S14: Hyperintelligent NFC Locker of the Future - Revision history

Preet: /* Project Source Code */

2014-08-06T23:59:47Z

‎Project Source Code

Proj user18: /* Actuator Sub module Software Design */

2014-05-24T16:39:32Z

‎Actuator Sub module Software Design

Proj user18: /* Testing & Technical Challenges */

2014-05-24T16:37:38Z

‎Testing & Technical Challenges

Proj user18: /* UART Communication Software Implementation */

2014-05-24T16:37:23Z

‎UART Communication Software Implementation

Proj user18: /* UART Communication Software Implementation */

2014-05-24T16:37:06Z

‎UART Communication Software Implementation

Proj user18: /* UART Micro-Controller Interface */

2014-05-24T16:30:00Z

‎UART Micro-Controller Interface

Proj user18: /* UART Communication Software Design */

2014-05-24T16:28:32Z

‎UART Communication Software Design

Proj user18: /* UART Micro-Controller Interface */

2014-05-24T16:27:06Z

‎UART Micro-Controller Interface

Proj user18: /* Actuator Subsystem Interface */

2014-05-24T16:24:17Z

‎Actuator Subsystem Interface

Proj user18: /* Actuator Subsystem Interface */

2014-05-24T16:23:24Z

‎Actuator Subsystem Interface

@@ Line 351: / Line 351: @@
 === Project Source Code ===
-Send me your zipped source code and I will upload this to SourceForge and link it for you.
+*  [https://sourceforge.net/projects/sjsu/files/CmpE244_SJSU_S2014/ Sourceforge source code link]
 == References ==

@@ Line 273: / Line 273: @@
 ====Actuator Sub module Software Design====
-For this actuator's submodule, PWM is needed to control the actuator's state (either extending or retracting). PWM is composed of a frequency and duty cycle. Because the actuator submodule has an "on" or "off" state, the duty cycles used are either 99% (max) or 0% (min). Additionally, frequency is not important for this module
+For this actuator's submodule, PWM is needed to control the actuator's state (either extending or retracting). PWM is composed of a frequency and duty cycle. Because the actuator submodule has an "on" or "off" state, the duty cycles used are either 99% (max) or 0% (min). Additionally, a specific frequency is not important for this module
 As shown in the hardware implementation of the actuator sub module, in order to extend or retract the actuator, 2 PWM outputs are needed. Each PWM output is connected to the motor controller's inputs. The motor controller inputs dictates the direction of the signal. In order to extend, one PWM1 output must be active, while PWM2 output must be off. Likewise, in order to retract, PWM2 output must be active, while PWM1 output is off.

← Older revision		Revision as of 16:37, 24 May 2014
Line 318:		Line 318:

	== 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:~~

	=== Testing ===		=== Testing ===

← Older revision		Revision as of 16:37, 24 May 2014
Line 313:		Line 313:


−	The system consists a master and a slave. There are two components within this password structure: The locker ID(1 byte) and the NFC password(4bytes). Once the master uC has received the NFC data, it sends the password structure to the slave. The slave is predefined with an array of passwords. The slave will search the array of passwords. If the slave finds a matching password, it will send a verification byte to the master uC. If it does not find a password, the slave will send a rejection byte. After receive the verification or rejection byte, the master uC will then toggle its actuator to lock or unlock the locker.	+	The system consists a master and a slave. There are two components within this password structure: The locker ID(1 byte) and the NFC password(4bytes). Once the master uC has received the NFC data, it sends the password structure to the slave. The slave is predefined with an array of passwords. The slave will search the array of passwords. If the slave finds a matching password, it will send a verification byte to the master uC. If it does not find a password, the slave will send a rejection byte. After receive the verification or rejection byte, the master uC will then toggle its actuator to lock or unlock the locker. Additionally, in this implementation, there are multiple slaves with its independent UART Buses. Because more than one slave that may want to communicate to with the slave uC concurrently, the slave uses FreeRTOS to context switch. This will allow the slave to process the passwords concurrently.
−
−	Additionally, in this implementation, there are multiple slaves with its independent UART Buses. Because more than one slave that may want to communicate to with the slave uC concurrently, the slave uses FreeRTOS to context switch. This will allow the slave to process the passwords concurrently.

	====Actuator Software Implementation====		====Actuator Software Implementation====

@@ Line 312: / Line 312: @@
 [[File:CmpE146 S14 NFCLocker Software UART.jpg|500px]]
-This system consists a master and a slave. Though using one of the master's UART ports, the master sends its locker ID(1 byte) and the phone's password(4 bytes) as a password. The slave will receive the 5 bytes of data and search its pre-defined array for the that unique password. The slave will then send 1 byte to the master distinguishing if the password is valid or not.
 ====Actuator Software Implementation====

@@ Line 201: / Line 201: @@
 [[File:CmpE146 S14 NFCLocker UART.jpg]]
-A master uC initiates the communication with the slave. A master uC will send data from the NFC module to the slave uC. The slave will process the data and either send a verification frame or rejection frame to the master which will enable the master to lock or unlock the locker. In this design, two separate UART ports are used. This allows the slave uC to take in data from both masters when they send data concurrently.
+Originally, the team wanted to use Ethernet as the networking medium between microcontrollers. Due to time constraints, the team abandoned Ethernet implementation and decided to use UART instead. In this UART implementation, a master uC initiates the communication with the slave. A master uC will send data from the NFC module to the slave uC. The slave will process the data and either send a verification frame or rejection frame to the master which will enable the master to lock or unlock the locker. In this design, two separate UART ports are used. This allows the slave uC to take in data from both masters when they send data concurrently.
 === Software Design ===

@@ Line 269: / Line 269: @@
 ====UART Communication Software Design====
-Originally, the team wanted to use Ethernet as the networking medium between microcontrollers. Due to time constraints, the team abandoned Ethernet implementation and decided to use UART instead. The locker system has multiple masters and one slave. In order to implement this design, multiple UART lines are used. The slave acts as a databank of passwords for the masters to communicate with. Because multiple masters may access the slave concurrently, the slave must be able to context switch to perform concurrent password checks.
+The locker system has multiple masters and one slave. In order to implement this design, multiple UART lines are used. The slave acts as a databank of passwords for the masters to communicate with. Because multiple masters may access the slave concurrently, the slave must be able to context switch to perform concurrent password checks.
 ====Actuator Sub module Software Design====

← Older revision		Revision as of 16:24, 24 May 2014
Line 189:		Line 189:


−	An actuator is used as the physical locking mechanism for the locker. An actuator can only extend or retract depending on the direction a PWM signal is given. Because there are only two wires for the actuator, the actuator can only extend or retract, but not both. In order to obtain both functionalities, a motor controller is used. The motor controller that is used has two input signal pins. These input pins allows the PWM ~~signal~~ to flow both directions. With software, the team used two PWM ports in which PWM port 1 will flow with a duty cycle of 99%, while port 2 has duty cycle of 0%. Depending if the actuator needs to lock or unlock, the two PWM ports are toggled. This allows a change of direction within the actuator	+	An actuator is used as the physical locking mechanism for the locker. An actuator can only extend or retract depending on the direction a PWM signal is given. Because there are only two wires for the actuator, the actuator can only extend or retract, but not both. In order to obtain both functionalities, a motor controller is used. The motor controller that is used has two input signal pins. These input pins allows the PWM signals to flow in both directions. With software, the team used two PWM ports in which PWM port 1 will flow with a duty cycle of 99%, while port 2 has duty cycle of 0%. Depending if the actuator needs to lock or unlock, the two PWM ports are toggled. This allows a change of direction within the actuator

	====NFC Interface====		====NFC Interface====

← Older revision		Revision as of 16:23, 24 May 2014
Line 189:		Line 189:


−	An actuator is used as the physical locking mechanism for the locker. An actuator can only extend or retract depending on the direction a PWM signal is given. Because there are only two wires for the actuator, the actuator can only extend or retract, but not both. In order to obtain both functionalities, a motor controller is used. The motor controller that is used has two input signal pins. These input pins allows the PWM signal to flow both directions. With software, the team used two PWM ports in which PWM port 1 will flow with a duty cycle of 99%, while port 2 has duty cycle of 0%. Depending if the actuator needs to lock or unlock, the two PWM ports are toggled. This allows a change of direction within the ~~PWM~~	+	An actuator is used as the physical locking mechanism for the locker. An actuator can only extend or retract depending on the direction a PWM signal is given. Because there are only two wires for the actuator, the actuator can only extend or retract, but not both. In order to obtain both functionalities, a motor controller is used. The motor controller that is used has two input signal pins. These input pins allows the PWM signal to flow both directions. With software, the team used two PWM ports in which PWM port 1 will flow with a duty cycle of 99%, while port 2 has duty cycle of 0%. Depending if the actuator needs to lock or unlock, the two PWM ports are toggled. This allows a change of direction within the actuator

	====NFC Interface====		====NFC Interface====