I couldn't find an existing thread for the AR.Drone 2.0 Flight Recorder, so here goes.
Feel free to reply here with Flight Recorder related stuff.
Feel free to reply here with Flight Recorder related stuff.
Flight Recorder
- Thread starter Jaeger
- Start date
I bought a Flight Recorder recently, but can't test it with the drone itself for several months.
Here's what I've found - drone-free - so far. (Apologies for the formatting.)
Windows 10:
* Windows drivers are included on the Flight Recorder internal storage.
* They don't work with Windows 10.
* I couldn't find any other drivers that worked with Windows 10.
Linux:
* I could see NMEA packets using: minicom -b 4800 -D /dev/ttyUSB0
Using gpsd and gpsmon to decode the packets under Linux seems like a good idea.
Unfortunately, gpsd is too smart, and switches to SiRF "raw" mode, which is persistent.
To reset to NMEA mode, kill gpsd etc. then: gpsctl -f -n -s 4800 /dev/ttyUSB0
This may be sufficient to "unbrick" a Flight Recorder?
I was unable to get a GPS lock indoors, but I could see several satellites so I'll give it a pass.
* The output from "fdisk -l" looks like garbage... But Windows could see the (broken) drivers.
Disk /dev/sdb: 3.69 GiB, 3959422976 bytes, 7733248 sectors
Disk model: Ultra HS-SD/MMC
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6f20736b
Device Boot Start End Sectors Size Id Type
/dev/sdb1 778135908 1919645538 1141509631 544.3G 72 unknown
/dev/sdb2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
/dev/sdb3 1869881465 3805909656 1936028192 923.2G 79 unknown
/dev/sdb4 2885681152 2885736650 55499 27.1M d unknown
Partition table entries are not in disk order.
Hopefully there's some useful information in there.
Cheers!
Here's what I've found - drone-free - so far. (Apologies for the formatting.)
Windows 10:
* Windows drivers are included on the Flight Recorder internal storage.
* They don't work with Windows 10.
* I couldn't find any other drivers that worked with Windows 10.
Linux:
* I could see NMEA packets using: minicom -b 4800 -D /dev/ttyUSB0
Using gpsd and gpsmon to decode the packets under Linux seems like a good idea.
Unfortunately, gpsd is too smart, and switches to SiRF "raw" mode, which is persistent.
To reset to NMEA mode, kill gpsd etc. then: gpsctl -f -n -s 4800 /dev/ttyUSB0
This may be sufficient to "unbrick" a Flight Recorder?
I was unable to get a GPS lock indoors, but I could see several satellites so I'll give it a pass.
* The output from "fdisk -l" looks like garbage... But Windows could see the (broken) drivers.
Disk /dev/sdb: 3.69 GiB, 3959422976 bytes, 7733248 sectors
Disk model: Ultra HS-SD/MMC
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6f20736b
Device Boot Start End Sectors Size Id Type
/dev/sdb1 778135908 1919645538 1141509631 544.3G 72 unknown
/dev/sdb2 168689522 2104717761 1936028240 923.2G 65 Novell Netware 386
/dev/sdb3 1869881465 3805909656 1936028192 923.2G 79 unknown
/dev/sdb4 2885681152 2885736650 55499 27.1M d unknown
Partition table entries are not in disk order.
Hopefully there's some useful information in there.
Cheers!
Have an AR.Drone purchased 2013. got it rebuilt now but have a new android phone. when I download the free flight 6 it connects with no internet and will not recognize the drone.
what am I doing wrong?
what am I doing wrong?
