Thanx Chip! You're right: the QM-RMC couldn't ping the WF2IR. I checked a different Wifi router (linksys WRT54GL) and the connection worked! Back on the original router it worked to. So I don't really know what the caused/solved the problem but your idea to blame the network was right...
toggle quoted message
Show quoted text
--- In Crestron@..., "Chip" <cfm@...> wrote:
Have you connected to your processor with the Toolbox Command Line tool and tried pinging the box *from* your processor - just to be sure they can "see" each other?
What happens when you try to connect to the IP & Port with a TCP/IP Client symbol? What values does the analog status output of the symbol change to after enabling the symbol?
- Chip
--- In Crestron@..., "controlfreakberlin" <markusdvorak@> wrote:
I want to establish a connection between a Crestron control processor and a WF2IR unit. Everything is set up and the TCP connection works when I use either a terminal client on my PC or a CommandFusion UI on my mobile to connect to the WF2IR but I can't connect to the WF2IR with the Crestron system as a TCP client on port 4998. Do you have any ideas what else I could try? Even all other devices in the network communicate with each other without problems (Crestron<->PC, Crestron<->CommandFusionDevice...) so I doubt it's a network problem...
Even checked it with a second processor and a plain SimpleWindows programm with just the TCP client in it...
Thanks in advance!
Markus
