hi,
I possess a SSC-32 and software Lynxmtion Visual Sequencer V1,16,per to make practice I have used sequencer to make to perform to my esapode some movimenti,hos saved the file with extension EEP and when I try to save him/it with GP Seq. in the EEPROM me from this errrore
“ERROR WRITHING 32 BYTESs BLOCK STARTING AT ADDRESS $00200”
what I have been wrong.
I have shaped the Sequencer in this way:
Com 3
Baud installments 38400
Gives bits 8
Stop bits 1
Ninth Parity
Flow ninth controll.
I’ve loaded your EEPROM dump onto a test SSC-32 here with no problems. We’re going to need to see an image or three of your setup in order to proceed any further here…
What version of the SSC-32 firmware do you have installed on your SSC-32? Do you have one that has a GP enabled… You can download versions of the firmware from: lynxmotion.com/p-395-ssc-32- … oller.aspx
Yep I know that , but could not tell for sure if he made the sequences with SEQ, and if it talked properly to the SSC-32… So I thought I would throw that one out…
I have a ssc32 with processor Atmega 168 complete of eeprom from 256 I have installed suil software GP 2-04,possiedo the software Visual Sequencer V1,16 that I have installed on the pc.
I am not really a beginner I have realized various robots if you go on you tubas it looks for robogeppo.
My question I hope that has been clear, I repeat her/it :
“ERROR WRITHING 32 BYTESses BLOCK STARTING AT ADDRESS $00200”
thanks for the help
Excuse me for the a little correct English I have used a translator.
It is very clear that that is your problem, however, no one knows what causes that error so we need more information. Give us a screenshot of the error message and a picture or two of your setup and we’ll try to get to the bottom of this.
Hi Geppino,
I make no assumptions about you being a beginner… I don’t consider myself to be a beginner, but I do still run into simple problems…
I also downloaded your EEP file to an SSC-32 without any issues as well. Given that the only way someone can help is to have some additional information from you such as a picture of the setup. Or we can suggest some generic debugging steps we would take if we were having this issue.
Things like:
a) What power is being given to the SSC-32. My test was done with a 6v wall wart… If you are using a battery, what voltage and have you tried replacing it and/or fully charging it.
b) Communication to PC. Do you have the 2 jumpers in for RX/TX. What baud rate are you running at. I tested at 115200 with both baud rate jumpers on the SSC-32.
c) What else do you have plugged into the SSC-32? Have you double checked to make sure no servo wires are plugged in the wrong direction? Have you tried to unplug all of them and see if that helps.
d) In SEQ if you click on the GP Sequencer button - does it show a picture of a 24LC356 I/P and show that there 32768 bytes and that it was tested?
e) If you click on the test button does it come back OK? If you click on the Hex/ASCII editor, can you read in the current contents? If any of these tests fail, have you tried to re-seat the current EEPROM? If so you might want to do as Jim suggested and try to replace the EEPROM…
As James and Jim have suggested pictures can help here.
f) What serial port are you using? True serial or USB to serial, if you’re using an adapter, what make and model?
g) What version of SEQ or LynxTerm are you using?
, but could not tell for sure if he made the sequences with SEQ, and if it talked properly to the SSC-32… So I thought I would throw that one out…