You might want to check the actual file names in build 165 (Complete 2DOF Hexapod Tutorial)
Filename Program description
h2prog1.bas Default program.
h2prog2.bas Tank mode and single joystick mode.
h2prog3.bas Single joystick mode and pan-and-tilt on left joystick.
Two of the files save as h2prog6.bas. No big deal.
I also noted that build 164 is called BH3 Body assembly? Maybe it’s common to another model?
Thanks i found it, i didn’t notice it at first, so i just started clicking all the links regarding the AH2… found some .bas files hidden in the tutorials. lynxmotion.com/images/html/build165.htm
I’m just not having any luck finding stuff this week. Short attention span i guess.
Been reading over the tutorials, in the complete tutorial, it shows toward the top the set of basic programs.
like: h2prog1.bas RC
If I currently click on these links, they are not found on your server. Side NIT - I am not sure I would Say RC here, my guess is they are more likely PS2…
Other minor NIT. In the first section about establishing a connection, you talk about USB to serial connection. You say:
To most users they will say what is an VCP driver. This is the only place in this document that mentions that TLA. You might want to point them to some posting or the like that describes what this is and how to do it.
Hard to find, not actually hidden.
More like, tucked away.
I actually spent a good 10 minutes checking for a download section on the website that may have offered sample code.
I was looking for code that i might be able to adapt for my own 2DOF hexapod.
I’m just a bit ditzy lately. Losing stuff, only to find it 10 minutes later, out in the open.
I just re-visited your download area yesterday for the ARC32’s VCP driver. I was surprised to see that two of my systems in a row would not recognize the FTDI chip, even 'tho I had drivers on my systems routinely work with FTDI cables. OK, it’s probably the 3rd (laptop) that had the proper driver already installed, and were I worked with the board previously (probably also where my programs for the ARC32 are).
Windoz was able to go out and find the proper driver (I was surprised) on one machine; much easier then trying to ferret out the proper driver to download from the FTDI website (although I’ve done it before). On the second machine it dawned on me that you had the driver on your website. Much better!