- Thu Jul 24, 2014 11:22 am
#173005
I am admittedly new to hardware and new to C/C++ish arduino code so this is all pretty new to me. I wanted to make a thread about this module as there is very little said about it on the forum. I struggled but managed to figure out how to do simple HTTP GET or HTTP POST requests using Transparent Mode which packetizes data sent over the UART interface. In my testing I found Software Serial to be unreliable using an 8MHz μC (Pro Mini 3v, FIO, etc.) so I suggest using Hardware Serial to communicate with the S6B if you intend to go that route. I will update this post as I learn more about the module. I hope this helps!
Most of my initial trial and error can be seen here in the discussion section of the SparkFun tutorial Internet Datalogging With Arduino and XBee WiFi.
Configuration:
This is pretty straight forward if you read the User Manual. Using XCTU you can sent any parameter necessary for the operation of the device. You can also set these parameters from inside code running on the μC by entering AT Command Mode (+++) and issuing the corresponding commands. The device can be communicated with either over the UART interface or its SPI interface. For reference an SPI arduino library by cjbearman here xbee-wifi-spi-arduino. I have not yet experimented with the SPI interface. There are two main modes of operation: Transparent and API. Transparent Mode simply packetizes and transmits data sent over the UART. The limiting factors of this mode include usage of a single TCP or UDP port, generally a fixed destination IP (unless changed in the program by entering AT Command mode), and limited feedback. The API mode is much more complicated and requires a specific frame structure but allows for greater complexity and control. I also have yet to experiment with this mode but probably will be in the future.
This is what the user manual has to say about it:
Transparent mode is a very basic mode but for many using this wireless module to log data to a web server of some sort (using a REST API for instance) it will be all you are really looking for. After setting the Destination IP and port of the server you simply have to print an HTTP GET or POST line by line over serial and have your data added (URL encoded) to the body of the request. Here is sample code I used to test sending a message to Pushover's REST API. Their API IP is 184.154.74.158. Also note that the Xbee S6B is looking for the Destination port in HEX. (80 = 50)
Most of my initial trial and error can be seen here in the discussion section of the SparkFun tutorial Internet Datalogging With Arduino and XBee WiFi.
Configuration:
This is pretty straight forward if you read the User Manual. Using XCTU you can sent any parameter necessary for the operation of the device. You can also set these parameters from inside code running on the μC by entering AT Command Mode (+++) and issuing the corresponding commands. The device can be communicated with either over the UART interface or its SPI interface. For reference an SPI arduino library by cjbearman here xbee-wifi-spi-arduino. I have not yet experimented with the SPI interface. There are two main modes of operation: Transparent and API. Transparent Mode simply packetizes and transmits data sent over the UART. The limiting factors of this mode include usage of a single TCP or UDP port, generally a fixed destination IP (unless changed in the program by entering AT Command mode), and limited feedback. The API mode is much more complicated and requires a specific frame structure but allows for greater complexity and control. I also have yet to experiment with this mode but probably will be in the future.
This is what the user manual has to say about it:
Transparent:Transparent Mode:
When operating in transparent mode, the modules act as a serial line replacement. All
UART data received is queued up for RF transmission. When RF data is received, the
data is sent out through the UART. The module configuration parameters are configured
using the AT command mode interface. Please note that transparent operation is not
an option when using SPI.
API:
As a general rule of thumb, API firmware is recommended when a module:
• sends RF data to multiple destinations
• sends remote configuration commands to manage modules in the network
• receives IO samples from remote modules
• receives RF data packets from multiple modules, and the application needs to
know which module sent which packet
• needs to use the send data request and device request features of Device Cloud
If the above conditions do not apply, (e.g. in a sensor node, or a simple application) then
transparent operation might be suitable. It is acceptable to use a mixture of modules
running API mode and transparent mode in a network.
Transparent mode is a very basic mode but for many using this wireless module to log data to a web server of some sort (using a REST API for instance) it will be all you are really looking for. After setting the Destination IP and port of the server you simply have to print an HTTP GET or POST line by line over serial and have your data added (URL encoded) to the body of the request. Here is sample code I used to test sending a message to Pushover's REST API. Their API IP is 184.154.74.158. Also note that the Xbee S6B is looking for the Destination port in HEX. (80 = 50)
Code: Select all
void setup () {
Serial.begin(9600);
}
void loop() {
delay(4000);
Serial.println("POST /1/messages.json HTTP/1.1");
Serial.println("Host: api.pushover.net");
Serial.println("Connection: close");
Serial.println("Content-Type: application/x-www-form-urlencoded");
Serial.println("Content-Length: 85");
Serial.println("");
Serial.println("token=APP_TOKEN&user=USER_KEY&message=Test");
}