You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Detection of badges connected via USB works under Windows but writing a message to the connected badge fails with the following error message from the CLI:
Error: incomplete write: 65 of 384 bytes
The total byte count depends on the size of the message but the written byte count is always 65.
The text was updated successfully, but these errors were encountered:
The device.write call seems to behave different on Windows (compared to Linux / MacOS).
Two ideas:
The API wants an "ReportID" as the first byte (as a prefix to the actual payload). But this ID is optional on Linux / MacOS. Fix: Prepend a 0x00 byte to the payload.
If that does not help. The write might be incomplete like a regular write to a file and we need to write the remaining bytes until all bytes are written (like write_all in std::io::Write). With or without the 0x00 prefix.
I would guess that the report id is missing and the write fails after the first packet (64 bytes + 1 byte report id).
Detection of badges connected via USB works under Windows but writing a message to the connected badge fails with the following error message from the CLI:
The total byte count depends on the size of the message but the written byte count is always 65.
The text was updated successfully, but these errors were encountered: