Band-aid: PERIODICREBOOT ON
There is a secondary command which changes the time of the reboot, but I can't remember it. It defaults to 2AM apparently, and it's supposed to do it "quietly" without lighting up the screen.
Make sure you report this, please. This is major and I can't believe it's still floating around after many weeks.
On Apr 26, 2013, at 9:06 AM, innoventgroup <innoventgroup@...> wrote:
Fellers,
How to I turn that on... I want to set that up, I cant afford for the panel to die again, now that the customer thinks it is fixed. Thanks Heath for explaining that and, now that you have, I have definitely experienced that scenario. As a matter of fact, I am still experiencing that scenario even after the update on the firmware, just not as dramatic as shutting down my crosspoint. Basically what it is doing now is that the serial and analog signals do not update with the rest of the system. For instance, I can use one of the iPads and change the radio station. Then I can go to another iPad and the station readout will show the updated value. But, when I go to the TSW-750s, I have to press a button to get them to update. Just some additional data for you.
Thanks again!!
DAVE
--- In Crestron@..., Neil Dorin <neildorin@...> wrote:
I was mostly referring to the associated reboot fixing it.
Thank to you Heath, I turned periodic reboot on on 80 panels Tuesday and it seems to have helped immensely!
Sent from my iPhone
On 2013-04-25, at 9:14 PM, Heath Volmer <hvolmer@...> wrote:
On Apr 25, 2013, at 9:02 PM, Neil Dorin <neildorin@...> wrote:
My bet is its the FB bug with the TSWs and the firmware update and resulting reboots corrected it...
I was just going to say that - but do we know that the update actually fixes it? I've been pretty deep into that particular problem and have been asking if it had been fixed. I'll stick with the daily reboots!
Dave, what we're referring to is a lovely bug where the TSW just stops responding to the feedback it's receiving. It transmits fine, but completely ignores all feedback until rebooted or sending in a new program - any activity that resets Core 3. It just appears stuck. Quite elusive. I don't know if I'm experiencing it any more because the panels are now set up to reboot themselves every day...
Heath
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]