¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Smart Graphics with Crosspoints


 

Hey Everyone,

I am programming a project with multiple touchpanels and a lot of sources so I decided to try my hand at Crosspoints. I pretty much get the jist of how it all works but I'm curious if anyone knows about this.

I ran all my TP joins(all panels driving identical signal names) through a CCP to an ECP and to my driver for a bluray player. Compiled and no error for previously defined driving source.

I then have all my Smart Graphics(D-pad, List also all panels driving identical signal names) going to the ECP directly. Compiled and no errors again. But I expected to get errors on that based on not routing through the CCP first.

I have all my ECCCs in place so I'm sure things will connect properly but I won't be able to load and test the program for a while and I don't want to waste time programming incorrectly.

All that being said, my question is

Does anyone know if it is required for Smart Graphic signal names to be routed through the CCP as well?


 

Crosspoint is a best practice. Its better to pass all the signals from the Crosspoint in order to avoid any confusion. And if you don't use Crosspoint then you just need to change the logic of the pages, i.e. just rename the pages signals and the functional/operating signals will remain the same for all the touch-panels. Hope this works.


 

You wont get errors that way as long as you dont have jammed or unconnected signals, but why are you sending the regular panel joins thru the crosspoints but not your SG joins? You went thru the effort of using crosspoints which is great- you should just do the whole panel including SG joins. Makes it easier to scale your programming.?


 

Thanks guys,

This project is an upgrade to a system and the VTP file already has joins but the previous guy did some whacky stuff and it looked like running all the SG traffic is going to cause some conflict with those joins so I tried running SG direct to the ECPs to see what would happen. More than anything I was expecting errors and was surprised not to see them. That's what originally caused me to wonder and ask the question.

I hate programming after someone else. I know there are many ways to pull of the same thing and some are pretty cool and I learn from it. But organization, flow and signal names aren't a standard and most of the time I find this makes it difficult to wrap my head around someone else's logic. I like things like Bluray_Play_press but this guy is long winded and inconsistent so I have things like Bluray_Smart_Graphics_Dpad_Enter_Button_Pressed and Bluray_Touch_Panel_Play_Button_Press.

And some of the logic is even worse because instead of OSC or AOS as a part of a signal name the guy uses long form and spells out Oscillator or Serial_Analog_One_Shot in already long signal names. It's been a pain just getting some of that nonsense in order but I guess I may as well pain myself some more and change the structure of the joins. I would rather have not had to reassign every join in the program cause there are over 1000 of them, but I also prefer consistency and it will probably help when I start debugging.


 

Sorry not really helping here, but Crosspoints is what keeps me sane. I've seen/had to work with WAY too many programs with 100's of buffers and I just feel bad for the original programmer because he/she didn't understand how crosspoints work or didn't know they even existed.

Learn them, love them!


 

I've built all my starter programs with Crosspoints? TP Connects to Room and Room Connects to Source.? In this fashion All TPs have a unique naming.? The room chooses the source to connect to and passes the control back to the TP.

TP CCross to Room ECross.? Room ECross has joins connected to Source CCross that gets connected to the Source ECross.


 

¿ªÔÆÌåÓý

My old programming template, that is located on my GitHub (), is all based on crosspoints.? The hardware drivers for touch panels and sources is all out of date at this point but the overall programming structure is still valid.

One thing to note - the crosspoints and the logic to drive them are all hidden inside modules.? This removes some of the complexity of working with crosspoints.?

Hope this helps

Jay

On 12/1/2023 12:44 PM, John Gabler wrote:

I've built all my starter programs with Crosspoints? TP Connects to Room and Room Connects to Source.? In this fashion All TPs have a unique naming.? The room chooses the source to connect to and passes the control back to the TP.

TP CCross to Room ECross.? Room ECross has joins connected to Source CCross that gets connected to the Source ECross.


 

I put all shared signals SG or not through Xpoints for a given panel, they aren't any different from regular panel signals.


 

¿ªÔÆÌåÓý

I use a set for the room (TP or HR? <>? Room) and a separate set for the device (TP or HR <>device) as I suspect going through multiple sets of crosspoints adds latency.

?

From: <[email protected]> on behalf of John Gabler <ComeAlive@...>
Reply-To: <[email protected]>
Date: Friday, December 1, 2023 at 12:44 PM
To: <[email protected]>
Subject: Re: [crestron] Smart Graphics with Crosspoints

?

I've built all my starter programs with Crosspoints? TP Connects to Room and Room Connects to Source.? In this fashion All TPs have a unique naming.? The room chooses the source to connect to and passes the control back to the TP.

TP CCross to Room ECross.? Room ECross has joins connected to Source CCross that gets connected to the Source ECross.