HELP! RIOS Keeps crashing!

I have been using the rios program on a lapttop to control my thesis project. The program is controlling kinetic sculpture via 2 GP2d12 sharp ir sensors. The program runs on a continuous loop, moving when the inputs are activated. The rios program keeps crashing, at least twice a day leading to very upset gallery owners…

I have tried:

restarting computer and card
turning off all the hibernation issues with computer
reinstalling software

Laptop is a compac 1600 series w/ windows 95 and runs reliably.

I am quite upset that i have spent over $1100 on lynxmotion products and i can’t get a software program that doesn’t continuously crash…
even visual sequencer crashes on my comp(but no other application does).
I even just bought a newer laptop and am going to switch out the old one.

Am i doing something wrong?
What can i do to fix this problem?
I will fail my thesis if i cant remedy this problem. please please please help me!

Hello mOTOR,

i need more information about this issue,

what kind of crash ?
is there an error message ?
are you using an USB to Serial cable ?
if yes, are you sure it’s not an USB to serial cable driver crash ?
Win 95 is not best OS to handle USB driver anyway…
make sure you are using the latest driver

what RIOS version are you using ?

is there any clue for me to start searching the issue,
i mean, are you using the sequence list player in RIOS ?
does it crash after a fixed number of hours, like every 4 hours…
does it crash while playing a sequence or while waiting for inputs,
is the SSC-32 card green LED still blinking when it crash ?
is RIOS still on screen when crashing or does it disappear without an error message?
what SSC-32 firmware version are you using ?

sorry, many questions :confused: but i need a starting point to search the issue.
if you have any kind of information to help me focus on something, just tell me, even if you think it won’t help.

alternatively, can you export the project as csv format and send it to me at [email protected] , i will test it here, add the “YourProjectName_SequenceList.txt” file too (in the installation directory) if you are using the sequence list player.

but…if RIOS AND Visual sequencer are both crashing on this computer…i suspect it’s a problem with the computer, because RIOS is not using the same system as Visual Sequencer to communicate with the SSC-32, RIOS is sending and receiving many data at a high rate (interpolated trajectory slices, inputs information etc…) and Visual sequencer only sends a small amount of data at a slow rate…

anyway, please send to me as many information as you can about the “crash behavior” to help to point at the problem.

you could try to use a win 98 sp2 too…i bet it will help

Ok I will attempt to explain everything in chronological order to your questions:

The application just crashes (quits with no error message).
I am using a serial cable, no us.
I am using RIOS v1.04.
I am using the sequence list player in rios.
It crashes unpredictably, but around twice a day.
RIOs disappears on screen when crash occurs.

I have to wait until the gallery opens to check the following:

blinking LED on ssc-32 card occuring on crash
if it crashes while playing a sequence or while waiting for inputs

I am going to put a fan in the laptop box to see if it is a cooling issue with the laptop as well.

Thank you so much for the help and your patience, i know that i am not the best at explaining things :slight_smile:

some other possibilities…visual sequencer crashes more than RIOS, especially when i open up a new project…if that helps. Should i reformat the comp and find a copy of windows 98 to install?

I am going to check the programming as well when i can get to it.(ie sequence list, moves)

I am also using the RIOS to control servos that aren’t attached to the original arm. I am using RIOS for it’s input capability. I bought Visual Sequencer, thinking that it had input capability, but realized that was not the case. I instead just simplified my project to run off of 8 servoes and run RIOS. None of the servoes are overstressed tho…which caused it to shut off all the servoes when i first ran the sculptures. I ahve since changed them to operate differently.

i am also going to check and see if the power to the building (which is under construction) gets shutoff for any reason. I taped off the circuit breaker to the outlet, . Turning off the power would turn off the card, but the laptop would run on battery power long enough to stay on. Does RIOS quit when the card gets shut off by chance? Just a thought… :bulb:

I will also post images as soon as my photgrapher gets some shots in the gallery.

is your PC running out of memory
is the hard Drive realy old?

The hard drive is the original hard drive, but has run without any problems.

There is plenty of memory…

I did reformat and there havent been any crashes so far…(keeping my fingers crossed).

I will keep you guys posted

again thanks!

Open task manager and watch the RIOS memory usage as it is running. If it continues to increase, it will probably eventually crash.

Good news !..i have RIOS V1.04 running on a Win 95 for 14 hours now, without a crash, playing a 4 sequences project with an infinite loop, i haven’t noticed any memory leak too.
there was some (few) memory leak in V1.03 but the V1.04 is ok.

it always increase but it’s not due to RIOS ‘code’ but to Windows’ memory management,
i’m using some double buffered graphical objects, when you open the “Play” window for instance, and play a project, some animated graphics will take more memory, depending on Windows version, but if you minimize the “Play” window while playing it frees many memory as there’s no graphics to display (RIOS doesn’t free any memory when minimizing the “Play” window, but Windows does, that’s why i’m saying it’s not due to RIOS ‘code’)

to search for memory leak is not so easy :wink: …you must deal with Windows behavior first then with the program itself, but the best way to find memory leak is to search in the program code, as the task manager shows Windows memory allocation (mostly for graphics) + program memory allocations + database engine memory allocations + etc…