Am I reading the bbgw schematic correctly.
We need to exclude its use of
p8 Pins BBWG Robotics Cap
11 WL_SDIO_D1 QEB2B
12 WL_SDIO_D0 QEB2A
15 WL_SDIO_D3 PRU ENC A
16 WL_SDIO_D2 PRU ENC B
17 WL_IRQ BATT LED 1
18 WL_SDIO_CLK BATT LED2
If the robotics capes is using traditional two drive motor setup then only
having two out of four encoders works. This fits my middle schoold kids
robotics chassies. I do not need BATT LEDs on the board a simple red light
on means low battery but honestly wireless means a socket connection tells
me all I need.
Issues I see are PRU code is in assembly what happens if it trys to use a
pin that it doesn't have an overlay to. If we need to batch the pru
assembly then assume we need a way to detect BBWG in the PRU assembly or
set a bit in the shared memory to let it know not to use those PRU encoder
pins. I haven't dug into the libroboticscape code to see how the Batt LED
pis are being used.
If there is a BB Blue Rev B in the works please ask them to conceder
bringing the PWM pins out to pins or connector. I imagine the drone
userswould want this as well as looks like they are using the servo outputs
to drive there escs versus the PWM as they two need more then 1 amp motor
controllers.
Can't wait to see the Mip edu kits and a quad (hex? in pictures only 4
motor outputs?) copter kit.
On Saturday, March 25, 2017 at 6:09:36 PM UTC-4, RobertCNelson wrote:
>
> On Sat, Mar 25, 2017 at 9:45 AM, Andrew DeVries
> <[email protected] <javascript:>> 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
> need to patch librobotic's on the bbgw to not take that specific pin.
> (side note, i didn't even look on the robotic's schematic, it might be
> a pin we can't redirect..)
>
> Regards,
>
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/44bb9e54-4a7a-457f-b7d8-3522b2828371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
