[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Bluetooth Q?



Greetings;

Where can I find a tut to tell me how to make this device:

[root coyote bluetooth]# lsusb -v
Bus 002 Device 005: ID 0e5e:6622  
Device Descriptor:                
  bLength                18       
  bDescriptorType         1       
  bcdUSB               1.10       
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth      
  bMaxPacketSize0        16                
  idVendor           0x0e5e                
  idProduct          0x6622                
  bcdDevice            1.34                
  iManufacturer           0                
  iProduct                0                
  iSerial                 0               
[...]

[root coyote bluetooth]# dmesg |grep Bluetooth
[    8.987403] Bluetooth: Core ver 2.14
[    8.987489] Bluetooth: HCI device and connection manager initialized
[    8.987492] Bluetooth: HCI socket layer initialized
[    9.114808] Bluetooth: Generic Bluetooth USB driver ver 0.4
[   21.093799] Bluetooth: L2CAP ver 2.11
[   21.093801] Bluetooth: L2CAP socket layer initialized
[   21.235952] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   21.235954] Bluetooth: BNEP filters: protocol multicast
[   21.315216] Bluetooth: SCO (Voice Link) ver 0.6
[   21.315219] Bluetooth: SCO socket layer initialized
[   22.169676] Bluetooth: RFCOMM socket layer initialized
[   22.169685] Bluetooth: RFCOMM TTY layer initialized
[   22.169687] Bluetooth: RFCOMM ver 1.10

[root coyote bluetooth]# hciconfig
hci0:   Type: USB
        BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
        UP RUNNING PSCAN ISCAN
        RX bytes:1104 acl:0 sco:0 events:45 errors:0
        TX bytes:445 acl:0 sco:0 commands:45 errors:0

[root coyote bluetooth]# lsmod |grep rfcomm
rfcomm                 35580  4
l2cap                  21260  16 rfcomm,bnep
bluetooth              52196  11 rfcomm,sco,bnep,l2cap,btusb

The modules are loaded obviously, but no /dev/hciN devices are created.

How can I turn this usb dongle into a 9600 baud rs-232 look/work alike?

I have acquired an rs-232 comm device that had an eb101 bt module instead of a 
db25 serial port for a legacy computer and intend to replace the cable with 
the bt circuit.  I can now communicate with this old computer using minicom 
over a serial cable, so I know the idea works, but the cable exposes both 
machines to the EMP of a nearby lightening strike, something the BT connection 
will isolate then from.

I just fired up the eb101 device on the legacy machine, but this dongle, 
despite both being called class 1 devices, and about 25 feet between them, has 
made no new entries in dmesg since I powered up the other one.  I would like 
to think the device discovery would apply but apparently not.

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Ambition, n:
	An overmastering desire to be vilified by enemies while
	living and made ridiculous by friends when dead.
		-- Ambrose Bierce



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]