Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Fusion SSI. Multiple Rooms in 1 program
|
Thanks in advance to anyone who can help me. I just finished the Fusion class last week but the answer to this question was only partially answered and now I regret not asking enough questions during the class.
It was explained to me in class if I have 1 processor running 3 rooms than I can add 3 SSI Modules (main module) to the program and make sure the SSID is different. Do I now need to add 3 "Fusion Room" symbols to the Ethernet Slot or somehow tie them all to the same Fusion Room symbol? I only ask this because I was told that a program can only have 1 Fusion Room in it but if I only use 1 and try to tie 3 SSI modules than i would get jammed signals and I can't see this working properly. My gut says to use 3 Fusion Rooms but I remember being told you cant have more than 1 per program. Shawn |
|
Hope your Fusion class wasn't as much of a waste of time as mine... I took the class about a month before they began using the SSI modules, and even knowing that was coming down the line, they only alluded to changes coming and didn't cover it at all.?Not that you asked...?
In any case, you'll want to add one Fusion Room definition to your program for each physical room in your program, and then connect that to a unique set of SSI modules for each of these rooms. Keep in mind, you'll also want to designate the only one of your SSI modules as "Primary_SSI" in the parameter settings. I also tend to set "Prefix_GUID" and "Append_Program_Slot" to Yes, since I sometimes run a single compile in multiple program slots for different rooms. Crestron's documentation isn't great on this, but you'll want to make sure the "Fusion_SSI_ID" and "Scheduling_ID" are unique to each SSI instance, since they are tied to crosspoints internal to the module. If you've attempted a compile, though, you've likely already found this out for yourself. If you're already implementing multi-Fusion Room support from a single processor, you may be interested in this bit of information. If you're implementing the Scheduling Awareness module, you can't support more than ten rooms from a 3-series processor. Fusion Support Group admitted to me that they hate the Scheduling Awareness module and how bloated and processor-intensive it is, but they also said it isn't a development priority. So, ten rooms it is. If you're not using it, you can get more like 15-20, but they wouldn't give me a hard and fast answer on that. This is with a 3-series processor, mind you. I wouldn't try it with a 2-series. There's more information to be had on multi-room support from a single processor, but I won't bore you with the rest unless you think you'll have use for it. Good luck! |
|
The largest I can attest to is 5x Fusion Room full modules ( each with Scheduling Awareness, 4x Static Assets etc) per Slot.
Born out of necessity, it's a pretty wild build with 40 ( SLOTS 2-9 x 5 each) in total, with SLOT1 handling all Fusion in/out comms from internal EISCs. CP3 alive and stable for 6 months straight. |
|
miketx
We have a campus with DMPS on a network where it cannot get out to the internet, but we are being sold a Fusion Cloud. They also want to use Room Scheduling touch panels.
How will Fusion be able to get to the equipment? Does the equipment point to the Fusion Cloud or does Fusion Cloud point to the equipment? To do this we were told to use a dual NIC CP3 with on side on an open network and the other on the closed network. This unit would then use a EISCs to tall to all of the controllers. With about 100 rooms and touch panels how will the CP3 handle all of this? Mike From: Crestron@... [mailto:Crestron@...] Sent: Tuesday, July 4, 2017 9:39 AM To: Crestron@... Subject: [Crestron] Re: Fusion SSI. Multiple Rooms in 1 program The largest I can attest to is 5x Fusion Room full modules ( each with Scheduling Awareness, 4x Static Assets etc) per Slot. Born out of necessity, it's a pretty wild build with 40 ( SLOTS 2-9 x 5 each) in total, with SLOT1 handling all Fusion in/out comms from internal EISCs. CP3 alive and stable for 6 months straight. [Non-text portions of this message have been removed] |
|
While I've only done "On-Prem" Fusion deployments and haven't messed with the FusionCloud yet, I believe they work opposite of each other.? When doing a local OnPrem Fusion deployment, the fusion server points to the processors/hardware and finds them.? When doing FusionCloud, I believe it works opposite and the devices each reach out the cloud to register themselves (since this makes going through firewalls easier).
toggle quoted message
Show quoted text
For your second question, I'm not sure I completely understand, but I'm not aware of how relaying a bunch of devices through a CP3 would work, unless they are just all on the Control Subnet and using the CP3 like a NAT firewall to get to the outside world?? In which case it would be automatic, but if that is the case, I don't know if I'd want to trust the built-in router on a CP3 to handle that kind of traffic from that many devices... I'd go with a dedicated router appliance.? I may be missing something here though, so... -Jason ---In Crestron@..., <mikes.tx@...> wrote : We have a campus with DMPS on a network where it cannot get out to the internet, but we are being sold a Fusion Cloud. They also want to use Room Scheduling touch panels. How will Fusion be able to get to the equipment? Does the equipment point to the Fusion Cloud or does Fusion Cloud point to the equipment? To do this we were told to use a dual NIC CP3 with on side on an open network and the other on the closed network. This unit would then use a EISCs to tall to all of the controllers. With about 100 rooms and touch panels how will the CP3 handle all of this? Mike From: Crestron@... [mailto:Crestron@...]
Sent: Tuesday, July 4, 2017 9:39 AM To: Crestron@... Subject: [Crestron] Re: Fusion SSI. Multiple Rooms in 1 program The largest I can attest to is 5x Fusion Room full modules ( each with Scheduling Awareness, 4x Static Assets etc) per Slot. Born out of necessity, it's a pretty wild build with 40 ( SLOTS 2-9 x 5 each) in total, with SLOT1 handling all Fusion in/out comms from internal EISCs. CP3 alive and stable for 6 months straight. [Non-text portions of this message have been removed] |
to navigate to use esc to dismiss