# How to look up in "decoded protocols" **URL:** \ **Category:** Logic 1.x (Legacy) Software\ **Created:** [December 8, 2019, 11:09am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189 "2019-12-08T11:09:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![andre.kjellstrup](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@andre.kjellstrup](https://discuss.saleae.com/u/andre.kjellstrup)\ **Post date:** [December 8, 2019, 11:09am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189/1 "2019-12-08T11:09:18Z")
So I have sampled some I2C Then used the search in “decoded protocols” to look up the setup read from device 0x11 I could click in the search results to display the data. Then I escaped, in order to see the following data. Now I see all “decoded protocol” data, and must manually find back to the time of interest? Is there/I wish there were/ a way to make “decoded protocols” scroll/show the data from the bytes looking at. Same for making a bookmark, I can make a bookmark, but there is no feature to automatically jump to a nearest item in “decoded protocols” Do I miss something, or isn’t this functionality there yet ? ![Screenshot from 2019-12-08 11-53-46](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/974c5a9646dadad4403d71c18529a799e1c7dd5c.png) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [December 10, 2019, 1:01am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189/2 "2019-12-10T01:01:36Z")
Hi Andre, thanks for the feedback. I completely agree with your frustration. This is something we plan to improve in the next version of our software (in Alpha at the moment). You are correct. When deleting your search text, the decoded data repopulates the search contents, which would have you lose your previously searched item. We will improve this! ---
**Author:** ![andre.kjellstrup](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@andre.kjellstrup](https://discuss.saleae.com/u/andre.kjellstrup)\ **Post date:** [December 10, 2019, 8:05am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189/3 "2019-12-10T08:05:55Z")
Thank you. Sometimes, one wish the results are as they are now (only matching data displayed) for instance, when one need to see how often something is happening. Other times, one needs to see the following byte(s) (match on more than one byte) Also: when some bookmarks or timing marker pair is placed it would be very neat to see them in the decoded protocol window. (maybe just a colored line, or some list items with different color.) Your software, is your main advantage, keep up the good job improving it. ---
**Author:** ![andre.kjellstrup](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@andre.kjellstrup](https://discuss.saleae.com/u/andre.kjellstrup)\ **Post date:** [December 10, 2019, 8:20am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189/4 "2019-12-10T08:20:25Z")
![Screenshot from 2019-12-09 23-13-56](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/ca073883c9fb9ca7722ff3acf66e9d4abce934b7.png) Additional feedback about current master (please note my previous post): This is how I look at one I2C request/command and data reply from slave. I zoom out to a decent size for the job, but the blue data fields are unreadable even when there are plenty of room around. When slinking anything in “decoded protocols” , the nice, smooth, animation does also mess with the final zoom level, after a “travel” , zoom level should be the same. - it is perfectly fine to zoom out during travel, as it gives a nice impression of what-is-where, but the end zoom should be preserved. Also, there are green/red dot’s on I2C data line, the red is not always after a NACK, I failed to find any documentation on the meaning of those. ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [December 11, 2019, 1:03am UTC](https://discuss.saleae.com/t/how-to-look-up-in-decoded-protocols/189/5 "2019-12-11T01:03:28Z")
This is all great feedback for us. Thanks Andre! “Other times, one needs to see the following byte(s) (match on more than one byte)” [TR] Searching through decoded protocol results for multiple byte patterns is something we are working on now. We will post an update on [discuss.saleae.com](http://discuss.saleae.com) once we release this feature. “Also: when some bookmarks or timing marker pair is placed it would be very neat to see them in the decoded protocol window. (maybe just a colored line, or some list items with different color.)” [TR] Good idea. I’ll discuss this with our developers “I zoom out to a decent size for the job, but the blue data fields are unreadable even when there are plenty of room around.” [TR] We’ve improved this behavior in the latest Alpha software by utilizing more of the blue box. Feel free to try it out below: > [@Alpha 13](https://discuss.saleae.com/t/alpha-13/183): > > This is the 13th alpha release, 2.1.0. We’ve bumped the minor version number because this release includes a big new feature, serial terminal (although it is just the core feature much more to come). As always, we would love to hear your feedback on every release! Reply here or create another thread. We’re currently focused on analyzers and making the digital usage, as Joe always says slight_smile, awesome! Windows [http://logic-io.s3.amazonaws.com/test-builds/Logic+Setup+2.1.0-master.exe](http://logic-io.s3.amazonaws.com/test-builds/Logic+Setup+2.1.0-master.exe) M… “When slinking anything in “decoded protocols” , the nice, smooth, animation does also mess with the final zoom level, after a “travel” , zoom level should be the same.” [TR] We will discuss this as well. Perhaps we may include an option to preserve/lock zoom levels. “Also, there are green/red dot’s on I2C data line, the red is not always after a NACK, I failed to find any documentation on the meaning of those.” [TR] Happy to look into this for you. The red dot should show up when both the SCL and SDA have returned to their idle state. Could you send in a support request for this using the link below? I will provide an upload link for your capture file via email once you send in a support request. [https://contact.saleae.com/hc/en-us/requests/new](https://contact.saleae.com/hc/en-us/requests/new)