Bluetooth accessory issus - unknown CoD
Bluetooth accessory issus - unknown CoD
- Subject: Bluetooth accessory issus - unknown CoD
- From: Hic Daniel <email@hidden>
- Date: Fri, 10 Oct 2014 12:41:09 +0000
- Thread-topic: Bluetooth accessory issus - unknown CoD
Dear Mr./Ms.
I work as a programmer in a company which is MFi manufacturer
We are using a Bluetooth communication between iDevice and our accessory. We had some problems to see our accessory during discovery proces within iDevice. It came out that the reason is a Class of Device (CoD). I went throught some Apples
documents and found out that in case of using iAP1 the CoD must be specified. That is all I have found yet because current documents don’t describe this issue because the most recent version of the protocol (iAP2) is not using CoD (or it is not necessary to
specify the CoD with iAP2).
There could be many combinations of Major/Minor Device Class and many of them we have tried are invisible to iDevice (they doesn't appear in the iDevice during discovery process). It would be very helpful to us if you could help us specify
CoD which will work with iDevices.
User can attach different type of sensors for measuring to our accessory such as pH, O2 and conductivity. And if you connect to this accessory with your iDevice you can see current values (also battery voltage and accessory name) and that
is all. As I said we tried some CoDs but the iDevice didn’t show them. It worked only if we set CoD belongs to audio set accessories but this is not a kind of our accessory.
Would be possible to give us a hint where we could find some information regarding to this issue or tell us how we should set it or which CoD are allowed and which ones are not?
Thank you very much for your answer.
Best regards,
Danil Hic
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden