Is there a BeagleBone Doctor in the House?

Hi Trent!

I think this may be quite hard, I took a look at the robotics cape schematic and pretty much every pin is being used. It's a shame, because had (say) solely SPI been used for the cape, then it would have been a quick thing to directly use the code from BBB to BBB-AI. I've tried to write an I/O library for BB-AI in C, but it's stalled a bit, it's not easy : ( Basically, a direct port of controlling I/O from C from BBB to BB-AI won't work, the register changes are sufficiently different.

There's bits of info on the beagleboard forum:

Long story short, for what would have been a high-speed way of interfacing (by directly controlling registers) it's quite hard, and I don't know of a good library of code for it today, and mine is nowhere near complete : ( There's some excellent information here that could help too from  Sean_Miller I've not had a chance to experiment with this yet, because I'd sadly put all my hopes in doing it by controlling registers initially BeagleBone AI Survival Guide V3.18: PWM, I2C, Analog/Digital Read/Write, Vision AI, Video Text Overlays, Audio, & Hardware

The ai version is so different at the pin level to almost guarantee trouble. The software  will not be compatible and new re write. Sorry ninjatrent

Hi Dr. Shabaz,

Thank you for clarifying this.

I will have use a motor controller for the BBAI

The BBBW is performing great with the robotics cape and Logitech cam. I might as well stick with that setup. So far it's running the included libroboticscape.

I was working on a piece of code from the provided examples and ran into an issue. My inexperience.

There's an example template and ones for each on board component. I'm having difficulties with combining the two pieces of code into something functional.

I would like to use the Ardupilot port to run the BeagleBone Rover.

https://github.com/imfatant/test

The main issue with running this, there's no mention in the Ardupilot manual for using the motor controllers. Other than this , everything else is automatically detected by  the Mission Planner ground control software.

With my BB Blue drone it was fairly simple to setup.

The main hindrance with that project is the Flight Deck software on my FrSky Transmitter is not displaying the mavlink telemetry from the Blue. Telemetry thru WiFi to Mission Planner works.

I need the drone to work outside the range of wifi access point and depend on the radio module connected to uart4 and passthru mavlink telemetry to the FrSky Transmitter's display. It's not working. I purchased the transmitter from a company that makes the Flight Deck software. It comes preloaded with the software. Everything works between the transmitter and receiver, mission planner is detecting the inputs from flight controls, I can even disable failsafes (Don't do this) and fly but I would be flying completely blind without tele display on transmitter. There's no way of knowing what is current flight mode and without the flight deck software working properly, I can't safely use any of the switches to select a flight mode. It's been a disappointing project. Currently sitting in a box on shelf.

There was an issue opened for this on the StrawsonDesign GitHub repo:

https://github.com/StrawsonDesign/librobotcontrol/issues/173

There is a dtbo for the BB AI but I am not sure if it is completely functional.

You may want to add to the issue to see if it can get more attention.