From charleyshf at charter.net Sun Nov 19 12:03:36 2006 From: charleyshf at charter.net (Charley Webb) Date: Sun Nov 19 12:03:49 2006 Subject: [WheelCommander] Wheel Commander problems Message-ID: <000a01c70c15$cc5a6070$7a01a8c0@duobeast> Hello, I am using a Basic Stamp module hooked to the Wheel Commander for RX and TX data, the problem is that I can send data to the WC, I can also send the calibrate command to the WC (K), and that works, I can also set the baud rate on the WC, HOWEVER I cannot receive ANYTHING from the WC, it's as if there is nothing coming out from the TX on the WC. I have also tried to reset the WC which changes nothing, so the same problem remains, I cannot receive any data from the WC at all. I have also tried the example code on the Nubotics website, however I get the same result. Is there something I am missing?? From plskeggs at noeticdesign.com Sun Nov 19 12:17:52 2006 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Sun Nov 19 12:18:06 2006 Subject: [WheelCommander] Wheel Commander problems In-Reply-To: <000a01c70c15$cc5a6070$7a01a8c0@duobeast> References: <000a01c70c15$cc5a6070$7a01a8c0@duobeast> Message-ID: <4560BBF0.7010609@noeticdesign.com> Charley Webb wrote: > I am using a Basic Stamp module hooked to the Wheel Commander for RX and TX > data, the problem is that I can send data to the WC, I can also send the > calibrate command to the WC (K), and that works, I can also set the baud > rate on the WC, HOWEVER I cannot receive ANYTHING from the WC, it's as if > there is nothing coming out from the TX on the WC. > Hi, Charley, sorry to hear you are having trouble. Please provide a description of exactly which pins on the WC are connected to exactly which pins on the Basic Stamp. Also, please tell me what baud rate you are using. Also, when you send the calibrate command, I gather that the wheels move, and that is how you know it works (or at least, does something). I assume you do not receive back the 'a' or 'n' acknowledgement bytes, in response to the calibrate command, right? Do you send the calibrate command before or after sending the baud rate command? Other things to try: - use an ohm meter and confirm that the wiring on the TX line from the WC definitely connects between the Basic Stamp and the WC - use the ohm meter to confirm that the TX line does not short to the adjacent Vdd or GND pins - use a volt meter to confirm the voltage on the DC power input lines to the WC is at or above 6.2v Sincerely, Pete Skeggs Nubotics Tech Support From charleyshf at charter.net Sun Nov 19 12:28:59 2006 From: charleyshf at charter.net (Charley Webb) Date: Sun Nov 19 12:29:09 2006 Subject: [WheelCommander] Wheel Commander problems In-Reply-To: <4560BBF0.7010609@noeticdesign.com> Message-ID: <001501c70c19$5853c870$7a01a8c0@duobeast> WOW!! Thank you for getting back to me. I am using a Basic Stamp, with the same connections as the ones in your example. Pin 0 - RX from WC'S TX pin J10.3 Pin 1 - Xmit to WC'S RX pin J10.1 The ground pin from the WC(J10.4) is connected to the basic stamps ground.(Wether I have this connected or not I can see when I send a command to the WC) When I send the 'K' command to the WC, it goes through this process of moving the wheels(servos) and it runs for about a minute and then stops, at that point the green led on the WC comes back on. So I know it's receiving commands from my basic stamp, I have also used the serin command without timeouts to see if ANYTHING is coming from the WC, which of course the basic stamp will stay there forever until something is received. I have the baud rate programmed on the WC at 9600, same as the basic stamp I also have a Basic Atom Pro 28 pin on a botboard that I am testing now, there are some differences in the code, however I get the same results. I send the baud rate command before I send the calibrate command, and I have also done the reverse. Everything else I have tried and verified connections. IS there anything else I can try? Thank you -----Original Message----- From: wheelcommander-bounces@list.nubotics.com [mailto:wheelcommander-bounces@list.nubotics.com] On Behalf Of Pete Skeggs Sent: Sunday, November 19, 2006 3:18 PM To: WC-132 WheelCommander Controller Support List Subject: Re: [WheelCommander] Wheel Commander problems Charley Webb wrote: > I am using a Basic Stamp module hooked to the Wheel Commander for RX and TX > data, the problem is that I can send data to the WC, I can also send the > calibrate command to the WC (K), and that works, I can also set the baud > rate on the WC, HOWEVER I cannot receive ANYTHING from the WC, it's as if > there is nothing coming out from the TX on the WC. > Hi, Charley, sorry to hear you are having trouble. Please provide a description of exactly which pins on the WC are connected to exactly which pins on the Basic Stamp. Also, please tell me what baud rate you are using. Also, when you send the calibrate command, I gather that the wheels move, and that is how you know it works (or at least, does something). I assume you do not receive back the 'a' or 'n' acknowledgement bytes, in response to the calibrate command, right? Do you send the calibrate command before or after sending the baud rate command? Other things to try: - use an ohm meter and confirm that the wiring on the TX line from the WC definitely connects between the Basic Stamp and the WC - use the ohm meter to confirm that the TX line does not short to the adjacent Vdd or GND pins - use a volt meter to confirm the voltage on the DC power input lines to the WC is at or above 6.2v Sincerely, Pete Skeggs Nubotics Tech Support _______________________________________________ WheelCommander mailing list WheelCommander@list.nubotics.com http://list.nubotics.com/mailman/listinfo/wheelcommander Nubotics Website: http://www.nubotics.com From plskeggs at noeticdesign.com Sun Nov 19 13:07:36 2006 From: plskeggs at noeticdesign.com (Pete Skeggs) Date: Sun Nov 19 13:05:46 2006 Subject: [WheelCommander] Wheel Commander problems In-Reply-To: <001501c70c19$5853c870$7a01a8c0@duobeast> References: <001501c70c19$5853c870$7a01a8c0@duobeast> Message-ID: <4560C798.80800@noeticdesign.com> Charley Webb wrote: > I am using a Basic Stamp, with the same connections as the ones in your > example. > Pin 0 - RX from WC'S TX pin J10.3 > Pin 1 - Xmit to WC'S RX pin J10.1 > The ground pin from the WC(J10.4) is connected to the basic stamps > ground.(Wether I have this connected or not I can see when I send a command > to the WC) > > When I send the 'K' command to the WC, it goes through this process of > moving the wheels(servos) and it runs for about a minute and then stops, at > that point the green led on the WC comes back on. > OK, sounds good so far. > So I know it's receiving commands from my basic stamp, I have also used the > serin command without timeouts to see if ANYTHING is coming from the WC, > which of course the basic stamp will stay there forever until something is > received. > You might try sending a '.' (sync) command, then check for a received character using serin with a timeout, then send another '.'. > I have the baud rate programmed on the WC at 9600, same as the basic stamp > Please confirm whether you also specify slow_comms. This inserts a delay between bytes, so the stamp has time to process transmissions. > I also have a Basic Atom Pro 28 pin on a botboard that I am testing now, > there are some differences in the code, however I get the same results. > Hmm, that's not good. > I send the baud rate command before I send the calibrate command, and I have > also done the reverse. > I'm not sure why, but our example comments out a call to initfw; perhaps because the test unit already had the mode and baud rate correctly set. Anyway, initfw does two critical things: - set the baud rate - set the mode to slow comms: |SEROUT 1, 84, ["F0289", LF] ' mode = counter rotating axes, inverted platform polarity, slow comms GOSUB getack You at a minimum need to do the mode setting, if you have already changed the baud. | > Everything else I have tried and verified connections. > IS there anything else I can try? > Have you tried hooking it to a PC using an RS232 level converter, as described in the manual, and run the WC Configuration Wizard? If you can do this, and it works OK, then you know for sure that the WC is OK. Sincerely, Pete Skeggs Nubotics Tech Support From charleyshf at charter.net Sun Nov 19 13:39:21 2006 From: charleyshf at charter.net (Charley Webb) Date: Sun Nov 19 13:39:27 2006 Subject: [WheelCommander] Wheel Commander problems In-Reply-To: <4560C798.80800@noeticdesign.com> Message-ID: <001601c70c23$2c6a9680$7a01a8c0@duobeast> Hi, Well I just finished building my RS232 level converter with a MAX233, and hooked it up to the WC, using the software for the WC, it works, it tells me which firmware revision I have(29), all sorts of information. I could of sworn I used the slow comms along with 9600 baud however I guess I didn't. So I changed my settings in the WC software, then hooked up my basic stamp, and wouldn't you know, it's working! I was working on this for 2 days, and I wanted to avoid building the TTL converter, I should of just built the converter first :) Anyways, thank you for your help. Now to get the programming!! -----Original Message----- From: wheelcommander-bounces@list.nubotics.com [mailto:wheelcommander-bounces@list.nubotics.com] On Behalf Of Pete Skeggs Sent: Sunday, November 19, 2006 4:08 PM To: WC-132 WheelCommander Controller Support List Subject: Re: [WheelCommander] Wheel Commander problems Charley Webb wrote: > I am using a Basic Stamp, with the same connections as the ones in your > example. > Pin 0 - RX from WC'S TX pin J10.3 > Pin 1 - Xmit to WC'S RX pin J10.1 > The ground pin from the WC(J10.4) is connected to the basic stamps > ground.(Wether I have this connected or not I can see when I send a command > to the WC) > > When I send the 'K' command to the WC, it goes through this process of > moving the wheels(servos) and it runs for about a minute and then stops, at > that point the green led on the WC comes back on. > OK, sounds good so far. > So I know it's receiving commands from my basic stamp, I have also used the > serin command without timeouts to see if ANYTHING is coming from the WC, > which of course the basic stamp will stay there forever until something is > received. > You might try sending a '.' (sync) command, then check for a received character using serin with a timeout, then send another '.'. > I have the baud rate programmed on the WC at 9600, same as the basic stamp > Please confirm whether you also specify slow_comms. This inserts a delay between bytes, so the stamp has time to process transmissions. > I also have a Basic Atom Pro 28 pin on a botboard that I am testing now, > there are some differences in the code, however I get the same results. > Hmm, that's not good. > I send the baud rate command before I send the calibrate command, and I have > also done the reverse. > I'm not sure why, but our example comments out a call to initfw; perhaps because the test unit already had the mode and baud rate correctly set. Anyway, initfw does two critical things: - set the baud rate - set the mode to slow comms: |SEROUT 1, 84, ["F0289", LF] ' mode = counter rotating axes, inverted platform polarity, slow comms GOSUB getack You at a minimum need to do the mode setting, if you have already changed the baud. | > Everything else I have tried and verified connections. > IS there anything else I can try? > Have you tried hooking it to a PC using an RS232 level converter, as described in the manual, and run the WC Configuration Wizard? If you can do this, and it works OK, then you know for sure that the WC is OK. Sincerely, Pete Skeggs Nubotics Tech Support _______________________________________________ WheelCommander mailing list WheelCommander@list.nubotics.com http://list.nubotics.com/mailman/listinfo/wheelcommander Nubotics Website: http://www.nubotics.com