I guess I'll call it an Aplha release. I'm not done with the installer yet. The system requirements are .NET 2.0 framework, Google Earth (and maybe the plugin) and DirectX must be installed.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en
http://www.google.com/earth/download/ge/
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en
http://www.google.com/earth/explore/products/plugin.html
Download the GCS
I would STRONGLY recommend NOT trying this in the field with a live plane! This program is for TESTING ONLY at this point.
To use the program, select your COM port with your GPS or AP connected through FTDI or USB to serial. Select your baud rate. Click Connect. You can try the Search COM button which will cycle through all your available COM ports at different baud rates looking for your data stream. The Search Baud button will only search on the selected COM port for your data stream at different baud rates.
Once connected, if it's an AP unit, the waypoints and home location should be set automatically. If you're not using AP then you can build a mission file using the AP config tool and copy the .TXT file into the missions folder that gets created in the root directory with the GCS executable. Don't worry, this process will be easier in the future.
On the settings tab, you can select different options for your instruments and Google Earth Settings. The cockpit view isn't working yet.
Chances are excellent that nothing will work with APM since I have done absolutely zero testing with APM.
This release also includes NO error trapping and it will fail if you start collecting serial data before the Google Earth window is loaded....
Let me know how things go....
Comments
2. I have set Serial data to the lowest limits (1 hz). Effect: I can close the window succesfully after 5 minutes. I will now leave it running for half an hour.
3. If i set 5 hz on all serial Data values, I cant close the window already after 30 sec, I have to use the task manager to close the GCS.
1. Sign of pitch and roll still wrong
2. If GCS runs for some time (<30 sec) and I try to close the window without disconnecting, the window freezes
Andre
And let me know, when a new version of your GCS is avaibale for testing.
In GPS_EM406.pde in the void GPS_join_data(void) function
after
climb_rate = intUnion.word; //m/s * 100
add
numSV = gps_buffer[87]; //Satellite Count
Somewhere at the top of ArduPilot_2_7.pde
add
byte numSV =0;
In GCS_Standard_text.pde in the function void print_position(void)
after
Serial.print(iTOW);
add
Serial.print(",SAT:");
Serial.print(numSV,DEC);
Serial.print(",FIX:");
Serial.print(GPS_fix,DEC);
2) That's a bigger problem. I'm not sure if the DirectX would be causing that or the thousands of data points in Google Earth. I have not tested longer runs. I'll look into it. Thanks!
PS, I'm also noticing an altitude problem with the flight line drawn in Google Earth. My line is drawn way above my house with a real GPS connected.
Two more observations with your GCS
1. It seems to me, that especially pitch goes into the wrong direction (sign problem?). Its probably also roll, but thats difficult to see in my environment
2. I had your GCS now active for > 1 hour and its dead. I cant the move the window, cannot bring the window in front any more, cant click on a tab, display is not updated any more etc. The task manager says its running...can I do something to provide more infos for you ?
-
11
-
12
-
13
-
14
-
15
of 16 Next