FabulaTech Forum Newbie
Re: Interference with Bluetooth
« Reply #2 on: Nov 21st, 2007, 2:38am »
In reply to your post I have been extensively testing, and in short I have found what causes the problem and how to work around it, so I can now move ahead with VSPK. Great! Thanks for the reply.
Details of what I found:
I reflashed the OS and tested the BT behaviour with VSPK and this is what I saw:
-To start with, Bluetooth can be enabled and disabled OK. I reset and rebooted and it is still ok.
-With Bluetooth enabled, I installed VSPK. Bluetooth can still be enabled and disabled.
-I rebooted/reset. Bluetooth can still be enabled and disabled ok.
-I started the VSPK U/I app, but didn't create any port pairs. BT still ok, including after reboot.
-I started the U/I app and created the pair 'Com4'/'Com5'. BT is OK.
-I deleted the pair com4/5 and BT is ok. Rebooted - still ok.
-I created the pair 2/3 and BT was ok. I deleted 2/3 and BT was ok. I reset and BT had died (couldn't be started).
I then reflashed the OS and repeated the above, except this time I created 2/3 but didn't delete it before rebooting. Before the reboot, BT was ok. After reboot, BT is dead.
Once BT has died, no amount of deleting pairs, rebooting, or uninstalling VSPK will recover it, until I reflash the OS.
I am wondering (even though the U/I only shows 1 com port: 'COM1') if there is actually a second serial port used by the OS for communicating with the BT chipset, and perhaps establishing a virtual port on COM2 or COM3 interferes with this invisible port, and deleting pairs and/or uninstalling VSPK does not restore the settings?
Anyway, so long as I only use COM4/5 it seems I'm all right, so I will strenuously recommend these settings in any associated documentation (and will mention the consequences). This means at least that we have a workable solution using VPSK and so can forge ahead with our plans.
Again, many thanks. VPSK looks like a great piece of work.