I’ve installed the bluetooth parts on both sides. The software that came with the dongle is different than the directions showed, but it was pretty straight forward.
The bluesmirf is found by the dongle and they connect on COM4. When I load the lynxterm program and select COM4 for configuration, my computer bluescreens. If I configure COM4 then turn on the bluesmirf and connection is made it won’t crash until I try to enter “ver” in the lynxterm window.
I’m running XP sp2 and the system has never crashed before. Any suggestions? Thanks much.
UPDATE I’ve been able to connect to the SSC32 via HyperTerminal without the computer bluescreening, so that would leave me to believe the problem is something in lynxterm?
Try another terminal program (sorry). It seems that some terminal program crash with the bluetooth Roving Networks (Broadcom) driver. After a while, they’ll probably upgrade the driver, and all will be well. Check which driver you got, and dowload the latest.
First, thank you for the quick reply!! I assume you’re talking about the Broadcom driver? I tried to download it by running their bluetooth program and is errored saying there was a problem with the bluetooth security…go figure.
I would really appreciate some guidance on fixing the problem that causes my computer to bluescreen. It’s been very frustrating as when I try something in hopes of success, my computer crashes again…I have to reboot and then try again…
Both powerpod and lynxterm causes the crash when I try to connect to the bluetooth COM port. It was suggested that I need to upgrade the bluetooth driver, but it wasn’t clear on that. Please, someone take a moment and help me.
A blue screen on your PC can not be caused directly by any standard application like a terminal program. If there was a fault in one of those, it would simply kill that program. Since your machine is faulting, it is most likely caused by the device driver. Note: It is very possible that some programs may cause the driver to fault and others may not as they may not all use the same features of the driver in the same way…
So I would also suggest that you make sure that the driver installed is the correct one for the your dongle and that you are running their current version, that is intended for Windows XP.
I was sure I just replied to this, but here it is again.
Not really any “fix” until the Broadcom drivers get better. Try “T2” terminal program. You can set up strings to send. I’m able to use it with my bluetooth setup.
You’ve already mentioned Hyperterm, which will work, but no scripts (test strings in response to function key presses).
You can send com strings. You said bluetooth with Send_CP_H3 (Powerpod)fails also? Try “T2”. You’ll have F1 - F12 buttons to push instead.
Make up strings as I have posted before to simulate the joystick and buttons on the PS2 joystick controller. “28 FF FF 80 A8 80 80 0D” for example is a joystick X command. “20 DF FF 80 80 80 80 0D” is a right button. These bits are all documented. Search for PS2 controller. I believe I also posted a list that I was playing with.
The Send_CP_H3 expects a reply from the 'bot. You probably don’t want that with the terminal emulator setup.
Are you the person also using an IBM T60 notebook? My IBM desk machine was OK with Docklight (my preferred terminal emulator), maybe Send_CP_H3 will be OK. Point is, try a different computer.
Hopes are that the drivers will get fixed up. Also, I didn’t try it then, but my T60 has internal bluetooth, which I didn’t figure out (you have to turn it on along with the RF stuff) until after I got the dongle working. Maybe it will do better. I’ll probably un-install the dongle stuff, and tryout the internal blue tooth later.
