<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting on Innosonix Docs</title><link>https://docs.innosonix.de/categories/troubleshooting/</link><description>Recent content in Troubleshooting on Innosonix Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.innosonix.de/categories/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshoot</title><link>https://docs.innosonix.de/software/idfm/troubleshoot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.innosonix.de/software/idfm/troubleshoot/</guid><description>&lt;h2 id="goal--when-to-use"&gt;Goal / when to use&lt;/h2&gt;
&lt;p&gt;IDFM does not list a device, UDP looks broken, or a firmware update fails. Match the symptom below.&lt;/p&gt;
&lt;h2 id="device-missing-from-the-list"&gt;Device missing from the list&lt;/h2&gt;
&lt;h3 id="symptoms"&gt;Symptoms&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;DEVICES&lt;/strong&gt; stays empty or omits a known amp.&lt;/p&gt;
&lt;h3 id="steps"&gt;Steps&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Confirm PC and amp share the same L2 segment if you expect &lt;strong&gt;UDP&lt;/strong&gt; discovery.&lt;/li&gt;
&lt;li&gt;Check &lt;strong&gt;UDP STATUS&lt;/strong&gt; — see &lt;a href="https://docs.innosonix.de/software/idfm/install/"&gt;Install&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Windows:&lt;/strong&gt; use &lt;strong&gt;HELP&lt;/strong&gt; → FAQ actions to re-apply firewall allow rules for IDFM.&lt;/li&gt;
&lt;li&gt;If you know the IP, use &lt;strong&gt;+&lt;/strong&gt; → add by IP.&lt;/li&gt;
&lt;li&gt;If the amp is on another routed subnet, use &lt;strong&gt;subnet scan&lt;/strong&gt; — broadcast will not cross the router.&lt;/li&gt;
&lt;li&gt;Confirm only one IDFM instance is running.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="expected-result"&gt;Expected result&lt;/h3&gt;
&lt;p&gt;The amp appears via UDP or as a manually added / scanned device.&lt;/p&gt;</description></item><item><title>Troubleshoot</title><link>https://docs.innosonix.de/software/maxxremote/troubleshoot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.innosonix.de/software/maxxremote/troubleshoot/</guid><description>&lt;h2 id="goal--when-to-use"&gt;Goal / when to use&lt;/h2&gt;
&lt;p&gt;Something does not connect, discover, sync, or route audio. Work through the matching section below.&lt;/p&gt;
&lt;h2 id="out-of-sync"&gt;Out of Sync&lt;/h2&gt;
&lt;h3 id="symptoms"&gt;Symptoms&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Floating &lt;strong&gt;OUT OF SYNC&lt;/strong&gt; alert in the UI&lt;/li&gt;
&lt;li&gt;Device &lt;strong&gt;SYNC&lt;/strong&gt; indicator not clean&lt;/li&gt;
&lt;li&gt;Levels or EQ on the amp do not match Maxx Remote&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="why-it-happens"&gt;Why it happens&lt;/h3&gt;
&lt;p&gt;Maxx Remote owns linked channels (&lt;strong&gt;Remote → device&lt;/strong&gt;). Edits in &lt;strong&gt;Maxx Control&lt;/strong&gt;, front-panel/other tools, or failed partial writes create differences. Maxx Remote detects them on periodic check-in.&lt;/p&gt;</description></item></channel></rss>