67

Import .logicdata capture


T
Thomasso

Would be nice to be able to open Logic 1.x capture files with Logic2.

A

Activity Newest / Oldest

Avatar

Tim

(#73071)
"Being able to open captures traces from Logic1 .logicdata files or even .vcd files would be very appreciated."


Avatar

Tim

twitter.com/daguro/status/1519451650477285376
"I would like to use the new version of Logic, but I need to compare output with existing trace captures. It is tedious to compare trace outputs from different versions."


T

Thomas

If its hard to implement a import possibility ... maybe it is more easy to build a converter tool?


Avatar

Tim

twitter.com/akohlsmith/status/1489823550659772416
"wow. Tried out @saleae Logic2 software ... nope nope nope nope. It's pretty but terrible UX. Can't even open/import old capture files despite this being a trivial feature. What the heck happened to the company providing a solid UI to their solid hardware?"


G

Geoff

I can't believe Logic 2 has made it to general release with no way of interacting with the 1.x logicdata format, despite it being 1) a rather obvious requirement and 2) requested over 2 years ago.

You're also now driving a wedge between new and old users of your software:

"Starting January 4 2022, Saleae has released a new hardware revision of our Logic Pro 16 devices. These new units are not compatible with the legacy Logic 1.x software"

So further to Tim's point about someone accidentally using the newer software, If you buy a new Logic 16 you MUST use the new software. And then to review capture files you need to use the "correct" version.

Norbert summarised it perfectly. I wouldn't want to have to track down a copy of Word 2003 because I have an old document. Wow.

Looks like my Logic 8 is the first and last Saleae product I buy... I love my Logic 8 but I can't justify spending any more money on an ecosystem where this kind of thing happens.


N

Norbert

Just imagine new version M$ Word is unable to open old version.


  • G
Avatar

Tim

(#66665)
"Just wanted to provide some quick feedback about your preference not to have backwards compatibility to your file format.
We are a group of few tenths of engineers collaborating and using your tools as our reference to exchange traces to debug issues.
If one of the team members, even unintentionally (laptop upgrade) forgets to use one specific version of your software and downloads the latest, he automatically forces all the team to move to the latest software once he produce a single trace file. Making this trace file again may not be that easy.... especially if you are hunting a bug that appears once a day... also please do not take for granted that moving into the latest version is also an easy option. We may be working offline in the customer domain.
Just wanted to provide some feedback ... keep up the good work!"


Avatar

Tim

"I am not referring about files between Logic 1.x and Logic 2, but between different versions of Logic 2. It seems that it is not allowed to open a file with an older version of Logic 2. Thus if someone from the team saves a file with the latest version, people that want to view this file should move to this version as well. That causes constant disruption…"


B

Benjamin

Hi Saleae,
This is an absolutely critical feature and I honestly can't believe this has not been implemented / fixed yet. Is there already a release date available for this feature?
Thanks,
Benjamin


Avatar

Tim

(#62901)
"As I would imagine you’ve heard from many in the industry, the main reason that I’m reluctant to move to Logic 2.x is the incompatibility of the saved capture formats. I regularly need to both look at traces from others and share traces of my own. Currently, the de-facto “standard” for sharing these traces is the .logicdata format. So, given that I can’t convert/import/export this format into/out of the Logic 2.x software it’s simpler to stay put with the Logic 1.x software. As a software/firmware developer myself, I understand the value of “starting fresh” and occasionally making some large, compatibility breaking, changes, but in this case, I think Saleae may be a victim of its own success. Now that .logicdata has become a de-facto industry standard, I don’t think you’ll see widespread adoption of Logic 2.x unless/until you also provide some tools for managing the support/transition of the legacy capture format. Of course, that last bit is all just my opinion, but I don’t think I’m unique in that viewpoint."


P

Paul

Still waiting on this capability - sticking with Logic 1.2 until we can open .logicdata files with logic 2.


Avatar

Tim

(#60761)
"cannot open logicdata file, not showing in this feature"


Avatar

Tim

(#59781)
"Hi. I'm here because of the Mac M1 issues. For me, Logic2 isn't able to record more than a moment of data, and when I did, I couldn't get the SPI analyzer working.

I'm writing mostly to let you know of the impact. I am using legacy Logic software and it's mostly working fine for me. But when I try to share my capture, others are unable to view it."


R

Ramon

I need this feature as well. Without it I'm, and I'm sure many others, never switching to Logic2.


Avatar

Tim

(#58448)
"please support loading of the legacy .logicdata files in the application or as an external converter program. We have a lot of sample files we would like to be able to analyze and it feels silly to keep two applications installed for this purpose.
.....
I find it strange that you do not have support for .logicdata on the roadmap.
We have a lot of captures from "one shots" which we want to be able to analyze in the future as well without juggling old installs. Even excel allows you to load old spreadsheets in the latest version :D

An offline converter would work as well of course."


A

Andrew

Yes, please! It is a little bit of a pain to need both versions installed.


Avatar

Tim

discuss.saleae.com/t/export-multiple-analyser-results-to-single-file/682/3
"It really would be nice if v2 software could import v1 logictraces… We have a lot of validation data that has been captured using Saleae devices, and have to keep both versions of the software available just so we can continue consulting them… Really?"


Avatar

Tim

See forum discussion here on this topic as well:
discuss.saleae.com/t/1-2-29-no-longer-supported/662


Avatar

Tim

(#53898)
"I downloaded version 2.3.5. with it I can not open the data I captured before. I was able to open *.logicdata with 1.2.18.
Now I can not open it with 2.3.5"


Avatar

Tim

(#56980)
"Export/import original Logic "logicdata" files. Deep history of traces generated with original Logic program."


Avatar

Tim

discuss.saleae.com/t/logic-2-and-logic-1-side-by-side/892/4?
"I use them both all of the time. Some things are still better in Logic 1 and many other things are better in Logic 2. It’s perfectly fine to switch between them.

But, I feel you about the lack of Logic1 file loading. I mean, they have the source code for both, how difficult can it be to support your own file format? At first it was like “yeah, they’re busy making a new, awesome program, give them some slack” but now it kind of seems to stick out like a sore thumb. I’m sure there are reasons. And, we can all live with it because we can still use Logic 1 (even if you have to fudge the V1 version most of us have installed because of the expired update thing). So, while I find it quite odd I tend not to dwell on it too often. Just load Logic 1 and view your captures. But, still, I’d really like to see support for it added soon."


Avatar

Tim

"This is ultimately essential - we have a workflow for which tooling needs to be able to open earlier captures - .logicdata files and/or .VCD"

(57234)


Avatar

Rene

It would be really helpful to have this feature implemented ... or at least have converter-tool for .logicdata to .sal data-files.


H

Harald

same here: we collected and compare lots of data and protocol logs.
being able to either convert "old" .logicdata to .sal (using external converter tool) or import old reference/testing data would help us a lot for the migration from Logic 1.* to 2.*


S

Steve

This is an excellent idea. We use your units quite a bit, and have a lot of data sets that we keep for reference and documentation purposes. Being able to import them into Version 2.X of the software is an important consideration before we can migrate to the newer software platform...


L

Lenny

Hello I could really use this feature to evaluate Logic 2. I have captures from a difficult customer problem, I was hoping that logic 2 extension capabilities could help me. But since I cannot import a logic 1 capture, I am stuck with using another solution. I am not sure that what you want to happen.


N

Neel

Status changed to: Open

M

Mattia

I always used the older version of Logic SW. Now, I want to start using the new version BUT all my debug database has been saved with older extension ".logicsetting" and ".logicdata". It could be usefull to implement an open/import function for the older Logic files.


S

Saleae

Status changed to: Under review

Avatar

PaulZ

This is important - I have some large .logicdata files that I'd like to import, and save just a portion of to substantially reduce the size. Alternatively, a tool to convert the files would be fine too.


  • E
  • B
  • B
J

Jonathan

I've been finding that the *.sal files are significantly smaller than the *.logicdata files. Possibly due to compression? I've been needing to compress *.logicdata files to save space, however with *.sal files, I no longer even bother.