Instrucciones de Actualización de Software y Notas de la Versión de Axia Iqx Versión 1412

Category view

Axia iQx version 1.4.12 software, update
instructions, and release notes
Published on Dec 30, 2024

Article summary
Scope
This article covers the (2001-00518-000) Axia iQx AoIP Console.
Preparation for Update
Axia iQx has two internal memory banks. Each bank contains room for a complete version of
operating software. This approach allows a software update download to be completed and
checked without the danger of making the unit inoperable if the download were to be
incomplete or corrupted. It also provides an easy way to try a new software version and still
return to the old version.
You can see the software version in each bank from the Setup web page. The lower half of
this screen, pictured below, shows the software versions present and allows you to select the
bank used at startup. To change banks, click the radio button for the desired bank and then
click on Change active bank.
Upload New Software
Note that while some consoles look similar, this does not apply to the Axia iQ or Radius
consoles that use the QOR engine.
This version has been replace by version 1.4.24, please see this version for updates
IMPORTANT! The iQx will reboot after you click
. Rebooting will
result in the loss of audio locally and at any unit using the local sources.

1. Click here to download the 1601-00569-005-iQx-1.4.12.pkg update file to a location on
your computer.
2. Using a Web browser, connect to the iQx to be updated.
3. Click on the Setup link under System on the left-side menu.
4. Under the Software update heading, click on the "Choose File" button, browse for, and
select the update file you downloaded in the first step.
Once updated, the name of the file you have uploaded will be displayed to the right of
the Choose File button, as shown.
5. Click the Upload image button.
The new version automatically uploads to the unused software bank.
This file must be uploaded to your iQx precisely as is. You can change the name of
the file when you save it, however, do not attempt to unpack the file.

6. When you are ready, select the new version by clicking the radio button next to it, then
click the  
button.
Known Issues
Surface firmware response to soft boot (#10918)
In some cases, the surface firmware will not respond to reset which happens during
a soft boot. This results in losing communication to the surface. You may need to
power cycle the iQx after updates from 1.2.2 or earlier.
Re-sync to Arbitrary PTP clock (#11028)
If the PTP source is an arbitrary clock (no GPS clock) and that device reboots, the
drastic shift in time can lead to difficulty in the iQx to re-sync. We recommend using
a PTP grandmaster, which keeps maintains current time. Alternatively, when the
sync is lost, reboot the iQx.
Release Notes
All fixes and features are rolled up from previous versions. You do not need to do incremental
updates. For example, if you are running 1.2.2, you do not need to update to 1.3.2 first. This
1.4.12 release already includes those.
Version 1.4.2 Features and Enhancements.
Added new HTML Surface option as licensable feature. Please contact your dealer for
information on this option and ask for part number 3002-00084-000 HTML5 Remote
for iQx
Some customers have indicated that after upload, the version shows 1_0.0.0 (15 Apr
2021 16:13:22) as in this image.
If this is the case, verify that the DATE shown is 15 Apr 2021 and proceed.
NOTE: This was resolved in version 1.3.2, but when upgrading from previous
versions, there may still be a need to power cycle after the reboot.

This feature is activated by clicking on License Management on the menu, pasting in your
License Key and Clicking Add License.
The feature is accessed by clicking Surface in the side menu. The HTML Surface is the same
as found in the iQs Virtual console.
Improved the meter decay rate to -12dB/sec
Version 1.4.12 Fixes
(iProbe) Fixed issues where wrong software numbering shown in iProbe.
(iProbe) Fixed issue where wrong logo shown in iProbe
(AES 67) Fixed issue where SIP Unicast mode was not working
Fixed rare issue where the surface locks up.
Memory now dumped to /var/crash on abnormal program termination
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.

Documento adaptado por Ing. Sebastián Vallejos

Axia Iqx Version 133 Software Update Instructions And Release Notes

Category view

Axia iQx version 1.3.3 software, update instructions,
and release notes
Published on Dec 30, 2024

Article summary
As of 15 April 2021 this version has been superceeded by version 1.4.12. Please click here to
go to that document.
Scope
This article covers the (2001-00518-000) Axia iQx AoIP Console.
Preparation for Update
An Axia iQx has two internal memory banks. Each bank contains room for a complete
version of operating software. This approach allows a software update download to be
completed and checked without danger of making the unit inoperable if the download were
to be incomplete or corrupted. It also provides an easy way to try a new software version and
still return to the old version.
You can see the software version in each bank from the Setup web page. The lower half of
this screen, pictured below, shows the software versions present and allows you to select the
bank used at startup. To change banks, click the radio button for the desired bank and then
click on Change active bank.
Upload New Software
Note that while some consoles look similar, this does not apply to the Axia iQ or Radius
consoles that use the QOR engine.
IMPORTANT! The iQx will reboot after you click Change active bank . Rebooting will
result in loss of audio locally, and at any unit using the local sources.

1. Click here to download the 1601-00569-004-iQx-r_1.3.3D.pkg update file to a location
on your computer.
2. Using a Web browser, connect to the iQx to be updated.
3. Click on the Setup link under System on the left-side menu.
4. Under the Software update heading, click on the "Choose File" button, browse for, and
select the update file you downloaded in the first step.
Once updated, the name of the file you have uploaded will be displayed to the right of
the Choose File button, as shown.
5. Click the Upload image button.
This file must be uploaded to your iQx precisely as is. You can change the name of
the file when you save it, however, do not attempt to unpack the file.

The new version automatically uploads to the unused software bank. Please ensure that
the new version number is displayed.
6. When you are ready, select the new version by clicking the radio button next to it, then
click the "Change active bank" button.
Known Issues
Surface firmware response to soft boot (#10918)
In some cases, the surface firmware will not respond to reset which happens during
a soft boot. This results in losing communication to the surface. You may need to
power cycle the iQx after updates from 1.2.2 or earlier.
Re-sync to Arbitrary PTP clock (#11028)
If the PTP source is an arbitrary clock (no GPS clock) and that device reboots, the
drastic shift in time can lead to difficulty in the iQx to re-sync. We recommend using
a PTP grandmaster, which keeps maintains current time. Alternatively, when the
sync is lost, reboot the iQx.
Release Notes
Version 1.3.3 Fixes
Fixed an issue where the DSCP tag was missing from audio outputs
Version 1.3.2 Fixes
Fixed a memory leak when constantly polling show profiles. 84 bytes per poll, which
would take about 5 million iterations before memory was depleted. If we assume polling
every second, it will take 60 days to run out of memory. Not likely anyone was impacted
by this, but a leak is a leak.
NOTE: This was resolved in version 1.3.2, but when upgrading from previous
versions, there may still be a need to power cycle after the reboot.

Shutdown sequence of CAN ports added to soft boot sequence to mitigate observations
of CAN port failure on the reboot.
Version 1.3.2 Features
Automix Functionality.
A new menu item is added to the Show Profiles screen, Automixer. Allows the user
to enable the channel into Automix and to define the priority within the mix. Zero (0)
is the lowest priority, and nine (9) is the highest priority.
Version 1.1.2 Fixes
Audio Delay issue MIC to HP (#11970)
AES67 offset misbehaving (#11156) (#12007)
AES67 offset not applied to VMIX (#11646)
MTR data in support of IP-Tablet and Pathfinder (#11237)
LWRP LVL function is not present (#11876)
3dB loss coming from the system (#12084)
Added support for non-standard RTP receive ports
Removed debug print that was spamming the log
Version 1.1.2 Features
Added the option to be able to sync to Livewire
Sync page now had a drop-down to select PTP or Livewire. (PTP is the default)
Added external indicator of SYNC Status
The Studio OLED now has text at the bottom right, indicating SYNC status. If not
OK, the text will blink.

Documento adaptado por Ing. Sebastián Vallejos

Axia Iqs 1

Category view
Axia iQs (AE1000)
3 Sub categories
1 Articles
Axia iQs AES67 Mixing Console
Published on Nov 18, 2024
With the introduction in 2019 of the Axia iQx, we combined the mix engine and control surface into one unit,
providing a simple, easy-to-install console capable of accessing any audio source on the network anywhere in the
world. iQs takes things…
Axia IQs (AE1000) Help Documents
2 Articles
Version 1.0.0
2 Sub categories
1 Articles
Version 1.1.33
3 Sub categories
1 Articles

Documento adaptado por Ing. Sebastián Vallejos

Axia Iprobe

Category view
Axia iProbe
1 Sub categories
Axia iProbe Help Documents
5 Articles

Documento adaptado por Ing. Sebastián Vallejos

Axia Iprobe Update Instructions And Release Notes

Category view

Axia iProbe Update Instructions and Release Notes
Updated on Jan 21, 2025

Article summary
Axia iProbe v1.2.1.4
Installation and Version Notes  
14 April, 2013
Installation Procedure:
1. Download the 3001-00040-019-iProbe-1.2.14.zip file and save it to a location on your
computer.
2. Install all service packs and critical updates for your Windows operating system before
proceeding.
3. Locate your License Number License Key before updating your existing version.
If you are installing v1.2.0 on a fresh machine, there is no need to install any previous
versions first your license key with work with a fresh installation of iProbe.
4. Uninstall the current version.
At the end of the uninstall process, you may be prompted to restart your PC.  Please
do so before continuing with the installation.
5. Unzip 3001-00040-018-iProbe-1.2.13.zip and double-click the Windows MSI file
 (iProbe.msi) to begin the installation. Follow the step-by-step procedure and enter your
License Number when prompted. Note: License numbers are all UPPER CASE and are
case sensitive.
6. At the end of the installation, you may be prompted to restart your PC. Once Windows
has restarted, the installation is complete.

For additional information, please consult the manual for iProbe, which can be found in PDF
format by clicking here.
Release Notes for v1.2.1.4  
New and Updated Features
iProbe now handles file names with beta identifiers like -XXX in the file name
Bug fixes
Fixed an issue where restoring from the BOOTPS screen was not working.
Release Notes for v1.2.1.3
New and Updated Features:
iProbe Protocol has been updated to be easier to implement for device manufacturers.
iProbe implements the new protocol completely while maintaining backward
compatibility.
iPlay stop button is now a play/stop toggle. Pressing play will play the last played
channel, if any.
iPlay component can now listen to Backfeeds.
iProbe now caches device icons, reducing network utilization
Bug Fixes:
Fixed a bug where omitting the forward slash from the FTP URL of a device's firmware
update caused failure to find and download them.
Fixed a crash bug traced to memory corruption in iProbe s Internet Explorer component.
Fixed a bug that resulted in incorrect meter values.
Fixed a bug that caused the device list to lose ordering if filtered
Fixed a bug that produced iPlay output garbage on computers with multiple network
interfaces

Fixed a bug that produced crashes when working with devices whose names contained
invalid filename characters.
Corrected handling of syslog filter level setting.
Release Notes for v1.2.0
New and Updated Features:
Automatic configuration backup and restore backed by Windows Task Scheduler.
iProbe can now be minimized to the notification area.
iProbe can now be bound to a specific network interface.
Full configuration backups are grouped into separate directories for easier management.
Bug Fixes:
Corrected a condition that resulted in an incomplete source list being presented to the
user.
Release Notes for v1.1.4
New and Updated Features:
New graphical design.
Works in Windows Vista and Windows 7, 32-bit and 64-bit versions, without elevation.
Inactive devices are now removed from the device list.
#0 and disabled duplicate channel errors are no longer shown.
Configuration backups and firmware updates are now stored in folders, which will be
common to all versions of iProbe from v1.1.4 on. On the first run, iProbe will
automatically migrate old files to the new locations.
Bug Fixes:
Various minor fixes.

Release Notes for v1.1.3
New and Updated Features:
iProbe's integrated BOOTP server now works properly on machines with multiple
network interfaces. The response is broadcast from the interface that received the
request.
iProbe now displays hostnames of LWRP devices (computers running IP-Audio Driver)
that respond to the IP command.
Bug Fixes:
Fixed problems caused by machines that have IPv6 enabled. iProbe now disregards IPv6
interfaces.
Release Notes for V1.1.2.4
New and Updated Features:
Password support for Axia Studio Engine.
Bug Fixes:
Configuration backup of Studio Engine. The system page now gives the proper Bank ID
after the bank switch.
Recommended version algorithm changed. iProbe no longer erroneously recommends
updating if the installed software version is higher than the downloaded package.
Nodes with user passwords in effect are now updated properly.

Documento adaptado por Ing. Sebastián Vallejos

Axia Intercom

Category view
Axia Intercom (Discontinued)
1 Sub categories
Axia Intercom Help Documents
5 Articles

Documento adaptado por Ing. Sebastián Vallejos

Axia Gpio For Show Profile Switching Iq Radius Raq And Desq Series Consoles Only

Category view

Axia GPIO for Show Profile Switching (iQ, Radius,
RaQ, and DesQ series consoles only)
Published on Dec 16, 2024

Article summary
Scope
This document covers the configuration of GPIO for control, and an indication of Show
Profiles in the iQ-series consoles. At the time of this writing, this includes;
iQ or Radius (with a QOR console engine)
iQx (built-in console engine)
iQs (virtual console with AE1000 engine)
Description
In addition to manually loading show profiles from the console surface, Show Profiles can be
recalled and the current profile indicated by GPIO. This is most useful when you want
something external to load the profile.; for example, an automation system.
Configuration
Remote control for Show Profiles and their status uses multicast GPIO (an unused Livewire
channel) to communicate status with a GPIO port somewhere on the system. The GPIO port
could be a physical port on the back of a QOR or GPIO node where you would physically
connect wires to the inputs for control and output to drive status lamps, control a switcher,
etc.  
Additionally, virtual GPIO ports like those found on the Axia IP-Audio Driver are
controllable by my third-party automation systems and require no wiring.  The premise is the
iQ Console Show Profiles are also controllable using Pathfinder. GPIO is NOT required.
This method is provided as an alternate method for control and monitoring of the Show
Profile.

same.  GPI 2 loads Profile A regardless of whether a physical or virtual port trips the pin.
In addition to controlling what Profile is loaded, the associated GPO (output) is active anytime
the Profile is active. Load Profile A, GPO 2 is active. Load profile B, GPO 3 is active.
Show Profile GPIO Configuration
1. Log in to the Web Page of the console you are configuring.
2. On the left side menu, click the Shows link.
3. Enter an unused Livewire channel in the Logic Port for Show Switching.  
4. Click Save.
We do not provide support for any automation system configuration directly. Please
contact your automation vendor for information on controlling Axia GPIO.
One practical application is to control a switcher or other audio route based on what
Profile is loaded. For example, when the "On Air" profile is loaded, the Record Bus
might be routed to the Automation system for recording phone calls, etc. When a
"Production" profile is loaded, some other Program Bus is routed to the automation or
recording software inputs.

GPIO Configuration
QPIO Ports on a QOR
GPIO Ports on an xNode
GPIO on an Axia IP-Audio Driver
Note that the GPIO channel entered in the previous step DOES NOT ADVERTISE. You
must type the channel manually in the following configurations.
The GPIO channel in the Axia Driver and the Audio Channel do NOT need to match. It's
okay to use channel 1001 for audio output and channel 16104 for GPIO.

Show Profile GPIO Table
Inputs (GPI)
Outputs (GPO)
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.
ID
Name
Pin
Notes
GPI 1
None command
Pin 11
Changes to the blank profile
GPI 2
Profile A command
Pin 12
Change to the A profile
GPI 3
Profile B command
Pin 13
Change to the B profile
GPI 4
Profile C command
Pin 14
Change to the C profile
GPI 5
Profile D command
Pin 15
Change to the D profile
ID
Name
Pin
Notes
GPO 1
Profile None lamp
Pin 1
Active when None
GPO 2
Profile A lamp
Pin 2
Active when A
GPO 3
Profile B lamp
Pin 3
Active when B
GPO 4
Profile C lamp
Pin 4
Active when C
GPO 5
Profile D lamp
Pin 5
Active when D

Documento adaptado por Ing. Sebastián Vallejos

Audio Interface Setup For Webrtc

Category view

Audio Interface Setup for WebRTC
Published on Dec 30, 2024

Article summary
Scope
This article serves as a how-to guide for setting up a source using WebRTC with a Telos
Alliance Axia Altus Virtual Broadcast Console.
Description
This article is meant to help remote users connect with our WebRTC remote monitoring and
contribution solutions. This guide references third-party products and should be used
according to their instructions. If you experience difficulty getting the installation to work, we
are happy to confirm your Altus setup; however, you may need to contact the other company
for further assistance.
Why WebRTC?
Leveraging WebRTC technology enables real-time media communications directly between
browsers and devices, essentially allowing talent at a remote location to connect to the mixer
all they need is an Internet connection and an HTML5-enabled web browser.
The delay in the headphone back-feed is one of the challenges that talent experience when
performing remote mixing, due in large part to the latency from the Internet sending a back-
feed with the voice included this also creates listening difficulty.  
Thankfully, on the Pro Audio side, there are many options available in the marketplace that
allow users to level the remote audio experience without breaking the budget. Let s take an
in-depth look at four options we have tested successfully, these third-party devices enable
users to monitor the local microphone (sidetone) right out of the box.
Options 1 & 2: All-In-One
This is a preferred option for a simple-setup as only two connections required to make this
work; one to the computer for power and audio transfer (typically via USB) and another for

headphone monitoring via a 3.5mm connection. These solutions have a microphone built-in
and it can be plug-and-play. The downside to this solution is there is not an easy way to
connect monitor speakers in addition to local headphones.
1. Elgato Wave 3: Link -> https://www.elgato.com/en/wave-3
a. Elgato Wave XLR: this one lets you choose your microphone, it acts more like a
traditional interface without studio monitor connections. Link ->
https://www.elgato.com/en/wave-xlr
2. Shure MV7: Link -> https://www.shure.com/en-US/products/microphones/mv7
As previously stated, there are other options available; however, the options discussed here
have been tested in the field. The Elgato Wave 3 and Shure MV7 are equipped with settings
for mic gain, headphone volume, and monitoring crossfade built into the microphone;
therefore, no other windows audio settings are required for operation. While these
microphones are compatible with their own software that allows for even more capability, we
encourage you to seek their product information directly for more information.
Option 3 & 4 : Audio Interface + Mic
The approach described below is still a great option and allows more flexibility because you
can select your favorite microphone. The concept is the same – the mic goes into the interface
via XLR, headphones can be used and most interfaces have a direct monitor. This solution
also has the ability to connect studio monitors to use in addition to headphones.
1. Focusrite Solo: Link -> https://focusrite.com/en/audio-interface/scarlett/scarlett-solo
2. Audient EVO 4 USB Audio Interface: Link -> https://evo.audio/products/evo-4/overview/
While we covered four field-tested options as of this writing, there are many others available
due to the broad range of similar products in the category. Please feel free to let us know if
you have found success with additional options.
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.

Documento adaptado por Ing. Sebastián Vallejos