Post by tronicgr on Jan 12, 2015 23:26:07 GMT
Small update on this:
Its not so easy as using xbee...
While it works perfectly over USB, for RFduino - RFduino network, it needs lots of conversion of the existing code for manipulating the data packets. It does not have ready COM encapsulation like the xbee... I'll give it a try as soon as I can.
You get the idea...
Thanks
Thanos
Its not so easy as using xbee...
While it works perfectly over USB, for RFduino - RFduino network, it needs lots of conversion of the existing code for manipulating the data packets. It does not have ready COM encapsulation like the xbee... I'll give it a try as soon as I can.
//Transmitter RFduino with MPU-6050
// Define my custom packet of 42 bytes.
struct myCustomPacket_t
{
unsigned char myCharA; // 1 byte
float QUATW; // 4 bytes
float QUATX; // 4 bytes
float QUATY; // 4 bytes
float QUATZ; // 4 bytes
float GYROX; // 4 bytes
float GYROY; // 4 bytes
float GYROZ; // 4 bytes
float ACCX; // 4 bytes
float ACCY; // 4 bytes
float ACCZ; // 4 bytes
// NOTE: compiler will reserve a byte here not defined
};
struct myCustomPacket packet;
RFduinoGZLL.sendToHost((char *)&packet, sizeof(packet));
//The Quaternion values are pre-calculated values from the DMP engine of the motion processor inside the MPU6050 chip... These are quite accurate and jitter free.
//Reciever RFduino connected on the USB of the PC (COM).
struct myCustomPacket packet;
void RFduinoGZLL_onReceive(device_t device, int rssi, char *data, int len)
{
if (device == DEVICE0){
memcpy( &packet, &data[0], len);
data_available = 1;
}
}You get the idea...
Thanks
Thanos
