February 2005 - Bluetooth-dev

Problems with multiple incoming serial connections
by Tico Ballagas 25 Feb '05

25 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hello- Has anyone else run into this problem? Any suggestions? Thanks -Tico _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… I need to support multiple incoming serial (RS-232) connections for an application that I'm developing. To set up my environment, I've created two different incoming serial ports using the Bluetooth Serial Utility. I've found that once I successfully connect and transfer data through one serial port, I'm unable to use the other port. To be more explicit, here are the chain of events: 1) Launch an application that opens and waits for data on /dev/tty.BTSerialPort1 2) Use a bluetooth enabled mobile phone to connect and send data 3) Close connection (bluetooth status in menu bar shows the device is no longer connected) 4) Launch an application that opens and waits for data on /dev/tty.BTSerialPort2 5) Use the same bluetooth enabled mobile phone to connect and try to send data This is where the problem occurs. I'm able to successfully connect to /dev/tty.BTSerialPort2 as indicated by both the mobile phone and the Menu Bar, but then a few seconds later the connection terminates for no apparent reason with no data transfered. After this point, I can still successfully transfer to /dev/tty.BTSerialPort1 without any problems. But I can never successfully transfer data on /dev/tty.BTSerialPort2. I have found that if I restart, sometimes I am able to transfer data to the BTSerialPort2 if I connect to it first. However, after that I'm unable to transfer to BTSerialPort1. This email sent to site_archiver(a)lists.apple.com

1 0

I want to subscribe
by 200009144 TEKLE HABTOM 20 Feb '05

20 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Rfcomm & nokia
by john jensen 15 Feb '05

15 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com User-agent: Microsoft-Entourage/11.1.0.040913 Hi, I have been trying to setup a simple rfcomm(SerialPortProfile) connection with my Nokia 6230, it works fine with a Samsung D500, but any other phone i tried refuses to connect, the phone just comes with a connection refused message???. My Samsung phone has a serialportprofile, Nokia however uses com1 any suggestions would be greatly appreciated... John Jensen _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: BNEP - Bluetooth kernel API
by Cyberspice 15 Feb '05

15 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com On 15 Feb 2005, at 00:05, Marco Pontil wrote: Melanie _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… You can still use ppp and create a LAN access point. This article explains how: http://www.macosxhints.com/article.php? story=20021103062212288&query=ppp Thanks for both the links, this one and the one in the other e-mail. This method should work if my PDA didn't insist on having a telephone number to dial. Also one of the things that I liked about the Mac was that no longer would I have to hack scripts and configuration files as I could do everything via the GUI. Having to write a script seems a retrograde step and no better than Linux. Finally I was seeing writing the driver as an intellectual exercise so I would still like to have a go at writing the driver. I've been to Apple's Darwin sources site and it doesn't list anything that appears to be Bluetooth. Does this mean the kernel level API is proprietary or does it just mean that no one thought about doing a standard API in the kernel for Bluetooth? This email sent to site_archiver(a)lists.apple.com

1 0

BNEP - Bluetooth kernel API
by Cyberspice 14 Feb '05

14 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hi everyone, Any help would be useful. Melanie _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… I've just joined the list. My query is this. As far as I can tell OS-X (even 10.3.8) doesn't BNEP, i.e. ethernet over bluetooth. This is disappointing as I use BNEP and my Linux PC to extend our house LAN to my PDA. I am now using a Mac as my every day workhorse and would like to do the same with that [1]. I.e. extend the LAN to my PDA via it. Wifi is not a viable alternative. I am an experienced embedded and Linux developer so I thought that if it's not supported I'll write the support so I've been researching bluetooth and network drivers on OS X. From what I can see all the bluetooth APIs are user domain and network drivers are written in the kernel domain. This is a bit of a problem as basically what is needed is a network controller driver that uses bluetooth for data transfer. Diagrams in Apple's documentation show that Apple themselves support both DUN and serial via bluetooth in the kernel. Also the L2CAP layer, the one I need to use, is actually implemented in the kernel but is supported by user land APIs. So where do I find the kernel land APIs? Or is Apple inconsistent between OS X versions and the only guaranteed ones are in user land. In which case how do I do this? I'm reluctant to have a kernel driver that uses a user land daemon to communicate with the bluetooth stack. [1] Yes I'm a switcher. Well kind of. I used Macs for several years professionally and then programmed them during my research at University but have never owned one. OS X finally won me over. This email sent to site_archiver(a)lists.apple.com

1 0

Re: L2CAP Maximum MTU / 0-Length packets
by Moritz Gmelin 14 Feb '05

14 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Any help from Apple would be appreciated. Regards Moritz Am 13.02.2005 um 21:49 schrieb Moritz Gmelin: Hi, Next question is about 0-length packets: Can anyone help on those two problems ? Regards Moritz This email sent to moritz.gmelin(a)gmx.de _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… Having PacketDecoder up and running again, I can confirm that both problems are related to the Mac side. 1. Packets larger than about 16000 bytes are being dropped although PacketDecoder displays them as correctly received. The l2capChannelData method of my Listener is simply not called for those large packets. 2. Writing 0-Lenght Packets is doing anything. PacketDecoder does not see any outbound packets. 1+ Byte-Packets are working correctly. When I try to open a L2CAP Connection from Linux to my Mac, the Mac offers a MTU (direction Linux -> Mac) of 32767. Sending data of size < 16000 is no problem, the receiver gets notified of incoming packets. But when the packet size exceeds 16000 (I don't know the exact number) my Application does not get notified of incoming packets. I can see the packets being sent by the linux side using hcidump. I cannot verify what is happening on the mac side since packet decoder does not work.... The Bluetooth specification allows for L2CAP Packets to be between 0 and 65535 bytes in length. When I send a 0-length packet from the Mac, I cannot see anyting coming in either on Windows (Widcomm Spylite Software) or on Linux (hcidump). Again, I cannot verify what PacketDecoder would see. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/ moritz.gmelin%40gmx.de This email sent to site_archiver(a)lists.apple.com

1 0

Re: 10.3.8 -> PacketDecoder2 dead
by Moritz Gmelin 14 Feb '05

14 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com When will we get an updated SDK ? Thanks. M. Am 13.02.2005 um 00:15 schrieb Alexander Traud: after installing the 10.3.8 update, my PacketDecoder has gone dead What is it that I need to install again? The Apple Bluetooth SDK 1.5.3 but this is *not* online yet: https://developer.apple.com/sdk/#Bluetooth Apple has updated the IOBluetooth package to 1.5.3 in Mac OS X v10.3.8. This email sent to moritz.gmelin(a)gmx.de _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… Installing Bluetooth 1.5.1. from 10.3.6 and re-installing Bluetooth-SDK 1.5.1 helped me out for the moment. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/ moritz.gmelin%40gmx.de This email sent to site_archiver(a)lists.apple.com

1 0

L2CAP Maximum MTU / 0-Length packets
by Moritz Gmelin 13 Feb '05

13 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hi, Next question is about 0-length packets: Can anyone help on those two problems ? Regards Moritz _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… When I try to open a L2CAP Connection from Linux to my Mac, the Mac offers a MTU (direction Linux -> Mac) of 32767. Sending data of size < 16000 is no problem, the receiver gets notified of incoming packets. But when the packet size exceeds 16000 (I don't know the exact number) my Application does not get notified of incoming packets. I can see the packets being sent by the linux side using hcidump. I cannot verify what is happening on the mac side since packet decoder does not work.... The Bluetooth specification allows for L2CAP Packets to be between 0 and 65535 bytes in length. When I send a 0-length packet from the Mac, I cannot see anyting coming in either on Windows (Widcomm Spylite Software) or on Linux (hcidump). Again, I cannot verify what PacketDecoder would see. This email sent to site_archiver(a)lists.apple.com

1 0

Re: 10.3.8 -> PacketDecoder2 dead
by Alexander Traud 12 Feb '05

12 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com User-agent: Microsoft-Entourage/9.0.5.4011 > after installing the 10.3.8 update, my PacketDecoder has gone dead > What is it that I need to install again? The Apple Bluetooth SDK 1.5.3 but this is *not* online yet: https://developer.apple.com/sdk/#Bluetooth Apple has updated the IOBluetooth package to 1.5.3 in Mac OS X v10.3.8. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

10.3.8 -> PacketDecoder2 dead
by Moritz Gmelin 10 Feb '05

10 Feb '05

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hi, M. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… after installing the 10.3.8 update, my PacketDecoder has gone dead (Error message on startup -> Bummer). What is it that I need to install again ? The Bluetooth SDK or the whold Developer SDK ? This email sent to site_archiver(a)lists.apple.com

1 0