Bluetooth COM Port

I have a bluetooth device that communicates over a virtual COM port.  I can discover the device and it's services, but can't seem to initiate the COM port.
Has anyone used the Bluetooth VI's to set up a virtual COM port?

Currently we do not support setting up virtual com ports through
bluetooth. At this piont our driver software makes too many checks with
the hardware it's communicating with, and this causes some problems
with trying to do a virtual com port through bluetooth. Is there any
reason you want to use a virtual com port and not just use the
bluetooth VIs to communicate with the instrument?
-Matt S.
LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.

Similar Messages

  • No Bluetooth COM port with Version 6.5.1.4500 (T530, Win7 64bit)

    Hi all,
    after installing the current bluetooth drivers for the T530 (I'm not sure which drivers were installed before - I think standard Windows 7 drivers), I have several nice additional bluetooth profiles supported, by the virtual Bluetooth COM port has disappeared .... und uninstall is not offered by the drivers' setup.exe.
    Does anyone have an idea how to get the COM port back?
    Thanks for help,
    Mark123

    Hi,
    I would like to know is there any update about the issue. If the issue is solved, will you please share the resolution here to help others in this forum who encounter similar issue.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Can I just have one Bluetooth COM port?

    Hi,
    I have just installed the Bluetooth stack and there are now lots of BT COM ports listed. They are over-riding COM ports I already had defined previously for other non-Bluetooth devices.
    Can I just add BT COM ports as and when needed?
    Regards,
    Jonny

    Before I installed the Toshiba Bluetooth stack (on Windows 2000), I already had other non-Bluetooth devices set up from COM1 to COM6.
    After I installed The Toshiba Bluetooth Stack, it created BT COM ports from COM1 to COM40.
    The COM ports it created from COM1 to COM6 are over-riding my non-Bluetooth COM ports, so that I can no longer use them.
    I had to uninstall the Toshiba Bluetooth stack before I could use them again.
    Why does the Toshiba Bluetooth Stack create all these COM ports? I don't want it to create any until I tell it which device(s) to connect to.
    Please can you help. Thanks.
    Regards,
    Jonny

  • Problem removing bluetooth stack / hidden devices / COM ports not released

    Hi
    Having problem completely removing Toshiba Bluetooth stack / hidden devices / com ports not released
    I uninstalled Toshiba BT s/w...
    But:
    1) Toshiba BT hidden devices still appear and I can not remove (get error)
    2) COM ports occupied by Toshiba BT not released (so they cannot be used by another BT stack) and still appear in registry
    ex: friendly name Toshiba BT Port (COM4) still in registry
    3) These unreleased com ports do NOT appear in device manager
    Thanks

    It seems that you still have some configurations which were not removed during the uninstallation.
    This means that the resources can not be release, because those are still necessary in case of a
    new installation of the stack.
    The first I would try is the following:
    - Install the latest Toshiba Bluetooth stack.
    - Uninstall it. Ensure that you answer all questions with "yes" ! This means also the one which asks if all configurations should be removed.
    - Reboot
    - Check again

  • Unable to create the bluetooth virtual COM port

    Hi all
    I install BS from Toshiba and it seems ok. Bt ir desn´t work. I see all the drivers installed, system devices, etc. No Toshiba BT ports can be seen. Local com ports only show modem port. Try to create a virtual port but get a message "unable to create a bluetooh virtual port" I have a satellite m100-145. Can anyone help on this ?
    thx

    Thx for your suport.
    I decide to reinstall windows and all software. Now it works.
    The error was due to the fact that if you have BS from Microsoft (called bluetooth monitor) and you install the BS from Toshiba after that, even if you remove the BS from MS, the BS from Tos is unable to create the virtual com ports (except modem).
    I try with the latest version of BS and the problem was not solved. So if there is a previous installation of BS fom MS the BS from Tos get the message of "unable to create the bluetooth virtual com port".
    Now i fixed reinstalling SO from beginning.

  • Bluetooth over serial com port

    I was wondering if I could somehow determine the COM port my bluetooth device is on. I have gotten as far as discovering my bluetooth device and extracting the correct address and device name using the Blueooth Discover VI, and I have been able to obtain the correct UUID number from the Bluetooth RFCOMM Service Discovery VI. Is there any way to obtain what com port it is on from what I have?

    CF_eee,
    Thank you for clarifying what you are trying to do.
    I have two suggestions for you. Each of them may be able to accomplish what you are trying to do.
    (1) Use the Windows Registry to look up information on connected hardware.
    On my computer, information about my Serial Port (COM1) is stored in the Windows Registry at HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\ACPI\PNP0501\1.
    Example keys are Class, ConfigFlags, DeviceDesc, Driver, FriendlyName, HardwareID, and Service (amongst others).
    You can access these registry values from LabVIEW using the Functions located at Connectivity > Windows Registry Access VIs. If you walk through the Enum or ACPI folders, you should be able to determine which Serial Port represents your Bluetooth device by parsing and matching against these keys.
    (2) Use the System Exec VI to call the devcon Command-line Utility from Microsoft
    The devcon utility can be downloaded here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q311272
    From the devcon download page: The DevCon utility is a command-line utility that acts as an alternative to Device Manager. Using DevCon, you can enable, disable, restart, update, remove, and query individual devices or groups of devices.
    The System Exec.vi can be found on the Functions palette at Connectivity > System Exec.vi
    You can find documentation on devcon at the download page (linked above).
    Jared A.
    Applications Engineer
    National Instruments

  • COM ports configuration

    I need to connect a PDA Fijitsu Siemens Pocket Loox to the PC using the Bluetooth. I have successfully installed software for the dongle on the PC side BUT there is a problem to connect PDA to the PC using Bluettoth Serial Port. PDA Bluetooth software (Pocket PlugFree) is ALLWAYS using COM5 but this port on the PC is not available because it's occupied by Bluetooth Fax Modem installed from the dongle installation package. If I disable the modem then COM5 is still not available (niether COM6 and COM7, which are also blocked for Bluetooth Modem and Bluetooth Null Modem and also can't be reconfigured). Please, don't you know how to reconfigure COM ports for the dongle?
    I use Windows XP on the PC.  Both devices can communicate to each other and files can be transfered with no problem.
    Leon

    Hi
    I had the same problem with my T61 and my HTC Touch Diamond, and found the help I needed here:  http://lopsa.org/node/788
    It did not work the first time, I had to do I a couple of times, but it finally worked out.
    Hope you get your problem solved.
    Best regards
    John Klit
    Message Edited by JohnKlit on 09-03-2008 06:24 AM

  • COM-port problem with MSI BToes USB Dongle

    I´ve had problem to get my Sony Ericsson T610 to work with my MSI BToes USB Dongle, so I tried to update my drivers. Now I have Microstar Bluetooth Software 1.4.2 build 10 but can´t get my Serial Port service to work. In Advanced configuration / Client Applications under "Bluetooth Serial Port" / "Properties", the only serial port I can choose is com0. Does anyone know how to fix this problem?
    /Peter

    Well, I think i´ve solved the problem. To get the com-ports to work I installed the software. Then I had a problem to get the phone to communicate with Sony Ericssons synk-software and outlook, but suddenly it worked and has worked since then. I have no idea what the problem was but now it works and I´m satisfied.
    /Peter

  • Write among COM ports in the same PC without cables

    How can I write to the memory address(es) of a serial COM port?  I would like to send data from one serial COM port to another in a manner similar to the that of the 'Simple Data Client' and 'Simple Data Server' vi examples.  This must sound strange since this is exactly what a null modem cable will do, externally.  I would like to eliminate the cable connection between COM ports that exsit in the same PC and communicate between them, internal to the PC, somehow. 
    Currently, I am using a LabVIEW vi to read a serial message on COM1, translate it, send the trsanslation out on COM2, so that a separate windows program (no .DLLs to interface with LabVIEW) can read the message on COM 3.  COM 2 and COM 3 are connected by a null-modem cable.  This requires three COM ports, and two serial cables.  I realize that I can use a physical loop-back jumper on COM2, for instance, where I send and read the translated message on COM2, but I still wonder if there is a method for doing this in memory, or something. Is there a way to accomplish the same objective with one cable (into COM1), no loop-back jumpers, and only two serial ports?  In summary, I want to read on COM 1, translate in LabVIEW, then write directly to another COM port, internally, without using a serial cable.  Can the 'IN PORT' or 'OUT PORT' vi's apply here?  Are these tools only for parallel ports?
    Hope this is not too confusing....  It seems like I am always trying to do something with LabVIEW that was not meant to be done....
    Thanks.

    Thank you.  If I pay the price they ask, this looks like it will create and share virtual COM ports - exactly what I need.  However, I would really like to find a way to do this in LabVIEW, such that I do not have to make my application dependent on another piece of third party software.  The 'Simple Data Client.vi' and 'Simple Data Server.vi', included in the shipset examples, seem to do this for TCP/ IP ports.  I wonder why the COM ports cannot be addressed at the memory level, in a similar manner???

  • Can two users share a COM port?

    I have a system services Labview executable that opens a VISA session on a COM port.
    But I also have a User Interface VI that needs to communicate with the device on same COM port.
    Is this possible?  Can I use a Shared Variable to keep the VISA Resource name and have multiple users (one at a time) communicate with the device?

    LabVIEW semaphores and all other LabVIEW objects like queues, notifiers, events, etc are not only process local objects only but even application context local only. While this makes no difference for built applications it is important inside the development environment as each LabVIEW project lives in its own application context (and tools started from the Tools menu run in yet another context). To do what you want to do, you need to implement some form of interapplication communication as Mark already mentioned. Or you can access named OS semaphores by calling OS APIs.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • How can I write to multiple daisy-chained network serial addresses through a single COM port?

    I have a VI to write to 3 PI Mercury motor controllers using daisy chained RS232 connected via a Prolific USB-to-Serial adapter. I know that it is possible to talk to the individual controllers because the PI terminal that I have recognises the addresses of multiple controllers and designates them Device 1,2,3. The VISA resource name when configuring the port just comes up as COM5 most of time, with seemingly no way to specify an address on that COM port. Occasionally the VISA resource is ASRL5::INSTR and as this is disconnected and re-connected, this address moves up a number (e.g ASRL7::INSTR). Can anybody tell me how I can configure my serial communication to allow me to individually communicate with the different devices through a single COM port?

    What does the manual say about addressing? RS-232 is not multidrop, the resource name is correct, and there is no additional configuration needed. There would have be a specific write in order to address a certain controller.

  • How to use shared variables to address multiple Watlow controller​s on the same COM port

    Hello,
    I am trying to use LabVIEW 2010 to control 4 Watlow temperature controllers on one COM port. 3 are Model 96 and 1 is an EZ zone controller. Each controller has a unique modbus address, and I am trying to read from and write to individual registers (such as closed loop setpoint) using shared variables. I am getting return data when reading (although the data appears to be invalid), but am unable to change the value in the register by writing. How can I be sure that the Modbus server is sending commands to the correct controller?
    Chuck
    Solved!
    Go to Solution.

    Peter,
    Thanks for the reply. I have actually solved that problem. I realized that the Modbus server address has to be the same as the controller's Modbus address.
    I have, however, run into another problem. Perhaps you could help me with that. I have a system with 4 Watlow controllers, 3 are series 96 controllers, one is PID only and 2 are ramping. The 4th controller is an EZ zone. I am using RS485 for communications and the controllers are all wired in parallel for communications and power.
    I have set up 2 Modbus servers for 2 of the controllers.
    This is the first I have ever worked with Modbus based communications. I have successfully programmed using the Modbus read/write VIs, and am wanting to move to shared variables. My questions right now revolve around addressing, Modbus I/O servers and COM ports. Specifically, at this point, I know the addresses need to match up between the server and the slave device (Watlow controller in my case), how many servers can I create and use on one COM port? If the number is limited, is there a way I can specify an address that I want the server to talk to? Will the broadcast mode work to request data values from the controllers?
    I'd appreciate any information you can help me with, or if you could point me to some sort of concise 'How-To' for Modbus communication.
    Thanks.
    Chuck

  • GPS Error on F3507g & Windows 7 "The GPS NMEA COM Port is not available" x200

    I have an X200 with a WWAN Card 43R153 (Ericsson F3507g) running Window 7.
    The WWAN reliably connects to Vodafone but I can't get the GPS to work.
    Device manager shows this port Enabled:-
    Ericsson E3507G Mobile Broadband MiniCard GPS Port (Com8)
    Driver Invogps.sys from Ericsson AB, Version 1.0.0.28  29/09/2008.
    Thinkvantage GPS version 2.50 is also installed and Lenovo System Update says everything is up to date.
    When I "Turn on GPS" or run 'Lenovs GPS"  I get this message:-
    The GPS NMEA COM port is not available. You need to check the following things.
    - Another GPS application is using the COM port.
    - COM ports is disabled. You can enable the COM port in the Device Manager.
    Location and Other Sensors shows nothing installed.
    I've tried deleting all the drivers and reinstalling but not luck.
    Has anyone else had the same problem and found a solution. I can't think of anything else to try.
    ThinkPad X200 7459-1P0

    If you are running a Windows 7 Weather Gadget on your desktop, try shutting it down entirely and see if that changes your GPS "in use" problem.
    Cheers,
    Bill
    I don't work for Lenovo

  • HyperTerminal sees a COM port but VISA does not

    It should not be possible that HyperTerminal sees a COM port but VISA does not. Does anyone know why or have any ideas?
    Here's some more info: I wrote a LabView (LV) program and deployed it (via the Application Builder) to some of our production department's PCs (some Windows XP and some Windows 7). We use it to set up products we design and manufacture through our device's USB serial port. The USB port is actually a virtual COM port (VCP) - a USB to Serial converter or "bridge". We have a custom driver for our device and since each device's USB bridge chip is programmed with a different serial number, every time we connect a new device to the PC the installer runs and assigns a new COM port number. This is so our customers can use multiple devices on a PC. Fine. On one of our production PC's we were close to  COM900 ports (HyperTerminal sees only up to COM256) when suddenly Win7 would not allow any more. We were able to uninstall orphaned (non-present) COM ports from DeviceManager ("DM") by starting it from a command console (DOS window) with a special command-line switch, "set devmgr_show_nonpresent_devices=1" then "start devmgmt.msc" (I have this in a batch file). In DM View menu you can "Show hidden devices" and uninstall them as if they were connected. I've also tried uninstalling them the normal way when the device was actually connected. Either way, sometimes, not always, depending on the COM port number, after reusing that port number by installing a new device which picks up that old, freed-up number, LV VISA doesn't see it. In other words, when "Refresh" is clicked in the COM port VISA list box, any new devices installed should be and normally are seen. (Refresh is not needed if the application is started after the device's driver is installed. It is only need if the LV application is open with the new device is added.) However, HyperTerminal does see it and lists it in the Properties screen, the "Connect using..." list box. And the port works with HyperTerminal. (Of course we've tried rebooting after uninstalling and/or reinstalling the device, with the same results.)
    When I've spoken to the NI Applications Engineers in the past about serial port issues (not about this problem) they have confirmed that if HyperTerminal can see the port then NI VISA should also see it. This is crazy. I am posting this in hope that someone can shed some light on this problem.
    Thank you. -Ed

    Good catch. Yes, we're using the Silicon Labs CP2102 and have created a "custom driver" installation package. Our new PCBs have a factory-programmed chip, so the PC reuses that COM port (COM3 on that PC). The problem is when we we re-program the CP2102 (setIDs exe) with our PID, and device strings (including the S/N), the PC runs our installer and assigns the next COM port number. I was hoping that maybe it would go up to 64K or something! Anyway, it surpassed COM256 but we ran into this problem when almost up to COM900.)
    There is a registry entry for each SN device, which shows the assigned port. If we delete the key with regedit, the COM port database (don't know the file name) still has the port number. That's where Device Manager comes in. It seems to allow us to manually delete the ports, but it would take quite a while to delete 900. (I was trying to make a batch file for DevCon, but couldn't get it to see the HW ID of the devices in need of deletion.) So we tried manually deleting a few. After doing that Device Manager shows that Windows (and HyperTerminal) can reuse the port number when a new device (new SN) is installed, but, as you know from this post, VISA cannot see unless I manually add it in MAX.
    I can't see how it has anything to do with the Silicon Labs driver. I might have to delete ALL of MY devices, then uninstall the driver files, reboot, then reinstall, as you suggested with the SiLabs driver. However, I don't see how VISA will now see these changes. VISA must have it's own database. That's what I thought deleting the ports in MAX would clear out, like a fresh install, but apparently not.
    I've been through Silicon Labs' tech support on other issues and they've been able to help on some. I could run this by them.
    BTW, have you noticed that Silicon Labs' chip and driver, while faster than NI's own "bridge" or serial-USB converter (I returned it because at $100 it's performance was worse than a $20 converter you can buy in Staples), is substantially slower than a real serial port? For example, our device can transmit 250 readings per second (a 12 byte string). A real serial port used with my LabView program can keep up, i.e.., graph & tabulate at that rate, but with a VCP we only get about 70 RPS. Same code. Can't figure this one out. They say the've tested the driver to 900 KB claimed. We're using 115KB here. Anyway, the VCP driver makes it look like a COM port which LV thinks it is. Why is it slower than a real port when the USB should be able to work almost 10 times faster than I'm using it (up to 1024 bytes per mSec per the full-speed USB spec, which SiLabs claims they verified)?
    Anyway, I appreciate your help. Thanks! -Ed

  • Exception while accessing com port from servlet

    I am trying to access communication port from a Servlet using java communications api's.
    But Following exception was thrown
    Caught java.lang.NullPointerException:name can't be null while loading driver com.sun.comm.Win32Driver
    The SecurityManager do not allow that opeartion.
    java.security AccessControlException:access denied (java.io.FilePermission c:\j2sdk1.4.1\jre\lib\javax.comm.properties delete)
    at java.security.AccessControlContext.java:270) at java.security.AccessController.checkPermission(SecurityManager.java)
    at java.lang.SecurityManager.checkDelete()
    at java.comm.CommPortIdentifier.getPortIdentifiers(CommportIdentifier.java)
    Please help me.Tell me what to do.how to successfully access a communication port from a Servlet.

    Hi there. I am also facing the problem accessing com port via servlet. if u have the solution, kindly forward to me at [email protected]
    many thanks

Maybe you are looking for