12-06-2012 06:23 AM
Hi everyone,
I have a problem with some LV code that connects to a BT product (that we manufacture). Intermittently the connection does not close correctly, this leaves the product in a connected state and my code cannot reconnect to it.
As soon as I stop the vi, the connection is released and the connection LED on our product extinguishes.
I was under the impression that the BT Close function should still execute even if an error has occurred (so the connection should always be closed when it is called).
The code was originally written in LV 8.6 but has recently been recompiled to LV2012 and I still see the problem.
Is there anyway to read the connection ID that is currently being used by the system and somehow force it to close? Has anyone else ever observed anything similar?
Thanks in advance.
12-06-2012 12:04 PM - edited 12-06-2012 12:04 PM
The Close VI's do not execute if there's an error.
I usually wire "clear errors" into the VI then merge errors ... like this:

12-07-2012 02:23 AM
I think it still runs (see below)
12-13-2012 04:13 AM
Hi SSK,
Have you had any success with this problem?
I believe that the message from SnowMule would be an acceptable form of error handling and will ensure that no error goes though the close Bluetooth connection.