If you suspect you may have a serial port or USB to serial cable issue this post from Laurent may be helpful. He was replying to some one who could use LynxTerm to communicate with the SSC-32, but RIOS would not work.
Lynxterm sends simple orders like “#0P1500#1P1500#2P1500…etc…” no matter what, that’s why it works with this software.
RIOS is very different, it tests always the arm position before doing something in order to be able to show the current arm position when entering the software and in order to know where to start from.
the All=1500 button is asking the arm position to the SSC-32 (“QP” commands) before sending “1500” orders, but if the SSC-32 doesn’t reply within the “Timeout” value it thinks the servos are disabled (by default).
Asking the arm position before sending the all = 1500 orders is used to return to the previous position when you release the ‘test’ button.
so…it’s a timeout value issue, we must wait the SSC-32 answer to the “QP” commands.
First, why using 38400bps ? is there a problem using 115200bps ? (anyway it works at 38400, but you should use 115200bps for better results)
Then could you try this settings :
Read interval = 0
Read Total Constant = 100
Read Total Multiplier = 10
if it works try to decrease the Read Total Constant the more you can by 10 steps else try to increase it by 50 steps till it works, then decrease the more you can…