RF Networking With MSP430 & the ez430-rf2500 Session 2 Miguel Morales, MSP430 Applications 6/5/2008 1

Size: px

Start display at page:

Download "RF Networking With MSP430 & the ez430-rf2500 Session 2 Miguel Morales, MSP430 Applications 6/5/2008 1"

Joshua Darrell Phelps
6 years ago
Views:

2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.

1 RF Networking With MSP430 & the ez430-rf2500 Session 2 Miguel Morales, MSP430 Applications 6/5/ Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 2 1

2 Hardware Setup Connect ez430-rf2500t targets onto RF header Remember to connect JP3! (RF Vcc) Connect MSP-FET430UIF to PC Connect JTAG to EXP5438 JTAG header If you have not installed the driver, please do so at this time Connect USB cable to PC COM If you have not installed the driver, please do so at this time Identify serial port open Device Manager Right click My Computer > Properties > Hardware > Device Manager > Ports (COM & LPT) Look for USB Serial Port (COMxx) 3 Software Setup If you have not done so, please install CCE 4 2

3 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 5 Networking Topologies Device Configurations Access Point (AP) Repeater (RE) Sleeping End Device (SD) End Device (D) RE AP SD D Topologies SD D AP Star AP Star w/ Repeaters Peer2Peer D D D 6 3

Application programming interface (API) Initialization smplstatus_t SMPL_Init(uint8_t (*callback)(linkid_t)); Linking smplstatus_t SMPL_Link(linkID_t *linkid); smplstatus_t SMPL_LinkListen(linkID_t

4 Application programming interface (API) Initialization smplstatus_t SMPL_Init(uint8_t (*callback)(linkid_t)); Linking smplstatus_t SMPL_Link(linkID_t *linkid); smplstatus_t SMPL_LinkListen(linkID_t *linkid); Peer-to-peer messaging smplstatus_t SMPL_Send(lid, *msg, len); smplstatus_t SMPL_Receive(lid, *msg, *len); Configuration smplstatus_t SMPL_Ioctl(object, action, *val); API calls are synchronous Do not return until operation is complete 7 Wireless Sensor Monitor Demo_ED Flowchart s e m a p h o r e 8 4

5 Wireless Sensor Monitor Demo_AP Flowchart 9 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 10 5

EZ430-RF2500 Development Kit MSP430 CC2500:

emulator 1 x AAA battery pack w/expansion

Wireless Sensor Monitor Demo Documentation

6 EZ430-RF2500 Development Kit MSP430 CC2500: 4 x SPI pins 2 x GPIO pins Made accessible to bypass the x2274 Kit includes: 2 x ez430-rf2500t target boards 1 x ez430-rf USB emulator 1 x AAA battery pack w/expansion board Development tools (IAR Kickstart) Wireless Sensor Monitor Demo Documentation (SimpliciTI, Tools) 11 MSP430EXP5438 Experimenter s Board 12 6

Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.

Uses ADC12 to sample accelerometer data Translates data to an (x,y) coordinate;

7 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 13 Lab Overview Tilt and Ambient Noise Sensing Tilt Sensor Uses ADC12 to sample accelerometer data Translates data to an (x,y) coordinate; keeps running memory of coordinate Ambient Noise Sensor Uses ADC12 to sample ambient noise Compares against five thresholds, displayed as volume bars (x,y) 14 7

8 Lab Goals Reinforce learnings from Session 1 Port the sensor applications to a SimpliciTI Project, enabling wireless communication Interleave the multiple real-time application tasks SimpliciTI Tx/Rx Heartbeat Tilt or Ambient Noise Sensing Define a method for distinguishing between applications, data types Implement a method of reliability 15 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 16 8

Lab 2.1 Goals Run the Tilt or Ambient Noise Sensor application 17 Lab 2.1 Tilt & Ambient Noise Sensing Hardware Setup Connect ez430-rf2500t targets onto RF header Remember to connect JP3!

9 Lab 2.1 Goals Run the Tilt or Ambient Noise Sensor application 17 Lab 2.1 Tilt & Ambient Noise Sensing Hardware Setup Connect ez430-rf2500t targets onto RF header Remember to connect JP3! (RF Vcc) Connect MSP-FET430UIF to PC Connect JTAG to EXP5438 JTAG header Connect USB cable to PC COM Identify serial port open MS Device Manager Right click My Computer > Properties > Hardware > Device Manager > Ports (COM & LPT) Look for USB Serial Port (COMxx) 18 9

10 Lab 2.1 Tilt & Ambient Noise Sensing Software Setup RUN YOUR CODE! (5 min) Open CCE Start Menu > All Programs > Texas Instruments > Code Composer Essentials 19 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 20 10

11 Lab 2.2 Goals Integrate the existing Tilt Sensor or Ambient Noise Sensor application into the demo_ed.c from Session 1 21 Lab 2.2 Goals Integrate the existing Tilt Sensor or Ambient Noise Sensor application into the demo_ed.c from Session 1 Commented for Lab 2.2 Commented for Lab

Lab 2.2 Goals Integrate the existing Tilt Sensor or Ambient Noise Sensor application into the demo_ed.c from Session 1 Commented for Lab 2.2 23 Lab 2.

12 Lab 2.2 Goals Integrate the existing Tilt Sensor or Ambient Noise Sensor application into the demo_ed.c from Session 1 Commented for Lab Lab 2.2 Integrating Existing Applications Change active project to tilt_wireless ambient_noise_wireless Note what is already implemented: Hardware initialization and sensor functions Timers, LCD, ADC12 Heartbeat semaphore / temp & vcc sampling What changed / what is new? The application header type message_struct_t Used for Lab 2.3 A callback function scb is defined Used for Lab 2.4 The send_message( ) function Used for Lab

13 Lab 2.2 Integrating Existing Applications To do Add a semaphore for the application declare in Locals section The semaphore should be set in the Timer_A routine #pragma vector=timer0_a1_vector interrupt void TimerA_ISR(void) { case 0x02: /* set the application semaphore here */ break; Check for semaphore in main while loop Copy / paste the main loop of application into semaphore structure, releasing semaphore at the end of main loop while( 1 ){ if( sselfmeasuresem ) { if( application semaphore is set ) { /* insert main loop from application here */ /* release application semaphore here */ Verify using Terminal window 25 Lab 2.2 Integrating Existing Applications (10 Minutes) Solution can be found in: demo_ed_sol_2_2.c To debug the solution project: Right-click demo_ed.c, select Exclude File(s) From Build Right-click demo_ed_sol_2_2.c, un-select Exclude File(s) From Build 26 13

14 Lab 2.2 Solution Commented for Lab Lab 2.2 Solution Set the semaphore in the Timer_A routine /********************************************************* * LOCALS *********************************************************/ static volatile uint8_t sapplicationsem; #pragma vector=timer0_a1_vector interrupt void TimerA_ISR(void) { case 0x02: sapplicationsem = 1; // // Set application semaphore break; Check for semaphore in main while loop Integrate the main loop of application into semaphore structure Release semaphore at the end of main loop while( 1 ){ if( sselfmeasuresem ) { if( sapplicationsem ) { /* insert main loop from application here */ sapplicationsem = 0; 28 14

15 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 29 Lab 2.3 Goals Implement the answers to the following questions: Is there a way to singularly identify my node? How can I distinguish between different types of devices or applications on a network? Access Point Tilt Sensor Ambient Noise How can I distinguish between the data types coming from those networks? Heartbeat Application 30 15

16 Lab 2.3 The Application Header SMPL_header Network ID Device Type ID Data Type ID Application Payload Network ID A value 0 9 identifying one of ten possible nodes in the network Device Type ID Identifies the application type (tilt vs ambient) 1 Access Point 2 Tilt Sensor 3 Ambient Noise Data Type ID Identifies the data type in the application payload 1 Heartbeat data (Vcc & temperature) 2 Application Data typedef struct{ // // Network identifier unsigned char nwkid; // // Tilt sensor vs ambient noise unsigned char devicetypeid; // // Heartbeat vs application data unsigned char dataid; // // Application payload unsigned char msg[ ]; message_struct_t message_struct_t app_package; 31 Lab 2.3 The Application Header To do: Identify the global variable: message_struct_t app_packet; ~/Application/app_support/xxx_support.h Identify the following lines in demo_ed.c: Setting the nwkid Setting the devicetypeid Setting the dataid in sselfmeasuresem block Add/Edit the following lines in demo_ed.c Set the respective dataid in the application semaphore Write the application data to the app_packet.msg[] buffer instead of the buffer[] variable Change the USB_Send_String function to support the app_packet variable instead of the buffer[ ] variable. Debug & Run the project; verify in the terminal window 32 16

17 Lab 2.3 The Application Header Identify the lines in code void linkto( ){ app_packet.nwkid = NWK_ID; // Set the network ID for the node app_packet.devicetypeid = APP_ID; // Set the device type ID for the node // according to tilt or ambient noise while(1){ if(sselfmeasuresem){ app_packet.dataid = HTBT_DATA_ID; // Set the data ID as heartbeat // Comment current USB_Send_String call and uncomment the following USB_Send_String( (unsigned char*)&app_packet.nwkid, 12 ); 33 Lab 2.3 The Application Header Add and edit lines of code void linkto( ){ while(1){ if(sappsem){ app_packet. = ; // // Set Data ID to reflect application data buffer[0] = app_data_value; // // Edit to fill the msg buffer in app_packet buffer[1] = \0 ; // // instead of buffer buffer[2] = 0x0D; buffer[3] = \n ; USB_Send_String(buffer, 4) // // Edit to send the app_packet instead // // see Lab 1_3 comments 34 17

18 Lab 2.3 The Application Header (10 min) Tool Box: #defines: #define HTBT_DATA_ID 1 // Identifier for temp & Vcc data #define APP_DATA_ID 2 // Identifier for tilt or noise sensor data app_packet.dataid = ; app_packet.msg[ i ] = ; Solution can be found in: demo_ed_sol_2_3.c To debug the solution project: Right-click demo_ed.c, select Exclude File(s) From Build Right-click demo_ed_sol_2_3.c, un-select Exclude File(s) From Build 35 Lab 2.3 The Application Header Add and edit lines of code Solution void linkto( ){ while(1){ if(sappsem){ app_packet.dataid = APP_DATA_ID; // Set Data ID to reflect application data app_packet.msg [0] = app_data_value; // app_packet.msg[ ] app_packet.msg [1] = 0x00; // Don t forget the null character! // TX the application packet to UART USB PC COM USB_Send_String( (unsigned char *)&app_packet.nwkid, 7) 36 18

19 Agenda Recap of Session 1 Hardware description Session 2 Lab Overview Lab 2.1 Tilt & Ambient Noise Sensing Lab 2.2 Integrating Existing Applications Lab 2.3 The Application Header Lab 2.4 Methods of Reliability 37 Lab 2.4 Methods of Reliability Demo_AP Q: How can we know if a message has reached its destination? A: Message acknowledgements Demo_ED Q: How can we use message ACKs to improve the reliability of our system? A: Message retries while(1){ if(speerframesem){ if(successfully received message){ Set MSb (ACK) bit in message; Send message as ACK; speerframesem--; // // Define an application-level function void send_message( x, y, z ){ while(missed_packets < threshold) { SMPL_Send( x, y, z ); ); // // Listen for an ACK if (ACK) { message was received; else { missed_packets++; 38 19

20 Lab 2.4 Goals Implement a reliability scheme to improve message delivery 39 Lab 2.4 Goals Implement a reliability scheme to improve message delivery 40 20

21 Lab 2.4 Goals Implement a reliability scheme to improve message delivery 41 Lab 2.4 Methods of Reliability Class is split into 8 x teams See paper at your desk for personal info Each team: Operates as its own network on a separate channel 1 x Access Point Send all information over UART to the network GUI Up to 9 x End Devices 42 21

22 Lab 2.4 Methods of Reliability To do (Access Point): Right click on the project title tilt_wireless : Click Active Build Configuration > Access Point Change the channel of operation in app_support/channel_select.h to the value on the paper at your desk Click Project > Clean Clean the tilt_wireless project Start the debugging session and hit Run Raise your hand if LED1 & LED2 do not light up Close any terminal window that is currently active. Open the ATC08 RF Lab Demo.exe GUI on the PC Select the correct COM port and 9600 baud Hit the Run button the top left-hand side of window) Partner with a teammate for the remainder of lab 43 Lab 2.4 Methods of Reliability To do (End Devices): From your paper on your desk: Identify your team Change the channel of operation Change your node s unique network address Change your node s NWK_ID Verify correct operation using a Terminal window Uncomment all SimpliciTI API calls Replace USB_Send_String() function with send_message( ) Implement message retries in send_message( ) Using #define MISSES_IN_A_ROW 1 // no msg retry Verify correct operation Using #define MISSES_IN_A_ROW 3 Verify correct operation; compare # of missed packets! 44 22

23 Lab 2.4 Methods of Reliability From your paper on your desk: Identify your team / change the channel of operation in // Lines in chann_select.h #define Chan_24XX Change your node s unique network address // Line 62 in Configuration/End Device/smpl_config.dat --define=this_device_address= {0xXX, 0x56, 0x34, 0x12 Change your node s NWK_ID // In the DEFINES section of demo_ed.c #define NWK_ID x // Set the node s network ID Verify correct operation Using the serial port + Terminal window (5 min) 45 Lab 2.4 Methods of Reliability Uncomment SimpliciTI API / replace TX calls void main (void) { while ( SMPL_SUCCESS!= SMPL_Init(sCB) ){. // Init SMPL nwk; join AP linkto( ); void linkto( ){ while ( SMPL_SUCCESS!= SPML_Link( &slinkid1 ){. // Link to the AP while(1){ SMPL_Ioctl( IOCTL_OBJ_RADIO, IOCTL_ACT_RADIO_SLEEP, 0 ); // Put radio to sleep bis_sr_register(lpm3_mode + GIE); // Sleep CPU until Timer ISR SMPL_Ioctl( IOCTL_OBJ_RADIO, IOCTL_ACT_RADIO_AWAKE, 0 ); // Wake radio into IDLE SMPL_Ioctl( IOCTL_OBJ_RADIO, IOCTL_ACT_RADIO_RXON, 0); // Radio IDLE RX // Comment or delete USB_Send_String( ) calls send_message(); // Check both sselfmeasuresem & sappsem! 46 23

24 Lab 2.4 Methods of Reliability Implement message retries in send_message( ) static unsigned char missed_packets = 0; // Static var to keep track of missed_pkts void send_message( linkid_t lid, uint9_t *msg, uint8_t len) // Replaced SMPL_Send( ) in linkto( ) { unsigned char misses, ack_received; if( SMPL_Success == SMPL_Send(sLinkID1, msg, len) ){ wait 2 us; if (received a message in return with the ACK bit set) Loop until ack_received = 1; tx_misses < MISSES_IN_A_ROW else tx_misses++; if(!ack_received ){ missed_packets++; Update LCD display( ); 47 Lab 2.4 Methods of Reliability (10-15 Minutes) Solution can be found in: demo_ed_sol_2_4.c To debug the solution project: Right-click demo_ed.c, select Exclude File(s) From Build Right-click demo_ed_sol_2_4.c, un-select Exclude File(s) From Build 48 24

25 Lab 2.4 Methods of Reliability Implement message retries Solution #define MISSES_IN_A_ROW 3 static unsigned char missed_packets = 0; // Static var to keep track of missed_pkts void send_message( linkid_t lid, uint9_t *msg, uint8_t len) // Replaced SMPL_Send( ) in linkto( ) { unsigned char misses, ack_received; while( misses < MISSES_IN_A_ROW ){ if( SMPL_Success == SMPL_Send(sLinkID1, msg, len) ){ if (received a message in return with the ACK bit set) ack_received = 1; else misses++; 49 Conclusions Did you notice When MISSES_IN_A_ROW == 3, there were still some packages dropped! Some packages were received 2 or more times by the AP! Possible Future Implementations Transaction ID AP and ED track a transaction ID AP compares expected to received Link timeouts If x heartbeats have not been received, link has timed-out Etc 50 25

26 Conclusions What did we learn? How to interleave the SimpliciTI real-time requirements with an existing application to enable the wireless transmission of your application data Program flow for SimplicTI End Devices and Access Points in a star topology How to identify and standardize application parameters not managed by the software stack How to improve the likelihood of message delivery using acknowledgements and message retries 51 Thank you 52 26

Introduction to SimpliciTI. Low-power RF protocol from Texas Instruments

Introduction to SimpliciTI. Low-power RF protocol from Texas Instruments Introduction to SimpliciTI Low-power RF protocol from Texas Instruments Outline Overview What is SimpliciTI? Device types and network topologies SimpliciTI software architecture Example: How to configure