I am looking for a little assistance…
I’m trying to get the Lynxmotion RIOS software to work.
I can send commands to my SCC-32 controller with the L6 arm,
and infact I can use the Lynx Terminal program fine.
But the Lynxmotion RIOS v 1.05 I can not get to work with my system.
It runs ok, and shows it communicating with the controller…
it shows the controller firmware version, but when I try the arm test,
( all servos to 1.5 ) it does nothing.
Any thoughts or suggestions? I’m stumped!
Thanks
Chris
I currently have it set that way…
And everything seems to work fine with the Lynx Term program.
I can send P commands ( #11 P1500 )
and even use the 'All = 1.5 ’ button works fine on the Lynx Term
software.
But using the RIOS Lynxmotion software, the All = 1.5 button does
nothing… ( the Green led on the board blinks like it understands the command, but the servos dont move )
So I’m not sure the differences in the two software programs.
Why the Lynx Term works ok but the other does not… same settings
and hardware.
The commands are identical as the the same person wrote both programs. I would look to compare the communication settings to make sure RIOS is set up the same as LynxTerm.
Can you suggest any other settings besides the ones listed below?
I’ve confirmed both are on COM4 38400 8-1-N with no flow control.
( the baud on the ssc-32 is set for 38400 also )
the Timeouts are set as follows,
READ Interval 20 ( tried a higher number like 100 even 250 )
Read Total Constant 10
Read Total Multiplier 10
Write Constant 1000
Write Mulitplier 100
This is something else I’ve noticed , if i load Lynx Term and get the arm
to all=1.5 it holds it’s position, Then if I load RIOS and click the SSC-32
button, the arm drops like it lost power.
Then If I click the TEST button on the SSC-32 config window,
all the servos ‘pulse’ But besides that, I have no control over the arm
using this program.
Is there any other patches, setups, configurations or anything else
I need to do? I just found it odd, that the ‘All = 1.5’ button in Lynx term
works fine, but in the SSC-32 software it does nothing, wont even power the servos. I’m really stumped.
I’ll try and uninstall RIOS and reinstall as I have no idea what else to do.
I forgot to tell Laurent to comment on this yesterday. I’m sending him an email so he will reply today. I know he mentioned changing the all=1500 buttons to include a 50mS delay inbetween each servo, but I thought it was only for RIOS ver 1.05. Which doesn’t really make sense here. Anyway, help is on the way.
I’ve been trying various things with my own arm, err… My robotic arm, trying to duplicate your problem. The only way I’ve been able to make mine act like yours is by trying to run everything out of just the wall pack. If I put a 9V battery on VL and remove the VL=VS1 jumper, it works just fine.
Yup… I have a 9V Batt on VL, the VL=VS1 jumper is removed,
and the power Pack is tied to VS1.
As I said, things work fine in Lynx Term v 1.09
I can send commands and use the ‘All=1.5’ button there fine.
But in the Lynx Motion RIOS v 1.05 software, I cant seem to get
anything to work right…
I’m using a Dell Latitude D620 with built in Serial port ( Com1 )
running Windows XP Pro 2002 SP2.
I’m really stumped here, I would think if it was a power supply
or setting on the SSC-32 it wouldnt work with Lynx Term either.
That is where I’m stumped. One software works, the other doesnt.
Thanks for all your help! I really appreciate it. Hope we can figure it out.
Lynxterm is sending 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…
