PEP Wiring vs. Phoenix Build Guide Wiring

I’m in the preliminary stages of trying to use PEP to create some gait sequences for my Phoenix. The first thing that I immediately noticed is that the SSC-32 wiring between the Phoenix assembly guide and the PEP manual appear reversed from each other. The PEP guide for example indicates that the left front leg uses Pins 0-2, but the Phoenix assembly guide seems to want to use Pins 24-26.

I’ve taken a lot of time routing my wiring, zip-tying everything, etc. so could someone tell me if the PEP manual is current? I’d like confirmation before I disassemble this robot and re-assemble it (lots of time!). Thanks!

-Jeff

The simple answer is that you can wire it up any which way you want. When Zenta originally did it, it was on pins 0-2, but later it standardized on 24-26, which is the order I use…

But if you are wired up for 0-2 than you have a couple of choices.

  1. Rewire to the newer standard. You can often get a way with undoing the wires from the SSC-32, unscrew the board, turn it 180 degrees, screw it back in and then reattach the wires… (It is a pain, but I have done it…). The plus with this is that if you wish to use some sequences that were done by other people than they will work as the pins match… [Or you can remap the in numbers of these sequences, but won’t go into that on the first pass]

  2. If you don’t care about other peoples sequences, than you can simply leave your wiring as it is. When you use the phoenix code you will need to change the config file. In particular the part:

[code];--------------------------------------------------------------------
;[SSC PIN NUMBERS]
cRRCoxaPin con P0 ;Rear Right leg Hip Horizontal
cRRFemurPin con P1 ;Rear Right leg Hip Vertical
cRRTibiaPin con P2 ;Rear Right leg Knee

cRMCoxaPin con P4 ;Middle Right leg Hip Horizontal
cRMFemurPin con P5 ;Middle Right leg Hip Vertical
cRMTibiaPin con P6 ;Middle Right leg Knee

cRFCoxaPin con P8 ;Front Right leg Hip Horizontal
cRFFemurPin con P9 ;Front Right leg Hip Vertical
cRFTibiaPin con P10 ;Front Right leg Knee

cLRCoxaPin con P16 ;Rear Left leg Hip Horizontal
cLRFemurPin con P17 ;Rear Left leg Hip Vertical
cLRTibiaPin con P18 ;Rear Left leg Knee

cLMCoxaPin con P20 ;Middle Left leg Hip Horizontal
cLMFemurPin con P21 ;Middle Left leg Hip Vertical
cLMTibiaPin con P22 ;Middle Left leg Knee

cLFCoxaPin con P24 ;Front Left leg Hip Horizontal
cLFFemurPin con P25 ;Front Left leg Hip Vertical
cLFTibiaPin con P26 ;Front Left leg Knee
[/code]

You simply need to change the numbers of each of the pins to match yours… Probably:

[code] RFCoxaPin con P2 ;Front Right leg Hip Horizontal
RFFemurPin con P1 ;Front Right leg Hip Vertical
RFTibiaPin con P0 ;Front Right leg Knee

RMCoxaPin con P6 ;Middle Right leg Hip Horizontal
RMFemurPin con P5 ;Middle Right leg Hip Vertical
RMTibiaPin con P4 ;Middle Right leg Knee

RRCoxaPin con P10 ;Rear Right leg Hip Horizontal
RRFemurPin con P9 ;Rear Right leg Hip Vertical
RRTibiaPin con P8 ;Rear Right leg Knee

LFCoxaPin con P18 ;Front Left leg Hip Horizontal
LFFemurPin con P17 ;Front Left leg Hip Vertical
LFTibiaPin con P16 ;Front Left leg Knee

LMCoxaPin con P22 ;Middle Left leg Hip Horizontal
LMFemurPin con P21 ;Middle Left leg Hip Vertical
LMTibiaPin con P20 ;Middle Left leg Knee

LRCoxaPin con P26 ;Rear Left leg Hip Horizontal
LRFemurPin con P25 ;Rear Left leg Hip Vertical
LRTibiaPin con P24 ;Rear Left leg Knee[/code]
Note: The above came from the old phoenix V1.3 code that had a #ifdef for the two different pin orders.

Good Luck
Kurt

Thanks Kurt,

I’m at a bit of a disadvantage as I’m not using an Atom processor. I’ve been working with Zbasic processors for the last few years and I have MANY of those processors. I’m driving everything from the Zbasic platform. I’ve got the fundamentals down, but I’m struggling to come up with some good gaits I can trigger from my processor. I was hoping the PEP could do that. Are there any resources I’m just missing? Any insight/help would be much appreciated! Thanks!

-Jeff

Sorry, I don’t know that processor…

The question will be, are you planning on using canned sequences on your phoenix or do you want dynamic gaits that can go in any which direction and speed and different leg lifts… If the later you will probably want to look at the gait code in the phoenix. It would probably not be hard to convert some of this to run on you ZBasic processor. I have done this for several different platforms (Basic Micro Arc32, Basic Micro Bap28/40… using C, Arduino Mega, Propeller, …) Most all of these have threads up here on this forum, with zip files…

The nice thing about Pep and SSC-32 here is that you can still use all of the sequences that others (Zenta) have produced and still use them. You simply store them in the EEPROM of the SSC-32 and issue a simple command to the SSC-32 to execute it…

Good Luck
Kurt

Kert,

Thanks so much for all the assistance. I’m looking to do dynamic gaits, but starting out with some sequence based gaits would be great. I’ve been searching through the forums and have found a variety of files, but I’m unclear on what’s the best starting point. The .csv files for different gaits made my Phoenix go NUTS in PEP, which I strongly suspect is because the servos are wired per the assembly guide vs. the PEP guide.

None of these languages is all THAT different. Is there a file someplace that has function based gaits, like “walk forward X steps, X speed”, etc? If so I’d bet I can port that easily. Can you suggest a good starting point? THANKS!!!

-Jeff

Hi,

Just want to shoot in that the manual is a bit out of date. The latest PEP version has the same pin config as the Phoenix assembly guide. :wink:

Oh, thanks Zenta! I noticed that the sequences that come pre-built into the PEP program seemed to work okay. My Phoneix goes nice into attack mode, etc. It’s the other downloadable sequences that make it go completely nuts. I’m guessing they are expecting different servo configurations?

I’ve reviewed the PEP manual and will be trying to walk through the “Gait” series of steps, are there any additional tutorials/info/resources that would help make the learning curve any less steep!

Thanks!

-Jeff