Hi Dialog,
I have been working on developing a super low power device based on the DA14580 dice and peripheral demos. I manufactured a number of devices around 7 months ago which worked fine, advertised properly and allowed for connection. However, despite being sat in a cupboard at approx. room temperature for 6 months and still showing around 90% battery (really pleased with this btw!) the devices still advertise but any connection attempt fails. Is there anything in the software that may be causing this that you know of?
Thank you for your time,
Best wishes,
Tom
Device:
Hi thomasburton,
I am not able to tell from tha information you provide a probable cause why the device is unable to connect, in general yes there are a lot of things in sw that can cause a connection malfunction, for example the client doesn't fullfil the security requirements of the peripheral, the device might be advertising in non-connectable mode, there is a custom condition in the sw that prevents particular connections, the device for some reason hits a reset and reboots after a connection attempt so it cannot be connected, and in general from sw side there are quite a few things that can happen and the device wont be able to connect.
Thanks MT_dialog
Hi Dialog,
Thanks for your quick reply. The problem is that it connected with no problems at all from an Android device 6 months ago and using the same device and software now it is unable to. I performed a reset on the device and it was able to connect again but this will not be possible in the final product design so it has to remain connectable for the lifetime of the product.
Best wishes,
Tom
Hi thomasburton,
Can you please let me know about the SDK that you are using ? You mention on the post that the SDK is 5.0.2.1, is that the SDK that it is used indeed ? There was a corner case in older SDKs where under a specific condition the receiver of the 580 got stuck but this is corrected in newer SDK version (from version 3.0.10.1 and on). So if you have a device that uses an SDK over the 3.0.10.1 shouldn't be the case, appart from that there is no obvious reason why the device isn't able to connect, does this occurs with all the devices that you have manufactured ?
Thanks MT_dialog
你好,我遇到同样的问题,我无法控制e sdk version(from version 3.0.10.1 and on) you said.could you send it to me ?Looking forward to your replay.
Hi lianchao,
What i am mentioning in the previous post is that all SDK versions after the 3.0.10 has the mentioned fix, so if you just use the latest SDK version it will have the mentioned fix. You will be able to download the latest SDK in the 14580 "Product" page in the "Software & Tools" tab in the "Software Development Kit" section.
Thanks MT_dialog
Thank you very much.I have got it. Another questions：
Because I can't find where I can post my questions,I have to post it here.A few days ago, I can receive the magnetometer data correctly. But these days, I suddenly found that I can not achieve it. The data remained unchanged. Nine sensors are the same problem. I can not solve it, can you help me?
Best wishes
lianchao
Hi lianchao,
Regarding where to post your questions, you will have to choose one of the available BLE categories (Hardware, Software, Tools), as soon as you are on the new page you should be able to see the "New Topic" button right above the list of the threads, so please use that in order to post your question.
Regarding your question, the fact that a few days ago you could receive magnetometer data and now you cannot doesn't give me any clues for what might be wrong, you will have to be more descriptive about your problem and perform some debug in order to give me some more clues, so please try to elaborate the question a bit and post your question in another thread.
Thanks MT_dialog