Having a DMX problem, "access to port denied"

[gmijackso]

I'm having a problem getting my DMX to work. Hopefully somebody will know what I'm doing wrong.

I have the Enttec DMX Pro dongle, and using Vixen 2.0.5.0 as is suggested in the sticky.

I am able to set up my controller in my profile, Com4, baud: 57600, Data bits:8, Parity: None, Stop bits: One.

I have the DMX add-in selected to start dmx stream on Vixen startup.

When I try to play a sequence I get two errors.
First is: "Enttec DMX USB Pro: Access to port 'COM4' is denied"
I then click "ok" and get: "Plugin Error Access to port 'COM4' is denied. Execution has been stopped"
I then click "ok" and I'm back vixen doing nothing, just like before I try to start the sequence.

I'm sure it's probably something simple, I'm new to Vixen this year, and the DMX is new to me this year too. Ran very simply blinky flashy last year using x-10.

As a note, if I run the Enttec pro utility with Vixen closed to see if it can see my dmx dongle, everything seems to be fine. If I click "find pro and connect" under the com port area, it is able to find it on Com 4, connects, and retrieves serial number and firmware version (1.44 if it matters) just fine.

Thanks for any help, hoping to get the lights up while I'm off work for Thanksgiving!

[omzig]

This problem has come up a several times before:

[/URL]http://www.doityourselfchristmas.com/forums/showthread.php?t=5185 (http://www.doityourselfchristmas.com/forums/showthread.php?t=5228)
[URL]http://www.doityourselfchristmas.com/forums/showthread.php?t=3495
http://www.doityourselfchristmas.com/forums/showthread.php?t=4372
http://www.doityourselfchristmas.com/forums/showthread.php?t=3253

[wjohn]

ah yes,

I too have seen this. KC has said that he would look into it, I have not seen a fix or patch posted.

I did what DynamoBen suggested, and reverted to the 2.0.5 version of code.

My fingers are crossed. I so want this show to work, each and every day for the next month.

[gmijackso]

Ok, so I'm confused. It seems that everybody has a different "fix" and somehow, some fixes don't work for some people, and one persons "fix" was to go to 2.0.7, which from what I understood dmx didn't work past 2.0.5, so it's something of a miracle right?

I'm already running 2.0.5, so I'm not real sure what to try. I guess I'll start working my way down the list and hopefully it'll get working.

[wjohn]

Honestly,

There is no fix. the advice to go to 2.0.5 beta seems to be the best.

http://www.doityourselfchristmas.com/forums/showthread.php?t=4737

hopefully KC is working on this issue, with the amount of DMX installed growing within the Vixen community, we are running the risk of orphan versions of code if we get stuck back on 2.0.5 Beta.

The ENTTEC Pro is made here in Melbourne so it must be a good product.

[electr0n]

The ENTTEC Pro is made here in Melbourne so it must be a good product.

;) I sure hope so because I am placing an order for one this weekend.

[DILA]

Another thing to check is the USB port on the Enttec Pro, mine is very loose and vixen woud be going along and bang, port error. My laptop was loosing the connection to the Pro. Fix was to bend the tabs in the USB port for a tighter fit, I then moved it around until it connected and duct taped to the desk it in that position :) So far it seems to be working.

Bob

[gmijackso]

There is no fix. the advice to go to 2.0.5 beta seems to be the best.

Yeah... problem is, even 2.0.5 won't work for me at the moment. I was planning on using a different PC for the actual display computer anyway, so hopefully I won't have the problem there. But still can't get it to work on my laptop to test with.

I'm pretty sure I even had it working at one point on 2.0.9 though I never hooked any devices up to the dongle then. I was just testing the dongle and got blinks on the dongle when I was sending dmx so I assume it was working then. Don't know what changed, but I started getting the error, and downgraded to 2.0.5 after reading the sticky, and still had the problem, and then posted.

I guess I'll finish sequencing, then hook everything up to the other computer and hope I can get it working.

[wjohn]

as soon as I get a COMM port not avail, Rtr issue, I find the only fix is a complete reboot. Re-starting vixen is not helping at all.

I have emailed/vmailed KC.... Fingers x-ed.

[P. Short]

I suspect that Vixen has obtained a lock on the serial port. This prevents any other program from accessing that port, and somehow or other Vixen is failing to unlock the port when it is finished.

[gmijackso]

Well, if vixen were locking the port, shouldn't unplugging the USB device solve that problem? I mean, once it's unplugged, the port disappears. Also, if Vixen were locking the port and never unlocking it, i.e. even after exiting vixen, then the utility wouldn't be able to connect to the port since Vixen would still have it under control, and I'm not having that problem.

You do raise an interesting point though. Ponder this. Perhaps, the DMX add-in, is grabbing the port on startup (as we tell it to) and when a sequence is played, Vixen tries to "re-grab" the port and is unable since the add-in is already using it. How necessary is the add-in?

I can kinda verify this? If I launch vixen, and turn on the DMX in my profile, but leave the plug-in off, my dongles LED blinks and I'm able to start a sequence without any errors. I can't check to see if I'm actually controlling anything (I bought the wrong 5pin to 3 pin adapter, new one is on its way). Can anybody confirm? Perhaps the add-in just isn't necessary?

[gmijackso]

I spoke too soon. It let me play the sequence once, then bombed on the second time. Shut down Vixen, and unplugged the dongle. Started vixen, plugged in dongle, opened sequence, started sequence, and everything worked (even the backwards cabling worked) I as able to control the first 4 channels of my display (that's all I have hooked up in my test). Gonna play around some more and see if I can get any more steps to breaking it or making it work.

[RJ]

This is an interesting problem. I can tell you that you do not want the DMX addin checked or it causes issues and always has on the pro or lynx dongle. This was done for the open to have vixen start outputting DMX on startup.

The most interesting thing is that not all people have this issue. It seems to be certain ones. For example, I have never seen that error. I have never had this error. and a bunch of my users have not either but some have.

Is it to do with the keep port open setting as I know this will cause issues. I think this was added to do something for the Renard's? Phil you could answer this as I am not sure. I remember it being added but not why.

It appears to be related to the software as I have seen both Enttec pros and the Lynx Dongles have it and they are very different hardware.

Most people can remove vixen totally off the computer including profiles and install 2.0.5 and it will work OK then, but some say it did not help them.

I also know that having a program and setting "use sequence plug ins" can cause problems as it seems to try to open the plugging again at the next sequence in the program.

It may well be a mix of these settings and this is why starting clean fixes it.

Just some input from someone trying to brainstorm.

RJ

[P. Short]

I'm not sure anymore why the 'keep port open' setting was incorporated. I think that one issue had to do with cross-fading sequences (where you want to enable the setting) and the other issue was something performance related or timing related (something to do with either the serial port or slow computers, nothing particularly specific to Renard).

[RJ]

I'm not sure anymore why the 'keep port open' setting was incorporated. I think that one issue had to do with cross-fading sequences (where you want to enable the setting) and the other issue was something performance related or timing related (something to do with either the serial port or slow computers, nothing particularly specific to Renard).

Thanks Phil, Thought it was but I think your right about it now that you say it. It had to do with crossfade I think it was closing and not opening the port agian or something so they added that option. I know it will give you problems on a standard setup with the DMX plugin.

RJ

[DynamoBen]

Another option is to change the com port that the dongle uses. The FTDI driver allows you change it. Go to the device manager, drop down Ports (COM LPT), select the FTDI com port and select properties. Somewhere in there (changes based on driver version) is a drop down for the com port number.

[nwcworld]

OK I'm having the same problem when i chose the Enttec DMC USB Pro plug-ins first it will say there is a problem then tell me access to port denied. i reinstalled the USB drivers and tried again, No errors when sequence is run but it still wouldn't run the relays. i unplugged the USB cable and replugged it back in when i did that only relay 3 kicks in and won't shut off, all other relays do nothing. does any one know how to fix this error?:confused:

[Macrosill]

OK I'm having the same problem when i chose the Enttec DMC USB Pro plug-ins first it will say there is a problem then tell me access to port denied. i reinstalled the USB drivers and tried again, No errors when sequence is run but it still wouldn't run the relays. i unplugged the USB cable and replugged it back in when i did that only relay 3 kicks in and won't shut off, all other relays do nothing. does any one know how to fix this error?:confused:

But you are using a kit74 parallel port relay board, not a dmx controller. A usb-parallel converter will not work.

[Valerie]

Hello,

I've been searching every topic about this problem and I also have the same problem.

I bought the DMX Pro USB from Enttec. I installed it on my laptop and there was no problem at all untill I removed some other software (daslight, sunlite, freestyler dmx, mydmx). Then suddenly it couldn't work anymore : I got the errors with the com port (access is denied), like others already mentioned.
I returned my pc to an older status, where all other software I removed was back again, now there was no problem anymore. It worked fine again...
Strange !!

But now I have a computer that has been formatted and there is nothing on it, except the Vixen software and I also have this problem again: access to com port... is denied .... etc, etc.
I also tried to give it a new port, in the driver AND in the software. The problem stays... !!!

Please help us out ! I want to try everything !

Kurt & Valérie

[DynamoBen]

But now I have a computer that has been formatted and there is nothing on it, except the Vixen software and I also have this problem again: access to com port... is denied .... etc, etc.
I also tried to give it a new port, in the driver AND in the software. The problem stays... !!!

Please help us out ! I want to try everything !


What version of Vixen are you using? Also where did you purchase your dongle (from the forum or from Enttecc)?

[RPM]

You mention that this is for an Enttec USB Pro dongle, so you can try their troubleshooting tutorial here http://www.enttec.com/support-center/index.php?x=&mod_id=2&id=41 and see if this helps.



Hello,

I've been searching every topic about this problem and I also have the same problem.

I bought the DMX Pro USB from Enttec. I installed it on my laptop and there was no problem at all untill I removed some other software (daslight, sunlite, freestyler dmx, mydmx). Then suddenly it couldn't work anymore : I got the errors with the com port (access is denied), like others already mentioned.
I returned my pc to an older status, where all other software I removed was back again, now there was no problem anymore. It worked fine again...
Strange !!

But now I have a computer that has been formatted and there is nothing on it, except the Vixen software and I also have this problem again: access to com port... is denied .... etc, etc.
I also tried to give it a new port, in the driver AND in the software. The problem stays... !!!

Please help us out ! I want to try everything !

Kurt & Valérie

[Valerie]

I bought the Enttec DMX USB Pro from a shop and was never used before, it's new.

I've already tried everything from the Enttec Support page, but it's still giving me the error. My USB Serial Port is on COM4, does it really have to be COM5 ? I've already tried that and still gives me the error...

What do I do next ?

Please help me !!!

[DynamoBen]

Does your dongle work with Enttec's test utility?

[RPM]

Have you tried changing your USB cable? Sometimes that helps.

As DynamoBen mentioned, have you tried the Enttec pro utility to see if it works with that application?
You can download it from their website here http://www.enttec.com/download/pro_utility_setup.exe

Are you connecting it to a USB1.0 or USB2.0 port on your computer? They say it should work on a USB1.0 port, but I've never had any luck doing so.

Also make sure you are not using the DMX add-in to start the DMX stream on Vixen startup. This is for the DMX Open and if you use it with the DMX Pro can cause problems.

You don't need to use COM5, you can use whatever COM port is available on your computer, but you must change the com port in Vixen to match whatever port your DMX dongle is on.

Robert


I bought the Enttec DMX USB Pro from a shop and was never used before, it's new.

I've already tried everything from the Enttec Support page, but it's still giving me the error. My USB Serial Port is on COM4, does it really have to be COM5 ? I've already tried that and still gives me the error...

What do I do next ?

Please help me !!!

[Valerie]

Yes, my dongle works fine with the Pro Utility test.

I've got the answer to my problem in the sequence from someone (Robert) who has had the same problem :
"I myself have also had the problem where after doing changes they don't seem to take affect until after saving and then reloading Vixen.
What I found is if you are playing a sequence and then pause it (instead of actually stopping it), and then do changes and then when you play it you won't see the changes until you actually use the stop command and then play it again.
I'm not sure why this happens, but it seems to be a quirk in Vixen as I've seen it in the last few revisions that I've run over the last couple of years."

When I do this, nothing else happens, no more problems about the "com port denied". So it's a bug in the software, I guess.
So I'm helped through my problem.

Topic closed ?

Now I hope there won't be any more problems and we can't start programming our christmas light display, because it's the first time we are going to put a light show on music.

Valérie & Kurt
www.kersthuisje.be
(see for pictures at "Foto's" and for movies at "Filmpjes")

Thanks all for your help you have given me !

[P. Short]

Have you entered this is a bug in the bug tracker system?

[Valerie]

No, I don't know how to do that.
How can I do that ?

Valerie & Kurt

[DynamoBen]

"I myself have also had the problem where after doing changes they don't seem to take affect until after saving and then reloading Vixen.
What I found is if you are playing a sequence and then pause it (instead of actually stopping it), and then do changes and then when you play it you won't see the changes until you actually use the stop command and then play it again.


This doesn't need to be entered into the bug tracking system. KC is aware of it and its not a bug, its by design. Long story short if you make changes while paused you won't see the effect until you stop...if memory serves its has to do with caching the data. A good rule of thumb is to avoid pause. ;)

[RPM]

This doesn't need to be entered into the bug tracking system. KC is aware of it and its not a bug, its by design. Long story short if you make changes while paused you won't see the effect until you stop...if memory serves its has to do with caching the data. A good rule of thumb is to avoid pause. ;)

The problem isn't so much that the changes aren't seen until after the sequence is stopped and replayed, the problem is that there is an "access to port denied" error after doing so when using the Enttec Pro plug-in. This is the problem that Valerie was having, and I have had this error happen to me as well.
Once in a while even restarting Vixen doesn't fix it and I have to unplug and plug in my dongle to get it to work again.

[DynamoBen]

The problem isn't so much that the changes aren't seen until after the sequence is stopped and replayed, the problem is that there is an "access to port denied" error after doing so when using the Enttec Pro plug-in. This is the problem that Valerie was having, and I have had this error happen to me as well.
Once in a while even restarting Vixen doesn't fix it and I have to unplug and plug in my dongle to get it to work again.

Ahh, that then has do with the FTDI driver. When this occurs Vixen doesn't release control over that com port properly, so on the relaunch you are denied access (which is why relaunching does help). Replugging the dongle resets the com port allowing Vixen access again.

Depending on the event(s) leading up to this issue it might be a bug on top of a bug. Or in the case of Pause its a feature on top of a bug. In either case be as detailed as possible in the report about circumstances and incarnations. RPM you might want to write this up since you seem most familiar with it.

[RPM]

Ahh, that then has do with the FTDI driver. When this occurs Vixen doesn't release control over that com port properly, so on the relaunch you are denied access (which is why relaunching does help). Replugging the dongle resets the com port allowing Vixen access again.

Depending on the event(s) leading up to this issue it might be a bug on top of a bug. Or in the case of Pause its a feature on top of a bug. In either case be as detailed as possible in the report about circumstances and incarnations. RPM you might want to write this up since you seem most familiar with it.

Strange thing about it is, for me it doesn't always happen in that particular sequence of events, but one way that it always errors is to play and then pause a sequence, then go into "Test Channels" mode.

[DynamoBen]

Strange thing about it is, for me it doesn't always happen in that particular sequence of events, but one way that it always errors is to play and then pause a sequence, then go into "Test Channels" mode.

Then use those steps, that then allows KC to walk through the code and see where the most likely soft spots are. Once that is know the other scenarios refine where the issue is.

[Valerie]

Strange thing about it is, for me it doesn't always happen in that particular sequence of events, but one way that it always errors is to play and then pause a sequence, then go into "Test Channels" mode.


Yes, I have also noticed that this error comes up this way.

So I do not click that button again, just when I have clicked pause, then I click stop as well, save it again, (and perhaps stop again), then it plays it good.
So actually I try to not click on the pause button, but instead the stop button, then there are no problems at all.

[rlmack]

Ahh, that then has do with the FTDI driver. When this occurs Vixen doesn't release control over that com port properly, so on the relaunch you are denied access (which is why relaunching does help). Replugging the dongle resets the com port allowing Vixen access again.
Hi, new to this site :D, but not new to the FTDI chipset. When you plug the dongle in, it does a internal reset of itself to clear its buffers. Windows also resets its buffers allowing you to start from a "clean slate". Other things that can cause wierd problems is the USB Bus driver. Different drivers and chipsets MAY not always work the same, even though they are suppose to. Have noticed different usb to serial dongles work with some apps but not well with others. Just a few things to consider. If you try your dongle on a different computer, it may work better or worse. Software makes designing hardware harder sometimes. I guess my point is sometimes its hard to pinpoint a source of a problem with so many hands involved (Microsoft, FTDI, Vixen, USB Bus Drivers, Ect).

Working on designing a DMX512 lighting controller for outdoors and was looking for a software that works well with DMX. Hoping that Vixen does. Is there a limit the number of networks it can handle?

[DynamoBen]

Working on designing a DMX512 lighting controller for outdoors and was looking for a software that works well with DMX. Hoping that Vixen does. Is there a limit the number of networks it can handle?

Vixen works well when using DMX control. Both the OpenDMX and the Entecc DMX Pro are supported. As far as the number universes Vixen supports its unclear. From a software perspective there is no limit, but we have yet to find the practical limit. In the past I have done testing up to 4 universes (2048 dimmers) and things seemed stable.

[wjohn]

The problem isn't so much that the changes aren't seen until after the sequence is stopped and replayed, the problem is that there is an "access to port denied" error after doing so when using the Enttec Pro plug-in. This is the problem that Valerie was having, and I have had this error happen to me as well.
Once in a while even restarting Vixen doesn't fix it and I have to unplug and plug in my dongle to get it to work again.

I am running 2.1.1.0 (latest forced update) and ENTTEC PRO, I have had this fault regularly when I and starting and stopping, channel testing, have two programs running back to back.