Hardware Service v6 - Version History

v6.6.1 3rd October 2025

New Features/Changes:

• Receive From AEQ Device: An option has been added to specify the IP address on which a Receive From AEQ Device listens on.  Previously it would attempt to bind to all network adapters on the computer, but this could sometimes fail depending on the network adapters in the computer.  There is no ability to edit this in the Hardware Configuration Editor, it is a settings file change only.  Contact Broadcast Radio Technical Support if you are using an Receive From AEQ Device that is not receiving line state changes.
• Virtual Network Device: The sending to the configured connections and listeners (TCP, UDP, COM port) has been parallelised to decrease latency.

The following issues have been fixed:

• Hardware Configuration: Send To AEQ Device configuration UI had no ability to enter the device's IP address.

• Hardware Monitor:  Manually turning off a line with the checkbox sometimes failed to apply the change and send it to the server.

• Virtual Network Device: The TCP Connect feature was not connecting to the configured endpoint.

v6.5.4 31st July 2025

New Features/Changes:

• Hardware Configuration backup files: The backup files that are created when you change your hardware settings are now given a date to show when they were created.

The following issues have been fixed:

• Hardware Configuration: Upgrading from v5 would not import line commands for Virtual GPIO devices.

v6.5.3 10th July 2025

New Features/Changes:

• Virtual GPIO device: You can now use computer names as an alternative to IP addresses when connecting OUT to a remote device.

The following issues have been fixed:

• Hardware Configuration: Exporting out a Virtual GPIO device to a hardware profile file could fail with an error message about null values.
• Virtual GPIO device: Fixed a problem with the devices not responding to HW? queries so were not transferring initial state when interconnecting remote Hardware Services.

v6.5.2 10th June 2025

New Features/Changes:

User interface update:

• All main areas of the Configuration and Monitor applications are now available in English, German and Norwegian.

v6.5.1 29th April 2025

New Features/Changes:

User interface update:

• The entire user interface has been rewritten using the modern Windows Presentation Foundation ("WPF") technology, moving away from the legacy WinForms UI. 
• WPF offers better rendering, particularly when Windows UI scaling is enabled which is increasingly common on modern displays.
•  The Hardware Monitor and Configuration applications have both been updated and now run in dark mode to bring them in line with other 6th generation Broadcast Radio Applications.
• As part of this change, minor UI changes have been made to the Configuration application.

Patch Bay:

• A new PatchBay link direction has been added - One WayWith Inversion.  This sets the destination line to Clear when the source line is Set, and sets the destination line to Set when the source line is Clear.

v6.3.3 3rd March 2025

The following issues have been fixed:

• Hardware Configuration: Saving a very large configuration with a large amount of scripts could fail to save the changes.

v6.3.2 12th February 2025

New Features/Changes:

• Hardware Configuration: Added in example Line Scripts.
• Hardware Configuration: Added additional example scripts for Debug, Hardware and Helper.

The following issues have been fixed:

• Hardware Configuration: Double clicking on some scripts would not add them to the script editor.

v6.3.1 25th November 2024

New Features/Changes:

• Added support for the PI Engineering X-Keys USB HD15 device.

v6.2.1 15th August 2024

Operating System compatibility:

This version requires Windows 10 or higher, or Windows Server 2016 or higher.

Broadcast Radio Software compatibility:

• This new version of the Hardware Service is designed to work with Myriad Playout v6 and all versions of SmartSign.
• Important: This software is not compatible with Myriad Playout v5 or Myriad Logging v5, so if you are using either of these products then you should use Hardware Service v5 instead.

New Features/Changes:

Scripting:

• The Hardware Service v6 contains a brand new powerful scripting language that allows you to build powerful action sequences that are triggered when the service starts up or when a hardware line changes.
• The scripting language allows you to read and write the status of every line in the system, as well as calling remote web services using GET or POST methods. Standard mathematic operations as found in JavaScript can aslo be used. You can also use block functions such as Do-While, If and Switch, and also create and call functions to simplify code layout.
• There are 3 separate scenarios that you can write scripts for:
  • Service Start: This script runs when the service has completed it's startup process, so is useful when you need to set an initial state for some lines -  for example, you might want to set a certain set of lines to be "on" at startup.
  • Global line change: This script runs whenever ANY line changes on ANY device that the Hardware Service is configured with. This can be useful if you need to use the same script on multiple lines but don't want to have to duplicate it onto each individual line.

The Context object can be used within a script to determine what caused the script to run.

Important changes from previous v6.1 Beta release - the REST method signatures have changed to use deviceReference instead of deviceLine. You will need to update any calls to these REST API. The WriteLine method has also changed to remove the pulseDuration. If you want pulse a line, use the dedicated PulseLine REST method instead. Please see the REST documentation for more information.