A quick release to get an important bug fix out. Also, low analog sample rates are available again! Perfect for long duration analog recording.
Low analog sample rates are back!
Note to people updating while Logic 2 is running: The “Logic not exiting” issue this update fixes gives the installer grief (on Windows at least) due to Logic not exiting during the update process! You can use Task Manager on Windows to kill the Logic processes (there are several and you probably need to scroll down to see them). You should only need to kill the one that is showing some activity.
Hmm. At the end of running the installer (and killing the two Logic processes as per the above comment), I got some error missing about a missing .cab-file and couldn’t proceed with the install. So in the end I was left with neither 2.3.6 nor 2.3.7 intalled
Are the colors less vibrant in this version than in 2.3.6? Or is it just because it’s Monday?
Hm… Sorry for the mess!
I suggest killing all Logic.exe instances (or just rebooting the computer), then uninstall 2.3.6 using “Add or remove programs” from the windows settings, then install 2.3.7 from the installer downloaded from the website.
You may want to manually delete “C:\Program Files\Logic” after 2.3.6 is uninstalled just to be sure.
Let me know if you still get any errors when installing 2.3.7
Nope, I don’t think we changed any colors in the app in between those two releases.
Downloading and running the installer worked fine
Just a recount of the open questions from previous releases:
px = ms
SDA label on the I²C configuraton pane.write or read on the terminal pane.read to for read from on the terminal pane.@rei_vilo and Saleae - I agree that many of your items in the above list would be great. Some could probably wait.
For example I multiple character search would be good, and likewise I am not sure if it is only currently the first character… When many times I may want to contains…
Terminal pane - As you mentioned it might be nice to see new line between some of the SPI/I2C data on the other hand, although would have to trade that off versus how much data you can see at once.
I do wish that the line ending stuff could handle line endings of just CR, or LF, or CR and LF. Could make it settable. or could simply see if you get one and the next one is the other ignore it…
Again other things on my wish list:
a) SPI and or HLA on SPI - With many devices there is another IO pin (often called DC for Data/Command), that emulate 9 bit Data. Wish you could somehow could optionally choose this extra signal and for example maybe record that as well with Reports and the like. Important for HLA, where you see that DC is asserted and as such you show which COMMAND was output for some device like a display…
b) HLA support for other analyzers, like USB…
b1) USB analyzer better choosing of what data shows up and/or reports. Again most of the time I wish to capture mainly only SETUP/INPUT/OUTPUT along with the DATA.
c) The ability to see multiple timing markers on the display. I often post pictures from Logic showing the timings of different sections of things.
Like how much time a SPI output took, and how long of gap between transfers…
d) USB capture dream - Wish I could capture USB protocol, when USB in High Speed (480 MBPs) but again probably not very likely… But one can always dream 
Again I like how the product is coming along.
Thanks @rei_vilo for summarizing these in a quick list! We’ve got this all logged internally now - except for Q3. It’s likely we won’t change it, but we’ll keep an eye for more feedback on it. Feel free to post that on the ideas page as well.
@KurtE Thanks! I see you put your vote in below. We’ll keep an eye on this. This seems like the most popular analyzer right now that is requesting HLA support.
For item c), can you describe what you mean by this? The Logic 2 software supports displaying as many timing markers as you like. I’m sure I might be interpreting this incorrectly. Let me know.
As for item d), we definitely need new hardware with higher sampling rates to support this.
For a), it looks like this would require reworking the SPI analyzer itself (to add a new data line). You can use our protocol analyzer sdk. Otherwise, you can post this as an idea too.
What I would do in original software was to add measurements… Example maybe see how long a packet took and how long of a delay to the next one…
Example:
You can see the two measurements using the old software. Note: This was mentioned in previous posting as well. I think it might have been: [Your Input Needed] Timing Marker User Interaction (Poll) - #5 by kazink
Note: I also liked back then when you were trying to enter a new measurement or the like, it would try to logically snap to a start or end point near where I have the mouse.
Note: a) was mentioned in previous thread:
A multiple input HLA seems like it would fit the bill for a “SPI with addons” analyser. I have a feeling support for multiple inputs by HLAs is on the roadmap somewhere. It has certainly been discussed to some extent in the past. See https://ideas.saleae.com/b/feature-requests/multiple-inputs-to-hlas/.
I’m not sure if it has already been mentioned somewhere. It would be much nicer if the SPI clock arrows matched the channel colour. See attached example:
@KurtE I’m starting to see what you mean. On Logic 2, when you add timing marker pairs, it looks pretty messy. Not easy to see the time difference between markers. See image below:
Would some sort of display between the timing marker pairs help? Like below?
Another idea would be to display “always visible measurements” above our measurement selection window (such that some measurements are always visible without having to click in the pink selection window to see them).
Let me know if you have any ideas on how we can best achieve what you need.
Regarding your note below:
Note: I also liked back then when you were trying to enter a new measurement or the like, it would try to logically snap to a start or end point near where I have the mouse.
The timing markers do snap to the nearest edges. Let me know any more details regarding the behavior you are describing.
Seeing the measurements (at least as an option) would be beneficial to me, especially when you are using the measurement to document the information.
Thanks
@segmentation I agree with you. We have this on the backlog now. Thanks!
