I am having issues sucessfully connecting my SQ5 to my router, a new Netgear RAX20.
Neither static nor DHCP is working.
The network connectivity LED on the back is glowing yellow, and my router LEDs signal a connection on the port the SQ is connected to.
My routers admin page does not show the SQ5 in its list of wired devices.
I have tried connecting a laptop to the router with the same cable on the same port as I did the SQ5, and the laptop successfully connects with both static and DHCP.
I also tried connecting the SQ5 to a second router, and the issues are the same.
When attempting a DHCP-based connection I get the following settings, indicative of an unsuccessful connection:
IP Address: 169.254.197.30()
Subnet Mask: 255.255.0.0()
Gateway: 0.0.0.0(*)
I attempted a downgrade to v1.5.0 as well as a hard reset (HF + IN while powering on).
Any tips on other things to try before contacting support?
The ā(*)ā and the assigned addresses imply that your unit has a self-assigned IP, which happens when it does not receive one from elsewhere (e.g. the router).
If your router is definitely set up to provide an address, the simplest thing to try would be to switch to static then switch back to DHCP with the router connected.
The SQ would then be looking for an address again.
Thereās more info in the SQ-MixPad help about this which you can see by touching the ā?ā in the āChoose Unitā screen or by going to āHelpā from the top left menu.
I have changed between static and DHCP multiple times using both routers, and on both versions 1.5.0 and 1.5.1, and before and after doing the hard reset.
Both routers are giving correct IP settings to my laptop when connected to the same port with the same cable, meaning DHCP is working as it should on the routers.
Static IP assignment should also work on these routers, but does not work for the SQ5.
As I mentioned this used to work on the exact same router last time I tried, about a month ago.
I also hooked it up to a third router, which I was using regularly in the past with the SQ5, and there was no network connection there either.
I suspect I need to get someone to take a look at it, unless there are other magic buttons to press to reset or get detailed diagnostics.
Your testing is sound, and unfortunately with that extra confirmation of doing everything correctly multiple times with software/firmware, it does point to something going on with the hardware.
This could be something as simple as a bent pin in the socket, but may go deeper.
Do check the socket, but otherwise please get in touch with your local distributor (https://www.allen-heath.com/where-to-buy/) who will be able to get this sorted for you.
Sorry, Ive forgotten to tell you how this story ended! I was just about to ship the mixer to the distributor, when someone said (I donāt know who, I was alone): āTest it once more!ā And so I did, connecting everything exactly as the night beforeā¦and it worked. And has done since, with both MixPad and Mixing Station Pro. I am left with equipment in perfect order AND the uncertainty that this might happen again since we never found out what caused the problem.
Greetings from rainy Western Norway!
BjĆørn
Sorry, Ive forgotten to tell you how this story ended! I was just about to ship the mixer to the distributor, when someone said (I donāt know who, I was alone): āTest it once more!ā And so I did, connecting everything exactly as the night beforeā¦.and it worked. And has done since, with both MixPad and Mixing Station Pro. I am left with equipment in perfect order AND the uncertainty that this might happen again since we never found out what caused the problem.
Greetings from rainy Western Norway!
BjĆørn
Thanks for the update.
Good newsā¦ sort of. Self healing problems still kind of scare me as you mentioned with the uncertainty!
I have had similar issues with three different SQ5ās. Two of them were house boards and were not well taken care of, and the third one is my own console which I care for like itās my own child. All three have been used with a Netgear routers and an Apple Airport Extreme. Iāve found that the order of boot up and connecting external hardware often impacts wether or not the console acquires an IP. Typically, I find that if I power the console and router up before connecting them and giving the router a decent amount of time to start, log into a user on the console (if applicable), then connect the consoles network port to the router before connecting anything else to the console, the console typically acquires an IP with no issues. If I connect an Slink device or a USB device (via the rear USB port), before connecting the console to the router, the console tends to not acquire an IP. This can usually be fixed by powering off the console, unplugging all external connections, restarting the console, and connecting the console to the router again before connecting any other Slink or USB connections. Sometimes toggling DHCP after disconnecting all external conenctions works as well but not often. All of this doesnāt always work though, and sometimes the consoles just wonāt acquire an IP at all. All three of them seem to experience cycles of, acquiring an IP no matter the boot up/connection order, only acquiring an IP when the boot up/connection order is followed, and not acquiring an IP no matter what. Often it takes multiple reboots and toggling network options over and over to get an IP in the case of the latter. Each cycle tends to last 1 to 3 weeks and then seems to randomly start displaying different behavior or just starts working again for a week or so before going back to struggling with acquiring an IP. It is honestly strange as any other device connected to the network, a phone, ipad, computer, etc, never has issues. Right now my personal SQ5 hasnāt acquired an IP at all for the last two days.
Apologies for resurrecting this zombie thread, but wanted to give credit where it is due.
I read this ages ago, and that one sentence apparently lodged in the depths of my brain. Thankfully it did.
Was dealing with a guest engineer today who had an SQ5 that would show no connection to his access point for him to control his console through the iPad app.
After failed troubleshooting it suddenly came back to me, so got him to take a look at the port. Lo and behold, 3 PINS were out of place!
5 minutes of him messing around with a leatherman knife (donāt ask), and he was back up and running with a huge smile on his face at the thought of not having to send his console in for repair while being on tour. Saved him a pile of money too, no doubt.