Skip to content

BLE communication on MKR1010, after some hours central will not discover any peripherals #281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AndreaScavuzzo opened this issue Jan 6, 2023 · 2 comments
Assignees
Labels
conclusion: duplicate Has already been submitted topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@AndreaScavuzzo
Copy link

AndreaScavuzzo commented Jan 6, 2023

hello,
I have implemented a communication between two Arduino MKR1010 using ArduinoBLE:

example from ArduinoBLE library (Tag: 1.3.2):
PeripheralExplorer (central)
Battery monitor (peripheral)

ArduinoIDE: 1.8.16 (Mac OS)

Initially after reset all is working, but after one ore more hours the central doesn't recognize any Bluetooth peripheral.

here the code but they are from the library example:
BLE_example.zip

(I have tried both latest firmware WIFI NINA 1.4.8 and 1.2.4 but with the same results, seems that with the 1.2.4 the behaviour is better)

I think that this is a very strange behaviour and is not accetable to have it from Arduino, how I can produce a project if after some hour of running nothing is working?

thanks,
Andrea

@per1234 per1234 added the type: imperfection Perceived defect in any part of project label Jan 6, 2023
@AndreaScavuzzo
Copy link
Author

hello,
I think that the issue is similar to the ticket: Fix BLE scanning block after few minutes #264

some fixes has been done on repository but they are not present in the official latest TAG (1.3.2),

With the latest files from master my issue is not yet present,
are you generating a new TAG with the file fixed?

thanks,
Andrea

@per1234
Copy link
Contributor

per1234 commented Jan 9, 2023

Thanks for taking the time to post an update @AndreaScavuzzo. Since the issue has already been resolved, I will close this as resolved.

As you pointed out, a production release has not been made since the time of the fix, but this issue tracker is used to track work to be done in the codebase hosted in this repository, so we close issues as soon as they are resolved in the codebase; not when the resolution is released.

@per1234 per1234 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2023
@per1234 per1234 added conclusion: duplicate Has already been submitted topic: code Related to content of the project itself labels Jan 9, 2023
@per1234 per1234 self-assigned this Jul 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: duplicate Has already been submitted topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

2 participants