two or more ofxlaser controllers in one network?

[GvBon]

I tried opening two ofxlaser apps to see if it was possible to use app A for laser A and app B for laser B in the same network.
This did not work. One app would end up with all lasers and the other with none. Is there a possibility to do so?

[sebleedelisle]

This should actually work fine as long as you don't connect to the lasers in both. Good luck!

[GvBon]

So you say it should be possible to run two ofxlaser apps at the same time on one computer connected over one network to two etherdream dac's where app A controls dac A and app B controlling dac B?
I tried and that didn't work.
Probably I did it a wrong way. What is the right way, if there is one?

[sebleedelisle]

I am saying that it certainly works here for me! Here's the process :

• open one app, make sure it hasn't automatically connected to any ether dreams. If it has, disconnect it. Then click the disconnect button again to completely clear it from the assignment panel
• open the second app and then do the same thing
• Now connect to the ether dreams in each app

Note that if you ever had a time when an ether dream was connected to more than one app, you will most likely need to reset it, as they don't like this and go into a weird state! I am putting in protections to stop this happening though.

Seb

[GvBon]

Hmm, would love to get this to work but not yet happening for me.

You say click the 'disconnect controller' button twice. This is not possible as the button disappears after the first click. The 'refresh controller list' button remains.

When I start both apps the first ends up with 3 controllers listed and the text: 'no laser controller assigned' and the second app has no listed controllers: 'no laser controllers found' and 'no laser controller assigned'.

I guess you mean by resetting the Etherdream controller powercycling? I tried but no result.

[sebleedelisle]

What version of ofxLaser are you using? Can you send me your source code?

…

On Thu, 30 Jan 2025 at 12:26, GvBon ***@***.***> wrote: Hmm, would love to get this to work but not yet happening for me. You say click the 'disconnect controller' button twice. This is not possible as the button disappears after the first click. The 'refresh controller list' button remains. When I start both apps the first ends up with 3 controllers listed and the text: 'no laser controller assigned' and the second app has no listed controllers: 'no laser controllers found' and 'no laser controller assigned'. I guess you mean by resetting the Etherdream controller powercycling? I tried but no result. — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3CESEOMFEA3GB7ZC6CR32NIK6JAVCNFSM6AAAAABWC2O37KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRUGM3DSMRZGU> . You are receiving this because you commented.Message ID: ***@***.***>

[GvBon]

Last version, just downloaded and tested again.
Source code is your example_Hellolaser.

Maybe I am doing it wrong. I have tested in two ways:
one: running two times Visual Studio (example_Hellolaser)
two: running twice the "example_HelloLaser_debug.exe" from the BIN folder.

[sebleedelisle]

Oh right, Windows 😬 Although I regularly test and build with Windows, I never tried this specific thing on Windows before until just now, and wouldn't you know it, it doesn't work! I have no idea why, sorry. It works fine on MacOS of course. 😅 It's such a low priority that I don't think I can commit any time to fixing this, but if you figure it out please let me know or make a PR. Thanks! Seb

…

On Fri, 31 Jan 2025 at 11:05, GvBon ***@***.***> wrote: Last version, just downloaded and tested again. Maybe I am doing it wrong. I have tested in two ways: one: running two times Visual Studio (example_Hellolaser) two: running twice the "example_HelloLaser_debug.exe" from the BIN folder. — Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3CEWVSVCPA5JX3ZLJE5T2NNKHNAVCNFSM6AAAAABWC2O37KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRWHE2DCNRRHE> . You are receiving this because you commented.Message ID: ***@***.***>