I have noticed from time to time, after building a sequence, that when I restart and come back to run the sequence, it has forgotten which Sevo’s need to be enabled for the particular sequence…
Is this a known issue or am I overlooking a step at startup?
the SSC-32 config form : servo enabled here (and saved into a cfg file)
just concerns which servo to enable when going directly to this form.
the sequencer form : each project contains informations about servos to enable.
so it could generate a confusion :
if you enable a servo going into the SSC-32 form, and if you go to the sequencer form after that, you can see the servo “enable” (this time) but it doesn’t mean the project contains the information to enable this servo each time you select this project…
to fix this :
fresh power on the SSC-32 and run SEQ
go directly to the sequencer form
select you project
click “go to” to initialize to a safe position
click on the “ambulance” icon to enable all the servos
click on the colored servo’s boxes which are disabled (on the gray button with servo #), it will open the servo’ sub menu.
click enable, the information is auto saved into the project.
Not sure about the snapshot thingy… But the copy a pose thing is already there. It’s a matter of adding a lable to a step. Also look at the AB links. This is a powerful way to swap positioning from one side to another.
type a label into the blank white box located in the step panel, let’s say “home position”
go to the insertion point where you need to copy the step
click on the “label” button (still in the step panel) it will popup a new menu
select the labeled step you want to copy with the list box (so “home position”)
click on “add”, “overwrite” or “insert”
if you have added the labeled step for example, the copy will be labeled too like this " '+ home position" meaning “i’m a copy of home position and i was added here” the " ’ " is here to avoid some issues when exporting into CSV format and using MS EXCEL to open the file
to save a project, use the export function (CSV export)
so if the new project version is worst than the previous, you can delete the current and import again the saved one