He already told you he can download your file onto his SSC-32 with no problems. So your computer is suspect. Do you have another PC, or USB to serial cable to try?
If it is a timing problem it’s certainly possible writing a specific value to a specific location can fail.
One other thing you might want to try, but it’s a long shot… Update the SSC-32’s firmware. Try rewriting the GP firmware. Not likely, but you never know.
Could you try some little test ?
1 :
try to load your EEP file then change manually the bytes from hex 0120 (in your original file E8 11 E3 …)
to E8 E3 11 … then click “Write”
it will help us to understand if the problem is the EEPROM byte at hex 0121 or if it is the “11” value
in fact we know that it’s not the Byte at hex 0121 because you’ve tried a 24LC256 and a 24LC512
anyway it’s interesting to see what happens when this “11” value is tried to be written elsewhere
2 :
then could you try to change manually the bytes from hex 0120 to E8 00 E3…(you said it works fine like this) then change the byte at hex 0220 (all zero in the line) to 11 00 …
then click “write”, if the value “11” is buggy it should now pop up the error message at address hex 0220, does it ?
3 :
if the error message is not poping up with this last test could you try to load the EEP named “moj hex Test.EEP” in this message
then try to write it to the EEPROM, does it write correctly ?
i see in a message that after it hangs, you can’t read the EEPROM until a complete erase :
in my opinion the only way to hang while reading only, is a communication problem
==> (could Mike confirm that no matter what’s in the EEPROM it will read anyway ? i mean between SSC-32 and 24LCXXXX)
4 :
could you try, using Lynxterm, download here lynxmotion.com/p-567-free-download-lynxterm.aspx
to connect to the SSC-32 and type “VER” first to see if it’s well connected it should return “SSC32-V2.04GP”
then type “R1” it should return “600” then type “R2” it should return “70” please confirm it’s ok <== important
Could Mike tell us what values for R1 and R2 he should test ? if you think it could be something to test Mike, thanks.
As Jim said, if possible try on another PC, these COM ports are sometimes…well…strange !
you should try too to use firmware V2.05…dunno
About ASCII, no problem with it, ASCII is ASCII
about the EEPROM, yes you can write value from 0 to 255 (hex 00 to FF) to each address
moj hex Test.rar (5.15 KB)
Laureatus: ok, sounds interesting. i will check that today evening when back from work and let you know.
ok then. time to test.
loaded origin EEP ->write-> error
changed bytes manually in SEQ hex screen->write->error
erase eeprom
tried to load modified EEP -> write -> error at address 120
original modified in SEQ hex editor to E8 00 03-> write->** success**
in SEQ hex added 11 at byte0 address 220 -> write ->** error at address 220**
error writing at address 240
VER test passed
R1 -600
R2 -70
i029.radikal.ru/1103/e0/b575f9f7657ft.jpg
tried firmware 2.05 - no success
one more thing:
when trying to load original EEP via “sequencer viewer” have write error at 120 but then read error at 103 popup.
tried to find for what this byte is responcible comparing 2 EEP modified and origin (origin at the top of screenshot) - servo 10 pin number - may be that help somehow
So yes, at address Hex 0121 there’s the servo #10 pin assigment, you set Pin 17 for servo #10
when you change the value Hex 11 at hex 0121 to 0, it was changing the pin assignment (the value hex 11 is 17 in decimal)
anyway,
now we clearly know that the problem is :
“it can’t write the value hex 11 (dec 17)” anywhere in the EEPROM"
that’s the weirdiest things i’ve ever see for a long time !
we know it’s not Sequencer fault because no matter the value between 0 to 255 to write for it (and it works here)
it’s not a firmware problem because it’s working here, With 2.04 and 2.05 (and previous)
it’s not a problem with the EEPROM because you’ve tested with a 24LC256 and a 24LC512
adding to this we have tried at address hex 221 and hex 240 with still an error message (starting at hex 220 and then hex 240)
i will ask you to perform another little test to make sure…
could you try to load and write the EEP with a “00” instead of a “01” at address hex 121 then write it to the EEPROM (it should work eh)
then close Sequence and open Lynxterm
connect and type “VER” to check if connection ok, it will return Firmware version
then type this line :
EEW -289,17
and press
this is the direct command to write a hex 11 at address hex 0121 (hex 11 is dec 17, hex 0121 is dec 289)
dont miss the “-” before the 289 !!
then close Lynxterm and run Sequencer
go to the Hex editor and try to read the EEPROM, is the value hex 11 correctly written at hex 0121 ?
i bet no
in my opinion it’s a communication problem, but maybe in the USB to serial cable driver (a bug) or in the cable itself (electronic part)
the best way to understand this, is testing on another PC
if it’s the same errors, try to grab another cable (other brand) and test with the new cable
(a serial to serial cable will be the best for this test, but maybe you have no DB9 plug on your PC)
it seems the value hex 11 can’t travel thru the cable
because the problem is when writting and when reading i suspect the cable electronics or/and the USB to serial driver (is it up to date ?)
maybe you should try on another USB port, it could be the USB port having a problem (it will ask you to install again the driver if you move the cable to a new USB port (or maybe automaticaly installing it dunno))
ok. I’ve got another usb-rs232 plug (seems to be made with FT232 chip)
also i have PCI -> rs232 card in my computer but not sure if it works fine (these new PCs are terrible if speak about LPT or 232 ports 
).
seems to be another loong weekend of struggling ahead 
will’ let you know about progress. as a final solution i think i can use another SSC32 port to avoi 11s to be generated, have some free, but probably this will not work since 11 might be somewhere in sequence 
and not planning to use PS2 controller or phoenix codes made by guys (Zenta, Xan not sure)
ok.during my additional tests found something else:
tried plug based on FT232 chip - no success
tried to put this byte via terminal issuing EEW command - in SEQ got read error at 120 so as you Laureatus suspected
tried use com port i have on PCI - LPT & rs232 card and here got something other interesting:
when ssc connected via usb-232 plug all ok (except this luckless byte in EEProm)
VER test gives correct response from SSC etc.
but
when connected via this card which teoretically gives physical COM port got that
i038.radikal.ru/1103/9e/a4ab0e186dcft.jpg
and additionally SEQ dont see SSC32
any ideas?
What’s the make and model of the PC?
assembled by myself
AMD Phenom II x4 965
motherboard MSI dont remember model
8GB DDR3
WIN 7 ultimate 64bit EN
finally had an occasion to try on another PC!!!
not a timeouts, not a cable but PC or OS issue
had an occasion to try on laptop Compal FL90, same prolific USB-RS232 adapter and finally originall EEP file jumped into eeprom without any additional setup etc. 
but still problem exist for me and my PC
**
Thank you everybody for so hard investigation!!!** 
I don’t have a problem believing that. I have seen some very weird things from a seemingly innocent PC! Check to see if there are any updated motherboard drivers.
Happy to see you’ve found a way to make it work
The “hex 11” byte killer PC 
…brrrrrrrrr…that was weird !
well, for me there is a problem believing that 
but anyway i’m happy that there is any solution.
first of all i’ll try to install XP on other partition and see what happen, i suspecting that win 7 is “too smart” to work with so easy things like eeprom writing.
Ha !
about the problem with the PCI card,
SEQ does not recognize the card because it uses the VER command to check
so if the VER commands returns bad message it won’t work
In Lynxterm, go to Port->setup (not the Teminal->setup)
then check :
Baud Rate : 115200
Data bit : 8
Stop Bit : 1
Parity : None
Flow Control : None
if all is correct in Lynxterm, check the same parameters in Windows hardware manager about this COM port
it is, double checked.
probably bad card driver, i had some trouble to make it run under win 7
and this message looks like response top ver but all chars are corrupted.
give me some time to install pure XP and verify. if all fine with that hardware on XP it will be drivers issue
ok. i should say all fine now.
it was a long story since yesterday with OSes but all of it finished or reinstallation of one i had before - Win 7 ultimate 64 bit.
now with my prolific usb-232 dongle all working, so result is - kind of trash in OS
anyway i did one more check and original RS port i have is not on PCI card but on motherboard. and this one still talking garbage things with SSC. io do not mind since prolific dongle working now.
so in total this story ends with happyend
thanks once again to everybody!
