¿ªÔÆÌåÓý

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

Re: ETC EOS IP Interface


 

¿ªÔÆÌåÓý

Transmit to?239.255.0.1 which should be universe 1. And set universe as 1. I¡¯d stick a switch in the middle with your PC and use sACN viewer () to look at what is going on. It may be that you are transmitting ?from the console and so its not seeing that. Either way, you should see the proc transmitting and the values at what you are sending them as. If you are seeing it transmit and nothing else, maybe there is something incorrect on the console side. ETC has great support and I¡¯m sure they would be glad to assist on the console side. I havent touched one in some time.?

--

Thanks,

Ryan Wilkinson
714.720.3741

On Jun 15, 2020, at 4:50 PM, F David A Coker <david.coker@...> wrote:

Transmitting
?
From:?[email protected]?<[email protected]>?On Behalf Of?Ryan Wilkinson via?
Sent:?Monday, June 15, 2020 5:50 PM
To:?[email protected]
Subject:?Re: [crestron] ETC EOS IP Interface
?
Are you transmitting or receiving on the Pro3 side?
?


On Jun 15, 2020, at 9:30 AM, F David A Coker <david.coker@...> wrote:
?
With respect to the sACN, we just cannot get this to work.? I am using the Crestron sACN module and this is how we have it connected.
?
Pro3 Subnet port to port 2 on the Ion Xe RPU.? We have the Ion Xe RPU set with an IP of 172.22.2.230 and it is talking just fine over the UDP ?and TCP/IP connections (although, as mentioned earlier, we never could get the TCP function working due to the OSC requirements).? As you can see, there are no network switches between the two, direct connect.
?
So, with this connection scenario, I have the sACN module set up with 172.22.2.230 as the IP, 5568 as the port and it is looking for universe 1.? But, the Ion Xe RPU will not respond to it, it totally ignores it.? And what is weird, I have a DMXKing Pro 1 and the Crestron talks to it just fine.? Any ideas as to why this is?
?
From:?[email protected]?<[email protected]>?On Behalf Of?Ryan Wilkinson via?
Sent:?Sunday, June 14, 2020 10:31 AM
To:?[email protected]
Subject:?Re: [crestron] ETC EOS IP Interface
?
No problem! Glad its working. OSC has some complications once it gets down to blobs. I know it would need to be implemented in C# as it gets pretty intense. Certainly willing to work on it if you would still need that but I do know most things can be fired off using their UDP API.
?
Regarding the port for sACN - what do you mean? sACN is a multicast protocol which talks UDP on port?5568 by default. The multicast address is selected based on the universe number per the standard. You shouldn¡¯t need to mess with anything and can send/receive using the standard one available in the Crestron libraries. Providing you are using real switches with IGMP snooping - it should pass correctly between everything.
?
?
?
On Jun 13, 2020, at 7:17 AM, F David A Coker <david.coker@...> wrote:
?
Hey Ryan,

Well, you are a genius!!!? We used the UDP instead and we are Live!!!!? Thank you so much!? On a different note, do you by chance know what port I would use for the sACN function??
?
?


Join [email protected] to automatically receive all group messages.