开云体育

Hi guys,
I know it does work to connect multiple Touchpanels, iPads and/or XPanels to the same IP-ID.

My question is if anyone had issues with that practice?

Best regards

No real issues, just depends on scalability and how many users are using the panels.? ? ? ?You can end up with Blue on Blue if the users are in different locations but if only a few panels and users in the same place then it's not too much of a problem and provides an element of resilience.? ? ?Troubleshooting is not too much of a problem as you can identify panels via their IP address in toolbox.

The most irritating bit is when one user is using the panel and then another user does something and hence the first user's panel changes without them touching anything....

Though it can be done, it's generally only recommended to do that briefly when testing (ex. running a VTZ as XPanel to emulate a TSW that's in another room, etc.), and not during actual deployment/runtime.

Crosstalk can particularly become a problem when you're using things like CRPCs and Smart Graphics applications (Media Player, etc.); less of a problem for a UI project only comprised of basic buttons/gauges/etc.

If you are using any of the widgets that use CRPC, such as the media player object, it will cause problems.? Some devices talk directly to the panel circumventing the processor.? If you are using strictly standard signal types it will work, but you will get the mirroring effect mentioned above.? I just use a standard signal prefix like tsw with the IP ID (tsw20) and then you can easily search and replace (or use the duplicate function) the copied panel and logic.? It is very quick to duplicate the subsequent panels.??

Definitely not recommended...
I learned this the hard way on a on a project 5 years ago. I had a bunch of TSWs and just used my iPAD project once to test something, setting it to the same IP-ID of one of the TPs...4 hours later, trouble-shooting all sorts of 'Red Herring' rabbit holes, I rebooted everything and got the system back. Discussing this with a Crestron buddy he told me that it was 'expected' behavior!...HaHA!

Having separate devices in your SMW/System also helps tremendously when trouble-shooting, not to mention that each panel is completely independent (though there might be a use-case to have them track each other)...
If you don't already know it, if you Right-Click/Drag from TSW #1 to TSW #2, you'll get a pop-up with a choice to 'Duplicate Device Programming' and even provide the ability to change the headers of all your signals - This is super efficient!
Also, having a standard/formatted header for all your signals (ex: tp001, tp002, etc.) will also facilitate rapid deployment.
then, if you have a logic folder for your first TP, you can just copy/paste the folder and use F9 to search/replace that header to get the next/subsequent TP logic...

Forgive me if this is super basic, but I know that there's many newer guys on this forum, and also, I can't tell you how many times in recent years that this *Old* guy has been shown a tool/method to simplify things that I said "Wow, how did I not know about that!!! - Thank YOU!!!"

HTH!

On Fri, Sep 24, 2021 at 04:08 PM, ckangis wrote:

Forgive me if this is super basic, but I know that there's many newer guys on this forum, and also, I can't tell you how many times in recent years that this *Old* guy has been shown a tool/method to simplify things that I said "Wow, how did I not know about that!!! - Thank YOU!!!"

Lol......?