follow me on facebook tweet me

Support Center




RSS Feed
Latest System Release Notes
Posted by Brad Campbell on 14 May 2013 10:19 AM

5/5/2013 Build 4873

  1. Changed the sound card routine to explicitly turn off RTS and CTS.


4/7/2013 Build 4845

  1. Changed the polling routine so that it will properly process instant status messages when sending a non-polling command.


3/17/2013 Build 4824

  1. Added Relay On and Relay Off commands for the WeatherWarn-2 interface.


2/26/2013 Build 4805

  1. Added code to verify that the number of status bytes received agrees with the expected number of status bytes.



  1. Added the Windows 8 guid to the application manifest.
  2. The program now makes an entry in SirenLog.txt when it connects or disconnects from the Weather Message Server.
  3. Changed the TCP/IP stack’s keep alive interval to 1 minute.


2/6/2013 Build 4785

  1. The decode routine now clears the internal polling variables.  This addresses an issue when the software hears responses to another encoder that is polling the sirens.  The status field should now be populated with the correct status.
  2. The call key save routine now runs in the current thread instead of the background.


2/4/2013 Build 4783

  1. The Call Key setup window now considers the “Disable Response Warning” as a warning instead of an error.
  2. For mixed system operation, the system will now place the mixed system’s dtmf or tone commands before the commands in the call key.



  1. The program now honors the email option settings for instant statuses.



1/19/2013 Build 4768

  1. The program now saves the siren database when a status reset is performed.  It also saves the siren database after a poll operation.
  2. The Call Key setup screen now has a “Disable Response” option.  This option, when checked, will control whether the sirens respond to activation commands.  This option should not be checked for Call Keys that have polling commands.
  3. The Manual Command screen now has a “Disable Response” option.  This option, when checked, will control whether the sirens respond to activation commands.  This option should not be checked when including commands that cause the siren’s to respond.


12/30/2012 – Build  4747


  1. Changed the physical file name used to store messages sent to Weather Message for emailing.  Corrects an issue with duplicate emails.


Read more »

Is everything working?
Posted by Brad Campbell on 20 February 2013 12:54 PM

Is everything working?

The basis of an automatic WeatherWarn activation considers a large number of “handshakes” between hardware and software across multiple systems will take place.  As an end user, how can I feel confident that these systems are functioning properly?  Let’s start by summarizing how the data travels and what must happen for an activation to take place.


  1. The EMWIN network utilizes PULL technology (via FTP server) to capture each product issued from every NWS issuing office around the country.
  2. The EMWIN network then utilizes PUSH technology to broadcast this information out via multiple servers as well as 2 satellites.
  3. WeatherMessage (WxMesg) ingests every weather product issued by the NWS regardless of issuing office and product type.
  4. WxMesg e compares each product to each alarm file created by the user to look for matching criteria (i.e. tornado warning for a specific county).
  5. Once a product matches the alarm file criteria, WxMesg passes the information to WeatherWarn.
  6. WeatherWarn receives the information from WxMesg and compares the product against each call key’s associated product.  If they match, the system looks for sirens within the polygon or the county (if not polygon is issued), selects those sirens and then processes the call key.
  7. If any other features are selected in the alarm file (email notification, activation statement, social media interface etc.), those actions are performed between steps 4 and 6.



Now you have the option to be confident !

Test Product:  Another small software application that comes with each WeatherWarn system is the WxScheduler (separate from WeatherWarn internal activation scheduler).  This software can be configured to run a test product which will be processed through WxMsg and WeatherWarn exactly like a real NWS product through EMWIN.  Simply configure the test product to a call key (we recommend a silent test and status request).  Once the scheduler program issues the product, the system will then activate the associated call key.  With a silent test and status request activated via test polygon, the end user can now verify the following:

  1. WxMesg processed the product and passed to WeatherWarn.
  2. WeatherWarn processed the product and activated the call key.
  3. The radio activated the sirens.
  4. The sirens returned their status.

WxMsg can be configured to send the results of your status request to a list of email recipients.    With the receipt of that email, the end user knows that all communication from start to finish (independent of EMWIN) is working properly.  This scheduled test product can be run as often as the end user desires.

Read more »

back to top