Telos Aalliance Aero Update Procedure via NF Remote

Software Update Procedure with Nielsen Watermark Verification

Applies to supported Linear Acoustic AERO platforms using NfRemote. Screenshots are taken from an AERO.8000 Nielsen update demonstration and the exact screen layout may vary by model and software version.

1. Purpose

This document describes the basic workflow for updating a Linear Acoustic AERO processor using the NfRemote Windows application. It also includes post-update checks for systems equipped with Nielsen watermarking.

2. Before You Begin

• Confirm the exact AERO model, serial number, current software version, and installed options.

• Obtain the correct Telos Alliance software update package for the specific AERO platform. Do not install an update intended for another product family.

• Use a Windows PC with network access to the AERO and a compatible/current NfRemote client.

• Record or back up important configuration information before maintenance whenever possible.

• Confirm that the facility can tolerate a temporary interruption while the unit updates and restarts.

• For Nielsen-equipped systems, record the existing SID/check digits, CBET information if used, active process, distribution type, and encoder status before updating.

3. Connect to the AERO with NfRemote

Step 1 - Launch NfRemote

Open NfRemote on the service PC. Enter or select the AERO IP address/host entry and the appropriate password. The default password may be 1234 on systems that have not been changed, but use the site-approved credentials whenever they differ.

Step 2 - Connect to the processor

Select the correct AERO entry and click Connect. Confirm that NfRemote opens the intended processor before making any changes.

Step 3 - Verify the target unit

At the top of NfRemote, confirm the product/model or instance information and verify that meters/status information corresponds to the expected system. If multiple processors are stored in NfRemote, verify the IP address and unit identity carefully.

4. Perform the Software Update

Step 4 - Open the NfRemote connection list

Return to the NfRemote connection/host list. The list can contain multiple saved entries for the same or different AERO systems. Highlight the exact unit to be updated.

Step 5 -  Take a Backup

Step 6 - Take down Nielson Information (if used)

Nielson is required to not be backed up and restored during updates. So it is required to take this information down and possibly reinput it after the updated process.

If Nielson is not used, please disregard this Step and move on.

Step 7 - Start the update

Step 8 - Allow the update to complete

Follow the NfRemote prompts and allow the transfer/install process to finish. The unit may disconnect from NfRemote and restart. Do not power-cycle the AERO unless the documented update process or Telos Alliance Support specifically instructs you to do so.

Step 9 - Reconnect after restart

After the processor has completed its restart, reconnect with NfRemote. Allow sufficient time for the AERO services and processing instances to initialize before judging the update as successful.

5. Post-Update Verification

Step 1 - Confirm new Version

Verify the version number, Navigate to System → System → System Information

Step 2 - Confirm normal audio processing

Verify input and output meters, program processing, loudness status, I/O, and any required local/secondary program paths. Confirm that expected instances show Run and that the facility is receiving normal audio.

Step 3 - Verify Nielsen watermarking

On a Nielsen-equipped AERO, select the applicable processing instance and open Nielsen Watermark. Check each required channel group (for example Channel 1-6, Channel 7/8, or Channel 9/10 as applicable). Confirm that Enable is active, Status reports Running, and the expected SID/check digits and CBET settings are present.

Example: Nielsen Watermark page showing an enabled encoder with Status: Running.

Step 4 - Check the Nielsen engine information

Open the About page within Nielsen Watermark and confirm the Nielsen watermark engine information is populated. Record the displayed API/engine/OEM information if required by the maintenance record.

Example: Nielsen Watermark Engine About page after the update.

6. Final Functional Checks

• Confirm the software version displayed by the AERO matches the intended release.

• Confirm all required processing instances are running and audio levels are normal.

• Confirm SDI/AES/AoIP paths used at the site are passing audio as expected.

• Confirm Dolby or other licensed features used by the facility are available and operating.

• For Nielsen systems, verify every required program path is enabled and reports a running encoder.

• If possible, confirm watermark detection using the facility’s normal monitoring/verification method.

• Record the model, serial number, previous version, new version, date, technician, and results of the functional check.

7. Troubleshooting

Let us know how we can help

If we can be of further assistance please reach out to us directly or click the Request Support at the top of this page