Difference between revisions of "Tips on Using Imote2"
From Cyber-Physical Systems Laboratory
Jump to navigationJump to search| Line 4: | Line 4: | ||
* When sending over UART, make sure the debug board is connected. | * When sending over UART, make sure the debug board is connected. | ||
* In TinyOS, TOS_LOCAL_ADDRESS is the last 2 digits of the mote id in hex | * In TinyOS, TOS_LOCAL_ADDRESS is the last 2 digits of the mote id in hex | ||
| + | * Even though the default maximum message size is 29 bytes, the Imote2 will only send a message if it has an even length. The call to GenericComm.sendMsg will actually return FAIL if you try to send a 29 byte long packet. | ||
Revision as of 21:14, 24 January 2008
- Washington State University has a great wiki with instructions on how to configure your platform to support the Imote2.
- The Imote2 uses the FTDI USB chip whose drivers may be downloaded here.
- Toggling an External Pin on the Imote2
- When sending over UART, make sure the debug board is connected.
- In TinyOS, TOS_LOCAL_ADDRESS is the last 2 digits of the mote id in hex
- Even though the default maximum message size is 29 bytes, the Imote2 will only send a message if it has an even length. The call to GenericComm.sendMsg will actually return FAIL if you try to send a 29 byte long packet.
