i just wanted to start a thread for people who want to talk about the new features of the sequencer and what they’ve achieved with the new features.
Now where’s my batteries?!?
That was fast! I haven’t even had a chance to post the announcement! 
can’t hang around when there’s fun to be had!
one thing i have noticed is that if i connect via bluetooth it does not recognise my eeprom. i have to use the db9 port.
hello rileyeffects,
so, you mean using SEQ connecting the emulated bluetooth COM port i suppose, and not using the SEQ socket client system, if so try to increase the Timeouts “read interval” value, try 100 then 120 etc…
Laurent
Hi Laureatus
I’m on Bluetooth as well.
Some issues…
Couldnt upgrade firmware over bluetooth, had to revert to serial lead and that would only work at 115200 baud.
I’m assuming should be using the 1-0gbeta.abl that has been available for a while.
When firmware was upgraded it recognised the EEPROM and allowed me in…
When I went back to bluetooth all worked except the GP Seq didnt see the EEPROM so I couldnt get in.
I adjusted the Timeouts quite high but still got nothing
um, what about the Config SSC-32 form ? can you move some servos other bluetooth, can you play a project in the “normal” sequencer form ?
if it’s only a problem in the EEPROM form it could need a higher “Read interval value” as EEPROM + bluetooth are slow…
tell me if the rest of the software is working please…i’m looking into my code during this time.
Oops sorry, yes it seems working for you Paulp, what about you rileyeffects ? are you using the right firmware ?
When trying to write a sequence, I get error:
Error reading 54 bytes block, starting at address $00103
This was writing an 8 step sequence for 18 servo’s
I did the same for a 1 step sequence for 18 servo’s and got:
Error reading 57 bytes block, starting at address $00103
I haven’t tried writing a sequence but everything worked over bluetooth except for the eeprom. i’ll keep playing and report what happens here.
i also could not upgrade firmware and had to use it at 115.2 baud rate over db9 port.
DB9 or bluetooth ?
DB9…
I believe the firmware update does require 115.2kb to work.
DB9 is the 9-pin port on the ssc-32.
So, for me, all these issues are Timeouts problems,
External EEPROM are very slow, it could take 64 seconds to erase a 24LC512…
adding to this the delay with DB9 to USB cables or bluetooth + the SSC-32 internal time to respond, it could result in a very high Timeouts value…
you should try 500 or 1000 for “read interval” value, then try to increase the “read total” constant 100 by 100, then try to increase the “read total multiplier”
try too 1000, 1000, 1000 for the 3 Timeouts value for bluetooth,
200, 100, 100 should be enough for an USB to DB9 cable,
and 10,10,10 (default) is perfect for a standard DB9 COM port.
but you can use 20,10,10 for some PCI->DB9 COM ports
Ok. This is all done with DB9 at 115200 all timeouts 20,20,20
Open HEx/ASCII Editor and Erase FF and Erase 00 both work fine and read back proves all set correctly. Erased all as FF…
Load a single move sequence in and Wrote. The data from &H0100 to &H165 inclusive had visible data set and all the rest set to 00.
Closed application just to be sure, restarted and went into Hex/ASCII and read data back in perfectly.
Opening Control Panel or Sequences immediately brings up the Error box.
If I then close the control panel or sequences and reopen it does not error until I press read.
I increased the timeout values in steps of 100 up to 1000 and it still fails…
As I said at the top, this is all with a Standard DB9 to the built in COM1 of my P.C.
The bit that gets me is that the Hex Editor works a dream…
This time, reconnected Bluetooth. 115200 with settings 40,40,40.
This is as low as I can go and still get it to recognise the EEPROM.
If I go into Hex/ASCII Editor I can read, format and write correctly.
Opening any of the others still causes the errors to appear.
I set the Timeouts as high as 2000 and still exactly the same.
Oops…that’s a bug 
dummy me ! i’m trying to read the EEPROM by block > 32 bytes…
in the GP Sequencer documentation, it’s written “Reads and Writes limited to 32 bytes at a time”
the hexa/ASCII editor is 100% ok with that, but the function which reads “steps” information in the control panel and in the Sequences viewer is not working if you use more than 10 servos. (try with 10 servos max to test).
i’m correcting this as fast as i can…
i hate bugs 
Cool
On another subject, your new advanced sequencer button thingy
I went on that, assigned a movement, tried it out and it worked. Went to choose another movement, went back on the panel to assign that one as well and it had forgotten the one I did before…
That appears to have resolved the issue of reading and writing. It works over bluetooth as well.
Just to be on the safe side though I tested using DB9.
The data appears to follow the formats you give in the excel spreadsheet…
I can identify the sequence numbers, steps and number of servos from the data.
When I go to the control panel and try to play, the bot jumps to a rather contorted shape and then cycles through what it thinks are the steps.
The sequence I uploaded contained 7 steps and I could see there were about seven movements it made but none of the servo positions were right.
the button assign is saved by project, so if you assign a button to a sequence in project “L6” for example, then if you go to project “H3” the previous button used is not assigned, or assigned to something regarding the “H3” project