Global Cache IP2IR sensor input (RMC4)


 

Has anyone used the IP2IR as a sensor input?
 
Apparently it broadcasts state changes via udp on port 9132, using a multicast IP of 239.255.250.250. 

Does the UDP symbol in simpl windows listen on multicast IP’s like that?  I’ve not had a manufacturer specify a multicast IP in the past, just UDP in general, and I most often specify 0.0.0.0 on the symbol. 

Thanks,
Mike


 

You would not be able to use 0.0.0.0 in this case on a properly configured network as the device needs to send a "join" message to the switch to let it know that it is interested in getting that data.

Multicast join/leave has been on-again-off again depending on firmware version (though processors with internal routers have been the most problematic so if you encounter issues you may be served to try upgrading or downgrading fw

Lincoln 


From: crestron@groups.io <crestron@groups.io> on behalf of Mike Taylor via groups.io <miketeachesclass@...>
Sent: Wednesday, November 20, 2024 6:02:48 AM
To: crestron@groups.io <crestron@groups.io>
Subject: [crestron] Global Cache IP2IR sensor input (RMC4)
 
Has anyone used the IP2IR as a sensor input?
 
Apparently it broadcasts state changes via udp on port 9132, using a multicast IP of 239.255.250.250. 

Does the UDP symbol in simpl windows listen on multicast IP’s like that?  I’ve not had a manufacturer specify a multicast IP in the past, just UDP in general, and I most often specify 0.0.0.0 on the symbol. 

Thanks,
Mike


 

Thanks Lincoln.  
 
In this case, would I'd just use the IP of the sending device rather than zeroes for the octets; I'll keep my fingers crossed that this will function.
 
Thanks!
Mike


 

Sorry, I initially replied on mobile and was a bit harried…

 

For multicast you need to use the multicast group ID as the address so that the processor/OS knows it needs to send the IGMP Join message to the switch. If you use the source IP address, much like 0.0.0.0 the switch has no idea that it needs to forward the multicast traffic (and the processor may or may not be listening for multicast traffic from that source IP)

 

 

--

Lincoln King-Cliby

Commercial Market Director
Sr. Systems Architect | Crestron Certified Master Programmer (Diamond)
ControlWorks Consulting, LLC
Direct: (+1)440.771.4807 | Cleveland: (+1)440.449.1100  | Boston: (+1)508.695.0188 | DC: (+1)202.381.9070 | London: (+44) (0)20 4520 4600 
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

 

 

 

From: crestron@groups.io <crestron@groups.io> On Behalf Of Mike Taylor via groups.io
Sent: Thursday, November 21, 2024 10:59 AM
To: crestron@groups.io
Subject: Re: [crestron] Global Cache IP2IR sensor input (RMC4)

 

Thanks Lincoln.  

 

In this case, would I'd just use the IP of the sending device rather than zeroes for the octets; I'll keep my fingers crossed that this will function.

 

Thanks!

Mike


 

Thanks again, Lincoln.