The first row (where I have the wires) are from the encoder on the motor. The other row is for connecting to the Arduino (eg. to an interrupt pin). I wasn't using that personally so you could omit them, ignore them, or tape them up somewhere.

I think the circuit just "ors" the two encoder outputs together so you can have a single interrupt pin (labelled INT on the board) which you connect to an interrupt (eg. D2/ D3) and then to see which way it is turning (if you care about that) connect ENC1 and ENC2 to some other pins.

I didn't care about the encoder as I was driving "visually", so I didn't need it to know exactly how much the wheels had turned.

Please post technical questions on the forum, not by personal message. Thanks!

Mine tend to slip off, and I find it impossible to adjust the track height. Maybe I'm not doing it right.

I just got my Rover 5 and had pulled the retaining bracket (metal L-brac with two screws inside the chassis) to pull the appendage out to set the height. I think it was an EE solution to a ME problem Unfortunately, if you have track slippage with the low profile mode, adjusting the height up will make it worse.

I have a composite eye (lots of IR) coming in next week to see how the Dagu demo will work. The DFR Romeo will be interesting in running the R5 Motor/Encoder Board (4motors/4encoders), (2) servos and (6) tactile buttons. I think there might be a 74HC595 chip and a dev board in there.

Thanks to Nick for opening this thread. I look forward to any further developments to this platform.

Hello! i have a problem, when logic power on Dagu is NOT powered from Arduino, motors rotate easily in both directions, but when i connect logic power (5V) from Arduino, motors begin to rotate harder in one particular direction. Firstly i connected logic from 5V Arduino pin which is near analog pins, then i tried to connect from ICSP pins, same result. Then I've done everything exactly like you to exclude my mistakes, but it doesn't work.

P.S. Moreover i bought two Arduinos and two Dagus, I thought i fired smth, but motors bahaves on both.P.P.S Everything works fine with Pololu motor driver shield and Arduino - motors rotate easily in both directons.

Yes, with Pololu Shield works fine. I wondered if there was some secret may be with Dagu, but if you don't know the exact reason, it can be anything) Nevertheless thank you for the reply and for your project!

Thank you = ) At this point the encoders are excessive -I guess- for me. I won't use them for my current project. Buying that 4 channel would be more convenient however I have've limited time and if a delay happens during shipping it won't be good for me : ) If I get stuck I'll get some help from the driver's schematic : )

I have a Rover 5 with 4 motors/encoders and use the Dagu 4 channel motor controller. I use the current sensing feature of the motor controller. Powered from a 2S Lipo at full PWM the motors draw about 1A /motor when turning left/right (when going forwards/backwards the motors draw less current). Stalled these motors draw over 3A a piece. I have used a cheap L298 board from Ebay on another robot and have taken a good look at the datasheet of the L298 chip. There are some things you need to take in to account. If you are pulling 1A from one channel of an L298 you will have a voltage drop of 1.8 - 3.2V on the output. That also means that a serious amount of heat is wasted in the L298. You need a big heatsink to dissipate that heat. The Dagu 4 channel motor controller uses fets with a very low RDSon, so there is only a tiny voltage drop. So no power is wasted and a heatsink is not necessary. The Dagu controller was especially designed for the Rover 5 and is rated for 4A stall current / channel. Here is a photo of my Rover: http://www.bajdi.com/?attachment_id=623 It's my "development platform"