---

Using Windows Explorer on your SqueezeMax, move the ZIP file under the SqueezeMax program code plugins folder.
For an HD SqueezeMax this is usually at C:\Program Files\Utah Scientific\Apps\plugins\. For an SD SqueezeMax this is at C:\Program Files\VertigoXmedia\Utah Scientific\Apps\plugins\.

Unzip the easplugin_install_1_4.zip ZIP file. Now move into the unzipped directory that appears.

Copy the two files :  alt_easplugin.ocx and alt_easplugin_installer.exe into (directly under) the SqueezeMAX plugins folder directory.

Make sure SqueezeMAX is NOT running during the plugin installation! If it is, then exit SqueezeMax.

Run the alt_easplugin_installer.exe app from a Windows Explorer view by double clicking the file alt_easplugin_installer.exe.

The original file easplugin.ocx will be moved to a backup file, easplugin.orig.ocx, if this file does not already exist.
If it does, it is left alone and the current file easplugin.ocx will be moved to a backup file easplugin.prev.ocx.

Two popup dialogs will present themselves during the installation phase. Just hit the OK button for each one.

Restart SqueezeMAX and the new EAS plugin will support TFT/SAGE/SqueezeMax LAN/DASDEC EAS NET/Direct EAS datasource edit.

The current version of plugin will display two dialogs, not one.
One will be small and empty and should not be closed. This one looks a lot like the original plugin but does not present any controls. The other will look like a regular Windows dialog and will have controls for setting various values in the SqueezeMax settings.ini file.

The current version of the plugin allows changes to be made to all of the provided configuration fields on the fly without restarting SqueezeMax.

The plugin does not support editing of all of the values in the settings.ini file. If for some reason any of the values are not correct, you have to carefully hand edit the setting in the file settings.ini under the Plugins directory while SqueezeMAX is NOT running. Then rerun SqueezeMAX for these new settings to take effect. This will not hurt any of the existing settings.

If the serial port is from a USB adapter, and this is not plugged in when SqueezeMax is first run, it is likely that the EAS plugin will need to be relaunched (by restarting SqueezeMax) after the USB adapter is first plugged in.

---

Using the DASDEC Web Browser interface, go to Setup->Net Alerts->EAS NET. You will need to create and configure an EAS NET client interface to each SqueezeMax. For details about using this configuration interface, see the user manual. Here is a condensed version specifically for interfacing to SqueezeMax.

After adding an EAS NET client interface on the Setup->Net Alerts->EAS NET page, there are a few values to fill into the client interface. The following operations apply from the top of the interface going down.

1. Reset the name of the EAS NET Client Interface (optional). Space characters are allowed in this field.
   
2. Make sure the interface is set to Enabled.
   
3. Check the box controlling when EAS NET data is sent. The box should be checked and labeled "Client will send EAS NET alert info prior to alert playout." This option allows the DASDEC to send the alert text data to the SqueezeMax prior to actual playout of the alert audio on the DASDEC. This needs to be paired to setting the GPI #1 input on the DASDEC to Hold Non-National EAS alerts until closure. See below.
   
4. More than likely the next box should be left unchecked. This will allow National Alerts to be sent to the SqueezeMax.
5. Set the IP address of the SqueezeMax in the form #.#.#.#. For example 10.0.0.123. Do not use leading 0's (eg do not set to (010.000.000.123).
   
6. Set the EAS_NET Event Transfer Protocol to the FTP Copy option.
   
7. Leave the Port at 21.
8. Set the SqueezeMax Windows User Name in the EAS_NET User field. This is the WarFTPD FTP user account name configured during WarFTPD instalation on the SqueezeMax.
   
9. Fill in the Password field with the configured WarFTPD user password.
   
10. <>Unless pre-configured SqueezeMax FTP schema option files already exist, set the Schema File pulldown menu selector to Default. You will need to create at least one schema the SqueezeMax using the provided editor. To do this use the provided Edit/Review Schema button to bring up the Schema editor. 
11. Three fields need to be edited. Look down the list and find the Schema Meta-Key Tag name called ALERT_EVENT_FILE_PATH. Enter the name of the WarFTPD mount point directory created earlier. If you exactly followed the instructions above, then for an HD SqueezeMax this should be set to /Data. For an SD SqueezeMax this should be /JambalayaData. If you renamed the mount point then you must use the name set in WarFTPD (one benefit of renaming the mount point is that you can create one schema file for all SqueezeMax boxes, regardless of whether they are SD or HD).  Now look further down the list and file the tag named ALERT_TRANSLATION_FILE_PATH. Set the value of this tag to the same mount point name. Now, look at the next listed tag ALERT_TRANSLATION_FILE. Rename the value for this from eas_translation$(ID).txt to EAS.txt.
    
12. Now save the schema file under a new name. Unless you have named the mount point the same (in which case you can use one schema file) then for an HD system we recommend naming it SqueezeMaxHDFTP., and for an SD system, SqueezeMaxSDFTP. The Save As GUI field appears at the bottom of the Schema editor page. Enter the desired schema file name and click the Accept Changes button below it. This will save your change and take you back to the original configuration page. Now set the schema file name to the new schema file you just saved. 
13. Keep the next two checkboxes for Composite Audio and EAS Audio files unchecked. No audio files need to be sent to the SqueezeMax. The next two checkboxes controlling options for the EAS Translation file need to be checked. The first option should read EAS Translation File will be sent (after it is checked). The next should be checked and will then read EAS Translation has newline characters removed. Video Start Delay Factor and Duration Extension Time can both be set to the default 0.
14. The last checkbox controls whether further FIPS code filtering is done. The default is to allow all forwarded alerts to any FIPS code to be sent to the EAS NET SqueezeMax client. If you want to add further FIPS code filtering (to be applied after the Decoder Forwarding filtering), uncheck this box and use the provided interface to select which FIPS codes must be present in an alert before it is EAS NET forwarded to the SqueezeMax client. NOTE: On DASDEC software versions 1.6-0b and greater, a second checkbox controls whether or not to apply filtering based on EAS codes.
    
15. For each remote SqueezeMax, repeat the configuration steps described above. A nice shortcut is the use the EAS NET configuration Duplicate button. Duplicate the SqueezeMax interface you just made, then change the interface name, IP address and schema if needed.
16. After every EAS NET to SqueezeMax client has been configured, and the DASDEC is active on the same network as the SqueezeMax, try a test alert. You can either use the DASDEC front panel button to issue a weekly test (touch it twice in a row), or you can use the One-Button alert interface under Encoder->Send EAS->One-Button EAS. After issuing the alert, confirm the EAS NET send by traversing to the Server->Logs->Operation Log (or use the quicklink Op Log at the bottom of the page) and looking for the logged results. Look for text logging the Originated Alert. Look for the logged results for the EAS NET clients before the description of the Originated Alert. The log will clearly show if the data connection and transfer was successful or failed from the DASDEC to the SqueezeMax. If it failed go back and look for mistakes in configuration. You can also verify the file transfer on the SqueezeMax under the proper Data directory.
    

  Go to the DASDEC/OneNet Web Browser configuration page Setup->GPIO. Set the #1 GPI input on the DASDEC to Hold Non-National EAS alerts until closure. A GPI contact closure from the Master Control needs to programmed to close upon alert activation on the SqueezeMax. This contact closure needs to be wired up to the DASDEC #1 GPI input on the DASDEC back panel. When an alert has been forwarded, the alert text will be sent to each SqueezeMax client, and then the alert audio playout will pend until the contact closure is made. Master Control can be programmed to make this closure when the SqueezeMax EAS alert is taken to air.
  On the DASDEC Setup->GPIO page, alert triggering via this contact closure can also be restricted based upon FIPS codes and EAS codes.  Use the provided DASDEC GPIO Activation Filter Configuration user interface to configure this option.

 If you want to have the DASDEC provide a relay contact closure during the alert hold time, set the #2 GPIO Output to During hold of EAS until GPI closure.