It’s possible to open projects files generated by SEQ with another program ? For example, if I code my own program in PHP to play (and not to share) my projects files connected in wireless. In fact, I don’t want to use the command line option because it’s work only on Windows and not on Linux.
Actually, I control my SSC-32 board with my PHP Player under Windows and Linux. Problem, my sequences are very (too) simples. With SEQ, the sequence created are more complex. More realist. My solution ? Creating sequence with SEQ and open and play it only with my PHP Player.
I wouldn’t imagine you can’t do it with PHP. It is a very powerful language and regex can do just about anything. I haven’t used SEQ for just about a year now, so I don’t remember how the inside of the file is. If the file is a simple text file that has a special ext, then its all possible. If the file is encoded or compressed in some way, then you’d have to figure out how they are compressing the file to decompress it so you can get the raw commands from it. I think your better bet is to have SEQ export a list of commands. Then have PHP parse those. Not very difficult to then preg_match the commands. You can even use psuedo-regex in this case. Or explode at \n and use a foreach and send each needle to your player.
I am sure the SEQ file itself contains a ton of information about the config, x/y position of the servo blocks in the program, color, name information, etc. Also information about the steps and if there is any mirroring, etc.
So, I think the best bet is to get SEQ to export the list of commands and use that, rather than parsing the SEQ file itself.
I’ve just started with the SEQ program, and have examined the two files generated. They are both CSV (Comma Separated Values) files, which can be read and edited with a simple text editor (NOT a word processor) program. Although the CSV’s have semi-colons! The servo positions (32) for each step in a sequence are there. I’m sure they could be parsed out relatively easy. You’d also want the speeds for the servos, and possibly other parameters that the SSC32 board can use.
I too would like the format of the two SEQ data files! I’d like to be able to import CSV data from sequences that I’ve generated, and easily extract a sequence for incorporation into the 'Bot controller code (like adding “canned” routines similar to “Attack!”).
It should be possible to command a 'Bot in a “teach mode”, and save off the sequences of movement used. One could simply “capture” the SSC32 commands with a terminal program, but I may want to take it further then that. And not just do various “walks”, but step through the creation of “canned” routines.
In the same way that the internal sequencer program of the SSC32 can be commanded, I’d like to be able to command the 'Bot controller. Yes, I’ve made up PS2 sequences that I can execute in the Docklight terminal control program, but I’m considering extending the capabilities. Seems like just creating a new “joystick mode” could be the trick to adding more commands via the PS2 7 byte framework. Or a completely separate command structure could be implemented instead. For instance, right now I could use a “position leg” or “position joint” command to send to the 'Bot controller code. This would allow me to debug the servo translation of my friend’s 'Bot; whose servos are arranged differently.
And while I’m on it, how DOES one** “step through”** a sequence in SEQ? I’ve yet to make that happen (must be in the manual somewhere).
I’m considering adding that provision (single step) to my 'Bot code so that I can see the individual steps. And with the EEPROM in the SSC32 board, one can cause a sequence to execute, but how about individual steps? I did see some EE read/write command sequences added to the SSC32 manual (someplace?)