You might notice that we’ve skipped Logic 2.4.47. We decided to cancel that release, but still sent it out to a few users who needed priority bug fixes. The release notes below contain changes from both releases.
What’s New
Add support for new Logic Pro 16 hardware revisions. (Minor supply chain changes, no functional differences.)
Add support for new Logic MSO hardware revisions.
Improvements
Reduce notification noise when switching between loaded session tabs.
The analyzer settings channel selector now shows MSO Digital channels with improved indicators.
Bug Fixes
Fix bug where if a Logic MSO derived digital channel threshold was out of range, new data would not be displayed until it was corrected.
Fix bug where adding an analyzer from the automation interface or the MCP interface while a capture was in progress would not return until the capture was manually stopped.
Fix issue where gaps appear in Logic MSO logic analyzer channels each time they are enabled.
Displayed time values like 0.6ns now round up to 1ns instead of down to 0ns.
Fix crash when closing Logic MSO sessions rapidly.
Fix issue where the annotation rail of digital channels still shows the trigger selector for loaded MSO captures.
Fix bug where centering the trigger at the wrong time lead to large trigger offset and a persistent crash on connect or launch with Logic MSO.
We were under the gun to get that public release out, because at the factory, we needed to change FPGA part numbers again (hello hardware revisions 13, 14, and 15) for our logic analyzer devices due to ongoing supply chain issues. We needed to get the software out the door to support those new models. (Specifically, a mistake was made that made this urgent: At the factory, we did a very small early pilot run of the new hardware revisions. Normally, I get all those units and keep them. I forgot to send those instructions this time, so the factory went ahead and shipped them with the normal build. A few weeks later, a new user wrote in mentioning the software reported that their brand new Logic Pro 16 required a software update, even though they were on the latest version.)
Regarding the analyzer settings, sorry about that! I was planning on letting this get fixed by default by fixing an upstream issue, where logic analyzer probes take so long to initialize that we just pretend they aren’t there when a new MSO is connected, triggering a settings migration to remove those channels from the analyzers. Unfortunately the fix keeps getting held up. (It’s a combination of firmware and software changes). I’m swamped at the moment, but I suspect a fix could be introduced in the meantime to restore the analyzer settings once a logic analyzer prove is detected. In the short term though, I recommend using presets to backup your settings. Sorry about this!
I’m pretty happy about the landslide of other bug fixes the last software release managed to include though.
No problem at all. The amount of work your tiny team gets through is amazing.
In the past I’ve used the presets feature so little I struggle to remember I’ve actually saved a preset, especially as I usually go for most of the week without restarting Logic. The presets workflow seems to work much better now than I remember the last time I used it years ago. I couldn’t tell you what changed though. That said, I’d still somewhat prefer to save presets as files with a file save dialog so I can save presets in the context of a project they pertain to. No panic for that change though!
In the mean time presets are a good work around for the analyzer issue so really, no panic there either.
Hello, I have conducted tests on the Logic MSO after receipt and identified several issues:
There is a phase offset between digital and analog probes, which becomes obvious when testing high-frequency signals such as the 50 MHz signal.
Severe packet loss occurs. We purchased this 1 GS/s logic analyzer for high-frequency signal measurements, e.g., 200 MHz signals. However, I found that packet loss readily appears when measuring signals above 30 MHz. The issue worsens noticeably when more than two digital channels are enabled. Accuracy is a critical specification for measurement instruments. Once packet loss happens, the data becomes inconsistent, not to mention the loss of vital raw data.
The trigger mode does not clear oscilloscope data every time signal capture restarts, which is counterintuitive for normal operation.
Phase offset and packet loss are critical problems. It is possible your RLE compression algorithm cannot handle high signal transition rates. A 1 GS/s logic analyzer is designed specifically for high-frequency testing. If the RLE algorithm cannot meet this requirement, we suggest adopting alternative processing methods or increasing the USB throughput.
@1179204235 Sorry for the trouble with that! I received your email via our customer support inbox. Let’s continue chatting there to debug this (I requested a few pieces of information to try and help us get to the bottom of this issue).
I measured the same 50 MHz sine wave with an analog probe and a digital probe. A phase offset exists between the two captured signals. Please help check what causes this issue. Thanks.
By default, the derived digital (from analog channel) has different logic thresholds than the digital probe channels. Did you set all channels to the same digital threshold settings? Even if set to exactly the same voltage thresholds in the software, there will likely be some variations in the hardware (actual DAC voltages, precise analog comparator switching point, signal propagation & filtering delays, etc.).
All that being said, I do wonder how Saleae has accounted for all the real-time delays throughout the different signal paths, including:
Probing and cabling differences
analog vs. digital probe loading
variations for each channel path
unique signal propagation delays
Analog filtering group delays
Digital probe USB design constraints
Digital logic comparator latencies
USB digital probe communication latency
USB digital probe sample clock sync across different probes
Analog vs. digital sampling clock domains
Any phase mismatches between interleaved ADC sub-converters
Edge speed dependencies: signal slew rate and rise times
Definitely, the Logic MSO digital probe USB-based design has some unique challenges vs. having digital inputs directly sampled on one digital parallel port all together.
Finally, instead of using a sine wave, you could test with some other input waveforms to help identify the digital phasing problem cause(s):
Fast Edge Digital Square Wave: Use a clean, fast-transition square wave to help isolate true propagation delays and jitter from slow-edge threshold issues
Slower Triangle Wave: Observe exact threshold trip points and check if custom digital threshold settings can compensate for any variations