can a Windows 7 Home Premium 64-bit os connect with rios (i’m using Robot Arm AL5A with SSC-32 board)? My com port is not communicating with SSC-32 through this 64-bit Home Premium Windows 7 version. I was able to connect using Windows XP Professional 32-bit, and XP Home 32-bit.
We will have to get Laurent in on this. I did a search for windows 7 64 bit and found this guy says it’s working for 64 bit Windows Vista Business.
viewtopic.php?p=59852#p59852
This guy says it won’t work with W7, but he couldn’t get it to work with any OS he installed.
viewtopic.php?p=59779#p59779
This guy says it works on W7 but he didn’t state if it was 32 or 64 bit.
viewtopic.php?p=59367#p59367
Sigh…
Hello Doost,
RIOS and friends are not yet tested on Windows 7 (32 or 64 bits),
All softwares are tested from Windows 95 to Windows Vista.
On your new Windows 7 installation you should check some things :
-
as it’s a new installation, you should check (in Windows) the COM port properties and set them as RIOS ones
(by default it could be 9600 in Windows, you must set it to 115200 or more) -
if you’re using an USB to Serial adaptator, check if you have installed the cable driver.
-
you could check too if there’s an updated driver for Windows 7.
-
try to download Lynxterm (free) and test with it to communicate with SSC-32 (‘VER’ command to start)
-
check if the right COM port is selected in RIOS and Lynxterm.
-
Try to increase the ‘Read interval’ value in the ‘Timeouts’ Window (try 30, 40, 50 etc…)
If you have any error message or more information about the way it doesn’t work please tell us
it will help to find where is the problem.
What sort of cable do you use ?
Does RIOS show some available COM port in the ListBox ?
Is it the right one selected ?
Do you see the SSC-32 firmware showing in RIOS main page (below the “Firmware” button) ?
Thanks Laureatus. I will try those suggestions. I now was able to install both Lynxterm and RIOS SSC-32, but my Windows 7 64-bit home premium edition is not communicating to ssc-32 servo controller. I am using FTDI’s usb to serial converter cable came along with AL5A robot kit from Lynxmotion. I have uninstall their VCP driver now but i don’t have the ssc-32 board at this time and not hooked up with the usb to serial converter. Now if I try to open RIOS to use it in virtual mode, program does not open and the message is :
Error reading comcombobox1–>comproperty: registry error ( win erro code:2) .
Thanks again for all you help.
That error means there is no serial port. All of our programs check for a valid serial port before they will open. Sorry, has to be that way.
Today, I was able to update the driver of COM port, and prior to that I changed baud rate to 115200, and now I am able to connect to usb/serial converter, and now RIOS is installed and working on my Windows 7 64-bit Home premium version 
Thanks for all the help.
Do you think you could post a link here to the driver? It could help others who follow… 
I do not know the link, but this is what i did:
From Control Panel->System->Device Manger->Ports->USB Serial Port, then right click & choose “update driver software”, and the message was updating driver…driver successfully updated, and then I closed all windows, and tried running RIOS, and then my Windows 7 64-bit version Home Premium was able to communicate with the RIOS. I am not sure if it was the Windows 7 driver that was updated or if it was FTDI driver that computer found and updated it.
Right now if I look into driver details of USB Serial Port (COM4), I see following 3 driver files listed:
c:\windows\system32\drivers\ftser2k.sys
c:\windows\system32\DRIVERS\serenum.sys
c:\windows\system32\ftserui2.dll
If it helps, that’s good.