So im working on a biped pete junior type bot, i have an SSC-32 connected unidirectionaly(i think thats a word) with a basic atom pro and im using a ps2 controller, i noticed that the seq has an export function and one of the options deals with eeprom, can i store these exports on the atom pros eeprom then use the ps2 to run these different sequences or should i upgrade my ssc-32 so that it has eeprom then use the ps2 controller to execute these sequences? if both work, which is easier? and is there any documentation on this im missing? ive been searching and just found he information page on eeprom with the ssc-32, the tv remote brat project page was recommended as help but offered little information, just a description of how cool it was. just point me in the right direction or give me a real compressed step by step, ill figure it out from there
The Short answer is I don’t think so. As SEQ will be looking for the SSC-32, when it does the export. There have been a few threads where some of us have tried to have programs on the BAP that emulated the SSC-32 or did a quick pass through. So far I have not heard of any such luck.
However you can have SEQ save the sequences into SSC-32 and then have a program on the BAP call up the appropriate sequence. This can be a pain to do as you need to switch the wiring to have the SSC-32 talk to the host and then back to talking to the BAP. Some of hooked up switches to make this easier.
There are probably ways you could have SEQ export the sequences to build a BAP program. You could then have your own code maybe write the stuff out to the EEPROM, either on the SSC-32 or on the BAP, but I don’t know if that would be worth the trouble.
Earlier on I wrote my own very primitive sequencer in VB that talked to my TV Remote control Brat. This program allowed me to generate a sequence that was stored in the BAPS eeprom that I could execute from one of the keys on the remote control. I was always going to expand on this to allow multiple sequences to be defined, but never did. I think others have done similar things, like wowy7.
Sorry I don’t have any specific things to recomend.
Kurt
it seems like a switch between the ssc-32 and the bb2 is the way to go once i upgrade the ssc-32(i mean, whats 10 more dollars anyway?) i realized that the seq can only output bap code if its for 8 servos or less, that wont work for me in the long run, my only remaining question is(and this was brought up in another thread) will i need a bidirectional connection between the ssc-32 and the bb2 so the bb2 can make sure everything is there?
any chance there will ever be a prewired switch made? or am i breaking down and buying a crimper and touching up on my soldering skills?
Remember the SEQ program has a good PDF users manual built into it. Not planning a switch harness product though.
In addition to the 2-wire cable running between the SSC-32 and the BB2 boards, I added a single wire jumper up from the SSC-32 board RX line, and put a short .025" pin into it to make it male. If I need to talk to the SSC-32 (quite a lot now that I’m playing with leg configurations) I just hang the normal 2-wire (3 pin housing) connector (black wire) on only the ground pin of the BB2, and plug in the male pin into the yellow data wire. A short DB9 M-F 3 wire extension is plugged into the SSC-32. OK, it’s not pretty, but it works fine until I get a little comm panel fabricated to take two DB9 connectors (for both boards) and a switch.
I’m still thinking that a little “Pass-through” program for the BB2 would be even more convenient for talking to the SSC-32. I need to get back to it. If the code was short enough, one could simply hold down a button when turning on power (or resetting) to run the pass-through code instead of the normal 'bot code.
Alan KM6VV