开云体育

**


I believe the correct information is that you can have as many ECCON's in
your program as you need, but the compiler treats them all as a single
object.


On Fri, Feb 22, 2013 at 8:52 AM, Travis th_wertz@...> wrote:

So if I understand your chart (which looks great btw), you are using a
ECCONNECT per CCROSS which means a ECCONNECT per touchpanel. I was told

in

training to only use 1 ECCONNECT in the program. I think it would be
easier to do it your way. Have you (or anyone) had any issues using more
than one ECCONNECT in your program?

--- In Crestron@..., Neil Dorin wrote:

Ok, so I've updated the flow chart and added some intermediate and

advanced

models of crosspoints.

These are by no means a comprehensive guide of crosspoint best

practices,

but rather just a more visual representation of hierarchy and signal

flow

intended to help people visualize the mechanics of crosspoints and

where

the signals go...

The advanced model I've added is not necessarily the most practical

example

of layered crosspoints but I thought it best to start there as a

conceptual

base and then expand into more practical multi-layered models.

Here's the link again: Understanding
Crosspoints<

On Thu, Feb 21, 2013 at 9:42 PM, Kris wrote:

**


I'm slowly starting to implement more cross point into my

programming.

The

easiest use is for using one panel to control diferent rooms.

Typically a

roaming ipad. I have also used them to control multiples of similar
devices. I could go ahead and just use a couple hundred generic joins

of

each type and route every single device through cross points, but I

find I

still take too long to find stuff in my folders if I do this. I

learned the

basics just by adapting some of crestrons example programs for their
centrack and idoc logic. I actually took over a project from another
programmer recently who in my opinion overused cross points. It is a

little

silly to use cross points for the most basic functions, but I do

understand

how this can expedite creating a project cookie cutter style.

--- In Crestron@..., "John" wrote:

I have written a fairly basic system for my home and have been

looking

at the code for a home that a friend of mine purchased where he was

given

the option to buy the simpl program which of course I recommended he

do it.

His program is all interlocks and buffers. Being self taught I

already

had figured out this method of multi-point control from the help

files

and

the primer.

I had already programmed my home in the same way because it was

easy

to

understand and debug.

I have reviewed the basic crosspoints program and would like to ask

if

this is the more professional way of programming a multi-point

control

system? Is there less overhead required on the CPU? Should the system

be

completely redesigned using a crosspoint system or can zones/devices

be

migrated over and the buffer/interlock devices left in place until

the

code

is replaced?

Since I have a small system with just 4 zones and a few components

that

are not critical to the operation of my home I have the ability to

rewrite

my system and enjoy doing it in my off time to relax and forget about

work.

Any insight would be greatly appreciated.

Thank You,
John.

[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