While the FAQ says it can’t be done, I’ve been using two LogicPro 16’s on a windows 11 computer using two instances of Logic 2.4.13 to collect data simultaneously from the two devices. After some searching I find a few other mentions of this on the forum, but little discussion on how to make it work well.
The trick is to get the second Logic device to connect to the second instance of the program so that you have “1 device connected” in each window rather than 2 and no devices. It takes a few connect/disconnect cycles, but eventually it works. I’ve also tried to get 3 & 4 devices running, but have only had real success with 3 for 48 channels total, running at 1.5625 MS/s , but at that rate either the USB or the display routine is getting bogged down, and it’s less reliable.
The question is, can this be made to work more smoothly? All that would be needed would be to have the Logic software request approval before connecting a second device, or something along those lines. It would also be nice to have simultaneous triggering of multiple instances, etc.
Peter
@pesherick Thanks for posting your workaround! I saw you had posted your workaround last month on an existing ideas post for recording from multiple Logic devices on the same PC (linked below).
We’re unable to provide official support for this set up, or in case any issues come up with it, but I’m glad to hear you’ve got something working on your end. Our dev team (3 members at the moment) is currently heads down on other high priority projects, but we’ll continue to keep an eye on more requests for this feature in the idea post above.
Feel free to post any updates you have here in case you’re able to learn more from this set up, or if you happen to have any updates on workarounds with regards to the connection hiccups you were seeing.
Any more thoughts on this? Running the most recent software (v2.4.44) and still have to perform Peter’s solution with one Logic MSO and one Logic 8. (It works with these two devices as well, with the Logic MSO connected and actively recording).
Any more bandwidth on the team to look back into this feature?
@thomas.jacob.bryant Peter’s workaround is currently the latest update on this topic. We’re continuing to track this request here, however, it is currently not on the roadmap to officially support.
Hi,
We have now 2026, I have the same problem now, That I would like to use minimum two independent Saleae Logic2 Apps with two Saleae Logic devices.
I do SW myself, and it shouldn’t be a big issue to wire up a command line argument you give at startup to the USB selector, especially since the device itself got a serial number in the USB identifier.
Honstly, I wanted to scale-up our agentic SW setup, and I did not expect that kind of limitation for such a tool that is used otherwise very successfully by so many professionals.
Please consider to re-priorities such small extension for the next release!
I propose a simple cli parameter, similar to the “automationPort” argument, where you can set the usb serial number of the device that should be used.
I wonder, how you test everything yourself with-out such feature.
We’re not ready to commit to it yet, but I have been experimenting on supporting this in a few different ways.
Today, our new headless automation library supports running simultaneous recordings from different devices.
So if you have 2+ devices connected, you can start recordings an each one individually through one instance if the library. It does not support 2+ independent instances though, and this won’t let you record interactively with the GUI software, but it can save *.sal files that can be opened with the GUI software. I’ve tested this with 4x Saleae Logic Pro 16s at once. Note - by default, a single USB host controller shares bandwidth between all connected devices. If your computer has multiple USB 3 host controllers, you can connect your units to different hosts to avoid the bandwidth sharing penalty. I was able to split my Logic Pro 16s between two hosts to get 100 MS/s digital on all 64 channels at once.
This is a big change from using the automation interface in the Logic 2 GUI, which will return an error if you try to start a recording while another recording is in progress.
Let me know if you try it, and if you have any issues with it. We basically got this for free in our new architecture but we didn’t advertise it because our main goal was to provide a headless implementation of the existing experience.