hey zenta,
would you be kind enough to add a simple step by step guide to getting Xan’s code/PS2 solution working. I’ve been trying to get it working with my LM phoenix set-up but not had much success.
Glad you like the short video - some of the gaits are very crude, but i wanted to get an idea of “what would happen if…”
Now i’m getting the hang of things i’m going to try and make the gaits much more subtle.
Just a bit of thinking out loud…
Using SEQ, is there a way to take individual PEP gait snippets (fwd, bkwd, rotate etc) and create an RC type control - so you could walk forward, while holding the up key then tranition into a rotate (say) when another key is pressed?
Cool video!! Great to “see” my code working on the LM phoenix. Mine is still waiting in the box But I will be home from my trip tomorrow so there will be some big progress in a couple of days
I think Xan’s thread is the right place to discuss his code and how to’s. OK? I’ve just made a post there where I explained what I did (not a complete step by step).
I know what your thinking about, I think the GP sequencer might be the solution for that. I’ve not started to test the GP-seq yet.
I’ve been experimenting with a solution for mounting the PS2 reciever on Phoenix. Here are some pictures of the bracket:
Mounted, bottom view just to show that I’m using the original mounting holes for the PS2 reciever housing:
A closeup picture of the PS2 reciever mounted:
Lynxmotion Phoenix together with the PS controller, just an overview:
I’m not if I’m totaly satisfied with this solution, but it work.
I’ve also been testing another solution by giving Phoenix a helmet or a more round body.
I like the solution for the receiver. I was thinking of mounting it the same way but since I was thinking of using a thin aluminium plate the screws going to the botboard where in the way. But I’ve got some spare material from BlackWido which allows me to make some drowned holes. I like the solution!
I see that you are very cautious with your LM phoenix by giving him a safety helmet If you are thinking of making a more round body you should take a look at the plastic that Crabfu is using. (I’m sure that you’ve seen his bots ) The plastic is some kind of low temperature moulding plastic. I was thinking of buying some to do some tests and see how it works.
As you know I’m also gone rebuild my phoenix to match the standard setup. 8)
Yeah, I’ve also been thinking of trying that kind of plastic material one time. Making a more “life like” body would be great.
Today I and my kids played with Phoenix outside in the garden. Here is a picture of her with the Lynxmotion setup (orientation of the SSC card). The big switch in the front are only temporary to switch between BB2 and serial input to the SSC card.
If you look closely there are some raindrops on her, it just began to rain… So I had to snap some pictures in a hurry!
I’ve modified Xan’s code and added a GP player and two different gaits. In this test video I’m controlling Phoenix with a PS2 remote. But I’m struggling with some bugs with the remote and its very hard to make a precise move. (I’ve commented that in Xan’s blackwidow thread). With a RC remote this was much easier, so that will be the next step.
Sorry for the long movie.
It is just a test and to demonstrate the power of combining live control and precalculated sequences.
BTW, the gait I’m using here is a 6 steps tripod gait and a spesial 9 steps ripple (I’m calling it quadripple) gait.
WOW! Your new movie makes the use of the GP Sequencer very clear! Nice movie! The speed using the tripod gait is great! Just 2 steps and phoenix is on the other side of the screen already! I can’t wait to check all the gaits out!
Thanks Xan!
The GP player are pretty useful to make your hexapod do more than just walking.
BTW, the GP player seem to have a bug in the ONCE command. When it play one sequence (ex. 0 -> 13 steps) it start with step 0 but it seem to end the player by sending step 0 one more time after playing step 13.
I solved it by always making sequences that start and end seqences with the same pose/data.
The movie made it very clear, I need to spend some time with the GP seq! But before that time I can’t help you with the GP bug. Maybe Jim has got an answer for the problem.
BTW: I’m planning to finish the mechanical part of my phoenix this evening. I’ll post some pictures when it is finished! 8)
I’m having a similar problem. Initially most projects were importing but I had increasing problems. Now none will import. I can export a file and that will import again but nothing created in PEP will import.
I include a SHP file of the same name with the CSV file and the data in the CSV is delimited by semicolons.
Well the problem could be with SEQ or the GP firmware. Both Mike and Laurent are on vacation. So I have not been able to get info back from them yet. Give us a little more time and we will have it resolved.
I love the cap screws used to mount the servos, much better than using Philips head screws. Another advantage to using cap screws is the ability to use ball ended allen wrenches for those tight angles.
Ok I have confirmation that it’s not a GP firmware bug, but rather how Mike thought it should work. He is open to input on this and make changes if needed. I suggested the possibility of creating another ONCE command, calling it ONCES to mean play the steps (S)hort one. Or not play the first step again. Input… we need input…
“It seems likes some phoenix csv files generated by PEP (zenta) are including an empty row causing some issue in SEQ. I’m modifying the code to avoid importing empty row (steps) and a way to auto delete bad row in existing corrupted database”
So it’s being resolved, but honestly the PEP needs to be looked at to prevent this from happening in the first place.