Twice I faced the same problem with the SQ-5: during use, the touch screen stopped responding. The screen still works, but no longer possible to use the touch function. The problem is solved when restarting the console… but not possible during a concert!
What to do ?
SQ5 V1.5.6
Were you using any control apps? Mixing Station can cause this by sending too much data too fast. Fixed in the current beta.
Thank you for your answer, indeed the SQ MixPad software was open on my PC.
Will it be solved in the next SQ-5 update or is it already solved with the 1.5.6 update?
I’m not sure when that gets pushed to main. The current Mac beta is 1.8.0(326). You may be able to switch to the beta release track in the app general settings. I don’t remember if that was a thing I had to sign up for.
A&H should really fix this in firmware. It’s some kind of buffer overrun that should be handled more gracefully.
Ok thank you for your answer.
I currently have the same problem!
I had no control software running…
Luckily I have my IPad with me, otherwise I wouldn‘t be able to run the Show :-/
Yesterday night it worked fine, didn’t get moved,…
SQ 5
Firmware 1.5.6 r4043
I had no control software running…
≠
Luckily I have my IPad with me...
Update:
After the Show is disconnected the network cable to wire router, rebooted, now it works fine again \o/.
Well, happened here, too. Booted up the SQ6, nothing else running. No touchscreen response. Rebooted the board, all is well. Scary.
@Keithjah, are there any diagnostics or anything I can run?
Hi Keith,
I undestand this issue could be not easy to troubleshoot but I guess needs to be analyzed in deep.
My feeling is that unresponsive touch screen at power on is not dued to HW problems (defective touch screen itself) since there are a lot of cases already reported here and I cannot believe that all units are defective…
Instead I guess it could be caused by network startup config (with external router for instance) during the first power on.
If you need further infos please don’t hesitate to revert to me.
Many thanks in advance !
Graz
Hi all,
@Graz is correct - anything intermittent is difficult to pin down, but if you haven’t already done so, please contact us directly about this using support.allen-heath.com.
We will do our best to help figure out what’s happened and will also be able to log and share symptoms with the development and test team to investigate further if required.
Thanks,
Keith.
I used the Ipad & software AFTER the touch screen didn’t respond 
Hi Keith and all,
just had the reponse from A&H Support… they clearly stated that this is an HW failure, no dubt.
Personally I’m not so sure …
Anyway, I will do as they suggested and arrange the unit to be sent for repair.
Let’s see at the end .
Keep you posted !
Please keep me updated about any outcome in regards.
Thanks & kind regards,
Graz
David Schumann of Mixing Station has definitely demonstrated that a burst of data on the network can overrun a buffer and produce a variety of results, including an unresponsive touchscreen. The SQ should handle that situation more gracefully.
My screen was nonresponsive on first start again yesterday. Once every 3 weeks is never going to be found on a test bench. Sigh. So far it’s always worked after a restart.
“On first start” My screen is also, now and again, non responsive. And here also; after a restart it always works. Thought it would be good to share this.
I had posted about this issue here. Support was telling me it was defective hardware but surely this seems like more of a software issue.
Still no real acknowledgement as either a widespread hardware or software from A&H.
This happened to me on Saturday at start up for the first time in over 2 years of owning the console.
Recently updated to 1.5.7 from 1.5.4…
A restart using the power switch sorted it - but it was a bit worrying. There’s definitely a firmware bug, I might go back as I’m not using any new hardware with component changes.
Hi all,
We have now managed to reproduce this (and log it as a bug) and it looks to be an issue in the boot process where the touchscreen does not initialise correctly.
This is very intermittent (it’s taken hundreds of boot cycles to catch) which of course makes it very difficult to work on (and especially to test!), but we will continue to investigate and have a fix available as soon as possible.
As you have found, and due to it being a part of the boot process, a reboot will clear the problem.
Because it will not be possible to run the shutdown procedure, it is safest to shut down when:
Apologies for this inconvenience.
Thanks,
Keith.
We have now managed to reproduce this (and log it as a bug)
Wonderful news. Fight the good fight.