MIDI + 24hr trigger = failure.

Ok I have been beating my head on this one for the last week and a haft. And need suggestions.

Situation:
Hog1000 console. Controlling a 136 desk channels, 10 non-dims and 1 LED
1 Audio cd with SMPTE being converted via a PPS-2 to MIDI input in the console.
Event: Daily static show for ice carvings with lights hosted inside a freezer.
Actions: 24hr clock cueing Fader 16 which hosts all the macro commands. At..
07:00 Warm up cue begins. (1hr warm up time to gradually bring lights out of frozen to safe operating temp.)
08:00 Show mode. = Normal daily run of show. General lighting at certian levels and one room of the freezer has a small light show sync to the SMPTE
23:00 Cool Down = Lights slowly dim out to OFF over a 30 min period (to prevent rapid temp change on the lamps)
23:30 OFF = everything is off.

Issue: When fully plugged in and running for a reasonable amount of time, (aka rebooting the console around 19:00) When 23:00 comes, it Executes the 07:00 command (>C16:T1) instead of its >C16:T3 command. At 23:30 it executes the 08:00 command.

Yes I have verified the actual on board clock was correct time. I have bench tested with two exact consoles. with exact same show loaded. Only difference is the Primary is connected to the DMX and MIDI cables. where the secondary is by its self only connected to a separate but identical LED fixture. Yes I have swaped the consoles places (Primary is disconnected, and Secondary is connected to DMX and MIDI) Same Issue occurs no matter which console is connected. Attempt was made to turn of the SMPTE to MIDI box before the 23:00 command. But it ignored it.

I have also found that when I arrive in the morning to see it missed its cues. If I change the clock to say 22:59 to see if the 23:00 cue happens. Nothing happens. but if I reboot the console. I can change the time to 22:59 again and the 23:00 cue will execute.

Has anyone had this kind of problem before, or can lead me down a path that can help solve this?
  • 0
    The PPS2 might be the cause of your problems.

    The PPS2 does not TRULY read SMPTE to convert it. It is mearly counting frames. If you send a PPS2 a timecode of 00:59:50.00 and run for 10 minutes and then change the timecode to 02:59:50.00...the PPS2 will continue from 01:09:50.00.

    I'm not saying this is what's happening to your situation, but it might be something to take a look at.

    Do you have a SMPTE reader in line that is confirming your timecode?
    Can you try inputting SMPTE directly to the console without the conversion?

    Just some ideas...
  • 0
    @jxgriffi That I was aware about. We actually had the issue of the cd replaying and the time code kept running. So we layed 5seconds of black to the begining and end of the track. We have a FastFoward F30 (www.ffv.com/Support/F30_Manual.pdf) In line to verify the time code is reading correctly. And It does.

    I am not necessarily blaming the TIME it's self, but more of the fact the time code starts and stops having an influence on the console's 24hr clock. Adding the 5 seconds of black with no time code, The console, PPS-2, and the F30 all read the time code correctly.

    I am just trying to understand the following things:
    -Why is the console activating the 07:00 Cue on the 23:00 trigger. and 08:00 cue on the 23:30 trigger.
    -Why when I come in the morning, and try testing the triggers by changing the consoles clock. why the cues don't respond. I am forced to reboot the console for it to work. (After rebooting the console I am able to change the time to 06:59, wait, and 07:00 trigger will work on time, then change to 07:59, and the 08:00 trigger works on time, change to 22:59, and 23:00 works..etc.)
    -What could it be appears to be disabling the 24hr daily triggers.

    btw:Current console:
    Hog 1000
    v3.3 (177)
    ROM Lib: v5.4
Related

www.etcconnect.com