Logic 2.2.3 - Download here!

[rani]

Can you maybe save the capture and share it with me?

[barcelona_fan]

Hello,
I downloaded the my Saleae’s calibration files manually and used them with the Logic 1 software for a while. When switching to Logic 2 I noticed that for the same device plugged, Logic 2 asks for a differently named calibration file (with a different hash as its name). Does this mean i’ll have to re-download the calibration files? or are the contents the same considering its the exact same hardware piece plugged, which means I’ll be fine by just renaming the calibration file to the hash Logic 2 software expects to find for the specific plugged device.

Thank you for your help in advance. Love your work and how Logic 2 is coming together so far!

[rani]

The calibration files are identical. If it’s ok to ask, why do you need to download them manually?

Love your work and how Logic 2 is coming together so far!

Thanks!

[Fabiano]

Hi,

I wanted to ask if it is really necessary to have OpenJDK using 1.25GB of RAM?

A feature I’d would like to ask is to bring back the ability to change the LED color on the unit (I miss the blue color ). I noticed you introduced a green box with the model of the unit; maybe if you right click on it would bring the color selection like on the timing markers:

Awesome steady work you guys are doing!

Thank you,
Fabiano

[rani]

That’s a great question!
We’re currently using elasticsearch to index and search analyzer results. We’re looking for better alternatives, and I’ll have a better answer in a week or two.

The LED color changes based on the state of the device - running, active, capturing, error. Would you like to change the colors of those states or just have one fixed color? (if it’s the latter, then why?)

Thanks for the feedback!

[jack.newman12]

Hi,
Just curious if you are considering making the python analyzers compatible with the Pulseview decoders (or at least easy to port).
Additionally, will the decoders have the ability to do multiple line output? e.g. Here Pulseview decodes ‘Bits’, ‘Fields’, and ‘Commands’ in a visually nice way.

I am loving the updates so far!

[rani]

The first version won’t be compatible with Pulseview decoders, however, I believe that it’d be super easy to port them as our modules will only have 3 functions:

• getConfiguration
• setSettings
• decode

Additionally, will the decoders have the ability to do multiple line output?

There will be an option to create multiple rows - in the configuration, the decoder will specify the names of the rows (you’ll be able to add data to existing rows or create new ones).

I am loving the updates so far!

Thanks

[Fabiano]

I’ve only seen the bright green when capturing, and dark green when idle. I didn’t know there were other colors. I used to set a minimum blue color (RGB #000001) to work at night under low light. As I tend to keep the boards + Logic Pro next to my keyboard, the dim minimum blue was just the right level of brightness in the dark . For the alpha, I’ve been using a tape over the LED…

[rani]

I think that it’s useful for most users, however, we can consider making the color of the different modes configurable in the future (so they won’t have to put a tape over it ).
You’re also welcome to create a new request on our the feature requests board:
https://ideas.saleae.com/b/feature-requests/

[markp]

Another Example of Poor Color Choice for Analyzer Bubble Text

If I add 4 Analyzers, the 4th one comes up with a Yellow bubble. The text is white. The white text on orange was bad, but this one is totally unreadable. Just saying…

My suggestion is to flip the text to black on the light backgrounds.

[rani]

How about this?

[markp]

That looks better! At least I can read it!

Mark

[rani]

We’ll have it on the next release
In about a week

[Emmanuel]

Hi

I’ve downloaded this version [2.2.3, Pro 8, macOS 0.14.6 (18G3020)] yesterday and use digital capture for a while, as well as the measurement feature - great feature, counting digital edges is very handful, thanks!

Moving back to my code, I heard that the MacBookPro fans were spinning unexpectedly fast. Using iStats Menu, I noticed that Logic2 which was fully idle for a couple of minutes was sucking out 130% CPU, that is more that a full core @ max power. Logic2 UI was not stuck, I’ve been able to successfully restart a capture. However its CPU time kept skyrocketing at over 100%, until I shut it down and restarted it…

On start up + idle, it already eats up 8%, which is unexpected and not really nice for a laptop, but not a show stopper. However 100% is. I’m not yet sure how to reproduce this, I’ll try to find a way.

BTW, it would be nice to add a link to the changelog from the About dialog, to be able to retrieve the changelog at any time, not only on the first run after an upgrade.

Anyway, again: amazing job.
Saleae HW build fantastic products, and now the SW/GUI make them really wonderful.

[rani]

First of all, thanks!

On start up + idle, it already eats up 8%,

Does it happen every time that you open the app?

However its CPU time kept skyrocketing at over 100%,

Please let us know if you can reproduce it. It shouldn’t happen when the software is not processing data.

BTW, it would be nice to add a link to the changelog from the About dialog

Indeed, we’ll add that!

[Emmanuel]

Does it happen every time that you open the app?
Yes, in both non-connected/demo mode and w/ an actual Saleae device connected, and it also reverts back to this value (7.5…8%) after a capture when the app is idled.

There is another, unrelated usability issue:

1. set a timer to stop the capture after some time (e.g. 2 seconds)
2. set a trigger (for instance, falling edge on a digital channel)
3. start the capture
   → this work as expected: wait for the trigger, then capture 2 seconds

Now
4. go back to the timer pane
5. start a capture
→ this time, the capture no longer waits for a trigger, and stop 2 seconds after the start button has been triggered

So

• when the trigger pane is shown, trigger + timer are used.
• when the timer pane is shown, the trigger is ignored.
  This is quite difficult to follow, memorise and IMHO a UI usability issue.

The capture behavior should not depend on which pane is viewed when the start button is hit. I think there should be something like checkbox to select which capture “filters”/criteria to activate/enable, it should not depend on a particular viewpoint. Alternatively, the Looping/Timer/Trigger button could be used to select a pane, and double clicking them should enable/disable the associated feature (w/ color feedback)

[rani]

It sounds like a bug. We’ll look into this (and get back to you).
Thanks for letting us know!

[rei_vilo]

@rani

How about this?

@rani Could you please change the colour of the labels on the left (e.g. Channel 1 Async Serial)? Please use white instead of light grey!

[rei_vilo]

The Capture Settings pane is still hard to read. Ok, numbers of the channels selected are in bold white but the unselected channels are hard to read in light grey.

The ticks in colour aren’t readable enough (e.g. channels 4, 5, 6 and 7 above). Could you please consider the other presentation from Alpha 13 below, obviously with the corresponding colours?

I’m using Logic on a MacBook Pro Retina. Maybe this explains all the comments about readability.

[rani]

We haven’t forgotten, no worries. It’s on our designer’s checklist to fix that