Mighty Scan problem

How long is your DMX run? Are you using DMX cable? Are you using a DMX Terminator?

Second, what's your controller?

Is this a NEW problem?

Might be time to read the manual a little bit. Maybe you've mis-addressed them?

Right now the run is just one mighty scan at a time. I'm just trying to get them running right before I put them up. I am using DMX cable but don't have a terminator.
The Controller is a Chauvet Obey 40 DMX Lighting Controller. It is a new problem but I haven't used the lights in a while but they were working fine the last time. Thanks in advance.

Tell me a bit more. You left out how long your cable runs is though. I have heard reports of others having problems with the Chauvet Obey 40 controller before. I am not here to slam Chauvet, as I also own some Chauvet gear, but they aren't my favorites.

You are going DMX IN to DMX OUT to get to the next light, right?

Without taking the time and effort to download a Mighty Scan manual, I can't say for sure what the issue is. You might be right, it could be a setting thing.

At a quick glance, the Obey 40 appears to be pretty muych the same as the ADJ DMX Operator Pro. I'm guessing the fade time fader is not on the full down position? This is something that has nailed me many times on my DMX Operator until I figured it out.

My run is really short. I'm just testing the lights so I only have one plugged into it. The line is about 5 feet long. I tried the fade time fader but didn't seem to help.
I'm wondering if the addressing could be an issue. The manual says that it is european and is minus one. I think I may try variations on the dip switches as well as re-checking the dmx line.

European? Strange.

Well, yeah, maybe it could be an addressing issue. For example, Korg uses(or at least used to, I don't have any new Korg gear to really test with, and what I can test with is consistent with what I'm about to say) that type of numbering system. Program 00 is actually program 01, so their banks go from 00 to 99 instead of 1-100, since you can only use 2 digits. It ends up being essentially the same thing but throws you out of whack if you can't wrap your head around it fast.

So, with that in mind, sure, try changing your addresses. No guarantee, but that might be it. But I'm not entirely sure since you say this was a working system and now this is a NEW issue.

Just to let you know, Elation has a DIP switch calculator that I recommend everyone download. It should save a lot of time with the DIP switch monkey business.

In the meantime, buy or build a DMX Terminator, they are handy to have around. You definately won't need it for testing with such short lengths, but I bet your runs go longer at events. Better safe than sorry, I say. I always use a DMX terminator. At my last show, I had 3 runs, all of which were at least 200 cable feet, 1 was over 300 feet, another was at least 250 cable feet.

But I digress. Back to your addressing issue:
Set the scanner to DIP 1 on, all others off. This SHOULD set you to DMX starting address 1. Power up your light, or if you changed the DIP switches while powered up, power cycle the light. Plug in DMX now if you haven't already. Press your Scanner 1 button, and I am now assuming that you know what channel controls what attributes. This might point out addressing issues.

I get the impression you're pretty familiar with how the light SHOULD be working, especially posting with a statement that the lights are moving SLOW like that. And the fact that BOTH are doing the same thing sort of points to perhaps the controller, not cabling or fixtures, OR, operator error. BUT, you've tried the fade time fader, so it's not that, and you've mentioned that perhaps you've got a speed channel, so you definately aren't lost.

It would be nice if you had more than 1 controller to test with, just to rule out the Obey 40, or narrow it down to it.

You wouldn't happen to have some old par cans and dimmer packs laying around just to test with? I know it's not a Mighty Scan, but I'm just throwing out ideas to test stuff working or not in the Obey 40. I'm not slamming the Obey 40, because if I suspected my ADJ DMX Operator, I'd be doing the same thing if I could.

I'm thinking that it may be the DMX terminator. Now that I think about it I never had one but I did have a strobe at the end of my line that had a terminal switch. That may have been it.

My standard advice is always "DMX Terminator and DMX cabling". Just play it safe, and of course I'm sure you're aware of how many people who just use microphone XLR cable for DMX.

With your test environment, you're using a 5 foot cable. While you SHOULD be using DMX cable(And I think you said you are), even if you weren't, you shouldn't have this problem. And because your cable length is so short, having a DMX terminator really isn't necessary but sure can't hurt.

Another goofy possibility is that you have your phase switch flipped. But this would totally prevent stuff from working at all.

So, I don't think adding a DMX terminator will help in your testing environment, but sure can't hurt either.

Phase switch? Is that on the light or the controller?

The phase switch is on the controller. It's done to accomodate lights that are wired backwards.

You can also get or make phase reversed cables, which unless it's your home run from the controller to the first light, phase reversed cables generally are the better way to go.

In my experience, all my fixtures are properly wired in phase, so I don't have this issue or this need for reversing phase. Also, in my experience, if you have the phase wrong, DMX just plain doesn't work at all.

Flipping the phase is just a troubleshooting element. It's fast and quick and easy to try.

What would be ideal is if you had a secondary controller to work with, just to help rule out the controller.

Another idea is that UNLESS you have stuff programmed into the Obey 40, blow it out back to factory defaults and see if that resolves anything.