开云体育

I use crosspoints... sometimes. It's a tool to use when appropriate. I tend to use crosspoints when a combination of digital and serial and/or analog signals are best grouped together. Also when I hate the fellow programmers that have to edit the code. J/K if a crosspoint system is commented and laid out properly, just like any program, it can be managed.

It's easy to think big with crosspoints, which is why it's easy to conceptualize why the resi guys do it. A commercial example I used crosspoints in a situation where the client wanted full control of a 128 x 128 matrix switcher with the capability of defining and recalling presets as well as defining and recalling a rotation of sources on groups of displays. It made sense to me at the time to make a few frameworks of crosspoints that allowed the flexibility desired. Presets created a one-to-many relationship with display crosspoints; Rotation had a one-to-one relationship with source crosspoints, pointing the 'actively connected source' through to the 'preset group of display crosspoints' at a user-determined time interval.

I also use it in small situations -- think of crosspoints like a crude 'class' of sorts in SIMPL in that it can encapsulate data into one symbol. Say, for example, an AV routing framework: serial strings for Source Name and Small Description, analog values for Matrix Switcher Input Number or Volume, and digital tags for when a source is In Use. All that can get encapsulated into and shared by one crosspoint ID. Parameters and details specific to a system are defined once.

A great lot of what I use has been absorbed from concepts discussed in this group over the years. I read way back when in two-thousand-something to use a crosspoint for sources, and manage the source power by the crosspoint's IN_USE digital output. That's gold. UnderstandingCrosspoints pdf in the files section. More gold.?

-Andrew