I have to get access to Bluetooth on a remote machine.
Here's how things are connected.
External Bluetooth Adapter connected to the client running the Remote desktop application.
The Remote Desktop should identify the device connected to the client since its connected to the USB port, but I am not able to access the Bluetooth stack on the remote desktop.
I just need to get the list of Bluetooth devices which is present near the client to appear on the server. Is it possible to do that ?
The KC-4132 is an embedded Class 1 Bluetooth USB Serial Adapter. This adapter enumerates using FTDI USB-UART bridge chip, so you get a virtual COM port. After sending the kcSerial command "AT Discovery" via COM port to the adapter, it will respond with a listing of all Bluetooth devices currently in range and discoverable. No messy Bluetooth stacks or drivers to interface with since the Bluetooth device is an embedded serial port adapter with its own command language.
Related
I am writing a Serial Port class in C++.
To test this:
I want to hook up a USB to SerialPort(RS-232) converter on one USB.
Connect a NULL modem cable from that SerialPort(RS-232) to Serial to USB convert to another USB on the same computer.
Yes I was able to hook up 2 (USB to RS-232 converts) to the same computer and connection between them was established via NULL modem cable.
Then I had to look in the DeviceManager ports to see what com ports I can use.
Ran a 2 instances of the program(client, server) communication worked well.
I'm designing a system that has a linux machine communicating serially with a microcontroller over a USB to RS-485 interface. I'd like to do this in Go if possible.
How can I programmatically send data over the linux machine's USB port?
I have a linux platform* that is connected as a usb device to an automotive device which acts as the USB host. The two devices should communicate over CDC/NCM, but the linux platform is not recognised by the automotive device and therefore the connection is not established. Surprisingly a connection to my computer is established correctly.
I now need to create a trace of that USB connection in order to check if there is an error in the USB handshake that can't be handled by the automotive device. As I cannot access the USB host, I need to create the trace from the gadget side.
I tried using usbmon and tcpdump, but this seems to work only for USB controllers configured as hosts on the tracing platform, not for ones configured as devices.
How can I configure usbmon to work also on devices?
If that is not possible are there any other possibilities to achieve this? (preferrably without hacking any drivers...)
Or do I have to use a Hardware USB sniffer?
BTW, all required modules (esp. g_ncm) are correctly loaded.
Thank you for your help!
stefan
*custom distribution on a freescale iMX6 processor (ARM), Kernel Version 3.0.35
I'm using node-serialport to work with USB devices, however on Windows I can't find out how can I connect to specific device. When I use list function there is only one item with COM3 address, however that is present always, even when no other devices are connected. How can I find out what is the USB device address that can be used for setting up communication?
I have been asked to figure out how to achieve bluetooth communication through an off-the-shelf dongle (in this case a dongle utilizing the Broadcom BCM2045 chip) using the FTDI Vinculum 2 (VNC2) USB controller. I have custom firmware written for the VNC2 to communicate with a generic USB device with the VNC2 acting as the host, and I can successfully read the VID and PID from the dongle as well as the USB device class, subclass, and protocol. I can also send data to the dongle using the bulk data endpoint and I believe the device is receiving though I have no way to tell at the moment.
So I believe I can communicate with the dongle, the problem is I have no idea WHAT to communicate to it in order to set it up in discoverable mode or to pair it with another discoverable device, nor how to actually transmit data through the wireless link once it is paired. I don't even know if there exists a standard communication protocol for this type of thing or if every device will be different. I have a vague understanding of the bluetooth protocol stack and it is my understanding that I won't be required to fully understand that as it should be implemented in the dongle on one end and in the android smartphone that we hope to connect to on the other end. Like I said, I can currently send data to the bulk endpoint, is it true that this endpoint is only for data transfer over the wireless link and I will need to connect to a different endpoint in order to send setup/configuration messages to the dongle?
In short, I need to know what data to send over the USB bus to control any generic bluetooth dongle if possible or at least one specific bluetooth dongle. I have a USB port sniffer but the complexity of the output while using the dongle to communicate is staggering and I doubt I'll ever figure it out.
Thank you in advance.
Bluetooth dongles communicate with host software stack using HCI (host control interface), which is defined in the Bluetooth spec. For reference, you can look at source code for the open source BlueZ stack (standard linux stack). You could run BlueZ on linux talking to your USB dongle, and use hcidump to capture actual packets going across HCI. You can also check out hcitool and hciconfig for performing specific actions.