Help us develop the next-generation software, now in alpha!
A lot of 12V automotive systems have a logic low level near 3V. Having the analog reading is better than nothing but suboptimal.
All the current saleae products have hard set voltage thresholds - even Pro 16 only has 3 fixed thresholds, it's not continuously variable. We're keeping this in mind for the future though. We actually originally planned to have a continuously variable threshold for Pro 16, but when we started to get behind, we replaced it with the simpler fixed three options instead.
With the current products, we've thought about a software feature to convert an analog channel to a digital channel using settable thresholds. This would have a substantial bandwidth limit, and a number of other drawbacks too. We're thinking about it inside a larger set of improvements to how our protocol analyzers work now. This could be somewhat similar to the feature suggested here: http://ideas.saleae.com/forums/214303-saleae-ideas/suggestions/7168478-add-virtual-channel-where-a-output-from-the-sdk-c
I can't say that we'll be doing this for sure, as per our feature commitment here: http://blog.saleae.com/software-feature-development-expectations/
however I can say that this is one of the areas of the software we're hiring for.
I'm looking at a 5 V analog signal that is toggling between 4.7 and 1.6 V. The ability to set the voltage thresholds that determine what is considered low and high for digital readings would be helpful. This would allow for me to see these as digital values and use some of those measurement tools. I believe this concept is similar to what the original poster had suggested.
You won't be notified about changes to this idea.