Hi guys.
When I first time run the RIOS with just powered on robot it does not activate servos accordinly to the configssc32.cfg file. When I try to do that manually and click “SSC-32” button, RIOS activates turn-table servo immediately and it turns counter clockwise to the limit at maximum speed servo can develop. The screen looks like incorrect.png (the most confusig thing is sliders are at positions beyond the limits).
If I open configuration file and select configssc32.cfg manually, the screen looks like correct.png and servos activated at correct positions. I expect this status by default when I run RIOS (without opening files manually etc). Or at least I expected from RIOS it can read the current servos positions and set the sliders accordingly.
If I play RIOS in virtual robot mode, everything is ok (as expected).
Is this my only problem or someone else can confirm that?
I tried to play with timeouts and baud rate, checked physical COM port and port via USB, tried different computers from different manufactures but no luck so far. In all tests I used Win XP SP3.
May be this problem comes not from RIOS itself but logic board. My one got “V2” sign on processor and RIOS reports SSC32-V2.03XE firmware
version.
Except of the initialization process everything works excellent.
I remember that I used to have this problem when using my arm. What are your timeouts set to? Are you using a USB to Serial cable or a true serial port? What adapter are you using? It would also be helpful to see an image or two of your wiring.
The problem sounds like it’s caused by communications issues. RIOS uses high speed bidirectional communication. The only way the sliders could be set to the wrong place is if the data were corrupted in this back and forth talking…
Thanks guys for quick response.
At present moment the timeouts are default (20 10 10). I tried (50 30 30) and (0 100 10) all they work but do not solve the problem.
I checked this issue with physical (hardware) COM-port and USB-emulated one (FT245BM?), the behaviour is absolutely identical. All the stuff was bought from Lynxmotion (COM extension cable and USB/COM adapter). I checked USB/COM and hardware COM on two different desktops and one notebook. No difference.
I have no issues with controlling the robot with RIOS (I replayed sequencies up to 100 times without a hassle), the problem happens only at first initialization after robot power cycled. This prevents me from starting command-line play, the screen says “you have to activate at least…servos” (something like that).
The board powered from two isolated power supplies.
I’ve sent an email to the program’s author. He should reply here soon.
Hi there,
If you’ve tried with different computers it should be a problem with the “USB to serial” cable
is the cable driver installed correctly and up to date ?
could you try with a pure serial-serial cable ?
does the problem occur when going directly to the Play form ?
or the Move form ?
(and clicking yes to initialize in the popup message)
it could be too a problem with registers (the SSC32 registers)
did you play with SSC32 registers using Lynxterm ?
if so, please check with Lynxterm the registers value/state
I have downgraded the firmware to 2.01XE and now RIOS works exactly as described in the manual (I can make any position as home position and can play sequencies from command line).
Before doing that I tried 2.03GP firmware for a change but result was the same as for 2.03HX, it does not fix the problem.
I did not play with registers, so I could not set them up into wrong statuses.
Interesting… We will look into this. No one else has reported anything like this.
If you will check this, please note that r0 register set to 0 (my one was set to 4, pulse offset enabled) helps to avoid this problem in firmware 2.03.
Another bug I discovered is how offset works. I got offset 100 for base (turnable table), it was set in my newly arrived board I don’t know what for. If I move robot to certain position using RIOS and just press “GoTo” button several times on the same step, the base makes shaking motion (back and forth, probably in the range of offset). The same happens if I disable and enable servos (using emergency button in RIOS). First I suspected broken pot in servo but when I set r0=0 the problem came off. When I turned offsets off I had to recalibrate range for the base servo in RIOS.
Now I use the firmware 2.01, r0=0 and quite happy with how RIOS works.
