Hi,
Does anyone have experience using the e_bluetooth library with the Bluetooth
bootloader? From what Ive found, the e-puck freezes whenever I call commands
within the library. The examples Ive found seem to want to use UART1 for
solely inter-e-puck communication and UART2 for debugging info. Since the
UART2 cable is pretty inconvenient, I was hoping there is a way to do all
communication (puck-to-puck and puck-to-programmer) over UART1. In the library
there are functions to activate/deactivate transparent mode, which look
promising for temporary communication with the programming PC, but there isnt
much documentation. Also, since Im using the Bluetooth bootloader, I think
that may be interfering with things. Im going to keep digging, but I was
hoping someone had some advice since Im starting to run out of summer vacation
(well, a lighter section of summer classes).
Heres a sample of the code Ive been trying:
#include <e_epuck_ports.h>
#include <e_init_port.h>
#include <e_led.h>
#include <e_uart_char.h>
#include <e_bluetooth.h>
#include <stdio.h>
char uart_buffer[128];
int main()
{
int i = 0;
char myPin[50];
e_init_port();
e_init_uart1();
e_set_body_led(1);
e_bt_find_epuck();
e_set_body_led(0);
while (1);
return 0;
}
Of note is that the body LED is never turned off so I believe this indicates
the puck hangs at e_bt_find_epuck(). Please let me know if I can provide more
info.
On another topic, Im trying to get the ball rolling on the wiki at
www.e-puck.org (http://www.e-puck.org/index.php?option=com_openwiki&Itemid=81).
If we can gather enough articles, Ill see if we can setup a wiki with a more
robust feature set. Anyway, if you want to be immortalized in the way that
only a public page with no write-protection can provide, I urge everyone to
start contributing. Feel free to post your articles or correct the mistakes in
mine.
Thanks,
Louis
_______________________________________________
E-puck-user mailing list
[email protected]
https://mail.gna.org/listinfo/e-puck-user