Tweet
Hi guys.
How send external signal to ims not GPI.
What format should it be and to which port should it be sent, TCP or UDP?
How send external signal to ims not GPI.
What format should it be and to which port should it be sent, TCP or UDP?
-
-
The "trick" to the triggers and cues that can occur regardless of where one is in the show are done with one of two files in the doremi/etc directory. There will be a file in there called "default_cues.xml" If not, there will be the "default_cues.xml.sampe" that can be turned into the "default_cues.xml" by simple renaming. Conveniently, The "Fire Trigger" cue is in the example. Here is what it looks like):
<?xml version="1.0" encoding="UTF-8"?>
<ShowPlaylist><Id>urn:uuid:928e91d2-4720-4b31-816e-55c423e8fc42</Id><ShowTitleText>default</ShowTitleText>
<AnnotationText>default</AnnotationText>
<TriggerCueList><TriggerCue>
<Id>urn:uuid:a2a36555-4ab0-4859-8316-2c748d5bacfc</Id>
<TriggerName>Fire Trigger</TriggerName>
<Action>Pause</Action>
</TriggerCue></TriggerCueList></ShowPlaylist>
The way to read this is that there should be a trigger called: "Fire Trigger". When that trigger is received, it will execute a macro called "Pause" (the "action").
If you don't have the trigger and the Macro, nothing will happen and note the exact spelling and case of each letter/space.
The default Fire Trigger is set to respond to GPI #0. But, you can change that by selecting and deleting the event. Then add in what you will be sending it. There are "blessed" devices like the projector, the eCNA automation and the JNIOR automation. For the rest, using "Any" will work. You define what the command will be (e.g. "FireStop"). So, you could have a Trigger Cue called "Fire Trigger" who's message is "FireStop" that could come from "Any."
From there you will need to format the command properly and there is a confidential document that defines that (you'll need to obtain from Dolby now). It takes the form of <size>,SIG,<ID>,device::<your command>,N,??\r\n. Your ID can be 0. The size are all of the characters in the command (including the \r\n). You use port 13200 with either TCP or UDP.
An example Trigger I use is called "QHDMI" The command to fire the trigger is this:
18,SIG,0,QHDMI,N,??\r\n
On the IMS, there is a Trigger with the name QHDMI (it does not have to have the same name but I did to keep it simple)...looking at that trigger, it is set to receive the signal from "ANY" and it is looking for the "message" QDMI (not the entire command).
Note, the Default Cues file is only active when a show is running. If you name your trigger cues file firealarm_cues.xml...they will be ALWAYS active, even if a show isn't running. You can have both files as well so some triggers only fire if a show is running while others will fire regardless of show status.
Does this sound overly complicated...IT IS!!!!! They have softened the blow a little bit by allowing one to use the show editor to build up a trigger cue file with all of the UUID stuff. You save it as a show...then find it and rename it as needed and place it in the proper directory. That will mostly ensure that the xml file gets made right. The Trigger cues themselves and the command you have to send will still require some trial and error to ensure you get the formatting just right.
So, to summarize:- Create/modify your trigger cues.
- Create/modify either a default_cues.xml and/or firealarm_cues.xml that has the triggers and the macros you want them mapped to.
- Format your TCP/UDP commands precisely has listed above (if it doesn't work, try adjusting the size up/down 1.
Good luck -
-
Before he bothers to write a list of commands for the IMS, he should check with the fire Marshall, or local fire department to see what they require. With Digital, I have run into varying requirements over the years... some are ok with just sending a show stop house lights up cue, most but not all wanted the lamp off, and quite a few wanted the system shut down completely... All are pretty easily done, except shutting the system completely down properly.Comment
-
You'd have to contact Dolby tech support (it would probably be easiest through your dealer). Hopefully, you have some sort of relationship set up in case you need tech support for a problem.
As to Mark's comments...the big one that the Fire Marshal has wanted (in every jurisdiction) was to kill the sound...not the picture. That said, it has been out policy that if a fire alarm signal is sent to us, we pause the player, bring the lights up full (if that option is available...even brighter than "up"), xenon lamp off and, if we have control over magnetic door closers, release the doors. We use the Eprad eCNA automation in just about all installations, even screening rooms. That is our point of integration for the fire alarm (aka life-safety system). So, it is what has the routine for handling it, not the server itself.Comment
Comment