Alpha 14

[vajrasana]

@rani

I don’t know if naming the channels upfront is a common use case

How would someone use this option of labeling channels. Default is “Channel #n”. Labeling it e.g. MOSI is the obvious choice to me.

@rani

1. Auto-detect analyzers - you capture data and the app does the rest for you by suggesting you the right analyzer with the right configuration. I believe that it’s a more robust solution.

Would be amazing. For example, it might be obvious that what ever your capture is SPI, but to find the correct mode(0,1,2,3) would be actually nice. But please leave the user a chance to change the suggested.

@rani

2. Allow users to write plugins such as that. In this case, you’d be able to intercept the “create analyzer” process and assign the channels as you like with code.

nice =). Which language, python :)?
While creating a interface for plugins, would it be possible to actually make use of a existing analyzer, and overwrite methods? I’ve something in my mind like replacing single Bytes or sequences of sniffed bytes with the actual command. e.g. a own plugin special written for say a LSM6DS3 sensor.

 # example for LSM6DS3
 MOSI: 0x8F followd by MISO: 0x69
 should be translated to:
 "Get WHO_AM_I register" and "WHO_AM_I: 0x69"

Thinking of it, would such a lookup be helpful for others too? The user would only provide a json-file with sequences and the associated replacements accordingly. The Analyzer would do the lookup. The next step would be a repository maintained by the community with the json-files for lot’s of overlay protocols.