# Logic2 / Logic1 empty bubbleText **URL:** \ **Category:** Logic 2 Software\ **Created:** [February 25, 2021, 2:08pm UTC](https://discuss.saleae.com/t/logic2-logic1-empty-bubbletext/930 "2021-02-25T14:08:14Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![ftrefou](https://avatars.discourse-cdn.com/v4/letter/f/7feea3/32.png) [@ftrefou](https://discuss.saleae.com/u/ftrefou)\ **Post date:** [February 26, 2021, 9:43am UTC](https://discuss.saleae.com/t/logic2-logic1-empty-bubbletext/930/4 "2021-02-26T09:43:12Z")
@timreyes bubbles actually don’t cause any critical issues. It’s more a visual aspect because they appear on channels where i display bubbles of different length. Logic2 has trouble to know wich frame to display. The trouble i’ve potentially identified is that frameV2 don’t show in tabularText, instead i only see Type: framev1. I’ve got a lot of overlaping frames so perhaps it’s causing this issue. Zoom out show protocol “high” interpretation: ![zoomOut](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/5028d6620b4a212a113182e9300b55741379298c.png) Zoom in show characters (and ATR isn’t visible anymore) ![zoomIn](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/7dfd214143fdc3bacf43eba50aeccb13c106f3f9.png) It’s perhaps a bad choice i’ve made to try to display different protocol levels over a single capture in the analyzer. @markgarrison I have to check before sharing source code, but you can reproduce this case by modifying your i2c analyzer: > **[saleae/i2c-analyzer](https://github.com/saleae/i2c-analyzer/tree/alpha)** > > alpha I attach the patch and a capture: [res.zip](https://discuss.saleae.com/uploads/short-url/aaqb7awrFiFOagAvpmh6xJkG6bB.zip) (33.0 KB) --- _[View the full topic](https://discuss.saleae.com/t/logic2-logic1-empty-bubbletext/930)._