Talk to the DM from a single program in one processor and do whatever you want with the rest. I've run larger systems off a single CP3
toggle quoted message
Show quoted text
On 2013-05-03, at 10:07 AM, Mark Delzer <mdelzer@...> wrote:
Biggest thing to be aware of is how you communicate to the 32x32. I have a
job going now with two 32x32s at head end. In my case i was using the same
code in each room and so I was defining all the analogs of all the i/o.
Because of this I have to buffer the signals with a serial buffer and only
enable them after a delay after the EISC connects. This keeps a reboot in
one of my classrooms from resetting the head end routes and interrupting my
head end VTC and recording units.
Mark
On Fri, May 3, 2013 at 11:27 AM, David Ives <david@...> wrote:
**
Hi folks,
I'm talking with a client who is designing a multi-room system with a
32x32 DM, a few 3 series procs and about 20 TSW panels. He's experienced in
AV (read: been burned before) and is concerned about packing all of the
programs into as few processors as possible.
What kind of limitations should we be concerned about?
The system will not be especially chatty. The rooms are almost all
separate rooms, some with just PC inputs and a single display and others as
VTC rooms.
Thanks!
-dbi
[Non-text portions of this message have been removed]
------------------------------------
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
