# Logic 2.2.14 **URL:** \ **Category:** Downloads / Releases\ **Created:** [May 1, 2020, 4:12am UTC](https://discuss.saleae.com/t/logic-2-2-14/490 "2020-05-01T04:12:49Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\ **Post date:** [May 7, 2020, 10:55pm UTC](https://discuss.saleae.com/t/logic-2-2-14/490/21 "2020-05-07T22:55:46Z")
Fixed, we’ll be live on 2.2.16 probably ---
**Author:** ![KurtE](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/kurte/32/189_2.png) [@KurtE](https://discuss.saleae.com/u/KurtE)\ **Post date:** [May 8, 2020, 12:00am UTC](https://discuss.saleae.com/t/logic-2-2-14/490/22 "2020-05-08T00:00:30Z")
On the 2nd part the issue was that the host software changed baud rates several times in a second, or so, where it would try one baud rate see if anyone responds, if not, it would try different one… Until something responds. With this I was having some issues where the analyzer would not pickup the data at the new baud rate, even when there were gaps between their logical packets. I will try to capture this again, but may be slightly fickle to get again. 0th issue is when you are doing terminal output with Serial, and the output stream is using \r characters to terminate lines, the terminal just keeps going back to start of row overwriting the data. Would be good to be able to choose what your line termination is. for the terminal output ---
**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\ **Post date:** [May 8, 2020, 12:40am UTC](https://discuss.saleae.com/t/logic-2-2-14/490/23 "2020-05-08T00:40:13Z")
Thanks for the detailed description 🙂 I’m not sure what the right solution for something like that is. Feels like automation scripts code be useful… > Would be good to be able to choose what your line termination is Would you like to add that to our feature requests board? I can to do as well ---
**Author:** ![KurtE](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/kurte/32/189_2.png) [@KurtE](https://discuss.saleae.com/u/KurtE)\ **Post date:** [May 8, 2020, 12:28pm UTC](https://discuss.saleae.com/t/logic-2-2-14/490/24 "2020-05-08T12:28:03Z")
Thanks @rani - I created a new feature request. I suggested either allow the user to choose line terminations. and/or allow either CR or LF to advance to next line, but only advance once if both characters are found as consecutive characters. ---
**Author:** ![rani](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/rani/32/343_2.png) [@rani](https://discuss.saleae.com/u/rani)\ **Post date:** [May 9, 2020, 2:43pm UTC](https://discuss.saleae.com/t/logic-2-2-14/490/25 "2020-05-09T14:43:07Z")
---
**Author:** ![anhnguyen2345](https://avatars.discourse-cdn.com/v4/letter/a/a587f6/32.png) [@anhnguyen2345](https://discuss.saleae.com/u/anhnguyen2345)\ **Post date:** [August 25, 2023, 3:50am UTC](https://discuss.saleae.com/t/logic-2-2-14/490/26 "2023-08-25T03:50:11Z")
Have the problem fixed yet ? I want to parse the log but facing the same issue ! ---
**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:** [August 26, 2023, 2:42am UTC](https://discuss.saleae.com/t/logic-2-2-14/490/27 "2023-08-26T02:42:45Z")
@anhnguyen2345 Are you referring to the issue with the Packet ID not incrementing properly when using our I2C analyzer? If so, we unfortunately don’t have a fix for this yet. We recorded this issue below, along with some potential workarounds in the meantime. > **[Bug Report - Packet ID Doesn't Work Properly - Logic 2 - Ideas and Feature...](https://ideas.saleae.com/b/feature-requests/packet-id-doesnt-work-properly/)** > > For LLAs that support Packet IDs (such as our I2C Analyzer), Packet ID remains at "0" for all entries in an export and doesn't count properly in Logic 2. > > Workaround: > The data table export includes enable and disable events. The data table h [Previous page](https://discuss.saleae.com/t/logic-2-2-14/490.md?page=1)