Modules exhibit weird behavior after recompile

#241795

Hey Crew, I have a weird scenario that I have been experiencing on a couple of my jobs.? I have an existing program on a CP3N that works just fine.? I recompile it with the latest databases etc. and now it exhibits unpredictable behavior.? This has happened twice in the last week.? Does anyone have any suggestions?? By the way, the program has not changed at all, just a recompile with the latest files.? Oh and the module was a S+ module on both scenarios.

Thanks,
DAVE

Weather App...Again...

#241794

Any others have sites with "Please Wait..." on the TSWs again, after the SG upgrade and it been working for months??

Latest Toolbox

#241793

So downloaded the latest version of the databases and toolbox. Now can't get any info from connected devices. Connect to processor, TPs, gateways etc and all I get is connected, receiving data. System Info remains blank. Have uninstalled and reinstalled, no difference.

Tried connecting to FTP site and can't do that either.

Re: Series 3 FW v1.8000.0014

#241792

As stated in my other thread recently, I've just updated to 1.8. So far so good, everything working as expected including file ops. I should know for sure in a few days if I don't get any emails from my lighting system.
-s

Re: Series 3 FW v1.8000.0014

#241791

Cool, Thanks guys!! (And any others who want to chime in!)

Rob, What was your Sonos Connection issues?
I ask because I'll never recoup the losses from the last year of Sonos Trouble-shooting and custom re-work of my code to make things more reliable (i.e. self-healing...)...

Re: Authorization for Connections

#241790

I remember when doing Crestron was fun.? So glad I'm close to retirement age too.? Thanks Brian for the heads up.

Re: Controlling powerpoint presentation from Crestron

#241789

Thank you for the answer Thorsten.

I did try that software but did not get it to work that good. So ended up using the MCE program instead.
That works fine but I cant find all the commands for controling Powerpoint, exept stop/start program and keyboard commands.
Would be nice if anybody has found a better solution :)

Re: Authorization for Connections

#241788

Great thanks for the info! Ive been in the habit for a while to set the Crestron App user credentials to Operator as in the past anything lower was just unreliable. But as for TSWs/TSRs I never setup the SETCSAUTHENTICATION and everything still works fine. As long as SECUREGATEWAYMODE is "default" the setcsauthentication is not necessary as it will use SCIP or CIP ports to communiate with the devices. I dont really see the need to turn it on especially in a resi settting and add more complication.?

Re: C# DLL version. #simplsharp

#241787

Thanks! that worked.

Re: C# DLL version. #simplsharp

#241786

开云体育

using Crestron.SimplSharp.Reflection;

?

Assembly.GetExecutingAssembly().GetName().Version.ToString()

?

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of Daniel Portugal
Sent: Monday, June 14, 2021 21:08
To: [email protected]
Subject: [crestron] C# DLL version. #simplsharp

?

[Edited Message Follows]

3-series environment. So playing in the? sandbox.
Unfortunately i cant use System.Reflection.Assembly.
//CrestronConsole.PrintLine(" Version:" + typeof(AvRouter).Assembly.GetName().Version.ToString());

I set my VS 2008 assembly to auto increment.

[assembly: AssemblyVersion("1.0.*")]

How do i get the actual version of the file to print to console?

C# DLL version. #simplsharp

#241785
Edited

3-series environment. So playing in the? sandbox.
Unfortunately i cant use System.Reflection.Assembly.
//CrestronConsole.PrintLine(" Version:" + typeof(AvRouter).Assembly.GetName().Version.ToString());

I set my VS 2008 assembly to auto increment.

[assembly: AssemblyVersion("1.0.*")]

How do i get the actual version of the file to print to console?

CLS-C6RF with Cresnet Control

#241784

Has anyone tried controlling the RF model with cresnet instead of wireless?
It has the same cresnet port in the back as the non RF version but it does have a sticker that says not in use.

I am hoping you can still use it or turn it on by forcing the non RF firmware on it.

Regards,

Re: Series 3 FW v1.8000.0014

#241783

No issues so far on my home PRO3 and my test PRO3

Re: Authorization for Connections

#241782

开云体育

Brian - "Time & Forehead Savior"

Thank you very much ??

Trey

Show quoted text

-------- Original message --------

From: Brian Matson <bmatson@...>

Date: 6/14/21 2:35 PM (GMT-06:00)

To: [email protected]

Subject: [crestron] Authorization for Connections

This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:

CP4 processor running the latest firmware
TSW-1070 running the latest firmware
TSR-310s running 2.001.0078.001 firmware
Everything setup using SSL and all cloud junk turned off.
User setup in the system for local Crestron devices as a "connects" user.

TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian

Re: Series 3 FW v1.8000.0014

#241781
Edited

it fixed a Sonos connection issue I had with the 3.1.0 modules in an RMC-3

Re: Authorization for Connections

#241780

Glad I've already retired!

Re: Authorization for Connections

#241779

开云体育

This is one example of why I have the utmost respect for members of this group. Taking the time to document this issue and share it with the rest of us is very cool of you Brian!

Ryan Cunningham?

Show quoted text

On Jun 14, 2021, at 12:35 PM, Brian Matson <bmatson@...> wrote:

?This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:

CP4 processor running the latest firmware

TSW-1070 running the latest firmware

TSR-310s running 2.001.0078.001 firmware

Everything setup using SSL and all cloud junk turned off.

User setup in the system for local Crestron devices as a "connects" user.

TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian

Re: Authorization for Connections

#241778
Edited

"TB couldn't explain why"?
...er, 'cause they didn't test it?...

Seriously though, thanks for the update, Brian!!

Re: Authorization for Connections

#241777

So glad I'm close to retirement age...

Authorization for Connections

#241776

This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:

CP4 processor running the latest firmware
TSW-1070 running the latest firmware
TSR-310s running 2.001.0078.001 firmware
Everything setup using SSL and all cloud junk turned off.
User setup in the system for local Crestron devices as a "connects" user.

TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.

Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.

This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.

Good luck!
Brian