Hi,
Thanks a lot for those quick answers. Appreciate to see that this BBB thread is so active. Ppoirier workaround (thanks a lot to him) is good to me for the moment. I just don’t want to loose my Copter so Voltage monitoring is enough to make it return home before it is too late. I hope however that it will be included in Ardupilot soon because without that it requires that I manually and constantly check Voltage to eventually send a RTL request to the Copter, involving in turn that the Copter would be at a distance covered by the ground station. Lot of constraint actually
Marc, you said :
That is a 2S backup power battery connection
Could you explain why you think that ? I did not see anything saying that it is dedicated to Backup main power. I though that it was for autonomous projects like Ardupilot. So if it is only for backing a main power, how would you imagine to power the BBB in a copter project ?
I am not the world’s biggest expert on this board – although I have one. I have shelved it and am using a Navio board until the voltage monitoring has been figured out!
If you are using a Frsky TX I would use a flvss voltage monitor and get your TX to alert you to a low voltage.
Thanks Marc. I am more and more asking myself if this board is really the best option for a Drone or Rover project Maybe is it too early at this stage of the Blue life. Well no matter, I will insist and continue to try with this board and…my next step is to connect my Frsky TX. Could someone tell me how you achieve it ? The two antennas coming out of the BBBlue looks like the one of my FS-I6 receiver. Is there an inboard receiver ? or are those antennas just for Wifi and BT ? If I have to connect an external receiver to the BBBlue, which one do you use ? The BBB JST connectors are not very standard (at least not the same of my receiver) and I would like to know if any receiver has it already.
Thanks
Well if you are using FrSky then just use a FrSky voltage monitor and you can get a low voltage alert. I have not used it yet but many have used opentx with it so that should be easy.
I think it is a good board but lack of current and voltage monitoring is crippling. If someone can figure this out it would be among the best value boards available. For me a Navio and RP3 is the best Linux choice.
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?
Maybe is it too early at this stage of the Blue life. Well no matter, I will insist and continue to try with this board and…my next step is to connect my Frsky TX. Could someone tell me how you achieve it ? The two antennas coming out of the BBBlue looks like the one of my FS-I6 receiver. Is there an inboard receiver ? or are those antennas just for Wifi and BT ? If I have to connect an external receiver to the BBBlue, which one do you use ? The BBB JST connectors are not very standard (at least not the same of my receiver) and I would like to know if any receiver has it already.
