开云体育

-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Kool-Aid Drinker
Sent: Sunday, May 12, 2013 4:47 PM
To: crestron@...
Subject: [Crestron] Re: 2-series stopprog causing watchdog reboot?

There's been a smattering of threads about the problem. The exact
conditions that produce it remain elusive.

Stopprog didn't give me many reboots, just really high utilization of
TCP_Read, UDP_Serv, LISR, and TIMER. Programs loads would fail unless
I did the same reboot/stopprog that you're doing.

Even a freshly booted processor with no program in it showed high
network-related utilization.

Apparently, there is beta 4.7 firmware that ameliorates the issue. I
can't confirm/deny its effectiveness -- I chose to roll back to 4.3.


On Sun, 12 May 2013 14:15:45 -0400, Lincoln King-Cliby
<lincoln@...> wrote:

My house is essentially running on two processors - there's a CP2E for
lighting/HVAC/security and general "supervision"- basically things I only touch once a year
or so, and a Pro2 [*wistfully* some day a Pro3] for audio/video/energy management/access
control that gets much more tweaking when I have free time.

The program isn't crazy - RealIdle is consistently >=84% and the HeapFree is generally
10-12 MB (on a 32MB processor). Program is running on CF but it would fit in internal
memory (it's more "so I don't have to wait for the COMPACT/"File System Maintenance")

What I've noticed for the past 6 months or so is that when I try loading a new program,
Toolbox fails miserably unless I stop the program first. But if I telnet to the processor
and do STOPPROG, I get exactly this far

PRO2 Control Console
Connected to Host: LJKC-PRO2
PRO2> stopprog
Stopping Program................................................................
..................

Before disappearing into the wild blue yonder... eventually the processor reboots

If I telnet to the processor while it's loading the program / running the initial solution
after rebooting and issue stopprog in the middle of that, the program stops just fine and I
cal load via Toolbox - but it's getting annoying (FYI, Progreset does gets hung/watchdogs
at the same point).

I can't recall having this issue with any of my clients' systems which is part of the
reason I'm even more perplexed/convinced that I have something lingering in a dark corner
that I need to take a flamethrower to, but the only changes in the last 6 months have been
fairly simple - move audio sources around, delete some redundant logic. I don't even think
any of the S+ has changed.

Software is current, firmware is current (4.007.0004)

It seems weird that the processor is running just fine, I only have issues trying to get it
to stop running.

Any guesses, ideas, or shots in the dark?

[Like I said, program is not huge - 4449 symbols / 7744 actual symbols / 23869 digitals /
5099 analogs / 3906 serials / 18.05 KB NVRAM / 1.56 MB Flash / 328.18 KB SIMPL+; ~30
Ethernet devices, ~49 Cresnet devices]

------------------------------------



Check out the Files area for useful modules, documents, and drivers.

A contact list of Crestron dealers and programmers can be found in the Database area.
Yahoo! Groups Links