Hi all , i have little doubt in changing GPS Baud rate. Currently its working in binary SIRF protocol in 57600 baud rate.. I would like to change it into 19200 baudrate. So i made few changes in 2.0.1 code and tested it but failed to get the GPS lock. What could be the reason.......

Changes i made were:
1. byte gps_buffer[100]={
0x24,0x50,0x53,0x52,0x46,0x31,0x30,0x30,0x2C,0x30,0x2C,
0x31,0x39,0x32,0x30,0x30,0x2C,0x38,0x2C,0x31,0x2C,0x30,
0x2A,0x33,0x39,0x0D,0x0A};
// change the buffer with 19200 instead of 57600 and change the Checksum value also

2. Serial.begin(19200); //Universal Sincronus Asyncronus Receiveing Transmiting in init_gps()

3. Serial.begin(19200); // in fastinit_gps()


I cant get the GPS LOCK . I send the command at 4800 BR=> $PSRF100,0,19200,8,1,0*39
but cant get the GPS LOCK what else i have to change?.

Hi, Happykillmore.
I am a new learner on ArduIMU.I only connected the ArduIMU with PC using FTDI cable, and I only changed #define PRINT_BINARY 0 to 1. But in HappyKillmore ArduIMUtest platform I cannot see the smooth change of the image when I touch the IMU.I dont know what's the reason for this.It sounds so strange.

I was taught to read using the Commodore Beginners Guide to BASIC that came with the original C64 :D I'd sit on my Mum's lap reading it to my Dad, I was only 4 at the time. Did my "hello world" at 5 (1987) and have pretty much been building ever since. Text based RPG, typing tutors, quoting systems etc. TBH this is the first time I've had a personal goal for it. I love the interface you have so far its perfect "analogue".
Very nice emulator too I'm hoping that I can just class everything up to make it modular for errors (there will be loads :D). Just finished a camera arduino extra that runs off a channel output from the APM (not done the APM code). Servo position represents function so I've just got to get the APM commands sorted.

Hi there Paul,

I'm following your GCS project with great interest and I'm using it when developing firmware for the UDB. Until recently your GCS parsed the "SERIAL_UDB_EXTRA" format just fine, even if I used XBee API activated in the GCS XBee (That means that the data becomes somewhat "garbled" since the API expects the data in packets. The result is that eh XBee adds some characters to the data, but the "raw" data is still there intact. A few versions ago I realized that this didn't work anymore. No great deal since I only use the API mode on the GCS XBee if I need to adjust the XBee aboard the UAV, but nevertheless it was an extra step to do each time. Now, today (29 Dec. 2010) I downloaded the latest(?) version 1.1.25 and can't get it to parse the "SERIL_UDB_EXTRA" format at all. I see the data coming in at 57600, but it doesn't become translated. (I must add that I have some extra strings in my personal telemetry use for controlling the XBee.) The 866MHz PRO has a duty cycle of 10% and therefore has to be reset at least in 6 minutes intervals). I do this via the telemetry data. Another important note is that I use this on a lab bench setup with X-Plane for HIL-simulation. That means that there is no actual GPS in the setup. The GPS data is fed to the UDB from X-Plane and later to the telemetry port. Have you lately changed the parsing so that my setup is "disqualified", or is there anything else going on here?

Otherwise, keep up the great effort of creating a useful GCS for every UAV nut ;)


Kind regards

Marc

hi,

very impressed on the great GCS sw.

I am developping a new IMU unit. I would like this module being ArduIMU compatible. Could you share the ArduIMU protocol ?

Regards

I would prefer the ASCII legacy as it is "easier" to troubleshoot. But for sure I will prioritize the efficency of the RF transmission (i.e. if binary mode is a must I will take it)

Regards

hi,

I've found the ArduIMU binary info. However I would be interrested on some samples (i.e commands).

 

Hi Happy,
Does your GCS support Arducopter?