4.1.3 Wireless Case Name: Case three Wireless – Unit tested: CC2500 Transceiver Assumptions: The MSP430 MCU is able to read and output power consumption information to the transceiver from a given outlet. Test Data: Hard coded data from software and power measurements given by the MSP430. Steps to be executed: Hard code data into the EZ430-RF2500 wireless Development Tool Using this code send a data packet to a different transceiver Read data from the transceiver and compare it to the original packet Autonomously send measured data from one power strip to another. Each power strip contains one microcontroller and one transceiver. Test low power consumption using wireless information. When a sleep mode signal is received the MSP430 should enter sleep mode. If a turn-on signal is received the MSP430 should send a second packet of information. The MSP430 should send a packet of information every 5 seconds. Repeat steps 1 through 4 indoors with a line of sight range from 10ft to 100ft. Again test for this range between 2 to 3 rooms on the same floor and then between rooms from adjacent floors. Expected Result: The transceiver should be able to send and receive accurate packet information between rooms. Summary: The wireless modules will need to be checked first for functionality and then for range and reliability. Communication between two to three rooms at 50 feet is necessary. If adequate range is not met then considering different antenna options can increase the range. Each unit should be able to consistently receive and transfer data bytes. Once all power strips are functional then the design will be tested to find the limitations in range of the design. The open air tests will be used to determine to maximum range of our design. By adding walls in between the wireless communication we can see how much of an effect different materials have on the range of the system. Case Name: Case four LCD – Unit tested: QSscreen Controller Assumptions: MSP430 is functional and can correctly send and receive data to other microcontrollers.
4.1.3 Wireless Case Name: Case three – Wireless Unit tested: CC2500 Transceiver Assumptions: The MSP430 MCU is able to read and output power consumption information to the transceiver from a given outlet. Test Data: Hard coded data from software and power measurements given by the MSP430. Steps to be executed: Hard code data into the EZ430-RF2500 wireless Development Tool Using this code send a data packet to a different transceiver Read data from the transceiver and compare it to the original packet Autonomously send measured data from one power strip to another. Each power strip contains one microcontroller and one transceiver. Test low power consumption using wireless information. When a sleep mode signal is received the MSP430 should enter sleep mode. If a turn-on signal is received the MSP430 should send a second packet of information. The MSP430 should send a packet of information every 5 seconds. Repeat steps 1 through 4 indoors with a line of sight range from 10ft to 100ft. Again test for this range between 2 to 3 rooms on the same floor and then between rooms from adjacent floors. Expected Result: The transceiver should be able to send and receive accurate packet information between rooms. Summary: The wireless modules will need to be checked first for functionality and then for range and reliability. Communication between two to three rooms at 50 feet is necessary. If adequate range is not met then considering different antenna options can increase the range. Each unit should be able to consistently receive and transfer data bytes. Once all power strips are functional then the design will be tested to find the limitations in range of the design. The open air tests will be used to determine to maximum range of our design. By adding walls in between the wireless communication we can see how much of an effect different materials have on the range of the system. Case Name: Case four – LCD Unit tested: QSscreen Controller Assumptions: MSP430 is functional and can correctly send and receive data to other microcontrollers.
Final%20Paper%20120%20pages.docx