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.

Parents
  • 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

     

Reply
  • 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

     

Children
No Data
Related