site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com joe On Jan 23, 2006, at 3:22 PM, Joseph Kelly wrote: When I use the Setup Assistant, however, I see much better results. Any ideas? joe _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/joeman%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... Sorry about my previous post -- it seems that the devices in question may have been bound to other host computers at the time. The lesson is to implement some kind of in-house policy re: device ownership when there are multiple devices and multiple host systems. Must I use the Apple Bluetooth Setup Assistant in order to talk to a device? I've got a bunch of nearly identical prototype devices, all with the same hardware and firmware. For certain of my devices, I seem to be able to discover the device, open it, authenticate it, and establish an RFCOMM channel, all without the Setup Assistant. For certain other devices, however, without using the Setup Assistant, they either fail at the authenticate stage with error 2, or the call to -openRFCOMMChannelAsync: never completes. This email sent to joeman@mac.com This email sent to site_archiver@lists.apple.com