¿ªÔÆÌåÓý

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

Re: TCP Client Stopped working

 

Chris,

I don't know if they are related at all, but ...
I have still been having issues with EISC connections between 3 and 4 series processors.
That is with the 2.7000.00040 firmware installed on the 4-series processor, which was supposed to fix the problem.
Just last week, I updated a site to the 2.7000.00052 firmware hoping that would be a permanent fix.
It is completely random and definitely a 4-series problem.
About once every month or two I have to reboot a CP4 running a D3 program.? It shows connected in the IPT but the CP3 doesn't.

If Crestron can't get its own EISCs connecting reliably, that has me concerned with all other ethernet communication.

Fun times!
Brian


Re: TCP Client Stopped working

 

Thanks, Jonathan, Brian and All,
It definitely seems like a highly intermittent issue, might even be a one-off sometimes. I'll be connecting into the site that I've had this issue with and will see if the connection has failed again (been since Friday afternoon).
I also have a case relating to this so we will see...
Jonathan: It would seen that this has been an issue since the beginning of 4-series...

Because of the '1' on the connect input (I'm changing this now) I can't try to restart on this project.
Have either of you found that a toggle on the Connect fixes the issue, or does it always require a program restart??

FWIW, I set up a simple TCP client test on both CP3 and CP4 with nothing to connect to them so that they would just keep trying to connect, basically testing if the symbol would give up after a while, and both are still humming along since Friday afternoon.
Both still toggle between Waiting and Failed, as expected.? The CP3 client waits a bit longer than the CP4 (20s vs 3s) but both stay on failed for just over 1 min then back to Waiting.
On my Vantage site, the TCP client just stayed on WAITING...


Re: TCP Client Stopped working

 

I've seen this as well. I have a case open with TB right now for it. What I was able to narrow it down to was if you lose link on the CS side of the processor that is what breaks the TCP/IP client. I was able to reproduce it everytime that way. I wrote 2 dummy demo programs and sent it in, one with a TCP Client and another with a TCP Server and took a video of it failing and a software reset/hardware reset fixing it.

I've never seen this on a 3 Series, only 4 Series, but I can certianly adapt my program to test it over on a 3 series as well. At home I have devices on CS that I'm using a TCP Client for communication and after switch reboots, switch firmware upgrades, power cycles, etc I've never found the devices to not properly reconnect.

I just checked my case and no updates since April 1st when they said they would mock up my programs and get back to me.


Re: TCP Client Stopped working

 

I've seen this since the very first CP4N we installed right after they came out, and your experience sounds a lot like mine. In S+, you can leave it to stay connected and automatically reconnect and it'll work, but a TCP Client symbol gets stuck waiting. Restarting the program is enough to get it working again. I've tried various catch-and-recover methods that seem to have worked, but I've been trying to make or use S+ or S# modules to handle TCP stuff anyway so I notice the issue less and less as a result. It's definitely not just you it's happening to!


Re: TCP Client Stopped working

 

¿ªÔÆÌåÓý

?FTR, I almost never turn the connect off with any device and have not had any particular issues until now...¡°

?

Same here.

Especially in my home/test-system, i?ve got a lot of TCP Clients in the program pointing to devices that are rarely switched on or connected because i just need them for some specific testing. Never had a problem that the TCP Client wouldn?t connect after the device is connected or switched on.

Actually, i?m assuming more issues with permanently activating and deactivtating the TCP Client, but it sounds as if that?s working reliably.

So i think i?ll give it a try.

?

Cheers,

Thorsten

?

Von: [email protected] <[email protected]> Im Auftrag von ckangis
Gesendet: Sonntag, 10. April 2022 23:57
An: [email protected]
Betreff: Re: [crestron] TCP Client Stopped working

?

Olivier,
Yeah, I'm not sure why I have a '1' on it (probably some legacy thinking...) at minimum, I usually make it an actual signal, that is driven by a '1', thru a buffer, so that I can at least toggle it in Debugger...
I like the concept of your approach, though I find that more often that not, you want the comm's running all the time for status updates (unless its a 1-way control). This in particular is a lighting system so there's alot that I want to have ready to go without having to poll and wait.

FTR, I almost never turn the connect off with any device and have not had any particular issues until now...
This is a *Problem* with Crestron and their TCP client...hopefully we'll see a fix soon...


Crestron Home + DMP alarm lightweight integration? #crestronapp #crestron

 

Hi, I have a Crestron Home system and a DMP (XR 150/500) alarm. I understand that a full integration of the DMP system into Crestron seems not possible but is there a way to just have the alarm status (Armed or Disarmed) show in the Crestron app? Seems like this output should be pretty easy to obtain but i¡¯m new to this so would appreciate any tips or guidance! Thanks, Doug


Re: TCP Client Stopped working

 

Olivier,
Yeah, I'm not sure why I have a '1' on it (probably some legacy thinking...) at minimum, I usually make it an actual signal, that is driven by a '1', thru a buffer, so that I can at least toggle it in Debugger...
I like the concept of your approach, though I find that more often that not, you want the comm's running all the time for status updates (unless its a 1-way control). This in particular is a lighting system so there's alot that I want to have ready to go without having to poll and wait.

FTR, I almost never turn the connect off with any device and have not had any particular issues until now...
This is a *Problem* with Crestron and their TCP client...hopefully we'll see a fix soon...


Re: TCP Client Stopped working

 

I never use "1" on a TCPIP client module, I always use a connection manager to connect to the device when needed and close the connection after. This can be as short as a few milliseconds to send a command and acknlowledge the answer or as long as the system or page is in used, but never 1.
I never had any problems this way.
At least disconnect from the device when it's not in use is a good idea.


Re: Master 2022, no virtual option? WTF

 

OLH: 1001189, or just search online help for Masters.
September 20-22, registration opens June 15th


Re: DM NVX creates a broadcast storm for ~2 minutes every ~ 30 minutes

 

A big shout out to Crestron_Programmer_84 for all his help!? The problem was resolved by turning off Spanning Tree Protocol the VLAN that is used for the NVX and other things being controlled.? ?Once I did that everything started to magically work.? ?Looks like I need to do some reading to understand the relationship between IGMP and STP.

Thank you to everyone for your suggestions.

Bryan


Re: Master 2022, no virtual option? WTF

 

has the date been released yet?


Re: TCP Client Stopped working

 

Yeah, It definitely seems very intermittent, as I at least have not seen it before...
In this case, I don't believe that the Vantage system was off-line at all (certainly not for hours/days) so it seems that the Client just disconnected itself...


Re: TCP Client Stopped working

 

¿ªÔÆÌåÓý

I¡¯ve seen an issue on my home system (PRO4) a couple times but not with enough frequency to get enough info for a proper bug report where if the Ethernet link is lost under some circumstances the connection will not retry until the program is reset. The status in the IPT is ¡°LINK LOST¡± ¨C but this doesn¡¯t happen on every link loss event. (Most recently I saw it because I was upgrading one of the edge switches in my AV equipment room)

?

The other thing to remember is that the TCP client retry time rises exponentially the longer it can¡¯t connect to the other device, e.g. the longer a device is off line the longer it will be between retrying the connection (I want to say the upper end is 65000 seconds but I¡¯ve never personally tried it) so if the device had been offline for ¡°a long time¡± that could explain why it didn¡¯t seem to be retrying.

?

Beyond those two cases though I can¡¯t say I¡¯ve seen any systematic issues with the TCP/IP client on the 3- or 4- series¡­. And I have a few applications where I know I¡¯d know if there were issues because the failure would be critically obvious.

?

?

--

Lincoln King-Cliby, CTS, DMC-E-4K/T/D
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? | Fax: (+1)440.449.1106
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

?

From: [email protected] [mailto:[email protected]] On Behalf Of ckangis
Sent: Saturday, April 09, 2022 11:22 AM
To: [email protected]
Subject: [crestron] TCP Client Stopped working

?

Hi All,
Wondering if others have seen this odd, intermittent behavior...and also a heads-up for others to watch out for it

CP4 (v2.7000.00040) has a TCP client communicating with a Vantage System (though I don't think the remote device matters).
It was working two weeks ago, and we checked yesterday (client is out of town) and found that it was 'Not Connected' and specifically not trying to Re-Connect.
The Status analog just stayed at '1d' instead of the typical toggling between 1d and 3d (Waiting for connect vs Connect Failed)
As I have a '1' on the Connect input, I could not test if toggling this would fix the issue, Rebooting the Vantage processor did not restore.
Only restarting the program slot restored the connection.

I spoke with Crestron TS to trouble-shoot this, as I've never seen this behavior before, and they have confirmed that they have seen this a few times, offering:
1. They said it was 4-series issue, spanning fw updates
2. Use an S+ emulation module of the TCP client until they fix the issue...:(

Clearly this is a specifically intermittent issue, as I have not seen anyone else talking about this lately, but they have confirmed that there is a problem....
In a related note, another friend of mine who I trust with his technical knowledge and experience, says that he has seen this issue? for years on both 3 and 4-series systems.
He feels that it is a long-standing issue that has not been dealt with and thus probably will not be fixed...
Given my experiences over the last 5+ years with TB, I would tend to agree.

To have to use a custom S+ module to handle this is absolutely ridiculous - the TCP Client is a native hardware device symbol...
What experiences have other had about this??


TCP Client Stopped working

 

Hi All,
Wondering if others have seen this odd, intermittent behavior...and also a heads-up for others to watch out for it

CP4 (v2.7000.00040) has a TCP client communicating with a Vantage System (though I don't think the remote device matters).
It was working two weeks ago, and we checked yesterday (client is out of town) and found that it was 'Not Connected' and specifically not trying to Re-Connect.
The Status analog just stayed at '1d' instead of the typical toggling between 1d and 3d (Waiting for connect vs Connect Failed)
As I have a '1' on the Connect input, I could not test if toggling this would fix the issue, Rebooting the Vantage processor did not restore.
Only restarting the program slot restored the connection.

I spoke with Crestron TS to trouble-shoot this, as I've never seen this behavior before, and they have confirmed that they have seen this a few times, offering:
1. They said it was 4-series issue, spanning fw updates
2. Use an S+ emulation module of the TCP client until they fix the issue...:(

Clearly this is a specifically intermittent issue, as I have not seen anyone else talking about this lately, but they have confirmed that there is a problem....
In a related note, another friend of mine who I trust with his technical knowledge and experience, says that he has seen this issue? for years on both 3 and 4-series systems.
He feels that it is a long-standing issue that has not been dealt with and thus probably will not be fixed...
Given my experiences over the last 5+ years with TB, I would tend to agree.

To have to use a custom S+ module to handle this is absolutely ridiculous - the TCP Client is a native hardware device symbol...
What experiences have other had about this??


Re: DM-PSU-3X8-RPS is Discontinued

 

¿ªÔÆÌåÓý

It¡¯s not as elegant (or rack mountable) but I think some multiple of PW-5430DUS is your answer

?

?

?

--

Lincoln King-Cliby, CTS, DMC-E-4K/T/D
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? | Fax: (+1)440.449.1106
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

?

From: [email protected] [mailto:[email protected]] On Behalf Of jrw_96 via groups.io
Sent: Friday, April 08, 2022 2:34 PM
To: [email protected]
Subject: [crestron] DM-PSU-3X8-RPS is Discontinued

?

Anyone have any suggestions for a replacement device that will supply PoDM+ power to all ports on a 64x64 blade?

Are we out of luck and stuck powering everything with wall warts?

-JRW


DM-PSU-3X8-RPS is Discontinued

 

Anyone have any suggestions for a replacement device that will supply PoDM+ power to all ports on a 64x64 blade?

Are we out of luck and stuck powering everything with wall warts?

-JRW


bosch dcn ccub-ul

 

Hi All,

Does anyone know where I can find configuration software for this unit? (bosch dcn ccub-ul)

Thank you


Re: QSYS with Mat Klucznyk Github

 

Scott,

I am currently using these module without any issues.
Can you post a snippet of the Fader (one with issues) and Core module?


Re: Calling a C# method from Simpl+

 

Thanks for the response and I was able to get this to work.?
Next: I am reading an XML document, converting to JSON (this works) and placing in a <List> but not certain how to get the list back to Simpl+.


Re: Control for NP-PA803UL / new protocol?

 

¿ªÔÆÌåÓý

I don¡¯t think 015. Power On is the actual command just the command number and name (if you look at other fields in the document there are hex bytes provided for e.g. DATA 02 and DATA 03. I think you¡¯re missing the actual protocol document.

?

See page 190 of for (a portion of) the protocol where power on = \x02\x00\x00\x00\x00\x02.

?

I¡¯ve been able to throw more or less the same commands at every NEC projector I¡¯ve seen in the past 12ish years. Incidentally there was a run of NEC projectors that would randomly lock up the COM ports at 38400 (or maybe at 38400 + DM); setting the baud to 9600 resolved that issue so more or less out of superstition I¡¯ll always set a NEC projector to 9600 rather than leaving it at 38400 .

?

--

Lincoln King-Cliby, CTS, DMC-E-4K/T/D
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? | Fax: (+1)440.449.1106
Crestron Services Provider | Biamp Authorized Independent Programmers | Extron Qualified Independent Programmer

?

From: [email protected] [mailto:[email protected]] On Behalf Of Tray Schaeffer
Sent: Friday, April 08, 2022 8:48 AM
To: [email protected]
Subject: [crestron] Control for NP-PA803UL / new protocol?

?

All,?

Working with new laser projectors here at a job site.? Set the PC cotnrol within the projector to 38400.?
Unfortunately, control via HDBaseT is not available due to the way things are wired.?
These are connected to DM-RMC-200 receivers from DM 32x32 (not CPU3).?
DM endpoints reports on line but have no comms at all with projector. Stereo mini is connected to the PC Control input on display, not the IR remote input next to it.?

Anyway, Seems that the control protocol may have changed since I last worked with one of these.?

See this document.?

?

?

The NP-PA803UL is listed.?

Not sure if the command should include the preceding number or not..?

From the document, power on = "015. POWER ON". Not sure of terminating char, if any is required.?

?

Any experience with these??

Thanks in advance,?


Tray