> the digital pin is not measured ,i have no multimeter, i dont know how
> to use the serial monitor, is it useful in such kind test?
> 我是不是没理解对LUZ的意思？
> 2012/11/18 Lutz Michaelis <sachsenpo...@gmail.com>
>> How do you determine what pin is HIGH? I assume you will have an output
>> in the serial monitor as well?
>> Nice debugging :-)
>> ~Lutz
>> On Sun, Nov 18, 2012 at 12:37 PM, zhou zhou <marczhouz...@gmail.com>wrote:
>>> I use a waterflow blink program to test the 32u4 digital pins by
>>> connecting the pins [D0 to D13], so there are 13 led.
>>> The normal blink sequence should be D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10
>>> D11 D13.
>>> the actual sequence is D2 D3 D1 D0 D5 D7 D8 D9
>>> D10 D11 D13.
>>> when program loaded,the D6 missed. and the first blink is the D2 ,not
>>> D0. the D5 is always bright ,no extinguish.
>>> I dont find where is the D12 pin in board ,and there are two D5 pins in
>>> board. i dont understand.
>>> When led blink ,two motors rotate, so D5 blink, motor1 turn forward,
>>> when D9 blink, motor1 turn back.
>>> When D9 and D10 blink, the tow motors should move backward, but motor2
>>> is not move when motor1 backward normally.
>>> When two motors move forward,the D5 D6 should blink, but the D5 and D7
>>> blink actually. so the D6 connect is unnormal.
>>> Although D6 is not blink, motor2 's forward is not influenced.
>>> so i think the connect may be have some problem in board
>>> below is the program
>>> ---------------------------------------------------------------
>>> int ledPin[13] = {0,1,2,3,4,5,6,7,8,9,10,11,13};
>>> void setup()
>>> {
>>> for(int i=0;i<14;i++)
>>> pinMode(ledPin[i],OUTPUT);
>>> }
>>> void loop()
>>> {
>>> digitalWrite(0,HIGH);
>>> delay(500);
>>> digitalWrite(0,LOW);
>>> digitalWrite(1,HIGH);
>>> delay(500);
>>> digitalWrite(1,LOW);
>>> digitalWrite(2,HIGH);
>>> delay(500);
>>> digitalWrite(2,LOW);
>>> digitalWrite(3,HIGH);
>>> delay(500);
>>> digitalWrite(3,LOW);
>>> digitalWrite(4,HIGH);
>>> delay(500);
>>> digitalWrite(4,LOW);
>>> digitalWrite(5,HIGH);
>>> delay(500);
>>> digitalWrite(5,LOW);
>>> digitalWrite(6,HIGH);
>>> delay(500);
>>> digitalWrite(6,LOW);
>>> digitalWrite(7,HIGH);
>>> delay(500);
>>> digitalWrite(7,LOW);
>>> digitalWrite(8,HIGH);
>>> delay(500);
>>> digitalWrite(8,LOW);
>>> digitalWrite(9,HIGH);
>>> delay(500);
>>> digitalWrite(9,LOW);
>>> digitalWrite(10,HIGH);
>>> delay(500);
>>> digitalWrite(10,LOW);
>>> digitalWrite(11,HIGH);
>>> delay(500);
>>> digitalWrite(11,LOW);
>>> digitalWrite(13,HIGH);
>>> delay(500);
>>> digitalWrite(13,LOW);
>>> }
>>> 2012/11/12 ken gu <dustlessim...@me.com>
>>>> Thanks.
>>>> 在 2012-11-12，下午2:06，Paul Adams <nihaop...@gmail.com> 写道：
>>>> > checkout here, very well documented:
>>>> http://wiki.xinchejian.com/wiki/Category:Swarm_Robots
>>>> > On Mon Nov 12 14:04:54 2012, ken gu wrote:
>>>> >> O, Thanks.
>>>> >> Have some information on it ?
>>>> >> 在 2012-11-12，上午8:34，nihaopaul <nihaop...@gmail.com
>>>> >> <mailto:nihaop...@gmail.com>> 写道：
>>>> >>> It's the Swarm robot platform Kengu.
>>>> >>> On Nov 12, 2012 7:22 AM, "ken gu" <dustlessim...@me.com
>>>> >>> <mailto:dustlessim...@me.com>> wrote:
>>>> >>> hi:
>>>> >>> everybody, What are the characteristics of this board ???
>>>> >>> thanks.
>>>> >>> kengu
>>>> >>> 在 2012-11-11，下午12:01，Paul Adams <nihaop...@gmail.com
>>>> >>> <mailto:nihaop...@gmail.com>> 写道：
>>>> >>> > sunny! are you crazy! dont kill yourself on this.
>>>> >>> > On Sun Nov 11 05:09:05 2012, sun sunny wrote:
>>>> >>> >> int m1 = 5;
>>>> >>> >> int m2 = 6;
>>>> >>> >> int m3 = 9;
>>>> >>> >> int m4 = 10;
>>>> >>> >> void setup() {
>>>> >>> >> pinMode(m1, OUTPUT);
>>>> >>> >> pinMode(m2, OUTPUT);
>>>> >>> >> pinMode(m3, OUTPUT);
>>>> >>> >> pinMode(m4, OUTPUT);
>>>> >>> >> }
>>>> >>> >> void loop() {
>>>> >>> >> digitalWrite(m1, HIGH);
>>>> >>> >> digitalWrite(m3, LOW);
>>>> >>> >> delay(1000); // jp1 motors are moing forward
>>>> >>> >> digitalWrite(m2, HIGH);
>>>> >>> >> digitalWrite(m4, LOW);
>>>> >>> >> delay(1000); // jp2 motors are moing forward
>>>> >>> >> }
>>>> >>> >> here are the code , i ve tried it , not problem with leds ^ ^
>>>> >>> i think
>>>> >>> >> i am just going to change the silk and probably some position
>>>> >>> of the
>>>> >>> >> component ^^
>>>> >>> >> 2012/11/10 sun sunny <sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>
>>>> >>> >> <mailto:sunnylyvo...@gmail.com <mailto:sunnylyvo...@gmail.com
>>>> >>> >> but the d6 for the motor controller remain the same
>>>> >>> >> 2012/11/10 sun sunny <sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>
>>>> >>> >> <mailto:sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>>>
>>>> >>> >> i probably know where the problem comes from , for the
>>>> >>> d0 to
>>>> >>> >> d7 , i come up with d0 to pd0 , but it is different
>>>> >>> ,sorry for
>>>> >>> >> that , that's my silly mistake
>>>> >>> >> 2012/11/10 sun sunny <sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>
>>>> >>> >> <mailto:sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>>>
>>>> >>> >> d5 on pin two
>>>> >>> >> d6 on pin 13
>>>> >>> >> d9 on pin 6
>>>> >>> >> d10 on pin 9
>>>> >>> >> check the lb1836 datasheet accordingly ^^ its a
>>>> bit
>>>> >>> >> different to the other motor controller
>>>> >>> >> and thax a lot to your efforts and patience , all
>>>> the
>>>> >>> >> problem will be fix in the next version ^^
>>>> >>> >> 2012/11/10 sun sunny <sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>
>>>> >>> >> <mailto:sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>>>
>>>> >>> >> 2012/11/10 sun sunny <sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>
>>>> >>> >> <mailto:sunnylyvo...@gmail.com
>>>> >>> <mailto:sunnylyvo...@gmail.com>>>
>>>> >>> >> i will upload the schemetics tomorrow :)
>>>> >>> >> On Nov 10, 2012 9:48 PM, "nihaopaul"
>>>> >>> >> <nihaop...@gmail.com
>>>> >>> <mailto:nihaop...@gmail.com> <mailto:nihaop...@gmail.com
>>>> >>> <mailto:nihaop...@gmail.com>>>
>>>> >>> >> wrote:
>>>> >>> >> you guys waited til now to test? Anyway
>>>> >>> just
>>>> >>> >> seems labeled wrong
>>>> >>> >> On Nov 10, 2012 8:26 PM, "spanner888"
>>>> >>> >> <spanner...@usabledevices.com
>>>> >>> <mailto:spanner...@usabledevices.com>
>>>> >>> >> <mailto:spanner...@usabledevices.com
>>>> >>> <mailto:spanner...@usabledevices.com>>> wrote:
>>>> >>> >> trying to get the motors going was
>>>> my
>>>> >>> >> first frustration
>>>> >>> >> I think I have identified below
>>>> using
>>>> >>> >> actual code to drive the motor pins
>>>> >>> - but
>>>> >>> >> NO code activates the 4th pin (R
>>>> Fwd in
>>>> >>> >> this scheme)!
>>>> >>> >> Also doing continuity checks from
>>>> the
>>>> >>> >> header pins to the motor controller
>>>> >>> >> creates even more confusion.
>>>> >>> >> 5 Motor L back
>>>> >>> >> 7 Motor R back
>>>> >>> >> 9 Motor L fwd
>>>> >>> >> My suspicion is that the chip pin#
>>>> >>> to port
>>>> >>> >> name to Ard pin# translation has
>>>> got
>>>> >>> >> confused and ALSO that there is
>>>> >>> something
>>>> >>> >> wierd with Ard pins D7/8 - either
>>>> they
>>>> >>> >> work different on Leonardo config
>>>> >>> or they
>>>> >>> >> are not connected on board.
>>>> >>> >> On 10/11/12 20:13, Lutz Michaelis
>>>> >>> wrote:
>>>> >>> >>> I got the same last night.
>>>> >>> Frustrated I
>>>> >>> >>> gave up. Now after Spencers email
>>>> >>> I am a
>>>> >>> >>> bit relieved.
>>>> >>> >>> Still did not get the motors
>>>> >>> >>> running....need to check the pins.
>>>> >>> >>> Do you have a pin map for the
>>>> >>> motors Sunny?
>>>> >>> >>> ~Lutz
>>>> >>> >>> On Sat, Nov 10, 2012 at 3:37 PM,
>>>> >>> >>> spanner888
>>>> >>> <spanner...@usabledevices.com <mailto:
>>>> spanner...@usabledevices.com>
>>>> >>> <mailto:spanner...@usabledevices.com
>>>> >>> <mailto:spanner...@usabledevices.com>>> wrote:
>>>> >>> >>> On 09/11/12 16:07, sun sunny
>>>> >>> wrote:
>>>> >>> >>>> is it working ? thats a good
>>>> news
>>>> >>> >>> Sunny asked "is it working" -
>>>> >>> >>> previously I thought I heard
>>>> >>> it was
>>>> >>> >>> working - now I am really
>>>> >>> confused -
>>>> >>> >>> has anyone actually run ANY
>>>> >>> code on
>>>> >>> >>> this board? If so can you
>>>> please
>>>> >>> >>> share your results!
>>>> >>> >>> Below is what I have found
>>>> after
>>>> >>> >>> painfully (because I first did
>>>> >>> a lot
>>>> >>> >>> of other stuff because I
>>>> >>> believed the
>>>> >>> >>> PCB silkscreen!) checking
>>>> >>> every pin
>>>> >>> >>> using the blink sketch to
>>>> >>> flash a pin
>>>> >>> >>> and a LED to see which pin
>>>> >>> actually
>>>> >>> >>> flashes I get:
>>>> >>> >>> Blink pin Pin Label on PCB
>>>> >>> >>> 0 2
>>>> >>> >>> 1 3
>>>> >>> >>> 2 1
>>>> >>> >>> 3 0
>>>> >>> >>> 4 4
>>>> >>> >>> 5 5 pin labelled D5
>>>> >>> on top row –
>>>> >>> >>> near “Xinchejian” - NOT the
>>>> D5 on
>>>> >>> >>> bottom row!
>>>> >>> >>> 6 7
>>>> >>> >>> 7 ???
>>>> >>> >>> 8 ???
>>>> >>> >>> 9 9
>>>> >>> >>> 10 10
>>>> >>> >>> 11 11
>>>> >>> >>> 12 6
>>>> >>> >>> 13 13
>>>> >>> >>> 14 -
>>>> >>> >>> 15 -
>>>> >>> >>> 16 -
>>>> >>> >>> 17 -
>>>> >>> >>> 18 -
>>>> >>> >>> 19 -
>>>> >>> >>> Bottom row pin labelled 5
>>>> >>> pin is
>>>> >>> >>> usually HIGH!!! It flashes a
>>>> bit
>>>> >>> >>> during programming.
>>>> >>> >>> Other comments:
>>>> >>> >>> - Pin 1 = Vcc LB1836M
>>>> *was not
>>>> >>> >>> soldered on the board I had*
>>>> >>> >>> - need switch or
>>>> header/jumper
>>>> >>> >>> for battery pack / power
>>>> >>> >>> .... or just remove
>>>> one
>>>> >>> >>> battery from pack!
>>>> >>> >>> - battery pack = almost
>>>> exact
>>>> >>> >>> size of PCB - a bit wider
>>>> >>> >>> - but front wheel/LED
>>>> >>> means
>>>> >>> >>> have to push battery pack to
>>>> rear
>>>> >>> >>> - wheels - mount on
>>>> >>> battery pack
>>>> >>> >>> - screw???
>>>> >>> >>> => use header/plugs
>>>> >>> for motor
>>>> >>> >>> wires??
>>>> >>> >>> - reset switch - can't
>>>> >>> reach if
>>>> >>> >>> shield plugged in
>>>> >>> >>> Leonardo serial ports are
>>>> >>> annoying -
>>>> >>> >>> at least on Ubuntu with the
>>>> >>> Arduino
>>>> >>> >>> GUI/terminal
>>>> >>> >>> Every time you reset the board
>>>> >>> - the
>>>> >>> >>> USB port dis/reconnects
>>>> >>> >>> - and it may re-appear
>>>> >>> with a dif
>>>> >>> >>> port number = nothing in the
>>>> >>> terminal
>>>> >>> >>> - it is now on the wrong port.
>>>> >>> >>> - or the terminal even
>>>> >>> opens on
>>>> >>> >>> the WRONG port and thus is
>>>> >>> tricks you
>>>> >>> >>> into thinking some other
>>>> issue is
>>>> >>> >>> going on!!!!!!!!
