Release candidate availability. Version 1.0.1-Rc4 for 25-Seven PDM II

Updated 1 week ago by Bryan Jones

Scope

The following release candidate is available for the 25-Seven Program Dealy Manager II (PDM II). This field update is only for the PDM II and can not be installed on older PDM platforms.


Description

Telos often makes early-release candidates available for general use where they might address issues reported by customers. Release candidates are updates that have not completed the entire approval process. Customers should be aware that unknown issues may exist in these versions and consider these issues before deciding to install. Any KNOWN issues will be noted in the release notes.

A download link to this update is provided in the next section. Please read the release notes before proceeding.

Issues addressed in Version 1.0.1-rc4

#16407: Fixed an issue where confidence meters were inoperative when in bypass

#19077: Fixed an issue where a factory reset might not reset everything

#19479: Fixed an issue where delayed data configuration was not set correctly from Web UI

  • No action is required. After the update, the correct setting will now be shown in the UI.

#20031: The Visible Livewire channels page found under INFORMATION now does not automatically refresh

  • Previously, the page would refresh automatically, making it hard to locate channels. The page can be refreshed manually from the browser.

#20506: Fixed an issue where changes in Livewire DST ADDR values via LWRP would not take effect

  • Livewire DST input changes could be made from the front panel but not by Pathfinder or other automation software.

#17591: Added uptime under the System heading on the INFORMATION page

#19645: PDM Name under CONFIGURATION now sets hostname.

  • Previously the hostname was always "pdmii" which made it difficult to identify in programs like Pathfinder when multiple units existed.

#20087: Added the ability for an AES67 AoIP receiver to receive from other than port 5004.

  • A new AES67 Rx Port is available when AES67 is chosen as the input type. Note that this is only available via the front panel or the front panel control in the Web UI.

#20435: Debounce GPIO inputs

  • GPIO is polled every 5ms. The change must last for three consecutive samples before being recognized

#20436: Additional logging of button press and release states.

#20284: TelosConnect has been renamed to SupportLink in the Web UI

#20584: Fixed issue where Livewire GPI and GPO would not work other than port 1


Installing the update

Do I need to bypass my unit before updating?

The short answer is maybe.

All PDMs contain a BYPASS relay; however, the BYPASS can only bypass the same PHYSICAL sources (Analog in to Analog out, etc.) and does not bypass any AoIP sources. Please refer to this document for more information on how BYPASS works in the PDM II.

Plan accordingly.

Getting the file and updating the firmware

  1. Click here to download the update. Store this file in a location on your computer for use in the next steps.
  2. In a Web Browser, navigate and log in to your PDM II.
  3. Click the UTILITIES link from the main menu across the top.
  4. Click the Choose File button. Then browse for and locate the update file you downloaded in step 1.
  5. Click the Install package button. The installer package will be uploaded to the unused bank. In this example, note that Bank 1 is the running bank, so the button says "Install package on Bank 0". THIS STEP WILL NOT CAUSE A PDM REBOOT and is safe to complete while the PDM II is in use.
CAUTION - Next step is to reboot the PDM II. Plan your bypass strategies accordingly.
  1. When ready to ACTIVATE the new firmware version click the Reboot from Bank X button.
There is no additional warning. Once the button is clicked, the PDM II will immediately reboot. A Full reboot should take around 60 seconds for the audio to be restored.

  1. Verify that **** Current Bank **** has switched to the newly updated version.


Let us know how we can help

If you have further questions on this topic or have ideas about improving this document please contact us


How did we do?