Re: Simple Bluetooth Questions: Help!
site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Yann Bizeul • yann at tynsoe.org Cocoa Developer Tynsoe Projects BuddyPop • GeekTool • SSH Tunnel Manager • ... http://projects.tynsoe.org/ Le 29 sept. 05 à 17:34, Joseph Kelly a écrit : Greetings, I'm using the serial device protocol on an RFCOMM channel. My questions: Thanks, Joseph K. _______________________________________________ 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/ml%40tynsoe.org This email sent to ml@tynsoe.org _______________________________________________ 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... (1) I am identifying my devices by their name. Basically, they are called "CompanyPrefix:DeviceName", so I get back a list of devices from IOBluetoothDeviceInquiry, I match the name against CompanyPrefix; I display DeviceName to the user. Is this a decent strategy, or is there a better approach to identifying my device? Another approach would be to just record the device ID ([device getAddressString ]), and maintain the customer/device association somewhare in your app. But since you are working on your own device, that does not make such a difference. (3) How do I enumerate devices without the UI in absence of IOBluetoothDeviceInquiry? Personally, I like the approach of listing device known of the OS (already linked) with [ IOBluetoothDevice pairedDevices]. But perhaps you don't want the users to link with the device on the OS side. About the rest of your question, I do not masterize BT enough to give you a valuable advice :-) I am building a bluetooth device that basically records some kind of simple periodic data in the field, and once it's within proximity, uploads this data to a host computer. I have developed a prototype application using the objective-C apis which I've gotten up and running in a matter of days -- thanks Apple! (The Windows Bluetooth implementation is something gawd awful by comparison!) (1) I am identifying my devices by their name. Basically, they are called "CompanyPrefix:DeviceName", so I get back a list of devices from IOBluetoothDeviceInquiry, I match the name against CompanyPrefix; I display DeviceName to the user. Is this a decent strategy, or is there a better approach to identifying my device? (2) Is there a way to get to a lower level public Bluetooth api? I've looked through some of the top level IOKit headers w/ no luck. I think if I could get an answer to this question, my following question might be moot. (3) How do I enumerate devices without the UI in absence of IOBluetoothDeviceInquiry? (4) How do I specify the passcode for a device programatically? (If you haven't figured out, I'm trying to prevent user intervention as much as possible because I'd like the discover-connect-upload process to be automatic) There's a chance I might downgrade the security model to eliminate passcodes. (5) Say I have 20 devices, and 5 host computers. I would like the devices to be bound to only one host, such that when the device disconnects (i.e. travels out to the field) and re-connects, only that host is able to connect to it. I know that I can cache the device address on the host, but can anyone suggest a strategy whereby I can guarantee that only that one host can connect to a particular device, w/o necessarily connecting to the device and opening a channel? Once again, I'm thinking of resorting to placing the Mac's bt address in the name field (i.e. CompanyPrefix:Address:DeviceName). Any answers whatsoever, or even a "how the hell should I know?" would be appreciated! This email sent to site_archiver@lists.apple.com
participants (1)
-
Yann Bizeul