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

Binary commands sent via UART (BT) to VI eventually get corrupted #313

Open
peplin opened this Issue Oct 29, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@peplin
Member

peplin commented Oct 29, 2014

I need to add more details here later but I wanted to create some record that I noticed it doesn't work reliably while working on the functional test suite running over Bluetoooth (#300).

@jwschmo

This comment has been minimized.

Show comment
Hide comment
@jwschmo

jwschmo Sep 4, 2016

any tips on this one? I have a use case that this would be helpful for.

jwschmo commented Sep 4, 2016

any tips on this one? I have a use case that this would be helpful for.

@jwschmo

This comment has been minimized.

Show comment
Hide comment
@jwschmo

jwschmo Sep 4, 2016

I should be more clear - the "ignore binary message received by the VI" part - was there a particular reason for that? it would be helpful to have that functionality so if I can start somewhere that would be appreciated.

jwschmo commented Sep 4, 2016

I should be more clear - the "ignore binary message received by the VI" part - was there a particular reason for that? it would be helpful to have that functionality so if I can start somewhere that would be appreciated.

@peplin

This comment has been minimized.

Show comment
Hide comment
@peplin

peplin Sep 4, 2016

Member

If I remember correctly, when it was enable the incoming messages would eventually get corrupted and the only way to recover was to restart the unit. I disabled it so at least it would stay up - I am not sure what the root cause might be.

Member

peplin commented Sep 4, 2016

If I remember correctly, when it was enable the incoming messages would eventually get corrupted and the only way to recover was to restart the unit. I disabled it so at least it would stay up - I am not sure what the root cause might be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment