Original LXSeries Forum

I am using LXConsole 3.1.3 (or thereabouts; downloaded on 8th June) on a Mac Mini running Mountain Lion, and have found that although it works fine on the first account I ran it on, it doesn't work on other accounts, even when made into administrator accounts (No connection, or similar, is displayed). Is there a known issue which would cause this? The rest of the software appears to work.

One thing which now occurs to me is that the user for which it works might own the application files. Is it possible that the application needs to be able to write to itself? (I'm away from the machine in question until tomorrow evening so can't check until then).

Thanks for a nice tool!

I did a test with LXConsole running on a Mac Mini (10. with a default (non-administrator) student account and an administrator account. I was able to switch back and forth by logging out of one account and into the other and use the same ENTTEC DMX-USB Pro widget to get separate output from each account. There was no need to unplug or otherwise restart the widget when switching between accounts. This setup used the D2XX driver that is installed with LXConsole.

Although I did not test the VCP driver, it is very likely not to tolerate being opened from more than one location. The VCP driver actually prevents the D2XX driver from working because it holds the connection to the widget open. My guess is that the same thing would be true once it was opened from one account, the widget would not be available from another.

Unless you specifically installed the VCP driver, you are probably using the D2XX driver. So you should be able to switch between users.

Each user will have their own preferences. So, it is necessary to check (for each account!) that DMX Output is set to "DMX-USB PRO". You should also look in the DMX Info tab and be sure that the D2XX driver is selected. And finally, in the DMX In tab that DMX input is NOT set to use the DMX-USB Pro.

If you started with an older version of LXConsole, you may have installed the VCP driver. In which case, you may want to consider uninstalling it so that you can use the D2XX driver instead. The D2XX driver will not work if the VCP driver is installed.

Hmm, odd. i'm pretty sure I'm not using the VCP driver. The only difference between our setups is the fact that mine is a Pro2 device rather than a Pro device.

The system will be coming off the show on Sunday so I'll see if I can do a little more digging then (and will also try to reproduce on another system).

After investigating this, it appears only to affect the Mk 2 widget. There are two solutions: You can simply physically unplug and re-plug the widget after switching users. Or, the latest build 3.1.10 adds the ability to use the Plug/Unplug Widget command to reset the connection after a user switch.

The cause of this problem is unclear. It may be a firmware issue with the Mk2 widget. LXConsole correctly closes the FT_Connection when it quits which is what happens when you log out one user. This should be essentially the same as unplugging. But, for some reason it is not.

The actual solution temporarily switches the Widget into read mode and flushes the connection when the "Plug/Unplug Widget" command is selected. Why this works is a mystery.

Thanks again for the reply and for the fix. I've used the software on another couple of systems since and haven't seen any issues.