RIOS Software - Problems with Project Movements

[left][LEFT]
warning.JPG I recently purchased and installed RIOS software on my Windows 7 - Laptop

I also have Flowbotics software. And the robot works fine with that software.

I can connect, configure, save, and setup the robot per the RIOS user manual.

However, when I build simple projects, “from scratch” the movements of the robot do not look like what I programmed. I notice that typically the “move” window seems to be disabling servos, when I enter. I get a warning message about disabling some of the servos

If I quickly return to the config window I see the servo are disable. Also when the program does move, I can see some of the program movements, like the base, and the gripper, but the shoulder and elbow are often not working. Many time I hit the ambulance button ON then off and the robot will return to the position that I set in the “Step”.

I need to get this fixed. The RIOS software is critical for a School Science project, where we were going to issue Socket commands to the robot from a C++ program. (Any other Ideas in the area as well?)

I have re-configured multiple time, re-tested, build multiple projects, etc. I have double checked the Comm setting, re-loaded the drivers.

Should I purchase the new SSC-32 USB board, I am using the older board, with the USB-to-RS232 cable?..[/left][/LEFT]

I need some new ideas?

THANKS,
Mike

Hi Mike,

We have analyzed your problem and are able to reproduce it with our own AL5D using an SSC-32U and RIOS, so the older SSC-32 should not be the issue.

We will investigate the issue and get back to you soon once we have more information.

Sincerely,

Thanks,
I have continued to research the issue and it seems to be related to the fact that the configuration that I save (many times), is lost somewhere in the processing. Each time I “stop” the 1.5 servo test, the robot does not return to the “home” position that saved in the configuration file. If I re-open the configuration file, on the configuration screen, the robot goes back the pre-programmed home position.

As soon as I do an "All = 1.5 test, then stop the test, the robot does not go back to the home…hence, it looses it configuration.

Also, after I re-load the configuration, the robot is fine, but typically, as soon as I try to run the project, the configuration is lost and the robot goes “OFF” track.

Attached is the another error message that I am getting, plus a screen shott of the files in the config directory (from inside the config window of RIOS). Note the “lock” plus the fact that I can not seem to find these files from the file exsplore, almost like they are hidden, but the permissions do not say that.

Thanks again.

Mike


No servo positions.JPG

Hi,

Thank you for the extra information, it may help figure out what is causing this.

Concerning the “missing files”, you may want to look at this information from a previous post:

We hope this information helps you.

Sincerely,

Thanks for the update…

How long do you think it will take to fix the “crashing” issue? Any ideas so far?

Thanks,

Mike

Hi Mike,

We are currently investigating the issue. Unfortunately, we do not yet have a clear picture of the issue or its cause(s), so we cannot estimate how long this process may take.

We will get back to you once we have more information.

Sincerely,

Are there any update to the RIOS issues with Windows 7?

I think you need to tell people that the RIOS software does not work effectively with Windows 7.

I had to go find a Windows XP Machine in order to get the RIOS software to work as advertised. Once I did that the software works great.

Mike

Hi Mike,

We are glad to learn you were able to use the software properly on Windows XP.

You may notice on the product page of the RIOS CD version that is does specify Windows compatibility. More specifically, it says :

While it does happen to work on Windows 7/8 for some computers, this is not officially supported.

Furthermore, RIOS has been classified as legacy software for a while now and it is now fully discontinued.

Sincerely,