There show the link problem with different master.
When the BT chip and driver are different, it show the different result.
Do you have any experience and idea with this sympton?
The DA14580 shold be support different platform that customer can used properly.
BTW, the SDK is 3.0.7.
Attachment:
Device:
Hi Wedy1227,
The SDK3.0.7 is a very old version and it is not currently supported. The latest version is the SDK5.0.4 and you could download it from our support website. So, I would suggest you to move into our latest SDK and try to replicate the issue. By the way, which example of the SDK are you working on? In addition, can you please clarify this statement : “When the BT chip and driver are different, it show the different result.” ?
Thanks, PM_Dialog
Hi, we have already used SDK3.0.7 for the product before, and it is based on the "keyboard" example.
According to my attachment in the last reply, it has the test result of the different chip in the OS.
I would just like to know do Dialog have any experience like this, it seems there is compatibility problem.
In more detail, the product working follow is like below:
1.Pairing to the laptop.
2.Connected to the system -> OS show "connected"
3.Then DA14580 enter paired mode -> OS show "paired"
4.Press the button on DA14580 -> OS show "connected" then excute the action
5. After the action, return back into paired mode -> OS show "paired"
当问题发生时,没有响应nse while push button.
There are two abnormal situation:
A. Press button -> OS show "connected" but without any action excuted then turn back to "paired".
B. Press button -> OS still show "paired".
From the protocol analyzer, I just observed that the DA14580 show there is Pin or Key missing then OS just rerminate the connection.
And the only way to recover it, is by removing the device information in Windows setting then re-bond again.
This abnormal sympton will happened in some laptops but not all, that is why I list the BT chipset in the OS and the driver version as your reference.
Hi sir,
Do you have any comment for this issue?
Thanks.
Hi Wedy1227,
As I mentioned in my previous post, the SDK3 is a very old version and it is not currently supported. Also. The latest SDK for DA14680 products, is version 5.0.4 and it does not contain “keyboard” reference example. For your case, I would recommend you to try to debug your software and try to find where it gets stuck.
Thanks, PM_Dialog
Hi Sir,
Yes, I do understand that there is no sample as keyboard reference.
I am curious about one thing, while I was trying debug I just found out that change the connection latency from 31 to 0 can improve the performance.
And the failure rate can be reduced.
But it is different from your SPEC as the picture in attach document. It show the default preferred con_latency is 31.
Do you konw why I can decreace the failure rate by change the parameter?
Besides, do you have any experience of the failure rate are different depend on different plattforms even I using the same con_latency 31?
Does Dialog have get similiar issue from other customer?
Thanks, Wedy
Hi Wedy1227,
Which is the supervision timeout that you have set to the device? Is the latency longer than the supervision timeout?
Thanks, PM_Dialog
Hi,
Connection interval min 7.5ms
Connection interval max 7.5ms -> change to 20ms
Connection latency 31 - >change to 0
Supervision timeout 2000ms
I do not think the latency is longer than Supervision timeout, neither before or after.
Hi Wedy1227,
As far as I know we hadn’t had any similar issues.
Thanks, PM_Dialog