Serialio.com BlueSnap AAA V 4.30SIO 3/17/2009 page 8
COMMON PROBLEMS and QUESTIONS:
My Bluetooth client can see the BlueSnap Standard and its serial service, but I can’t connect:
This is most likely
caused by a security setting on your client. If a pin code is required,
the default is “1234”
. Some clients have these settings
off by default, others have them on. To check and disable security: From
your PC desktop, click My Bluetooth Places, go to
the Bluetooth Device configuration (or Advanced Configuration) drop down menu, click on the client applications tab, Select
the Bluetooth serial port application name, and click on the properties button, if “secure connection”, or “authentication”, or
“encryption” is checked, un check it.
Changing the clients COM port
: Widcomm stack, (and others) allows you to connect to BlueSnap Standard using a “Virtual
COM” port mapper. The software installs with a default COM port, usually COM3, COM4, or COM5. To change this setting:
From
your PC desktop, click My Bluetooth Places, go to the Bluetooth Device configuration (or Advanced Configuration) drop
down menu, click on the client applications tab, Select the Bluetooth serial port application name, and click on the properties
button, then you can change the com port.
Connecting to more than one BlueSnap Standard from the same client at the same time:
Bluetooth allows 7 devices at
a time in a piconet. Widcomm stack allows you to create multiple instances of serial port profile and connect to multiple
BlueSnap Standards at the same time. To do this: From
your PC desktop, click My Bluetooth Places, goto the Bluetooth
Device configuration (or Advanced Configuration) drop down menu, click on the client applications tab, Select the Bluetooth
serial port application name, and click on the ADD COM port button, then you can add another Bluetooth serial port and assign
it to another virtual com port (such as COM9).
Connections can be made but during data transfer, no characters flow, or bytes are dropped.
Check to see if your flow
control signals are properly connected, and enabled in the serial software you are using. A common mistake is to connect
during the boot config timer window, in this case, all characters will be ignored until a $$$ is seen, and no characters are
forwarded to the remote device. If remote configuration is enabled, a good way to ensure that the device is not waiting for
configuration is to issue “---“<cr> at the beginning of a connection and before any user data is sent.
Another common problem is related to hardware flow control, it is not enough to simply disable flow control in your
communications software, the BlueSnap Standard expects to use hardware flow control, so do disable this on the BlueSnap
Standard you must either remove the CTS flow control jumper, or short pins 7 and 8 (RTS, CTS) of your cable to permanently
enable the flow control.
