Fixed random pause/hesitation when printing

[digant73]

BUGFIXES:

• Fixed [Q] Random pauses or hesitation when printing. #2761: Based on deep analysis and testing shared by @rondlh on [Q] Random pauses or hesitation when printing. #2761
• Improved partial message retrieval handling: Serial_Get finction in SerialConnection API improved to prevent the possibility to read multiple times the same partial message on next function invokation until the message if fully received from serial port. It also avoids to read multiple times the same partial message in case of failure on the serial connection (e.g. due to EMI)

fixes #2761

PR STATE: Ready for merge

[rondlh]

How to get this PR merged asap?

[digant73]

It seems to be enough to solve the issue (just keeping in this PR the minimal code).Serial_Get (reader) and USART_IRQHandler (writer) are totally decoupled now. #2761 is open since April. Other features like advanced ok or any other improvement can be provided in a separate PR.

[rondlh]

It seems to be enough to solve the issue (just keeping in this PR the minimal code).Serial_Get (reader) and USART_IRQHandler (writer) are totally decoupled now. #2761 is open since April. Other features like advanced ok or any other improvement can be provided in a separate PR.

@digant73 Are you responding to me? If so then you seem to have misunderstood my question...

[digant73]

It seems to be enough to solve the issue (just keeping in this PR the minimal code).Serial_Get (reader) and USART_IRQHandler (writer) are totally decoupled now. #2761 is open since April. Other features like advanced ok or any other improvement can be provided in a separate PR.

@digant73 Are you responding to me? If so then you seem to have misunderstood my question...

I have also to work and travel during the day. If you are afraid about the possible issue due to no use of volatile for wIndex I just made an edit in my last comment in #2761. It will be added.

[rondlh]

I have also to work and travel during the day. If you are afraid about the possible issue due to no use of volatile for wIndex I just made an edit in my last comment in #2761. It will be added.

I mean this... many PRs have NOT been merged for a long time, perhaps BTT is not paying much attention, so the question is how do we get your recent work merged asap? I'm not worried about the volatile variable, it has been off during all of my testing.

[digant73]

I have also to work and travel during the day. If you are afraid about the possible issue due to no use of volatile for wIndex I just made an edit in my last comment in #2761. It will be added.

I mean this... many PRs have NOT been merged for a long time, perhaps BTT is not paying much attention, so the question is how do we get your recent work merged asap? I'm not worried about the volatile variable, it has been off during all of my testing.

I can only suppose that some PRs are not merged for reasons that the author perfectly know. After that said, as far as I see BTT is OoO since more than 10 days. I already asked BTT to consider to merge many PRs if it can help.
In the meanwhile users having the issue in #2761 can download this small PR and test it. It was not even planned from my side due to all the private club unfortunately terminated with no public PR release at all... But no fix was damaging only the community

[V1EngineeringInc]

Niiiice!!

[rondlh]

Merged 🥇 Great job, thanks for your support!

[V1EngineeringInc]

Thank you both for putting in the effort. This has been a bug for a very long time.