A Luos protocol low level analyzer for Saleae Logic applications: tracking the communication data and analyzing the communication protocol, when using a Saleae Logic analyzer.
Some times, the analyzer decode the crc in the right way but doesn't gives a correct interpretation of its value.
In the screenshot above, the crc decoded value is 0x0FCD wich is correct but the analyzer intepret it as "not good". This default seems to be not systematic.
Hi! I'm a Product Manager at Saleae and we’ve made improvements to our analyzer build process. Specifically, we cleaned up the build system, and switched to cmake, so there aren't multiple project files anymore. By implementing the changes outlined here you will be able to provide the community automatic builds in addition to a simplified build system. Let us know if you think you can make the changes or if you’d like us to make the changes for you.
Additionally, if you would like to update your analyzer so that results appear in Logic 2’s data table you can follow the steps outlined here. Note that if you upgrade your analyzer to FrameV2 it will not be backward compatible with Logic 1.
We really appreciate your time and effort! Please let us know if you have any feedback or questions. Thanks!