-
Notifications
You must be signed in to change notification settings - Fork 294
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
Transmit call fails when size is > 12 #443
Comments
maximum length for cec spec is this, we can put a guard to help developers |
Where are you getting the maximum number? All the documentation I can find says it's 16, not 12. |
the first 4 are taken by transmission data, @opdenkamp will confirm my thoughts |
thank you! |
Can you elaborate on what specific information those 4 bytes represent? |
Hi @srobins6 , I've responded to your question in the email to you've sent. You can send 16 bytes of data, 2 of which are taken by the header (initiator, destination, opcode). I've verified that this is working correctly on libCEC 4.0.2+ There was a bug in an old version of libCEC which prevented the last bytes from being sent, which has been fixed. If it's not working for you, then you may have to upgrade: https://github.com/Pulse-Eight/libcec/releases/tag/libcec-4.0.3 |
I am still having this issue with libcecsharp specifically, haven't tested with other libraries |
I have tested sending a 16 byte packet with CecSharpTester: https://github.com/Pulse-Eight/cec-dotnet/tree/180cbe2b4e2b2d6a58c4b22d09760aba4b67a8e5/src/CecSharpTester Have you upgraded to the latest version? |
Updating the status here too: this is caused by a bug in the firmware on the TX side, which results in TRANSMIT_FAILED_TIMEOUT_DATA when attempting to send out a 16 byte packet. |
This isn't caused by the firmware after all, but was caused by a buffer that couldn't fit this. |
In LibCecSharp the Transit function fails when command.Parameters.Size > 12
The text was updated successfully, but these errors were encountered: