Jump to content
Vari-Lite Controls Support Forum

kgallen

Regulars
  • Posts

    2,091
  • Joined

  • Last visited

  • Days Won

    109

Posts posted by kgallen

  1. This is almost always a battery issue or accidental movement of DIP switches on the PCB when swapping the battery (others feel free to correct me!).

    I would swap the coin cell for a guaranteed new one then boot the desk a couple of times since the software will need to rebuild some internal tables since the battery went flat. Trying to reinstall the OS will probably take you down a blind alley.

    Also I recommend looking through through the Forum for other comments on this issue as this a common query.

    Does your Leap Frog run FrogOS (10.12 latest) or ZerOS? There are two styles of Leap Frog with very similar names which is confusing.

  2. Betapack 1 are solidly reliable so this is surprising to have a ‘total dead’.

    There is no overall fuse in the unit as they can be wired single or 3 phase delta or star.

    Are you sure your supply is ok? Check your supply MCB/RCD first if you haven’t. Does an Act 6 work in the same supply socket?

    The Betapack power led should be lit (red or green depending on analogue desk supply polarity). None of the channel fuse neons should be lit. 

    Can you investigate more and provide more info?

  3. If you really think this is correlated to start/end of show I would have a good think about what electrical disturbances could be happening in the venue. Tea urns, house lights, that sort of thing.

    I got into the habit of always using a small computer UPS with my lighting (and sound) desk just to cover those brown-out situations that can occur on electrical systems and cause computer-based devices to crash or restart.

  4. I just looked in the manual, assuming it’s Geyser P7.

    Theres nothing special. 1 channel for fog, then 14 for pretty lights. I didn’t see anything about the machine going to sleep.

    Also seems there is nothing the DMX controller (FLX or Chauvet) could do wrong or cause what you observe. 
     

    Is the machine powering off completely?

    Are you trying to fire smoke continually? 

  5. Usually smoke machines have very simple controls. A channel for smoke, maybe a channel for a fan (more usual on a hazer). So the fixture profile is usually very unexciting compared to say a moving light. I would patch dimmer channels at the address your smoke machine is set for and have a play. Look at the DMX map that should be in the smoke machine document. Is there a channel that needs some weird value to keep the smoke machine awake? Within the Fixture patching steps you can create your own fixture for the smoke machine if you think the library one has some issue once you’ve played with the dimmer-per-channel thing above and checked the manual for any weirdness for the smoke machine. 

  6. Your fault is probably in “cue 2” where there are blocking values that stop the mover prepping for “cue 3” but in your real cue list where you’ve been copying what I said in previous posts is most likely the case. I’m assuming here you haven’t deliberately set ‘Don’t Move’ in any related cue Cue Settings - if you have that’s self explanatory!

  7. Copying cues results in blocking cues when you paste. You will see white intensity numbers in the output screen. 

    1. Save your show. 

    2. GO into a cue you copied to, which shows the white intensity numbers.

    3. Press and hold UPDATE to bring up the options window. Ensure SmartTag is enabled (red stripe). Press enter (or tap the playback go button)

    Blocked values should change from white to purple (tracked) (unless you subsequently changed them after pasting in which case they will be blue or green) and now your move on dark into that cue should work.

    4. Repeat for other copy-pasted cues.

    Note: There is a method to unblock a whole playback in one go but I can’t remember where that option is. Check the manual.

    4. Check the results on stage.

  8. OK this is 10 years old comment, but this is where Jon told me the association of dimmer has to be within the fixture. I think at the time I was trying to do something vaguely similar to you where I had a patched Source 4 and wanted to associate the scroller with it to support move on dark.

     

  9. The scroller uses the intensity channel of the associated fixture to know when ‘dark’ (as I’m sure you’re well aware). Scroller probably only has colour attributes. 

    You might have to patch the lamp+scroller and patch the ‘lamp’ to an unused DMX address then use that bogus lamp fixture intensity to control your move on dark. 

    I think early days of my FLX I asked a similar type of question and it just came down to you need that linked intensity channel to support move on dark.

    I know you probably don’t have time or access but this is a candidate for having a play to see what methods can be used to fool the desk whilst maintaining a usable workflow. I don’t think anyone left here knows how the desk actually uses the fixture information under lamp+scroller to know what cheats are viable.  

  10. 8 hours ago, Davidmk said:

    @Sol That seems a nice idea but ye "Cannae change the laws of physics" (or LTP).

    If you did then everything else would break.

    @kgallen @Archie D Opinions on that?

    I think it would have to be a ‘built in’ effect. The key to this as identified at the start is the ‘release’ instruction the desk needs. I’m not sure even user macros on FLX can make this any easier. Some sort of ‘auto release’ would be needed. 

  11. I’ve read with interest what @Davidmk has written. I agree the key to this will be fixture Release to get back to your background colour. 

    However I can’t as yet think of a neat generic way to do this. All I can think of at present is you will need a set of playbacks equalling the number of ‘white’ lights you want to overlay. Each of these playbacks will light one of those lights. Each has 2 cues. The first cue lights the light and releases the previous playback in the sequence. The second cue triggers the next playback. This ‘next’ playback has the two cues as above, the release being for that first playback. Repeat playbacks like this for each sequence light.

    You could have a ‘master’ playback that triggers the first playback in the sequence and a second cue that releases all of the sequence playbacks. 

    This is not readily expandable and quite clunky to implement. Also changing the speed will require exiting the cue times on each playback. Yuk.

    Possibly you could have a master playback that triggers and releases each sequence playback, that would probably make time editing far easier and all the sequence playbacks need to do is light the light.

    As yet I can’t think of a better way. At least on FLX/S there are no real shortage of playbacks and the sequence playbacks could be buried on a later page.

    We’ll all keep having a think as this is fundamentally not unusual as a requirement. 
     

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.