On Sat, Mar 25, 2017 at 9:45 AM, Andrew DeVries
<
andrewa...@gmail.com> wrote:
> Thanks for the reply, Sorry from the post I thought the issue was just with
> the battery monitor code knocking out the Wireless and when I looked at the
> updated source code looked like that module was disabled if not Beagle Bone
> Black. I am not using his cape just trying to use his libraries. We already
> have a bunch of robotics chassis but with large motors that can draw as high
> as 6 amps so can't use BB Blue as PWM pins don't come out to pins. We
> already have 6 BBGW and drew up an expanded Grove Cape that brought out all
> the Robotics Cape Pins added servo pins etc into groups to go to our motor
> controllers etc.
>
> So if I want to move forward using the Robotics Cape Code Base will it just
> be avoiding this one conflict pin or is there a lot of pins. In my case I
> have no battery monitor as not using his cape so easy enough to roll my own
> overlay and avoid this pin.
>
> Any other gothcha's between the Beagle Bone Green Wireless and the Robotics
> Capes that you know of?
So librobotic's uses dev mem and just takes that pin on load. We just