I’ve stared working on EEPROM support for my servo sequencer program and I have a lot of questions that I really need help with concerning how it will work. Most questions are aimed at zenta due to the fact that he is the one that brought this feature to my attention.
Should the program export entire projects or single steps at a time?
Should there be extra information for each sequence such as a label and/or a discription?
Should I include an entry table to read out so that the user can know how many sequences are on the EEPROM? (this could help with the automation process but it could use valuable space)
More questions will be added as I come across them. Any responses are greatly apreciated.
My assumption here is that you are talking about exporting your sequences to the SSC-32 EEPROM. If this is the case it should be stored in the standard format as described in: lynxmotion.com/images/html/build137.htm
I have played around some and have VB app and BAP program that does this. It reads in either EEPROM files or CSC files and then allows the user to choose which ones they wish to export. I also have code to allow me to modify the servo numbers as to be able to use Zentas sequences for BAP28 and export to Arc32 (my own format)…
There is a memory map at the start of the EEPROM that gives the starting memory address for a sequence. If a sequence number is not defined, the corresponding 2 bytes in this table should either be 0000 or 0xffff. You can calculate the size of each sequence by reading in the header at the start of it that contains the number of servos and number of steps. I believe SEQ writes out all of the sequences consecutively starting at address 0x100…
