• State Verified Answer
  • Date
    drewid
  • Date
  • Replies 4 replies
  • Subscribers 184 subscribers
  • Views 6471 views
  • Users 0 members are here

Problem with movers moving

Setup:

Eos w/ 1.9.whatever (the most recent update, too many numbers, too little attention span)

2 VL2500 Spots that had been initially in effects but have since had all effects removed for the preceding 5 cues (all of which are move cues, the first of which has an intensity change as well).

I have a 5 second cue in which the VLs are supposed to move (Tilt ~20º, Pan ~60º, nothing major), move the 2nd gobo wheel to drop in a prism, and begin spinning that prism.

What happens:

The VLs spend the entire 5 seconds doing the gobo wheels properly and smoothly, but not pan/tilting.  In the Live Table display, the VL pan and tilt attributes are changing as though they are making a smooth pan/tilt, but the fixtures themselves do not move.  Then, as soon as the cue finish, they jump to the new position.

Questions:

Is this a problem with the Eos, the VLs, or my programming? What is going on? Can the VLs not handle a simultaneous move/gobo change?

I've sent the last hour and half changing things, rewriting cues, and experimenting. Like I said, originally there were effects and I thought exiting the effects was the problem, but I've since removed the effects and it doesn't improve.  I'm flummoxed.

  • 0

    Hi drewid,

     

    I have seen something like this with VL1000's before, but not 2500's. They do seem to have problems with moving and gobo changing simultaniously, but I've never had the opportunity to investigate the issue.

    You could stick a DMX tester on the line if you have one to prove that the console output is behaving as expected.

    If you want to send me a showfile, gparker[at]etcconnect[dot]com I'll take a look for you.

    I don't think it's likely to be the culprit, but have you checked the Position Mspeed hasn't accidentally had a level change?

     

    Graham

     

  • 0

    Take a look at your position mspeed to see if it is changing between the cues.  This can cause what you are seeing

     

  • 0 in reply to Druuka

    That worked, thanks!

    I've never dealt with Position Mspeed before (it doesn't appear in the manual anywhere and haven't had anyone mention it in any training I've ever had), but it was indeed changing to 0 with the effect up and didn't change back to 255 until the next cue (with no move effects in it). So, manually fixed it an it works. I don't think I'd have ever found how to check it with the About key if our local vendor hadn't been helping out with the show (or asking here...). I think even a vague mention of Position Mspeed would be useful in the manual.

    But yeah, Position Mspeed was the problem. Thanks!

  • 0 in reply to drewid

    position mspeed is part of the fixture profile.  There are some fixtures that don't use speed channels and others that do.  There may also be speed channels for other items (color, beam, etc.) It is always good to look over all the attributes of a fixture to determine how you want to program them.  If you are making palettes you should decide to either have speed values in them or not depending on how you wish to deal with speed channels.  I usually omit speed channels from palettes and presets unless I make specific palettes/presets to control the speed of the fixture internally.  In some cases the speed channel can be useful to change how the fixture moves especially when you are doing very long timed moves. 

     

    Hope this helps.

     

Related

www.etcconnect.com