IDFM
IDFM (Innosonix Device and Firmware Manager): discover amplifiers, set IP and hostname, and update firmware before Maxx Control or Maxx Remote.
IDFM (Innosonix Device and Firmware Manager) is a desktop Electron app for bringing amplifiers onto a working network plan and keeping firmware current. Use it before Maxx Control or Maxx Remote. That workflow includes micro MAXX and other MAXX amplifiers.
| Need | Tool |
|---|
| Discover amps, set IP / hostname, update firmware | IDFM (this section) |
| One amplifier — DSP, routing, device settings in the browser | Maxx Control (on the device) |
| Many amplifiers — projects, groups, offline planning | Maxx Remote |
Tip
Always finish network and firmware setup in IDFM first. Maxx Remote and Maxx Control assume devices are already reachable on a planned IP.
Download
Get IDFM from the Innosonix downloads page (IDFM tab):
| Platform | Artifact |
|---|
| Windows | .exe installer (NSIS) |
| Linux | .AppImage |
| macOS | .dmg (universal) |
Product overview: innosonix.de/software.
Recommended path
- Install IDFM and confirm UDP STATUS.
- Discover devices and set IP (hostname / identify as needed).
- Update firmware if newer images are available.
- Continue with Maxx Control (single amp) or Maxx Remote (multi-amp).
How discovery works
IDFM has two ways to get devices into the list — they are not two equal “discovery protocols”:
| Method | When | How |
|---|
| UDP broadcast | Same L2 segment / VLAN (preferred) | Broadcast to 255.255.255.255 on UDP 9453. Works even if the amp’s IP is on a different subnet than the PC, so you can still change IP settings. |
| Add by IP / subnet scan | Routed networks where broadcast stops at a router | You add a known IP, or scan a /24 range. IDFM then probes the device over HTTP (device REST API) — and the loader path when needed. |
Routers do not forward UDP broadcast. Across VLANs, use add-by-IP or range scan — see Discover and IP.
Ports (PC ↔ amplifier)
| Traffic | Port / address | Purpose |
|---|
| UDP 9453 | broadcast 255.255.255.255 | Automatic discovery and UDP-based network config |
| TCP 9454 | amplifier IP | Firmware loader / update path |
| HTTP | amplifier IP (device REST, typically port 80) | Manual add and subnet-scan probe (/rest-api/…) |
Some update paths also use HTTP 8080 on the device for file upload. Allow these in the PC firewall (and between VLANs when you use scan/add).
In this section
| Page | Use when |
|---|
| Install | First download, platforms, firewall / UDP status |
| Discover and IP | Find devices, STATIC/DHCP, hostname, identify, routed nets |
| Firmware | Download / import .inx, multi-device update, offline; MAXX² bootloader fallback |
| Troubleshoot | Missing devices, port in use, update failures |
1 - Install
Install IDFM on Windows, macOS, or Linux from the Innosonix downloads page, then confirm UDP discovery is allowed on the commissioning PC.
Goal / when to use
Get IDFM running on the PC you will use for commissioning so amplifiers can be discovered and configured.
Download
- Open the Innosonix downloads page.
- Select the IDFM tab.
- Download the build for your OS:
| OS | File | Notes |
|---|
| Windows | idfm-….exe | NSIS installer — choose install directory; desktop / Start menu shortcuts available |
| Linux | idfm-….AppImage | Make executable, then run (no separate installer) |
| macOS | idfm-….dmg | Universal build; open the DMG and install the app as usual |
IDFM may offer an in-app update when a newer tool version is published on the download service.
First launch
- Start IDFM.
- Open the DEVICES page (default).
- Check UDP STATUS (top right).
- Confirm devices appear, or that the status does not show UDP blocked / port unavailable.
Expected result
The device table loads. Online count updates as amps answer discovery. If nothing appears yet, continue with Discover and IP (same L2 segment, or add/scan).
Firewall and UDP status
Automatic discovery uses UDP 9453. The PC firewall must allow IDFM to send and receive that traffic on your control network.
- Use UDP STATUS to see whether discovery sockets are healthy on local interfaces.
- If another IDFM instance is already running, you may see a port already in use message — quit the other instance.
- Windows: if devices never appear, open HELP in IDFM. The FAQ can re-apply Windows firewall allow rules for the app, or (last resort) temporarily disable the firewall profile while diagnosing. Prefer fixing rules over leaving the firewall off.
macOS
On first use, grant local network access if the system prompts. Discovery needs it.
2 - Discover and IP
Use IDFM to find Innosonix amplifiers (UDP discovery or add/scan), then set STATIC-IP or DHCP, hostname, and identify the physical unit.
Goal / when to use
Put every amplifier on the site IP plan: discover (or add) devices, set STATIC-IP or DHCP, name them, and confirm which physical unit is which.
Prerequisites
- IDFM installed with healthy UDP STATUS when you expect automatic discovery
- PC on the same L2 segment as the amps for UDP broadcast, or known amp IPs / reachable routed subnet for add/scan
UDP discovery (preferred)
On the same switch / VLAN, IDFM discovers amps with UDP broadcast on port 9453 (255.255.255.255).
- Open DEVICES.
- Wait for rows to appear (hostname, model, firmware, IP, status).
- Filter or sort the table if you have many units.
UDP discovery still works when the amp’s configured IP is on a different subnet than the PC — as long as they share the same broadcast domain. That is how you recover “wrong IP” units without serial console access.
Example (wrong subnet, same switch)
PC: 192.168.0.33 / 255.255.255.0
Amplifier: 192.168.99.2 / 255.255.255.0
Unicast HTTP may fail, but UDP discovery can still list the amp and accept a new IP configuration.
Expected result
Amps show as online in the list. You can open IP / hostname dialogs from the row.
Set IP (STATIC or DHCP)
- Click the IP cell for the device.
- Choose TYPE:
- STATIC-IP — enter IP, subnet, gateway
- DHCP — device takes an address from the DHCP server
- Click SET.
- Optional on DHCP: NEW DHCP LEASE to renew.
After a STATIC change, wait a few seconds for the list to refresh. After DHCP, the old address may go offline until the amp reappears with the new lease.
Tip
For installed systems that Maxx Remote will manage, prefer planned STATIC-IP (or reserved DHCP) so discovery and linking stay stable.
Hostname and identify
| Action | How |
|---|
| Hostname | Click the hostname cell → enter a unique name → SET HOSTNAME |
| Identify | Use IDENT on the row so the physical amp signals which unit you selected |
| Location | Optional site text via the location cell (stored on the device when reachable over HTTP) |
| Device page | Use the external/page control to open the amp’s web UI (Maxx Control) once the IP is reachable |
Add by IP or subnet scan (routed networks)
Routers do not forward UDP broadcast. If the PC and amps are on different routed VLANs, use + above the device list:
- Add by IP — enter a known amplifier IP (device must answer ping / HTTP).
- Subnet scan — enter the first three octets of the target
/24 (for example 192.168.99) and scan. IDFM probes live hosts via the device HTTP REST API.
Example (routed VLANs)
VLAN1: PC 192.168.0.33 / 24
|
ROUTER
|
VLAN2: Amplifier 192.168.99.2 / 24
Scan or add in 192.168.99.0–255. After add, configure IP/hostname as needed (unicast path must reach the amp).
Expected result
Added devices appear in the list (often marked as manually added). Save the list if you want them remembered on next launch.
On DEVICES you can save, clear, or export the current device list. Saving helps when you rely on manually added units across sessions.
3 - Firmware
Update amplifier firmware in IDFM: download or import .inx packages and flash one or many devices before Maxx Control or Maxx Remote commissioning.
Goal / when to use
Bring amplifiers to a known, current firmware before commissioning with Maxx Control or Maxx Remote.
Note
Keep devices on a current release when possible — newer firmware includes stability and security fixes.
Prerequisites
- Devices listed and reachable in Discover and IP
- For a successful update, the PC and amplifier should share a reachable unicast path on the same subnet (loader / update traffic is not the same as UDP discovery-only)
- Internet on the PC to fetch images from Innosonix, or
.inx files copied from another machine
Check for updates
- Start IDFM with network access.
- Open the FIRMWARE tab. A red badge can indicate newer images are available to download.
- The FIRMWARE UPDATES control (when shown) summarizes devices that have a newer release than they are running.
IDFM compares discovered device versions against the firmware catalog and images you have stored locally.
Download firmware (online)
- Open FIRMWARE.
- Download the images you need for the models on site.
- Files are kept on the PC so you can update later without internet.
Local store (created by the app):
~/Innosonix/IDFM/firmwareStorageFolderIDFM/
(On Windows, under your user home directory with the same folder names.)
Import firmware (offline)
When the commissioning PC has no internet:
- On a connected machine, download
.inx files from the downloads page (or download them inside IDFM and copy from the store above). - Transfer via USB or similar.
- In IDFM FIRMWARE, import the
.inx file(s).
Update devices
- On DEVICES, select the units to update (or open update from the toolbar).
- Choose UPDATE DEVICES / the firmware update flow.
- Confirm the target image per model.
- Start the update and wait until each unit finishes and returns to a running state.
You can update multiple devices in one session when images are already local.
Expected result
Device firmware columns show the new version. Amps reboot as required and come back online in the list.
Important
Do not power-cycle amps mid-update. If a unit is already in the firmware loader and not on the same subnet as the PC, connect the PC directly (or fix routing) before retrying — see Troubleshoot.
Manual bootloader fallback (MAXX²)
On MAXX² amplifiers with a front-panel display (for example MA32/D², MA32/LP², and similar models), you can force the device into bootloader mode from the front panel. Use this when you want more manual control over the update workflow, or as a recovery path when a normal update does not start.
Warning
Use this only when needed. Power the device off before you start, follow site electrical safety rules, and keep holding ESC + OK until the bootloader is active.
Steps
- Power the amplifier off.
- Hold ESC + OK on the front panel.
- Power the amplifier on while keeping ESC + OK held until it enters bootloader mode.
- In IDFM, select the device and run the firmware update with the correct
.inx image (see Update devices above).
Expected result
The amp appears ready for an IDFM update from bootloader / loader state. After the update finishes, it returns to a normal running status.
4 - Troubleshoot
Troubleshoot IDFM when amplifiers are missing, UDP discovery fails across VLANs, or firmware updates do not complete.
Goal / when to use
IDFM does not list a device, UDP looks broken, or a firmware update fails. Match the symptom below.
Device missing from the list
Symptoms
DEVICES stays empty or omits a known amp.
Steps
- Confirm PC and amp share the same L2 segment if you expect UDP discovery.
- Check UDP STATUS — see Install.
- Windows: use HELP → FAQ actions to re-apply firewall allow rules for IDFM.
- If you know the IP, use + → add by IP.
- If the amp is on another routed subnet, use subnet scan — broadcast will not cross the router.
- Confirm only one IDFM instance is running.
Expected result
The amp appears via UDP or as a manually added / scanned device.
Port already in use
Symptoms
Message that the required port is already in use.
Steps
- Quit other IDFM windows / instances.
- Restart IDFM.
- If it persists, check whether another tool on the PC is bound to UDP 9453.
Expected result
Discovery starts; UDP STATUS is healthy.
Routed VLANs / no automatic discovery
Symptoms
Amps never appear until you type an IP; Maxx Remote discovery is also empty on the same PC.
Why
UDP broadcast (9453 to 255.255.255.255) stops at routers. That is expected.
Steps
- Add by IP or scan the remote
/24 — see Discover and IP. - Ensure the PC can ping and reach device HTTP (REST) on that VLAN.
- After IP plan is correct, Maxx Remote can use manual add the same way — see Maxx Remote · Prerequisites.
Firmware update fails
Symptoms
Update warning about subnet / reachability; device stuck in loader; progress never finishes.
Steps
- Put the PC on the same subnet as the amp management IP (unicast path for loader TCP 9454 / update). UDP discovery alone is not enough.
- Download or import the correct
.inx for that model first (FIRMWARE tab). - If the unit is already waiting in the loader and still unreachable from your current network, connect the PC directly to the amp (or fix routing) and retry.
- Do not power-cycle during the update unless support instructs you to.
- If you need a more manual recovery path on a MAXX² front-panel amp, force bootloader mode with ESC + OK at power-up, then update from IDFM — see Manual bootloader fallback.
Expected result
Update completes; device returns to a running status with the new version.