Hi. I’m working on a team where we have a lot (Think 100+) of tests currently interfacing the logic1 software, that we’d like to migrate to using logic2. However, the experience is that when running a test using the logic2 software, the unit can’t run a test using logic1-software afterwards without being power cycled.
Is there any way to circumvent this in software, without having to power cycle the units? So we can run a test using Logic2 software, and then Logic1 software without issue on the same (old-ish) Saleae Logic. We would otherwise have to migrate all tests being run on a single node at the same time, including legacy tests.
@mthu Which specific Saleae Logic model do you own out of the ones pictured below?
Also, what specific versions of the Logic 1.x software, and Logic 2.x software, are you using?
I tested the following using a Logic 8 (I did not test with our Socket API for Logic 1, or Automation API for Logic 2 to try and isolate the issue to the software only).
Connect Logic 8 directly to the PC via USB cable
Open the Logic 2.4.14 software. Ensure the device connects to the software and start a capture.
Close the Logic 2.4.14 software.
Open the Logic 1.2.40 software. Ensure the device connects to the software and start a capture.
As a starting point to debugging this, can you confirm that the above steps work on your end?
We’re running Logic 1.2.29 on Debian, along with Automation API for Logic 2 in our testsetup.
We’re using
SAL-00115 Logic Pro 16 Black
SAL-00116 Logic Pro 16 Red
As well as non-Pro Logic 8s, but mostly Pro 16s.
However, I just did a quick test, and I can confirm the above does not work on my end - downloaded 1.2.40 to sanity-check that it’s not an 1.2.29 issue:
I connected my logic8 to my Debian machine, and booted up Logic 1.2.40.
Opens up nice and clean, can do a capture.
Shut down Logic 1.2.40, Afterwards, booting up 2.4.14 (I only start it and let it initialize the analyzer, I don’t do capture).
Shutting down 2.4.14, Afterwards, again, booting up 1.2.40, and I get the following error message: A Logic device was found, but there there was a problem connecting to it. This is probably because we don’t have permissions to access it. Take a look in the drivers folder for instructions, or run this program as root (i.e. use sudo from the command line). This could also be caused by having multiple instances of the Logic software running. Let us know if you still have any problems.
The solution to be able to use 1.2.40 again is for me is unplugging and replugging the analyzer.
Note that the logic analyzers LED turns blue from off when booting up 1.2.40 and remains blue, and when then booting 2.4.14, the LED goes green. The LEDs don’t go off until the device is unplugged.
HW version used for testing:
Model: Logic 8
Serial #: F4B43DDB708E136E
Hardware Revision: 1.0.0
The 1.2.40 and 2.4.14 were fresh downloads from the website made today.
The leading hypothesis in the house is that it’s the firmware write by 2.4.14 that version 1.2.29/1.2.40 doesn’t want to downgrade. Compared to your test it looks like we are also impacted by running Debian and not Windows - but I don’t know if you’ve seen anything in this area before?
@mthu Thanks so much for providing a detailed way of reproducing the issue. I was able to reproduce it on Windows 10 by following the same steps you provided.
To set expectations properly, we unfortunately won’t be able to provide a fix for this, as this very likely requires an update to our older Logic 1.x software for which we no longer provide official support for. Having said that, we still do provide it as-is for anyone that needs it.
The best solution would be to migrate your automation test flow to use our Automation API for the Logic 2 software.
In case you run into any issues with that, or have any specific questions for us, we’ll be certainly happy to help look into those for you!
