Skip to content
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

development version hex file is not working properly #12

Open
jkandasa opened this issue Apr 3, 2017 · 2 comments
Open

development version hex file is not working properly #12

jkandasa opened this issue Apr 3, 2017 · 2 comments

Comments

@jkandasa
Copy link

jkandasa commented Apr 3, 2017

@tekka007 I tried development version hex file 8MHz from https://github.com/mysensors/MySensorsBootloaderRF24/tree/development/hex it did not work as expected. I noticed firmware request is too slow from node. I guess recent chnages has some huge performance issue. I tested with MyController.org. I do not have windows environment to test with MYSController.

I using 8MHz file from https://forum.mysensors.org/topic/4991/mysbootloader-1-3pre2-testing Which is working awesome and quick response from node.

@NativeFail
Copy link

Hello,

same here with latest bootloader or with v13pre2. uploading firmware take couple of minutes then upload take pauses for 2 or 5 secondes between each transfert.

@joro75
Copy link
Contributor

joro75 commented Dec 6, 2020

With the latest MYSBootloader firmware (1.3.0-rc.1) I also see several pauses of 2 seconds, but that is only caused by bad radio connections. If a request for the next data frame is not transferred correctly to the gateway (for example if it is corrupted during the wireless transmission), then a 2 second timeout is used to wait for a response, and if no response is received, it will request again the next data frame after that 2 second timeout.

Could this explain the 2 seconds pauses that you are observing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants