Would it not make sense for Ardupilot to support SBUS FrSky sensors? They
are cheap, work well, and are available. Easy for me to say I know. Maybe
FrSky would sponsor the work needed.
I agree, Ollie’s power brick looks a good candidate.
I do not have a lot of clout with devs. Do you think this will gain any traction? I have not actually seen many other people suggest it, but using S-Port sensors just seems to make so much sense to me.
I scanned through the issues list, and someone else has also requested this: https://github.com/ArduPilot/ardupilot/issues/6296
Because the frsky sensors and protocols are designed to provide telemetry information and not flight control data, there may be technical limitations, but that’s speculative.
I see. Or alternatively could we run a PiCam and OSD with a conventional VTX. I could make a stab at the porting as these have been done for the Raspberry Pi.
Hi all! I am currently running Ardupilot (Arducopter 3.5.2) on a Beaglebone Blue and I would, in a separate python script, access the data coming from the ADC and the I2C ports (some gas sensors will be deployed there). I run Debian GNU/Linux 8 (jessie) with kernel 4.4.91-ti-rt-r137 and my DTC Version is 1.4.4. Up to now, I am able to access the analog port (thanks to another ardupilot user!) with the RoboCape rc_test_adc C code. Importing the Adafruit library for either the adc or the I2C in a Python script returns a RuntimeError due to a conflict with the standard Cape. If someone could help me, I have two questions for you:
how can I access the I2C?
I have plugged the Ublox M8N GPS into the GPS port, but I am not able to get the GPS work. I run Arducopter by “arducopter -A udp:192.168.7.1:14550” to connect to the laptop via USB. On Mission Planner, I see correctly all data except for GPS (there is the “No GPS” message). I have tried by adding the “-B” option with all /dev/ttyO* or /dev/ttyS* paths but nothing happens. The Serialx Baud and Serialx Protocol values are set correctly in Mission Planner.
Sorry for the inexperience, I am quite new both to the Ardupilot and the Beaglebone world.
Thanks for your time, kind regards
Luca
Solved it. Both Telemetry and RC. I was having two different problems on two different radios.
For the benefit of others who might use the pre-compiled ardupilot-blue, I’ll broadcast my noob mistakes here.
The 3DR Sik V2 telemetry radios were fine. The BeagleBone and ArduPilot software were fine, the problem was that I was using UT0 rather than UT1 on the BBBL (whose pins are preconfigured for telemetry in ArduPilot-Blue). The command switch that ultimately worked was:
–C /dev/ttyS1
and for GPS (which had stopped working)
-B /dev/ttyS2
Then, on my RC link problem, I’d failed to successfully change the output from my ezUHF RX to PPM on Pin 1 using the Immersion Tools software and USB connection. Seems I hadn’t hit the “Upload” after toggling my choice.
Hello all, I need help with choosing connector wires for my components. I have a 3DR Radio V2 that I will be connecting to the BeagleBone Blue and also my RC Receiver for PPM. Where can I connect these and which connectors will I need to buy?
Al the important information is there.
Also you can read all the replies on this blog, on reply 39 there is a picture showing how to connect the receiver.
True but I cannot identify if the JST-SH-4 connector will fit my receiver, (it is an FS-X6B receiver), also, JST-SH-4 is a 4 pin connector whereas the PPM connector will be obviously 3 pin, so is the info even correct? Also, there is no mention about connecting telemetry radios.
You have to build the cables and I see you receiver is 5 volts, so it should be powered using a 5 Volt source and feed the PPM using a voltage divider to pin 4
@Thalaivar Maybe I dont understand what you are asking
Receiver
The RC receiver signal has to be connected to connector E4 pin 4. This pin is a multi protocol pin (S.BUS, PPM-Sum, Spektrum Satellit DSM), the protocol will be automatically detected. Make sure the signal does not exceed 3.3 volts, otherwise your BeagleBone Blue can be damaged.