With RIOS 1.03 and SSC-32 cannot set serial port to COM 5, just COM 2, or COM3. COM 5 is my IOGear GBU 311 Bluetooth Serial link that sets its COM port to COM5, and I cannot set it to an available port COM 2 or COM3.
Any trick to either RIOS or the XP Bluetooth to get them to talk?
red
Hum, if Windows ‘see’ the COM5, RIOS must ‘see’ it too, but :
- it’s only compatible with RS232 serial port.
- the serial port must be activated before running RIOS, or you’ll have to click on the main form ‘setup’ button if it’s not listed in the COM port listbox
- i’m not sure, because i don’t know the IOgear GBU 311…but i think it need a Bluethooth to RS232 system on the SSC-32 side to make the IOgear GBU 311 emulate RS232 port uh ?..i mean, if only the GBU is connected, it’s a bluetooth multy purpose port only (NOT emulating RS232 while a bluetooth to RS232 peripherical unit isn’t connected to GBU)
what are you using SSC-32 side ?
You could try re-assigning the hardware serial ports in BIOS and free up COM2 or 3 for your controller board.
I’ve used com2, 3, 5, 9, and one of my friends used com20 on the lynxterminal, and they functioned perfectly.
I assume that Laurent used the same code in both, so I don’t think that the actual com# is an issue.
Partial sucess: Reinstalled the IOGear Bth USB drivers that established a outbound Com8 and inbound Com10 connection to a Slave GBS301 (Bth-Serial).
Rios, when started after all the “pairing” is finished can see the Com 8 and Com10 ports in its drop down box.
However, even though the PC’s Bth SPP icon indicates a paired connected link to the remote GBS301 Serial device, Rios cannot see the SCC-32 and sits there waiting…I have verified that the bitrates are same (115200/8n1) in Rios and GBS301 RS232 Serial Adapter connected to it.
I think I need to troublesheoot the Bth connection.
Tnx for help.
I don’t have any usefull input. I’m a hardware kinda guy. 
But please let us know your progress on this. I’ve been asked about bluetooth wireless use with the SSC-32 many times before. Good luck!
SSC-32 (and Mini-ABB as well with Basic Editor) does not work when connected to a IOGear GBS301 Serial Bth adapter. PC has Bth GBU311 USB configured as SPP Serial Port. SSC-32 and Mini-ABB work when connected to a SIIG USB Serial Adapter as COM2. And Hyperterm connected to Bth Adapter (on COM10) with a loopback plug echos characters. And 2 instances of Hyperterm respectively connected to the USB Serial port adapter on COM2 and Bth on COM10 back-back w/null send characters back and forth. But no go when Bth at same bit rate connected to the SSC-32 or Mini-ABB.
There’s somethng unique about the Bth Serial interface.
Any ideas?
That’s way beyond my understanding…
Have you tried finding Bth tech people on the web?
Some cable replacement projects run into problems with software timeouts. When a physical cable is used, the software can have a very good idea of the maximum communication and response times to expect from the hardware, and some authors cut the timeouts very close to that. Introducing any delay or speed degradation (even though it says 115k2, you’re probably not getting that much throughput).
Check all the software and see if it has adjustable timeouts. If the software/hardware combo allows you to setup the serial port for lower speeds, try that too.