开云体育

I had this problem with an Adagio a few years ago. I had a bad IR file that worked fine in a PRO2 but when specific buttons were pressed it would lock up the Adagio until power cycled. -Russell

We're installing one of these F3 projectors and I wasn't able to test it in the office before it went to site. The DD people actually do the install themselves and I was also under the impression that

FB reports what the TSTAT is doing, regardless of what the program told it to do. A user can adjust the stat locally, and FB will report that back to the program. [Non-text portions of this message

I had a similar issue with a CP3 a few months ago. In my case the IR outputs were DOA and power cycling, updating firmware, etc. had no effect. Everything else worked fine. I had to RMA the unit.

I've tried the weather module when it first came out, failed, and haven't tried again... Your CP2e is apparently running 4.7.x firmware, which I haven't been impressed with, and don't have any systems

I'm adapting my thermostat module to work with the infinet thermostat, and I don't have one to play with. There's one thing that concerns me. In the help file, it says to tie the Analog FB lines to

I have a CP3 that has had a problem twice now, where all 8 IR ports simply stop outputting anything. Everything seems fine (ethernet, serial, relays, etc…) when it happens. From debugger I can see

+1 -- I like it. On my machine, sometimes Toolbox opens in a few seconds, but sometimes it takes forever for some reason, it is nice to know that it is actually doing something. Jon From: castor_97

Avoid the prodigy multicast module! It's another of those cases (like the original iPhone symbol) where an intern invented a protocol and implemented it poorly in S+. wrote:

XSIG through a UDP symbol. Just tested with two programs on a CP3N and one on a CP2e. Fine and dandy, with the exception that the two CP2N programs didn't exchange data. <lincoln@...>

Its with the crestron weather module. The program runs perfect on CP3 without this error but wont work on the CP2E that has this error. Has to be in the processor itself but cant find out what would

Probably easier to just do the IPID changes rather than figure out something that might work. :-) Also, you can import EISC symbols into other programs, so if you didn't know that, that might save

UDP aimed at the broadcast address for your (sub)network, e.g. 10.0.0.255 for 10.0.0.0/24 Haven't tried it with a Crestron processor though... Lincoln -- Lincoln King-Cliby, CTS Sr. Systems Architect

I do believe I have done a UDP subnet broadcast and had other processors receive that as well too, but that could get even more messy than managing client connections as in the previous reply.

Yes, but if I need two things to talk to it simultaneously - like multiple CCROSS into a source device's ECROSS. Yet another area where network-enabled crosspoints would be dandy...

Couldn't you disconnect the sockets when you're not using them?

Isn't the server socket a one-at-a-time thing though? [Non-text portions of this message have been removed]

I believe a TCP/IP server socket with the address of 0.0.0.0 will allow any IP address to connect to it, then do what you will with clients from the other processors.

You seem to have inside information Neil, are you saying that the EISC will generate a single packet when multiple transitions occur on a single logic wave, rather than a packet for every change?

I have a client and 3 out of 4 of her Ipads are cellular capable on AT&T, and she lives in an area of terrible cell reception. The result of this, and not the best wi-fi, is that the 3 AT&T ipads do a