Error creating output thread...again!
Posted: 21 Oct 2009, 07:26
(Sorry for starting a new thread but I think I have searched the forum to no avail)
Ok...I’m having trouble with Freestyler talking to my new Enttec USB Pro. They were friends for a couple of weeks and now they have mysteriously stopped talking?
Here’s what I’ve checked so far:
1) The drivers for the dongle are correct – FTDI for the USB Pro
2) I have identified the correct COM port via the device manager
3) I have selected the correct COM port when I set up Freestyler
4) I have changed the COM port a number of times and managed to get the dongle working (the Pro Utility software from the Enttec website tells you when it’s connected and even allows you to send out a ‘test’ DMX signal on the first 16 channels. I checked this by connecting it to a fixture)
5) Tried ‘running’ : regsvr32.exe threading.dll (not sure what this does)
6) Try to identify any processes running in the background that may be competing for the port and close them down.
7) Updated the firmware on the dongle a number of times (version 1.44)
Does anyone have any other ideas as to what may be happening?
Thanks in advance!
Ok...I’m having trouble with Freestyler talking to my new Enttec USB Pro. They were friends for a couple of weeks and now they have mysteriously stopped talking?
Here’s what I’ve checked so far:
1) The drivers for the dongle are correct – FTDI for the USB Pro
2) I have identified the correct COM port via the device manager
3) I have selected the correct COM port when I set up Freestyler
4) I have changed the COM port a number of times and managed to get the dongle working (the Pro Utility software from the Enttec website tells you when it’s connected and even allows you to send out a ‘test’ DMX signal on the first 16 channels. I checked this by connecting it to a fixture)
5) Tried ‘running’ : regsvr32.exe threading.dll (not sure what this does)
6) Try to identify any processes running in the background that may be competing for the port and close them down.
7) Updated the firmware on the dongle a number of times (version 1.44)
Does anyone have any other ideas as to what may be happening?
Thanks in advance!