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

Client getting back the tail of its own transmission. #15

Closed
yo2loj opened this issue Sep 8, 2016 · 3 comments
Closed

Client getting back the tail of its own transmission. #15

yo2loj opened this issue Sep 8, 2016 · 3 comments

Comments

@yo2loj
Copy link
Contributor

yo2loj commented Sep 8, 2016

There is an issue with the fact that if there are queued packets in an module at the end of a transmission, the transmitting client will get back a short sequence of its own Dv packets.
This is not a major issue, but it has some side effects:
In DCS, since each packet carries complete header info, it will match the users own info which may show up on the transceiver screen.
In Dextra mode, since the last few frames don't have header infosm it will put a blak message on screen. This is most disturbing e.g. on the UP4DAR, where it will erase the screen at the end of an incoming transmission.

@yo2loj
Copy link
Contributor Author

yo2loj commented Sep 8, 2016

I implemented a patch for this issue and it seems to work properly.
Pull request #16 created.

@LX1IQ
Copy link
Collaborator

LX1IQ commented Nov 6, 2016

Hi, yes we know about this issue, and we had a look at your patch.
Well in fact, your patch works, but would put a second mechanism to the existing, which will be double employment.
We are going to extend the existing function already in place to avoid this behavior.
Thank you for you work.
73, Luc

@yo2loj
Copy link
Contributor Author

yo2loj commented Nov 6, 2016

Let's say it is more a "proof of concept".
Any other solution which prevents this behavior would be ok.
I will close the issue since it is acknowledged.

@yo2loj yo2loj closed this as completed Nov 6, 2016
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

2 participants