S15: Wireless Power Transfer System - Revision history

Proj user2: /* Testing & Technical Challenges */

2015-05-25T06:38:36Z

‎Testing & Technical Challenges

Proj user2: /* Team Members & Responsibilities */

2015-05-25T06:37:14Z

‎Team Members & Responsibilities

Proj user2: /* Team Members & Responsibilities */

2015-05-25T06:35:22Z

‎Team Members & Responsibilities

Proj user2: /* Software Design */

2015-05-25T06:32:36Z

‎Software Design

Proj user2: /* Hardware Interface */

2015-05-25T06:30:52Z

‎Hardware Interface

Proj user2: /* Design & Implementation */

2015-05-25T06:28:06Z

‎Design & Implementation

Proj user2: /* Software Design */

2015-05-25T06:26:13Z

‎Software Design

Proj user2 at 06:08, 25 May 2015

2015-05-25T06:08:54Z

Proj user2 at 06:08, 25 May 2015

2015-05-25T06:08:16Z

Proj user2 at 05:26, 25 May 2015

2015-05-25T05:26:08Z

@@ Line 307: / Line 307: @@
 == 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?
+Some of the challenges faced during the projects were:
-Make a smooth transition to testing section and described what it took to test your project.
+=== Issue #1 ===
 <u>ISSUE</u><br>
 The current sensing on the receiver through the 1 ohm resistor has a lot of noise riding on the signal. Using a software digital filter was not possible since it would put the software in a blocking mode for the duration of the capture. This would change the topology of the software architecture and deviate from being a good RTOS implementation. A quick alternative option needed to be implemented.
@@ Line 321: / Line 317: @@
 ) to implement a Hardware filter before the ADC readings were taken. Even with hardware filter the signal was still noisy. Along with Hardware filter implementation, there was still noise on the signal and showed in terminal window of software. This variability in signal would cause "Hunting" on the transmitter platform where the platform would jitter. A software digital filter was implemented so the signal was smooth and some hysteresis was added to the PID control system of the tuning table.
-=== My Issue #2 ===
+=== Issue #2 ===
 <u>ISSUE</u><br>
 The voltage output from the receiving antenna was ~33Vrms and all the electronics for the SJSU board were running at 3.3V logic. Even with voltage dividers it still presented a danger to damage the SJSU board ADC channel in case a large spike lasting long period was generated.
@@ Line 328: / Line 324: @@
 A very cheap and simple foldback voltage regulator was implemented which produced 3.3V DC. This ensured that the absolute maximum voltage that the ADC would see was 3.3V. To further protect the SJSU board peripherals, a Instrumentation amplifier block was placed between the 3.3V supply and the ADC. This gave us some confidence that in the worst condition the damage will first be sustained by the Instrumentation amplifier and not the ADC channel.
-=== My Issue #3 ===
+=== Issue #3 ===
 When we first implemented the software layers, we handled and decoded all the wireless packages in the top level while the lower two layers also required data feedback to the top level. In this case, the top level needed to listen two queues or to fill feedback to the wireless quese which are both impossible.
 So we changed the whole architecture and moved the decoding and wireless feedback to the middle layers that made the whole software simpler without any layer violation.

@@ Line 32: / Line 32: @@
       - Learn wireless mesh driver and develop wireless mesh interface to send information between transmitter and receiver
       - Design and implement command parser for master/slave
-      - Tasks between master and slave
+      - Communication layer for tasks between master and slave
 *  Team Member 4

@@ Line 32: / Line 32: @@
       - Learn wireless mesh driver and develop wireless mesh interface to send information between transmitter and receiver
       - Design and implement command parser for master/slave
 *  Team Member 4

@@ Line 236: / Line 236: @@
 [[File:S15_244_G11_Software_FC.jpg]]
-The wireless task on the master sends out a broadcast signal periodically to see what slave devices are present in the area and is always waiting on the slave nodes that may be present. The slave device, in our case the receiver, asks the master to start transmitting power on first waking up. The total data transfer that can take place through one packet is 32 bytes, of which 24 bytes is meaningful data and 8 bytes is overhead.
+The wireless task on the master sends out a broadcast signal periodically to see what slave devices are present in the area and is always waiting on the slave nodes that may be present. The slave device, in our case the receiver, asks the master to start transmitting power on first waking up. The total data transfer that can take place through one packet is 32 bytes, of which 24 bytes is meaningful data and 8 bytes is overhead. Each time the slave or master spits out a packet, it waits for the acknowledgement on successful delivery by the virtue of wireless API used.
 Package structures between three layers:

← Older revision		Revision as of 06:30, 25 May 2015
Line 213:		Line 213:

	=== Hardware Interface ===		=== Hardware Interface ===
−	In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.

	[[File:S15_244_G11_MotorIF_BD.jpg\|800px\|thumb\|centre\|Motor Interface Block Diagram]]		[[File:S15_244_G11_MotorIF_BD.jpg\|800px\|thumb\|centre\|Motor Interface Block Diagram]]

@@ Line 194: / Line 194: @@
 The image below shows the project assembly. The loop on the left is the transmitter connected to a power supply while the one on the right is the receiver and mounted on a DC stepper motor (not visible in the picture) to change its orientation to the position of maximum power transfer. The load motor can be seen attached to the receiver loop and is driven wirelessly.
-[[File:S15_244_G11_Hardware_Assembly.png|800px|thumb|centre|Project Assembly with the Transmitter (right) and Receiver(left) loops]]
+[[File:S15_244_G11_Hardware_Assembly.png|600px|thumb|centre|Project Assembly with the Transmitter (right) and Receiver(left) loops]]
 The sections below provide a descriptive overview of the hardware block and flow diagram.

← Older revision		Revision as of 06:26, 25 May 2015
Line 237:		Line 237:
	[[File:S15_244_G11_Software_FC.jpg]]		[[File:S15_244_G11_Software_FC.jpg]]

		+	The wireless task on the master sends out a broadcast signal periodically to see what slave devices are present in the area and is always waiting on the slave nodes that may be present. The slave device, in our case the receiver, asks the master to start transmitting power on first waking up. The total data transfer that can take place through one packet is 32 bytes, of which 24 bytes is meaningful data and 8 bytes is overhead.
	Package structures between three layers:		Package structures between three layers:

← Older revision		Revision as of 06:08, 25 May 2015
Line 330:		Line 330:
	When we first implemented the software layers, we handled and decoded all the wireless packages in the top level while the lower two layers also required data feedback to the top level. In this case, the top level needed to listen two queues or to fill feedback to the wireless quese which are both impossible.		When we first implemented the software layers, we handled and decoded all the wireless packages in the top level while the lower two layers also required data feedback to the top level. In this case, the top level needed to listen two queues or to fill feedback to the wireless quese which are both impossible.
	So we changed the whole architecture and moved the decoding and wireless feedback to the middle layers that made the whole software simpler without any layer violation.		So we changed the whole architecture and moved the decoding and wireless feedback to the middle layers that made the whole software simpler without any layer violation.
−
−	~~=== My Issue #4 ===~~
−	~~<u>ISSUE</u><br>~~
−
−
−	~~<u>RESOLUTION</u><br>~~
−