Tech Notes from the Field

We installed the RCS NexGen a year ago.  As of today we still have issues with the NexGen – Sage Endec communications.

Our NexGen system is installed with no GPIO, or opto-relay, equipment.  We are 100% IP control with the system at this time.  We run EAS Required Weekly Tests, generated from the NexGen, without any issues.  It is pretty simple once set up.  NexGen is configured to look at the IP address and Port  of the Sage Endec, monitoring for any Sage originated activity.  If an alert or Required Monthly Test (RMT) comes in, NexGen is supposed to “see” it and act accordingly.  It works sporadically at best.  Today we had 2 of 3 stations run properly.

What could be the problem?  No one seems to know or ask the proper questions.  We have tested time and again the Sage Endec for the information it sends out.  It exists.  It’s there.  It just needs to be acted upon.  The NexGen will not “see” the information.  It does not acknowledge that an alert or test has come in.  If  it does, it works just fine.  If it doesn’t, then manual intervention is required or the Sage takes over and runs the alert or test on the air, interrupting programming.

I ask the question: Why does the NexGen machines not see the information consistently?  It is there to be acted upon, so why does it not see it?  NexGen is installed on Windows 7 server class computers.  NexGen runs on layers of older code.  I conclude one of two things:  1) the older IP stack on which NexGen is build stops responding, or 2) the Windows 7 computer “shuts down” something such that the information is ignored.  Anyone have experience with Windows 7 boxes acting odd like this?  Could there be a miscue between the application and the physical NIC?

We continue to send logs to RCS for evaluation.  No one seems to have answer.  One year later.  Any Windows 7 insight is greatly appreciated, and if you have an RCS NexGen running IP control, let me know what experiences you have.

Cheers!