Develop standard, re-usable inexpensive solutions for IP-enabled always-on UAVs over cellular IP networks such as GPRS, 3G, 4G etc.
Primary goal: Telemetry over low cost cellular [achieved in testing]
Secondary goal: Bi-directional GCS/Telemetry over cellular IP [achieved in testing]
Tertiary goal: High speed IP for streaming IP video over cellular 3G/4G
STATUS: Bi-directional telemetry over cellular IP (UDP or TCP) is now working. It has been flown successfully while logging live telemetry to a GCS at home, several miles away [distance is really unlimited]. Currently working on improving code, more testing and broader hardware support.
Comments
@Bernt:
Just a short question:
Have you measured or estimated how much data volume you need for your video stream and telemetry transmission (e.g. in Megabytes per second, minute or hour)? Because most of the SIM card flatrates have daily or monthly limits...
Had a great flight yesterday, worth sharing.
Happy flying everyone...
Hello all!
Anybody tried this??
http://uavmatrix.com/viewpost/2/62/116/0/PX4-PixHawk/Setting-Up-Ras...
I´m having some problems with Inadyn, I´ve made DynDns using the no-ip.info, similar than your, and in the inadyn.conf I used:
--password PASSWORD
--receiversavier.no-ip.info
--dyndns_system default@no-ip.com
--background
--update_period_sec 600
I added the /usr/sbin/inadyn & line to the rc.local file...
But when I made the grep INADYN I don´t obtain absolutely nothing...
Please, have you got any idea of what is happening??
Help:
Current set up: APM > RPi > 3G router (I replaced the dongle with the router as I need an extended antenna, you can do this with some dongles but the router is much more robust).
I first had a 3G dongle in the APM/RPi set up (sakis3g etc) but I couldn't connect, no heartbeat packets. That and I kept burning out dongles, if you don't have an antenna connected to the dongle they fry.
So I bought the 3G router, first I connected the APM to the RPi via the UART2 pins down the starboard side of the APM to a DB9/RS232 level shifter module (the APM works on 5v, the RPI works on 3.3logic) that connects straight to a serial port on the 3G router.
Again No heart beat packets :-((((( Ok I thought it was the RS232 module.
So I then connected the APM to the RPi via the UART2 pins on the APM to the GIO pins of the RPi. Assigned the RPi with its own IP and the traffic is directed to the GIO pins of the RPi with a port address. The 3G router forwards the traffic from the APM to port 5760 and the 3G router has a DyDns. The RPi uses Ser2net to do the serial to net conversion.
And guess what, no heart beat packets.
So then I tested with the FTDI cable from APM to RPI and still the same, no heart beat packets.
I have tried to connect MP to my Dydns on port 5760 (I haven't tried 14550).
If there is anyone that can assist us please do?
Cheers, RS
UPDATE: I've also managed to connect the GCS with 4G. So I have 4G (Aircraft) to 4G (GCS). I'll post a video shortly on www.4gmetry.com
Hi Nick, thanks and sorry for late answering, I regulary check for new posts on http://diydrones.com/group/4gmetry However I don't know about interference, but everything seems ok (and very fast)!
Many thanks Cxgiacomo, I'm sharing a lot of knowledge for free about 4Gmetry (on www.4gmetry.com) - it's completely open source. If you have any suggestion or improvement please post on any forum! Thanks again, S.
Thanks Silvio, I have a feeling that 3G/4G telemetry is going to explode in the commercial market in the next 2-3 years... that site is a great place to sell new companies on the potential useage.
I've written a short tutorial for dummies about 4G telemetry (4Gmetry.com) and related best practices. I hope this can help. Bi-directional telemetry (UDP or TCP) is perfectly working. Your vehicle can now go several miles away [distance is really unlimited].
I have been observing here for a while, several posts about the use of "AT+W" to store your current configuration, this command does not effect parameters that may be of use to this forum. In addition the "AT+CIPSCONT" command will move the current network centric parameters such as the results of a "AT+CIPMUX" command from ram to navram, this can preserve many of the network critical parameters for a complete list, the applicable command reference manual or issuance of "AT+CIPCONT?<cr>" (may be "AT+CIPSCONT=?<cr>" or the ever popular "AT+CIPSCONT <cr>") to query the results. One anomaly I have noted on a factory fresh SIM900D is that if you use this approach (AT+CIPSCONT) after you set "AT+CSTT" correctly the module connects automatically at start up, but does so incorrectly locking the device off the network, I have not been able to recover from this state, so I intentionally set an incorrect value for "AT+CSTT", utilize "AT+CIPSCONT" and then set "AT+CSTT" manually on each boot up, this minimizes the total number of commands after boot up to 2. AT+CSTT & AT+CIPSTART. I would be happy to hear of a resolution, but wanted to pass along an 8 hour lesson along with my new found knowledge of "AT+CIPSCONT"!
-
1
-
2
-
3
-
4
-
5
of 12 Next