Anyone set up the IP configuration with these two? It is very cool, and it receives tests just fine... One question / issue, How in the world do I tell the box to run a RWT? Do I need to still set up relays for that? I figure if it can tell the box to proceed with other kinds of tests it should be able to "coordinate" with NexGen to send an RWT. Opinions welcome!
-
Get involved.
We want your input!
Apply for Membership and join the conversations about everything related to broadcasting.
After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
If you use a disposable or false email address, your registration will be rejected.
After your membership is approved, please take a minute to tell us a little bit about yourself.
https://www.radiodiscussions.com/forums/introduce-yourself.1088/
Thanks in advance and have fun!
RadioDiscussions Administrators
SAGE Digital Endec and NexGen
- Thread starter gettinbyagain
- Start date
Hmm.. great question. Did you check with the folks in Ogllala? You probably aren't the first to ask. Maybe they can help.
df
df
Sure have.. They say "Everything is Automatic"
Trying to give the tech support person a lesson in EAS 101, and describing how we need to be able to transmit a RWT randomly during each week didnt really help matters. We used to just schedule it in selector like a promo and trip the relay, but with the TCP IP it is quite different.
Trying to give the tech support person a lesson in EAS 101, and describing how we need to be able to transmit a RWT randomly during each week didnt really help matters. We used to just schedule it in selector like a promo and trip the relay, but with the TCP IP it is quite different.
Is the Sine System ACU-1 part of your NexGen system? This white, 1 rack unit box used to be included for net catching on the DRR.
I think most people use an opto on the Sine unit to remotely fire the SAGE unit for RWT.
I think most people use an opto on the Sine unit to remotely fire the SAGE unit for RWT.
WNTIRadio said:
I have not seen a way to make it fire a test with the Ethernet port. However, I have a client using Nexgen and is still able to run random weekly tests. The announcement cart is run, then run the macro that pauses the log and closes the relay on the Sage that runs the test. Then the relay closure from the Sage telling the Nexgen to "play next". Piece of cake.
Thanks,
They have a PCI SeaLevel card, SO I suppose I can hook it up the old fashioned way
Just thought there may be a way to do this since NexGen DOES trigger event forwards such as RMT's after the current element has finished playing.
They have a PCI SeaLevel card, SO I suppose I can hook it up the old fashioned way
Just thought there may be a way to do this since NexGen DOES trigger event forwards such as RMT's after the current element has finished playing.
NexGen does NOT forward your EAS test. The SAGE unit is in your program circuit and interrupts the audio feed. It then inserts EAS system data/audio.
Does your station have an engineer? That's who you should discuss this with. It's not hard to trigger the SAGE with NexGen relay closures.....
Does your station have an engineer? That's who you should discuss this with. It's not hard to trigger the SAGE with NexGen relay closures.....
Taylor,
I am the engineer and I was merely asking if anyone had experience with this setup. I am more than familiar with how it interrupts the chain, and setting the Sage/NexGen up with relays etc, but was wondering how one part of the TCP/IP operation works.
I watched an RMT come in the other day, signal NexGen (NexGen actually notifies the operator on the screen... if there is an operator) and then NexGen wait until the end of the currently playing element then fire up the Sage, wait for the sage to finish, and then continue with the next element all without us touching anything. Pretty cool over TCP/IP.
rfguygg,
How do you schedule / forward a RWT?
Thanks for all of your responses.
I am the engineer and I was merely asking if anyone had experience with this setup. I am more than familiar with how it interrupts the chain, and setting the Sage/NexGen up with relays etc, but was wondering how one part of the TCP/IP operation works.
I watched an RMT come in the other day, signal NexGen (NexGen actually notifies the operator on the screen... if there is an operator) and then NexGen wait until the end of the currently playing element then fire up the Sage, wait for the sage to finish, and then continue with the next element all without us touching anything. Pretty cool over TCP/IP.
rfguygg,
How do you schedule / forward a RWT?
Thanks for all of your responses.
gettinbyagain said:
Can you explain to the rest of us how you get it to do it over the TCP/IP link then?
I can post more details when I am in the office tomorrow, but... To get the RMT and any warnings / watches etc (as you define in the Endec) to forward,
It really depends on the automation system you have, but if you have NexGen, you need to be sure you are on a fairly recent vintage. You set up the SAGE just like an IO device in CONFIG then IO... One of the drop downs lets you choose Sage, and specify the IP address of the unit.
There are a few other specifics, but I found the Help file in nexgen actually helpful. If it does not specify how to set up the IP based Endec you need to upgrade the version.
It really depends on the automation system you have, but if you have NexGen, you need to be sure you are on a fairly recent vintage. You set up the SAGE just like an IO device in CONFIG then IO... One of the drop downs lets you choose Sage, and specify the IP address of the unit.
There are a few other specifics, but I found the Help file in nexgen actually helpful. If it does not specify how to set up the IP based Endec you need to upgrade the version.
My version of NexGen will not do that (at least I think it won't) - thanks for the heads up!
- Status