I have an application running RxTxCOMM on Windows 10 64 bit with Java 8.
This app uses USB serial port adapters, because the newer PCS do not have enough serial ports. I updated Java 8 to Java 10 and the RxTxCOMM does not work.
On Java 10. when there are no USB adapters plugged in, the app works and successfully gets the
serial port not found errors
but it immediately crashes when I plug in an USB Serial Adapter.
Related
I am trying to connect My laptop windows 7 64 bit to any android device or Bluetooth headphone its not find device.BT driver is updated.in Bluetooth discovery setting i tick and apply but not save it is hanging out.
I've created a WDK library for interacting with a Bluetooth LE device (closly following the example here). The library worked well on a previous version of Windows - I was able to connect to my device, write characteristics and get asynchronous notifications. Once I updated to Windows to version 1709 (build 16299.98), the library stopped working:
pair the device via Settings-->Devices-->Bluetooth
the BLE device blinks a led as an indication of Advertising
Run my application which uses aforesaid library
Once the application opens the paired device's handle (using hDevice = CreateFile(pInterfaceDetailData->DevicePath, GENERIC_WRITE | GENERIC_READ, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL);), the device blinks spasmodically, indicating that it connects and disconnects very fast.
Sometimes, after several long seconds, the device has solid light, indicating it is connected (the status in Windows Settings is also 'Connected')
Any access to the device from my code (e.g. by calling BluetoothGATTSetDescriptorValue() to enable BLE notification), fails with a timeout (ERROR_SEM_TIMEOUT))
For some reason, first-time pairing with the device does not exhibit these symptoms.
Any ideas?
If its relevant, my local Bluetooth device is Qualcom Atheros USB module (VID_0489&PID_E076&REV_0001).
This was an issue with Windows 10, resolved in KB4054517
I am intending to connect a device 1 (in master mode, Bluetooth Ver 2.1) to a device 2 (in slave mode with Win CE 7 OS, Microsoft Bluetooth Ver 2.1).
Here I need the connection to happen without any user interaction and automatically accept the pairing on device 2 running WIN CE 7 OS.
On similar device 2 if running Windows 7 OS, this can be achieved by handling in BluetoothWin32Authentication callback function by "e.Confirm" of 32feet InTheHand.Net.Personal.dll API.
Could someone help in navigating to correct set of API's (if exists) to enable similar automatic pair accept behavior for Win CE 7 OS.
Will be very grateful for the guidance.
Thank you.
I have an Asus USB-BT400 Bluetooth Dongle, it works with BLE devices. I also have an TI Sensortag, i installed the drivers and software and I can connect my PC to the sensortag (using windows 7 or windows 8.1 in VM, both works).
Windows doesn't find drivers for the sensors (I think 8 in total) so I would like to know how I can communicate to them. I already exposed a COM port for the bluetooth device (that's possible via Bluetooth settings). I tried the BLE device monitor, where the COM port shows up, but it gives an error (no response from BLE host at port COM3). I also tried the windows Desktop app (win8), which doesn't work either.
I would be glad for any solutions, resources and hints which do not require me to buy the Dongle from TI website for ~50$.
Thank you!
I don't believe it works under anything less than Win 8.1 as the OS must have the BLE Profile drivers.
Running VM is not going to help, as you need those drivers at the base OS level.
Problem Iam facing closely related to the an old thread here:
SerialPort.Open() freezes the system if data was received previously (Compact Framework)
Windows embedded CE 6.0 running on a x86 based SBC having 4 serial ports based on 16550 UART(part of the x86 SoC itself).
Connect a field device to a serial port that transmits at regular periods.
Open this serial port in a native app and keep reading data from the connected device.
The native app uses the standard Win CE serial Communication API(CreateFile(), SetCommState(), ReadFile() etc.
Close this serial port. But serial data is still getting into the Windows CE system.
After some time try to open this serial port again. The whole Windows CE system HANGS.
After debugging the Windows CE kernel the hangup seems to be happening because of an infinite loop created in the Serial PDD driver after the port re-open. Still debugging...
Anyone has come across this problem already?
P.S> The same hang problem happens even if .Net CF SerialPort class is used & the same steps are followed(using a C# SmartDevice Console type app built in VS2008).