On 04/24/14 01:06, James wrote: > William Kenworthy <billk <at> iinet.net.au> writes: > > >> The bluez-5 stack is causing me some problems. >> What am I missing/misunderstanding? > > These wireless protocols, have many versions (variants) and > nuances via the prticular hardware that is used. Some light > reading might better postion you? > > > https://www.usenix.org/legacy/event/woot07/tech/full_papers/ > spill/spill_html/index.html > > http://www.ti.com/tool/packet-sniffer > > net-wireless/bluez-hcidump (never tried this one) > > > I would think that there should be some open-source Bluetooth packet > sniffers that may help diagnose the problem. > > I was able to find : > > MAC Address Prefix Manufacturer > 001103 kawamura electric inc. > > > using the MAC address. Perhaps an email to their tech support > descriping your problems might help? > > I suggest you dissect the packets and hardware and look for the issue > to your problem. Can you move the BT device to a winblozs box and > see if it works? Amplifiers die all the time, particularly if they > are overheated or fed noisy power...... > > could be hardware or software related..... dissect the pieces, > > HTH, > good_hunting! > James > >
I was able to get it working manually - gentoo's init scripts are out of date with bluez 5, blutoothctl is broken (or probably just poorly documented which equates to the same thing if the command doesn't work) . In bluetoothctl: power on scan on agent on default-agent pair <dev_id> trust <dev_id> exit In a shell: rfcomm bind rfcomm0 <dev_id> do serial port stuff with /dev/rfcomm0 rfcomm unbind rfcomm0 bluetoothctl connect command does not work - connects and immediately disconnects with an error gentoo's rfcomm initscript has removed the -f flag which bluez 5 does not have, but it also looks like the bind all in the 5.17 ebuild is also not supported by late bluez5 so it immediately exits and no rfcomm device is created. Ive adapted my python script to the changes now - but the pairing does not survive restarting bluetooth so I'll need an expect script to set it up each bluetooth re-init as it looks like there are no scripting hooks in bluetoothctl. BillK
