QSC K10.2's random fails ?

[bucephylus]

They're not unreliable in general, they just are susceptible to getting caught in a boot loop. If you go to my post (#4) in this thread there a link to my k12.2 saga. Or just Google 'qsc protect mode 4' or similar. If they're currently healthy then a firmware update will stop that from ever occuring.

I followed your advice, and looked up the Protect Mode issue. I also found multiple postings that the K.2’s still running the earlier Firmware do not have the issue.

QSC will tell you that you risk overcurrent damage with older versions; but, the overwhelming user feedback I found is counter to that suggestion.

I do not run my monitor at high volumes. Our stage mixes tend to be lower volumes, even on big stages. I think I’ll choose to let the sleeping dog lie, but will keep your much appreciated advice in mind.

Edit: Scrap that. I’m going to go ahead and attempt to upgrade to current. Will post back.

Upgraded both 10 and 12 to Firmware 2.1.43. Crossing my fingers and holding my breath, because I use one or the other at nearly every gig. To some extent, I feel like I fixed something that wasn’t broke. I suppose that’s how we do things now.

 

[pfschim]

Perhaps, I may be living on borrowed time on thin ice; but, I’ve been using a K10.2 as a vocal monitor on every gig for the past 4 years, and as a bass AND vocal monitor for the past 14 months with zero issues.

@pfschim , did you ever sort out the issue you had?

I did a firmware update around the time of the original post and all has been good with my K10.2's. I do still use them from time to time, but I have been trying to move to IEM's more often, and then I switched to using a QSC CP8 when I need a physical monitor.

 

[stubbsonic]

I'm so glad I found this thread. I only got my K10.2 a few months ago, and the firmware was 1.3.0. There was an update available (2.1.43) and it looks like it addresses the protection trigger issues raised here. Thanks to you all, I was able to be proactive and get in front of any issues.

The process was a bit convoluted on a newer mac. Had to register at QSC, and the instruction video was a bit outdated, as it didn't include a few additional steps related to macOS's more strict security protocols. Also, the process was slower and more opaque than in the video. It showed that it had 4 steps, and Step 3 seemed like it was uploading firmware a second time (perhaps it had to do two updates?)

 

[pfschim]

I'm so glad I found this thread. I only got my K10.2 a few months ago, and the firmware was 1.3.0. There was an update available (2.1.43) and it looks like it addresses the protection trigger issues raised here. Thanks to you all, I was able to be proactive and get in front of any issues.

The process was a bit convoluted on a newer mac. Had to register at QSC, and the instruction video was a bit outdated, as it didn't include a few additional steps related to macOS's more strict security protocols. Also, the process was slower and more opaque than in the video. It showed that it had 4 steps, and Step 3 seemed like it was uploading firmware a second time (perhaps it had to do two updates?)

cool. the K2's are good sounding boxes. glad you got yours updated.