Chances are high that your project would benefit from a custom protocol analyzer for Saleae Logic. Whether it's adding on another layer to parse I2C transactions to the specific devices on your product, a minor tweak to an existing protocol analyzer, or building a decoder for a new/proprietary protocol entirely from scratch, we're the experts you've been looking for.
We developed our first protocol analyzer using the Saleae Logic Protocol Analyzer SDK in June 2012, long before Binho even existed as a company. There are very few engineers more familiar with the Protocol Analyzer SDK than those on our team. We're aware of all the nuances of supporting both Logic 1.x and Logic 2.x desktop software versions, including implementation requirements (Frame V2) for Data Table and HLA support, as well as for Terminal View.
We've really polished up our skills with the release of our I3C Basic Protocol Analyzer Plugin, having built up a lot of functions and tooling to make building and debugging analyzers a breeze. We're geared up to deliver custom protocol analyzer plugins in record time and with impeccable quality. There are actually two types of protocol analyzer implementations -- the purpose, capabilities, and development scope are quite different. We're well prepared to identify the best approach for your project.
Low-Level Analyzer Development
Low-Level Analyzers are built using the C++ Analyzer SDK and must be compiled for each platform. These analyzers get access to the raw frames of the digital captured waveform and can be used to decode any digital protocol. These can be built from scratch when necessary, but in most cases, new analyzers can be based on the code of an analyzer of a very similar protocol -- the folks at Saleae publish the code of their low-level analyzers so that derivative works can be produced without needing to re-invent the base decoding algorithm again. The caveat with the low-level analyzer is of course the time it takes to get the development environment configured, as well as the requisite C++ expertise.
We developed our first protocol analyzer using the Saleae Logic Protocol Analyzer SDK in June 2012, long before Binho even existed as a company. There are very few engineers more familiar with the Protocol Analyzer SDK than those on our team. We're aware of all the nuances of supporting both Logic 1.x and Logic 2.x desktop software versions, including implementation requirements (Frame V2) for Data Table and HLA support, as well as for Terminal View.
We've really polished up our skills with the release of our I3C Basic Protocol Analyzer Plugin, having built up a lot of functions and tooling to make building and debugging analyzers a breeze. We're geared up to deliver custom protocol analyzer plugins in record time and with impeccable quality. There are actually two types of protocol analyzer implementations -- the purpose, capabilities, and development scope are quite different. We're well prepared to identify the best approach for your project.
High-Level Analyzer (HLA) Extension Development
High-Level Analyzers are new to Logic 2.x desktop software and are written in Python. HLA Extensions provide a mechanism to perform additional parsing on the decoded output from an existing low-level analyzer. For example, if you want to apply an additional layer of decoding on top of SPI, I2C, or UART, then a custom HLA is exactly what you're looking for. Since these are simple scripts written in Python, there is no pain in setting up a C++ build environment, no compiling for each platform, etc. The caveat is simply that these analyzers cannot access the raw digital waveform and can only be utilized when the low-level analyzer for the protocol already exists.
We've got the experience to deliver best-in-class solutions using Low-Level Analyzers, HLA Extensions, and when necessary, solutions which combine both. We'd be glad to review these options with you and help you make the right choice based on your project requirements and desired outcomes.
We developed our first protocol analyzer using the Saleae Logic Protocol Analyzer SDK in June 2012, long before Binho even existed as a company. There are very few engineers more familiar with the Protocol Analyzer SDK than those on our team. We're aware of all the nuances of supporting both Logic 1.x and Logic 2.x desktop software versions, including implementation requirements (Frame V2) for Data Table and HLA support, as well as for Terminal View.
We've really polished up our skills with the release of our I3C Basic Protocol Analyzer Plugin, having built up a lot of functions and tooling to make building and debugging analyzers a breeze. We're geared up to deliver custom protocol analyzer plugins in record time and with impeccable quality. There are actually two types of protocol analyzer implementations -- the purpose, capabilities, and development scope are quite different. We're well prepared to identify the best approach for your project.
Let's Discuss!
Join us for a discussion regarding the development of a custom protocol analyzer for your project. We'll cover the potential benefits of a custom analyzer, the recommended approach and estimated scope of development work based on a brief conversation regarding your protocol. We can also answer any questions you might have about the features of Saleae Logic and functionality that your logic analyzer will have upon completion.