It’s been a while since I’ve released the first version of my code. The code has improved a lot and is still getting better with all your input. I will release version 2.0 in some time and I could also use some input from you all.
The code is used for all kind of projects. Every project comes with his own unique setup concerning dimensions, electrical connection and remote. Most of you know that the code can be changed to work with all kinds of hexapods. To do this you’ll need to change some values spread around the code.
I was thinking of making it easier to adapt the code for the different setups. Instead of making a #ifdef like I did with the SSC setup I’m thinking of making a separate configuration file for the dimensions and a separate file for the remote type. Instead of using one large file we will have 3 files. One containing the main code. The second will contain all the project setup concerning connections and dimensions. The last one will contain data for the input.
To get the program to work you’ll need:
The universal main program
One of the remote files (PS2, Wii, RC)
One of the configuration files (Phoenix, xH-3, etc.)
This keeps the main program easy to update without the need to walk through the whole program to adjust the variables. It is easy to get a version that suits your setup. And it will keep the main program clear.
It sounds like a good idea using separate config files, I wasn’t aware that was possible . It should be much easier to get an overview of the code and also easier to alter the config for another hexapods.
Personaly I think I’m probably gonna make a complete mess out of your new code anyway
Sounds like a newer version of powerpod! Depending on how difficult it is, you may want to also be able to configure it such that one of the remote files is: Automomous or the like…
this is great!
people that are new to robotics will like this! it will be nice to have a choice and a mix and mash of codes so people can adopt robotics in a comfortable way!
**To get the program to work you’ll need: ** The universal main program
One of the remote files: (PS2, Wii, RC, Serial Link, Autonomous.)
One of the configuration files: (Phoenix, xH-3.)
Add-in’s: (leg configuration, gaits, Pan/Tilt, etc)
this would make it very simple to follow and allow people to edit parts of each code without having to look at hundreds of lines of code!
I’ll toss my quarter’s worth in on this too. Yes, using separate configuration files would make it easier to find and change those values or code one needs to change for their application. It’s a great idea!
Thanks for all the reactions! Unanimous voted for the separate files! 8)
I’m not planning on making an Autonomous program for the phoenix but it would be easy to make a template for it. The suggested remote file can be renamed as input file and the input can be almost everything you want. PS2, Wii, Serial, or a couple of sensors on the hex with some logic to make it Autonomous.
Kurt, can I use the CHR-3 dimensions that you send me in the PM for the CHR-3 Configuration file?
It is probably a good starting point. However there are multiple leg types with different dimensions. So we will need to probably have different ones for differnt legs, like powerpod does.
. It should be much easier to get an overview of the code and also easier to alter the config for another hexapods.
Yes, using separate configuration files would make it easier to find and change those values or code one needs to change for their application. It’s a great idea!