parrot ar drone 3g mod

Researchers from the computer science department at the Stevens Institute of Technology have added a 3G-radio to an AR.Spooky stuff if you ask me. Alcatel-Lucent flies Parrot AR.Drone 2.0 over 3,280 feet using LTE: reach out and buzz someone (video)Drone 2.0 is many good things, but "long-ranged" isn't what comes to mind with a 165-foot maximum distance between pilot and quadrocopter. Not to be daunted, Alcatel-Lucent has conducted a test with an ad hoc LTE network, a USB modem and a smartphone to see just how far the remote-controlled aircraft could go on 4G. In practice, quite far: thanks in part to the inherently wide coverage of the 800MHz band in France, the team flew the AR.Drone more than 3,280 feet (one kilometer), all while streaming 720p video of the farmland below. Besides giving us ideas for a North by Northwest remake, the flight emphasized the possibilities that come when we have access to a long-distance wireless link with high bandwidth, such as monitoring crops or some very literal field journalism.
The challenge will be convincing Alcatel-Lucent to share its trick and let us pester our not-so-next-door neighbors. From around the web ear iconeye icontext file Sign up or log in to customize your list. Here's how it works: Anybody can ask a question The best answers are voted up and rise to the top I am attempting to compile support for a Huawei E3276 usb LTE modem for an embedded Linux/BusyBox installation on a Parrot AR Drone 2.0, which is based on kernel 2.6.32; however, I am running into some issues after loading the kernel modules. I start off by loading the necessary kernel modules: This modem behaves like an Ethernet NIC that presents a routed interface (192.168.1.100 on an eth port), so all the actual 4G setup is done on the modem itself via a web interface (in case you're wondering why I'm not including qmi_wwan drivers). Then I plug in the 4G modem until I get the following entries in dmesg and lsusb: Bus 001 Device 002: ID 12d1:1f01 Huawei Technologies Co., Ltd.
scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 12 usb-storage: waiting for device to settle before scanningar drone parrot fonctionnement /home/stephane/.ardrone/linux/ardrone2_ARDrone2_Version_20130102/Linux/kernel/omap/drivers/usb/core/inode.c: creating file '012'parrot ar drone preisvergleich hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002parrot ar drone troubleshooting hub 1-0:1.0: port 1 enable change, status 00000503macdev drone dx parts scsi 8:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2parrot ar drone 1500mah battery
At this point I use the modeswitch command to bring the device into modem mode: usb_modeswitch-1.1.9-arm-static -v 12d1 -p 1f01 -W -M 55534243123456780000000000000011060000000000000000000000000000ar drone alternative firmware This succeeds and changes the product code and reconnects it: Bus 001 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem usb-storage 1-1:1.0: disconnect by usbfs usb 1-1: usbfs: process 4792 (usb_modeswitch-) did not claim interface 0 before use hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s usb 1-1: USB disconnect, address 12 usb 1-1: unregistering device usb 1-1: usb_disable_device nuking all URBs usb 1-1: unregistering interface 1-1:1.0 hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 usb usb1: bus auto-suspend usb usb1: usb resume hub 1-0:1.0: port 1: status 0101 change 0001
hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s usb 1-1: new high speed USB device using musb_hdrc and address 13 usb 1-1: skipped 4 descriptors after interface usb 1-1: default language 0x0409 usb 1-1: udev 13, busnum 1, minor = 12 usb 1-1: New USB device found, idVendor=12d1, idProduct=1001 usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0 usb 1-1: Product: HUAWEI Mobile usb 1-1: Manufacturer: HUAWEI Technology usb 1-1: no configuration chosen from 1 choice /home/stephane/.ardrone/linux/ardrone2_ARDrone2_Version_20130102/Linux/kernel/omap/drivers/usb/core/inode.c: creating file '013' Spurious irq 95: 0xffffffdf, please flush posted write for irq 56 Unfortunately, after the usb_probe_device step, it shows that it has found a configuration, but is not choosing it without an explanation. Can anyone help me discover the reason for it not proceeding with the found configuration?
What diagnostic steps should I take? What tests should I try? kernel-modules embedded modem lte huawei I'm trying to do the same thing you are: get a 3G/4G modem to work on the ARDrone2. I'm not as far along as you are though, I only just managed to get my hands on the toolchain, and my first few attempts at a hello world have crashed. I don't really have an answer, only an idea. I did a quick google on your log messages, and I found this: However, I believe the ARDrone2 is using kernel 2.6.32.9, and after looking through the code files mentioned in that bugzilla it seems to me that the mentioned fix is present. So that got me thinking: the ARDrone2 has a uclinux build, which generally targets embedded systems, and hence builds are optimized with minimalistic features. Maybe some flag wasn't set when the kernel module in the drone was compiled (file generic.c has comments which seem to also hint at this around the relevant line with the #if !defined statement).