Just assembled a 4DOF T-HEX but unable to upload the standard T-HEX code from the website into the BAP/BB2. I’ve worked the kinks out of the Basic Micro Studio and got that running- was able to upload and run an available test program (aprotut1.bas) with no problems. But when I try to upload the “t_hex_4dof_control_ps2” program, I can’t get past the compiling stage and keep getting:
I’ve gotten a test program to run successfully and would like to rule out Basic Micro Studio, the USB/serial cable, and board itself as culprits and can only assume its the program itself? I was using the standard code provided on the website though, so must assume I’m missing something else obvious. Didn’t see any other references to it in the forums, either. Does anyone have any ideas?
Thanks, I appreciate any help. This T-Hex is a monster and I can’t wait to get it up and running.
An excerpt of code (around line 150 like the error says) is below. I know its completely out of context, though. (Also, sorry I couldn’t figure out how to put it in the nice box like the forum says to do):
…
; Switch bot on/off
IF (DualShock(1).bit3 = 0) and LastButton(0).bit3 THEN ;Start Button test
IF(HexOn) THEN
'Turn off
BodyPosX = 0
BodyPosY = 0
…
Did you open one of the basic programs (.bas) or did you open the project file (.prj)? This program is set up as a project which contains several *.bas programs. Try clicking on project then open I think. I don’t have it on this PC. Hope this helps.
Thanks for the speedy reply. That made it through the compiling and uploading stage. But after completion, the T-Hex doesn’t give the short beeps, nor do the legs snap to position when selecting “start” on the PS2 controller as indicated in the tutorial. There’s no sign from the T-Hex once the program is complete.
Probably need a little more information. Which program did you download and install?
What is the state of the PS2 transmitter and receiver? Is one light on and the other flashing on the receiver? It might help to see some pictures showing the wiring. Things like how the wires are hooked up to the PS2. If still no response from it, may suggest try running the PS2 test program, that you can find up at: lynxmotion.com/images/html/build034.htm
Thanks, I’ll give the PS2 test program a try. But I originally uploaded the “T_Hex_4Dof_PhoenixV20_PS2” project per the advice above from the LynxMotion website (which included 3 .bas files) using Basic Micro Studio. I’m using a wired PS2 controller and have double/triple checked the wiring per the tutorial diagrams (in pins 12-15 on the botboard II, ensuring the colors are all in the right order and all other jumpers are where they’re supposed to be).
But I’ll give that PS2 test program a try in the meantime. Thanks!
PS2 controller test program works like a champ! No issues there. I also tried loading the Bot Board II testing program from the BASIC Micro Studio Programming Tutorial and get the results it says I should.
Well, I’m still at a loss. I’ve successfully run both the PS2 controller program as well as the available Bot Board II test program and both worked fine. But when I load the T-Hex project files (the ones right off the website), nothing seems to work- no tones, no PS2 button response, no servo movement, etc…
I did notice the T-HEX tutorial text says to plug the connection between the BotBoardII and SSC-32 (“DC-01” cable?) to P08 while all the images show P10. When I put it into P08, I get tones from the board on start up and from the controller when buttons are pressed, but still no response from the servos (and I’ve definitely checked proper power supply to the SSC32). Still very puzzled. Any more ideas?
Here’s what I’m using:
BAP28
Basic Micro Studio 2.0.0.15
Wired PS2 Controller
My quick look at the code, looks like it should be on P10/11.
Also I am guessing that the code is using the binary commands to talk to the SSC-32. If this is so, you need a version of the SSC-32 firmware that supports this.
Fixed the text in the assembly guide. Sorry about the confusion. The code is set by default to NOT use the binary firmware, so you shouldn’t need to change the firmware to the binary version. I suspect another problem. Could you post a couple of clear images of your wiring?
Actually, this weekend, I reviewed the wiring again and noticed the included cable that goes from the Botboard to the SSC was a 2 conductor wire that didn’t match the pins in the drawings (on the SSC side, the two cable’s pin receptacles were adjacent and only covered the RX and GND, and on the BotBoard side, only covered P10 signal and GND with no middle wire to go to P11). So I modified a spare 3-conductor servo extension I had laying around (per the instructions) and it works now. Well, works better- At least the legs move and responds to controller inputs.
However, the 'Bot seems to be reeled back on its heels and the legs don’t seem to move in any semblance of order. In fact it flips itself over and looks like a real spider after you squish it and it goes through its death throes. Quite scary how life-like it is, actually. But it doesn’t walk and barely stands. Let me go back through the initial SSC set up and make sure the servos are biased correctly and the horns are aligned as required.
