Just got my Brat setup … Everything is working fine with a serial DB9 connection … However I also got a BlueSmirf and BT dongle from Spark (same as in the Brat tutorial used the links in the tutorial to order) … I setup the software and dongle as instructed … My laptop makes a serial connection between the dongle and the Smirf …
However as soon as I try to connect to the Brat from either Lynxterm or SEQ … My laptop Bluescreens … I am running XP (fully patched) and I followed all the tutorial as far as the setup for the port in the apps (Lynxterm) … I can get through the setup in the apps (tell it to use Com10 and other settings) and as soon as I click connect … I see the dongle and Smirf LEDs flash and my machine bluescreens
Yes … ordered and got the same parts as Jim’s instructions …
Smirf is the one with rubber duck ant (WRL-00158) … and USB dongle looks like the black one in Jim’s Tutorial (I ordered from Sparks using Jim’s links in his tutorial)
When I make a serial connection to it throught BT software it shows connected and if I run Hyperterm the dongle connects to the smirf card and the LEDs green … but the Lynx apps BSOD my laptop when connecting.
When you plug in the dongle, go into device manager and see what virtual com port it has been assigned and make sure it is the port you are using. Also check the propertys to see if the it appears to be working.
In case anyone else w/ similar problem stumbles across this thread…
I’m also just starting to use a BlueSMIRF for wireless serial Bluetooth to an SSC and was getting a blue screen (BSOD, IRQL_NOT_LESS_OR_EQUAL). This happened immediately every time either LynxTerm or the Lynxmotion Visual Sequencer tried to send data.
In my case, I was using my laptop’s built-in Bluetooth transceiver. I have a Dell XPS 1710. The Bluetooth hardware is labeled Dell Bluetooth 355, but is based on a Broadcomm chipset. A BSOD like this is almost always going to be a driver issue. I was already running latest for my laptop model per Dell. The newer OEM Broadcomm drivers wouldn’t install. I took a chance, and installed slightly newer drivers from Dell for the Dell Bluetooth 355 that were listed on the XPS 1730 laptop. That worked. Most of this paragraph is only of interest if you’re using a Dell laptop like me. The summary is find newer drivers if you get BSOD.
However, one thing of interest specific to Lynxmotion maybe: I noticed before updating the drivers that I could send commands via Hyperterminal with no problems. It was only when I tried using Lynxterm or the Visual Sequencer that the BSOD occurred. I didn’t think to try my custom programs before updating the driver, but it does seem possible that the underlying libraries or COM port setup procedures being used by the Lynxmotion programs triggered the driver bug somehow.
… They have agreed to allow me to RMA the item … so all is good 