From joseph.easley at verizon.net Wed Sep 1 15:08:23 2004 From: joseph.easley at verizon.net (Joseph Easley) Date: Wed Sep 1 22:45:41 2004 Subject: [WheelWatcher] Non right-angle connector? Message-ID: <1094076503.3598.14.camel@localhost.localdomain> I'm putting one of these inside a custom made wheel and would prefer to use a vertical instead of a right angle header so I can make the wheel diameter a little smaller (like the unit in the installation pictures on the website). Is there an option to get a vertical connector (or none at all) so I don't have to manually unsolder six of these tiny connectors (one for each wheel)? Thanks, Joe From plskeggs at noeticdesign.com Wed Sep 1 22:51:24 2004 From: plskeggs at noeticdesign.com (Peter L. Skeggs) Date: Wed Sep 1 22:51:29 2004 Subject: [WheelWatcher] Non right-angle connector? In-Reply-To: <1094076503.3598.14.camel@localhost.localdomain> References: <1094076503.3598.14.camel@localhost.localdomain> Message-ID: <4136B4DC.6070404@noeticdesign.com> Joseph Easley wrote: >I'm putting one of these inside a custom made wheel and would prefer to >use a vertical instead of a right angle header so I can make the wheel >diameter a little smaller (like the unit in the installation pictures on >the website). Is there an option to get a vertical connector (or none >at all) so I don't have to manually unsolder six of these tiny >connectors (one for each wheel)? > > Joe, Thanks for your question. Vertical connectors are on the list of available models, but so far my distributor has purchased right-angle only. I'll let them know of your interest in them stocking those options. Were you considering buying from Acroname or Hobby Engineering (an Acroname distributor)? Sincerely, Pete Skeggs WheelWatcher Support From RATHBOREY at aol.com Wed Sep 22 13:18:05 2004 From: RATHBOREY at aol.com (RATHBOREY@aol.com) Date: Wed Sep 22 13:18:24 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode Message-ID: <4A221ACA.700CC123.024E85C4@aol.com> Hello, I just bought wheel watcher, but have problem integrating it on the oopic-r. I used to use a different encoder that has just 2 channels, channel A and channel B, and it work fine. The wheel watcher has extra clock and direction. Is there any example other than the one at http://www.nubotics.com/support/ww01/code/oopic/ww01_oopic2p_square.osc.php . Any recommendation? Thank for your time, -- Vatana From plskeggs at noeticdesign.com Wed Sep 22 13:39:16 2004 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Wed Sep 22 13:39:18 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode In-Reply-To: <4A221ACA.700CC123.024E85C4@aol.com> References: <4A221ACA.700CC123.024E85C4@aol.com> Message-ID: <4151E2F4.8050408@noeticdesign.com> RATHBOREY@aol.com wrote: >I just bought wheel watcher, but have problem integrating it on the oopic-r. > Sorry to hear you are having trouble. >I used to use a different encoder that has just 2 channels, channel A and channel B, and it work fine. The wheel watcher has extra clock and direction. Is there any example other than the one at http://www.nubotics.com/support/ww01/code/oopic/ww01_oopic2p_square.osc.php > > No, not yet. >Any recommendation? > > You should be able to use the ChA and ChB signals from the WheelWatcher (the yellow and blue wires, pins 1 and 3, just like you used with your other encoder. You don't need to use the extra clock and direction. In fact, that's what the example you referred to does; it uses the oQencode objects with the ChA and ChB signals. I do indicate how to hook up CLK and DIR, but in fact they are not used in the program, so you really don't have to hook them up. Does this help? Sincerely, Pete Skeggs WheelWatcher Tech Support From RATHBOREY at aol.com Wed Sep 22 15:28:14 2004 From: RATHBOREY at aol.com (RATHBOREY@aol.com) Date: Wed Sep 22 15:28:22 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode Message-ID: <56528C41.02DB8797.024E85C4@aol.com> Hello Pete, I haven't get it to work yet. Below is my short code, can you see any problem? I want to turn on an alarm when the encoder read certain value, if greater than 20. The right wheel will run forever. Thank you a whole lot, Vatana, Dim A As New oFreq Dim FRWheel As New oServoSP1 'F stands for front Dim FLWheel As New oServoSP1 Dim FREncoder As New oQencode Sub Main() call Wheel call Encoder A.operate = 1 'set alarm ready to be turned on FREncoder = 0 'initialize to zero FRWheel = 30 'speed at 30 if (FREncoder > 20) then call sound end if End Sub Sub Wheel() FRWheel.IOLine = 11 FRWheel.Operate =cvTrue FLWheel.IOLine = 10 FLWheel.Operate =cvTrue End sub Sub Encoder() FREncoder.IOLine1 = 31 'B input at line 31 FREncoder.IOLine2 = 30 'A input at line 30 FREncoder.Operate = cvTrue FREncoder.signed = 0 'set count from 0 to 65535 End sub Sub sound() A=64936 oopic.delay = 50 End Sub From plskeggs at noeticdesign.com Wed Sep 22 20:08:14 2004 From: plskeggs at noeticdesign.com (Peter L. Skeggs) Date: Wed Sep 22 20:08:17 2004 Subject: [WheelWatcher] RE: wheel watcher interface with oopic-r's oQencode Message-ID: <41523E1E.6070503@noeticdesign.com> > > >Hello Pete, >I haven't get it to work yet. Below is my short code, can you see any problem? I want to turn on an alarm when the encoder read certain value, if greater than 20. The right wheel will run forever. >Thank you a whole lot, >Vatana, > > Hello, Vatana, I will try to build up a robot tomorrow to test your program on. But meanwhile, please confirm whether the WheelWatchers appear to behave properly, as discussed in the FAQ: * *Why am I not getting good counts from the encoders? */Check the behavior of the LEDs while your servos are turning. Do this either by turning the wheels slowly by hand (rough turning can strip the gears in the servos, *so be gentle!*) with the power on to the WW-01s but off to the servos, or by using your own test program/. /The green LEDs should be solid on or off, and should only change state when the direction of wheel rotation changes. The red LEDs should blink on and off, once per stripe -- 32 times on and 32 off for each wheel rotation. If the green LED is flashing when it shouldn't be, or if the red LED is not pulsing 32 times per rotation, make sure your wheels are on tight. If the wheels are too high above the WW-01 PCBs, there won't be enough light reflected to the sensors on the boards. It is best to use the screws provided with your servos to hold the wheels in tight. If you are still having problems, check the alignment of the PCB with the AL-02 alignment tool with the wheel temporarily removed. Also, check that the codewheel stickers are flat against the wheel, without bubbles under them, and that they are clean. / Good luck. -Pete WheelWatcher Tech Support >Dim A As New oFreq >Dim FRWheel As New oServoSP1 'F stands for front >Dim FLWheel As New oServoSP1 >Dim FREncoder As New oQencode > >Sub Main() > >call Wheel >call Encoder >A.operate = 1 'set alarm ready to be turned on >FREncoder = 0 'initialize to zero > >FRWheel = 30 'speed at 30 > >if (FREncoder > 20) then >call sound >end if > >End Sub > >Sub Wheel() > FRWheel.IOLine = 11 > FRWheel.Operate =cvTrue > FLWheel.IOLine = 10 > FLWheel.Operate =cvTrue >End sub > >Sub Encoder() > FREncoder.IOLine1 = 31 'B input at line 31 > FREncoder.IOLine2 = 30 'A input at line 30 > FREncoder.Operate = cvTrue > FREncoder.signed = 0 'set count from 0 to 65535 >End sub > >Sub sound() > A=64936 > oopic.delay = 50 >End Sub > From plskeggs at noeticdesign.com Thu Sep 23 11:47:23 2004 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Thu Sep 23 11:47:25 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode In-Reply-To: <56528C41.02DB8797.024E85C4@aol.com> References: <56528C41.02DB8797.024E85C4@aol.com> Message-ID: <41531A3B.6040501@noeticdesign.com> Found the problem. Your program has a bug. You need to have a loop around the statements 'if (FREncoder > 20) then... end if' so that it waits long enough. As it is, you start the wheel turning with 'FRWheel = 30', then immediately check only one time for FREncoder > 20; at this point in time, the wheel has probably not even moved yet. You need to loop around it like this: ... FRWheel = 30 ' speed at 30 do ' keep trying until enough time has passed that the wheel has rotated far enough... if (FREncoder > 20 then ' finally the wheel has turned 20 ticks; play a sound call sound exit do ' get out of the loop end if loop ' do something else... End Sub This makes your program repeatedly test FREncoder until it reaches 20, then plays the sound. I added 'exit do' to leave the loop so your program can do something else. Let me know if this fixes it for you. It works for me. I did have trouble with some basic things, like connecting ChA and ChB to the wrong pins, but once I got that worked out, I found the loop problem. Sincerely, Pete Skeggs WheelWatcher Tech Support RATHBOREY@aol.com wrote: >Dim A As New oFreq >Dim FRWheel As New oServoSP1 'F stands for front >Dim FLWheel As New oServoSP1 >Dim FREncoder As New oQencode > >Sub Main() > >call Wheel >call Encoder >A.operate = 1 'set alarm ready to be turned on >FREncoder = 0 'initialize to zero > >FRWheel = 30 'speed at 30 > >if (FREncoder > 20) then >call sound >end if > >End Sub > >Sub Wheel() > FRWheel.IOLine = 11 > FRWheel.Operate =cvTrue > FLWheel.IOLine = 10 > FLWheel.Operate =cvTrue >End sub > >Sub Encoder() > FREncoder.IOLine1 = 31 'B input at line 31 > FREncoder.IOLine2 = 30 'A input at line 30 > FREncoder.Operate = cvTrue > FREncoder.signed = 0 'set count from 0 to 65535 >End sub > >Sub sound() > A=64936 > oopic.delay = 50 >End Sub > >_______________________________________________ >WheelWatcher mailing list >WheelWatcher@list.nubotics.com >http://list.nubotics.com/mailman/listinfo/wheelwatcher > > > > From RATHBOREY at aol.com Fri Sep 24 17:14:55 2004 From: RATHBOREY at aol.com (RATHBOREY@aol.com) Date: Fri Sep 24 17:15:06 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode Message-ID: <28D20577.2B471ACC.024E85C4@aol.com> Hello Pete, I haven't have any luck on this. I also try to connect the black and the red wires to ground and 5V respectively. Then I connected channel A and channel B to channel 1 and channel 2 on the oscilloscope respectively. I don't see any square wave signals. How do I know if the wheel watcher that I have is defect or nondefect? Thank you Pete, -- Vatana An Lab (407) 823-0190 Cell(850) 292-4722 From plskeggs at noeticdesign.com Fri Sep 24 22:14:49 2004 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Fri Sep 24 22:48:47 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode In-Reply-To: <28D20577.2B471ACC.024E85C4@aol.com> References: <28D20577.2B471ACC.024E85C4@aol.com> Message-ID: <4154FEC9.9000008@noeticdesign.com> RATHBOREY@aol.com wrote: >I haven't have any luck on this. I also try to connect the black and the red wires to ground and 5V respectively. Then I connected channel A and channel B to channel 1 and channel 2 on the oscilloscope respectively. I don't see any square wave signals. How do I know if the wheel watcher that I have is defect or nondefect? > > I sent you an email about how to check the WheelWatchers by observing the LEDs. It is in the FAQ: http://www.nubotics.com/products/ww01/faq.html * Why am I not getting good counts from the encoders? Check the behavior of the LEDs while your servos are turning. Do this either by turning the wheels slowly by hand (rough turning can strip the gears in the servos, so be gentle!) with the power on to the WW-01s but off to the servos, or by using your own test program. The green LEDs should be solid on or off, and should only change state when the direction of wheel rotation changes. The red LEDs should blink on and off, once per stripe -- 32 times on and 32 off for each wheel rotation. If the green LED is flashing when it shouldn't be, or if the red LED is not pulsing 32 times per rotation, make sure your wheels are on tight. If the wheels are too high above the WW-01 PCBs, there won't be enough light reflected to the sensors on the boards. It is best to use the screws provided with your servos to hold the wheels in tight. If you are still having problems, check the alignment of the PCB with the AL-02 alignment tool with the wheel temporarily removed. Also, check that the codewheel stickers are flat against the wheel, without bubbles under them, and that they are clean. / / Other questions: 1. Have you done this LED test? What do the LEDs look like when you turn the wheel? 2. Are you using servos and standard injection molded wheels as pictured on the website? What kind of servos? Where did you buy the wheels? 3. Have you placed the sticker on the wheel as shown in the assembly photos? http://www.nubotics.com/products/ww01/assembly_photos/index.html 4. Please check the wiring of the connector. Did you plug the colored wires into the correct holes on the connector housing as shown in the manual? See: http://www.nubotics.com/graphics/connector.gif When wired correctly and plugged in to the WheelWatcher, pin 2 connects to ground and pin 8 connects to +5v. The pins are labelled on the circuit board in white paint (silkscreen). NOTE: the pin numbers on the circuit board are not the same pin numbers as shown in the table in the manual; the pin numbers . If hooked up correctly, when you apply +5v and turn the wheel, you should see some activity on the LEDs. Do either of them light up? 5. Do you have a digital camera? If so, turn on the power to a WheelWatcher, and with the wheel removed, look at the two black infrared sensors. You should be able to see the bluish glow of the infrared LEDs. If you don't see a glow (in the camera's LCD viewfinder or after taking a picture), verify that you do see a glow when looking at some other device such as a TV remote control when pressing a button on it; if you don't see a glow then, then your camera has an IR filter that makes this test not useful. 6. Measure the voltage between pins 2 and 8 on one of the WheelWatchers. Do you get close to 5.0v? Is the sign (polarity) correct? Good luck. Sorry you are having so much trouble. -Pete From RATHBOREY at aol.com Tue Sep 28 13:14:08 2004 From: RATHBOREY at aol.com (RATHBOREY@aol.com) Date: Tue Sep 28 13:14:22 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode Message-ID: <0ED38BD6.4AC43808.024E85C4@aol.com> Hello Pete, I get it working. The main problem was that I followed the wrong schematic. I was reading the following page when I was mis-guided: http://www.nubotics.com/support/index.html. I didn't follow Connector's pin out, but instead follow the diagram which was wrong. Actually it is very easy. I think you should remove the wrong diagram. -- Vatana An Lab (407) 823-0190 Cell(850) 292-4722 From plskeggs at noeticdesign.com Tue Sep 28 14:04:31 2004 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Tue Sep 28 14:04:35 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode In-Reply-To: <0ED38BD6.4AC43808.024E85C4@aol.com> References: <0ED38BD6.4AC43808.024E85C4@aol.com> Message-ID: <4159D1DF.1060803@noeticdesign.com> RATHBOREY@aol.com wrote: >Hello Pete, > >I get it working. The main problem was that I followed the wrong schematic. I was reading the following page when I was mis-guided: http://www.nubotics.com/support/index.html. > That link just goes to the overall support page. >I didn't follow Connector's pin out, but instead follow the diagram which was wrong. Actually it is very easy. I think you should remove the wrong diagram. > > Which diagram is wrong? The Block Diagram on page 2 of the product brief (http://www.nubotics.com/products/ww01/ww01-pb.pdf)? Were you assuming the block on the right was the connector, and the pins are numbered down the edge, or what? Or was it a different diagram that is wrong? Glad to hear it is working now. -Pete From RATHBOREY at aol.com Tue Sep 28 14:15:23 2004 From: RATHBOREY at aol.com (RATHBOREY@aol.com) Date: Tue Sep 28 14:15:39 2004 Subject: [WheelWatcher] wheel watcher interface with oopic-r's oQencode Message-ID: <283B7B35.7A1EF0B2.024E85C4@aol.com> Hello Pete, Go the website below: http://www.nubotics.com/support/index.html Under Documentation click on HTML (Product Brieft in HTML). Above Block Diagram there are 6 different colors: 1.yellow 2.black 3. blue 5. orange 7. violet 8. red To the right are two block diagrams. Those block diagrams contain mistaken information. Although it notes that pin 7 is indicated by triangle, I still misled. -- Vatana An Lab (407) 823-0190 Cell(850) 292-4722