Re: Crestron Home Driver Using the Driver SDK

开云体育

Thanks Oliver.

I guess I have to start reading and follow the path that Crestron has laid out rather than the way I usually learn new things.

P.S. - I didn't know you were a skier.? You gave it away with your "off-piste" reference?

On 2/18/2021 3:30 AM, Oliver Hall wrote:

Show quoted text

The reason I (and others) have said that Extension Devices are easier to implement than other CCD device types is kind of a "bad thing" if you're looking to be a CCD purist.
It's largely because you have greater opportunity to NOT follow the CCD SDK architecture and go off-piste.

CCD has a specific architecture which is (very roughly) a base driver class, coupled with a transport (e.g. TCP, Serial, ...) and a device (or device family) specific protocol (e.g. the language the device speaks).? These classes are dependant upon one another and need to interact in some very specific ways to work properly, such as device instantiation and removal - what does my device do at start-up, how do I clean up after myself, are commands fire and forget, or do we need to maintain a connection, what happens when the connection is broken, and so on.? In the case of a Display, Cable box or AVR, you really need to stay in your lane for this stuff - but it's often not apparent (from the docs/samples) how you're supposed to do that.

As Caleb pointed out - you find your way through a lot of trial and error, which isn't where we want to be as driver developers.

Extension devices are a bit different - because the consuming app (i.e. Crestron Home) doesn't have any understanding of what the driver actually *does*, it's easier (or less improper) to break out of the CCD mould and implement your transport and protocol any way you like, and if you already have that code from a SIMPL#/S+ version, then it's either that, or re-write the older driver code from scratch in a CCD conformant architecture.

Even so, Extension devices have other elements that "normal" drivers don't - such as the UI definition, translation files, and - most likely - a heavier reliance on User Attributes (a CCD way of passing in custom data).? They all come with their own ways to trip you up on your first few outings... or even after a few years!

And before anyone asks - yes - the frustrations and challenges and suggestions on where improvement can/should be made is all reported back to Crestron, directly into the drivers team & product managers.

Re: Topics in Home Automation - New Article in Residential Tech Today

#239993

开云体育

Thanks so much for pointing that out.? It is very weird, the link says the right thing but goes to the wrong place.? This link should work.

Thanks again

Jay

On 2/18/2021 5:52 AM, mark kaye wrote:

Show quoted text

i think the link is going to the previous article on shelly?

Re: C# http server - realtime data fed to html. #simplsharppro

#239992

Thanks Troy I’ve started going down that road.?

Re: PTZ Optics

#239991

Use the module I linked to previously, then the UDP client in Simpl, enter the IP in the config, open it and enter the correct UDP port, connect the string.

--

?

Jeffrey Franck – CTS, DMC-E-4K, Master Technology Architect
Conference Technologies, Inc.?
248 N. Cleveland
Wichita, KS 67214
Direct: 316-247-9690
Office: 316-651-0119?
JFranck@...

?

Re: Topics in Home Automation - New Article in Residential Tech Today

#239989

i think the link is going to the previous article on shelly?

Re: Extron DMP 128 crestron module

#239988

Hi Crestronfreak55,
Good Day!!!
Thank you very much for the modules you have created. By the way i am newbie in this field, i had CTI-P 101 long time back (2014) since then i haven't touch any programming. I used to handle full Site Projects from scratch to handing over.?
Since our programmer left the company and went to his home country for good, i'm the one who needs to handle crestron programming.
almost done with it like controlling Projector Screen, projector Lift, projector, Stage Curtain, Extron IN1608 except volume control of DMP128 plus. All i need to do is to control Pre-Mix Gain and Mute of Channel 1 and 2 of DMP 128 Plus. I used your module Extron DMP 128 Plus Input Gain-Pre mixer gain. Two of those, Left and Right Channel.
I can mute/unmute but i cant control the faders up and down. Kindly support me on this one please.
Thanks you.

Sincerely,
Rogelio L. Lobrio

Kaleidescape access from multiple control systems

#239987

开云体育

Hi,

?

i?m currently updating the programming for a system that involves an older Kaleidescape V700/M300 combo.

Programming is distributed among 3 Crestron control units (2 x CP3 and 1 x MC2E). One of them is running the Kaleidescape IP Control Module, communication to the other control systems is done via Intersystem Communication.

I?d like to add the IP control modul to the other two programs as well to get rid of the EICs.

Are the Kaleidescape systems capable of handling multiple connections?

?

Cheers, Thorsten

Re: Crestron Home Driver Using the Driver SDK

#239986

The reason I (and others) have said that Extension Devices are easier to implement than other CCD device types is kind of a "bad thing" if you're looking to be a CCD purist.
It's largely because you have greater opportunity to NOT follow the CCD SDK architecture and go off-piste.

CCD has a specific architecture which is (very roughly) a base driver class, coupled with a transport (e.g. TCP, Serial, ...) and a device (or device family) specific protocol (e.g. the language the device speaks).? These classes are dependant upon one another and need to interact in some very specific ways to work properly, such as device instantiation and removal - what does my device do at start-up, how do I clean up after myself, are commands fire and forget, or do we need to maintain a connection, what happens when the connection is broken, and so on.? In the case of a Display, Cable box or AVR, you really need to stay in your lane for this stuff - but it's often not apparent (from the docs/samples) how you're supposed to do that.

As Caleb pointed out - you find your way through a lot of trial and error, which isn't where we want to be as driver developers.

Extension devices are a bit different - because the consuming app (i.e. Crestron Home) doesn't have any understanding of what the driver actually *does*, it's easier (or less improper) to break out of the CCD mould and implement your transport and protocol any way you like, and if you already have that code from a SIMPL#/S+ version, then it's either that, or re-write the older driver code from scratch in a CCD conformant architecture.

Even so, Extension devices have other elements that "normal" drivers don't - such as the UI definition, translation files, and - most likely - a heavier reliance on User Attributes (a CCD way of passing in custom data).? They all come with their own ways to trip you up on your first few outings... or even after a few years!

And before anyone asks - yes - the frustrations and challenges and suggestions on where improvement can/should be made is all reported back to Crestron, directly into the drivers team & product managers.

Re: Crestron Home Driver Using the Driver SDK

#239985

But isn’t there a pile of stuff going on in almost every driver?? Of course the next one will go much,much faster. I’m just concerned about the learning cliff.

Thanks?

Show quoted text

On Wed, Feb 17, 2021 at 8:38 PM Caleb Radecky <caleb@...> wrote:

Well, to be fair there is a pile of stuff going on inside the Pentair module and there was a bit of "well if I knew I was going to need the data this way" moments. I feel pretty confident that the next one I attempt will take me 1/8th the amount of time this one took.?

The steps to create an extension in the documentation do show how to implement them, I'd start there.

Caleb Radecky |?Manager, Online Products & Services
Crestron Silver Certified Programmer | DMC-D-4K | DMC-E-4K
ControlWorks Consulting, LLC |?Crestron Services Provider?|
D.?440.771.4809 |?O.440.449.1100?X1109 | F.440.449.1106 |

From: jbasen <jay.m.basen@...>
Sent: Wednesday, February 17, 2021 22:24
To: [email protected]
Subject: Re: [crestron] Crestron Home Driver Using the Driver SDK

Thanks Caleb.?

I’ll take a look at that section of the SDK.? I’ve just always liked to start with something that illustrates the correct approach to a programming paradigm rather than trying to figure that out from documentation.?

All the drivers I’ve been releasing on my GitHub are S# with S+ wrappers.? However I’ve only dug into S# Pro once and that was years ago during the original S# beta.? I just haven’t had a need for S# Pro since

It doesn’t give me a lot of confidence that it has taken you a month to take an existing S# module and port it to Home.? How many people can dedicate that much time to develop a single driver for a real world project?

Thanks again?

Jay

On Wed, Feb 17, 2021 at 8:03 PM Caleb Radecky <caleb@...> wrote:

We are just about to release version 2 of our Pentair IntelliCenter module which was a SIMPL+ module rewrite in SIMPL#. That task alone was a fun challenge and we were about to release that version until we decided to wrap in the Crestron Home components in the same library that plays with SIMPL Windows. It’s taken me about a month – from not knowing anything about extensions, to about to release the Pentair IntelliCenter Driver. While I don’t have any code that I can share, I started off following the Create an Extension Driver section of the SDK documentation with the goal of just having a button do something on the CP4-R, and worked out from there which I think would be good for someone starting out. It wasn’t until I didn’t understand one of the steps that I referenced the samples. While the samples do compile and run(I think I actually ran them once when Lincoln had enough of me screaming at the CP4-R in a WTH moment) I only use them for reference material. The process was certainly A LOT of trial and error.? Documentation is ok, there is a lot of reading between the lines, and a lot of going may places on the SDK site to put the jigsaw puzzle together.

?

Jay I know you know your way around Visual Studio, but for anyone else reading this, if you haven’t really played with SIMPL# and/or SIMPL#Pro and you’re trying this out, be prepared for steep uphill battle.

?

Caleb

?

Caleb Radecky | Manager, Online Products & Services
Crestron Silver Certified Programmer | DMC-D-4K | DMC-E-4K
ControlWorks Consulting, LLC | Crestron Services Provider |
D. 440.771.4809 | O.440.449.1100 X1109 | F.440.449.1106 |

?

From: [email protected] <[email protected]> On Behalf Of jbasen
Sent: Wednesday, February 17, 2021 21:17
To: [email protected]
Subject: [crestron] Crestron Home Driver Using the Driver SDK

?

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay

Re: Crestron Home Driver Using the Driver SDK

#239984

开云体育

Well, to be fair there is a pile of stuff going on inside the Pentair module and there was a bit of "well if I knew I was going to need the data this way" moments. I feel pretty confident that the next one I attempt will take me 1/8th the amount of time this one took.?

The steps to create an extension in the documentation do show how to implement them, I'd start there.

Show quoted text

From: jbasen <jay.m.basen@...>
Sent: Wednesday, February 17, 2021 22:24
To: [email protected]
Subject: Re: [crestron] Crestron Home Driver Using the Driver SDK

Thanks Caleb.?

I’ll take a look at that section of the SDK.? I’ve just always liked to start with something that illustrates the correct approach to a programming paradigm rather than trying to figure that out from documentation.?

All the drivers I’ve been releasing on my GitHub are S# with S+ wrappers.? However I’ve only dug into S# Pro once and that was years ago during the original S# beta.? I just haven’t had a need for S# Pro since

It doesn’t give me a lot of confidence that it has taken you a month to take an existing S# module and port it to Home.? How many people can dedicate that much time to develop a single driver for a real world project?

Thanks again?

Jay

On Wed, Feb 17, 2021 at 8:03 PM Caleb Radecky <caleb@...> wrote:

We are just about to release version 2 of our Pentair IntelliCenter module which was a SIMPL+ module rewrite in SIMPL#. That task alone was a fun challenge and we were about to release that version until we decided to wrap in the Crestron Home components in the same library that plays with SIMPL Windows. It’s taken me about a month – from not knowing anything about extensions, to about to release the Pentair IntelliCenter Driver. While I don’t have any code that I can share, I started off following the Create an Extension Driver section of the SDK documentation with the goal of just having a button do something on the CP4-R, and worked out from there which I think would be good for someone starting out. It wasn’t until I didn’t understand one of the steps that I referenced the samples. While the samples do compile and run(I think I actually ran them once when Lincoln had enough of me screaming at the CP4-R in a WTH moment) I only use them for reference material. The process was certainly A LOT of trial and error.? Documentation is ok, there is a lot of reading between the lines, and a lot of going may places on the SDK site to put the jigsaw puzzle together.

?

Jay I know you know your way around Visual Studio, but for anyone else reading this, if you haven’t really played with SIMPL# and/or SIMPL#Pro and you’re trying this out, be prepared for steep uphill battle.

?

Caleb

?

Caleb Radecky | Manager, Online Products & Services
Crestron Silver Certified Programmer | DMC-D-4K | DMC-E-4K
ControlWorks Consulting, LLC | Crestron Services Provider |
D. 440.771.4809 | O.440.449.1100 X1109 | F.440.449.1106 |

?

From: [email protected] <[email protected]> On Behalf Of jbasen
Sent: Wednesday, February 17, 2021 21:17
To: [email protected]
Subject: [crestron] Crestron Home Driver Using the Driver SDK

?

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay

Re: Crestron Home Driver Using the Driver SDK

#239983

Thanks Caleb.?

I’ll take a look at that section of the SDK.? I’ve just always liked to start with something that illustrates the correct approach to a programming paradigm rather than trying to figure that out from documentation.?

All the drivers I’ve been releasing on my GitHub are S# with S+ wrappers.? However I’ve only dug into S# Pro once and that was years ago during the original S# beta.? I just haven’t had a need for S# Pro since

It doesn’t give me a lot of confidence that it has taken you a month to take an existing S# module and port it to Home.? How many people can dedicate that much time to develop a single driver for a real world project?

Thanks again?

Jay

Show quoted text

On Wed, Feb 17, 2021 at 8:03 PM Caleb Radecky <caleb@...> wrote:

We are just about to release version 2 of our Pentair IntelliCenter module which was a SIMPL+ module rewrite in SIMPL#. That task alone was a fun challenge and we were about to release that version until we decided to wrap in the Crestron Home components in the same library that plays with SIMPL Windows. It’s taken me about a month – from not knowing anything about extensions, to about to release the Pentair IntelliCenter Driver. While I don’t have any code that I can share, I started off following the Create an Extension Driver section of the SDK documentation with the goal of just having a button do something on the CP4-R, and worked out from there which I think would be good for someone starting out. It wasn’t until I didn’t understand one of the steps that I referenced the samples. While the samples do compile and run(I think I actually ran them once when Lincoln had enough of me screaming at the CP4-R in a WTH moment) I only use them for reference material. The process was certainly A LOT of trial and error.? Documentation is ok, there is a lot of reading between the lines, and a lot of going may places on the SDK site to put the jigsaw puzzle together.

?

Jay I know you know your way around Visual Studio, but for anyone else reading this, if you haven’t really played with SIMPL# and/or SIMPL#Pro and you’re trying this out, be prepared for steep uphill battle.

?

Caleb

?

Caleb Radecky | Manager, Online Products & Services
Crestron Silver Certified Programmer | DMC-D-4K | DMC-E-4K
ControlWorks Consulting, LLC | Crestron Services Provider |
D. 440.771.4809 | O.440.449.1100 X1109 | F.440.449.1106 |

?

From: [email protected] <[email protected]> On Behalf Of jbasen
Sent: Wednesday, February 17, 2021 21:17
To: [email protected]
Subject: [crestron] Crestron Home Driver Using the Driver SDK

?

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay

Re: Crestron Home Driver Using the Driver SDK

#239982

开云体育

We are just about to release version 2 of our Pentair IntelliCenter module which was a SIMPL+ module rewrite in SIMPL#. That task alone was a fun challenge and we were about to release that version until we decided to wrap in the Crestron Home components in the same library that plays with SIMPL Windows. It’s taken me about a month – from not knowing anything about extensions, to about to release the Pentair IntelliCenter Driver. While I don’t have any code that I can share, I started off following the Create an Extension Driver section of the SDK documentation with the goal of just having a button do something on the CP4-R, and worked out from there which I think would be good for someone starting out. It wasn’t until I didn’t understand one of the steps that I referenced the samples. While the samples do compile and run(I think I actually ran them once when Lincoln had enough of me screaming at the CP4-R in a WTH moment) I only use them for reference material. The process was certainly A LOT of trial and error. ?Documentation is ok, there is a lot of reading between the lines, and a lot of going may places on the SDK site to put the jigsaw puzzle together.

?

Jay I know you know your way around Visual Studio, but for anyone else reading this, if you haven’t really played with SIMPL# and/or SIMPL#Pro and you’re trying this out, be prepared for steep uphill battle.

?

Caleb

?

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of jbasen
Sent: Wednesday, February 17, 2021 21:17
To: [email protected]
Subject: [crestron] Crestron Home Driver Using the Driver SDK

?

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from crestron.com/developer and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay

Re: Crestron Home Driver Using the Driver SDK

#239981

I can't answer your question, but I find it more than a little ironic that Crestron's door lock example would have so many features, when door locks in Crestron Home have only the bare minimum functionality.  Or at least that's the way it was the last time I looked, and people have complained about it for years.

Show quoted text

--- On Wednesday, February 17, 2021 at 9:17 PM, Jay Basen wrote:

I've had a request to port the Weatherflow Tempest weather station driver I
wrote to Crestron Home.  How bad can it be.  So, I downloaded the driver SDK
from crestron.com/developer and got it installed on my laptop.  Then I started
to try and dig in.  Crestron supplies a bunch of sample projects so I figured
that was the best place to start.  I could find a nice simple sample and then
start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather
station, is the easiest type of driver to create so again, how bad can it be.

So, I look at the extension driver samples and there is one for a door
lock.  Opening up the sample Crestron has chosen to include every possible bit
of functionality you can think of for a door lock.  It includes access list
support, jam support, and the list goes on.  All that extra functionality in a
sample that you are using to try and just get started with something new
obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot
run" level.  As stupid simple as possible.  Once I have a clue I can take baby
steps and move onward to something a bit more complex.  Now a door lock isn't
like trying to learn to speak English by trying to read "War and Peace" but
with all the added functionality Crestron included it is certainly at the level
of a novel by Earnest Hemingway.

So, this saga finally brings me to my question.  Does anyone, who has gone down
this path before me, have a really, really, really basic example of an
extension driver they are willing to share?  Something at the level of
controlling an IoT relay from Crestron home where all you can do is turn it
on/off.

Thanks in advance for the help.

Jay

Crestron Home Driver Using the Driver SDK

#239980

开云体育

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from crestron.com/developer and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay

Re: SWAMP - weird bug?

#239979

开云体育

That was how I originally programmed it but whenever the amp powered on we had an obnoxious noise and the client couldn’t stand it so leaving it in a ready powered on mode was the only way I could avoid it.

Show quoted text

On Feb 17, 2021, at 4:58 PM, Greg B <gregb@...> wrote:

?
[Edited Message Follows]
for a work around either turn the output on and off at program start or turn the Sonance dsp on/off with 12v trigger or IP commands

Re: PTZ Optics

#239978

Hi.
What module do you use to make it work in UDP and how did you configure the camera? I can't do it.
Thank you in advance.
Manu.

Re: SWAMP - weird bug?

#239977
Edited

for a work around either turn the output on and off at program start or turn the Sonance dsp on/off with 12v trigger or IP commands

Re: SWAMP - weird bug?

#239976

I just tied my room off signal to input 2 on the Sonance DSP card which is empty. It simulates the room off condition. Did you report your situation to True Blue? They kept insisting what a mature product this is and how they’ve never seen this before. I can see if an AVR is attached it masks the issue but it seems like you are aware of it. If you opened a case for this issue I’m ready to get my pitchfork and torch. This turned into a plane trip visit to find out it’s not resolved with equipment exchange. I could have shifted my inputs as mentioned but my solution was available and worked.

Re: Lighting in Simpl from scratch

#239975

The Crestron Home part of the system isn't very large.
The main program on the PRO3 is based off the Adapt model, and I know that you're familiar with their framework.
Even the guys at Pantech hadn't tried a system with many Pyng connects.

The second processor is a CP4-R.? In my earlier post I mistakenly referred to it as a CP3-R.
It was responsible for the infiNET EX lighting, shades, climate, and a small handful of keypads (around 100 loads, 20 shades, 5 tstats, 8 keypads).
Now, it lost its climate duties!

The third processor, a CP3, handles the custom environmental programming.
That includes Infratec heaters, outdoor Somfy shades and awnings, pool control, camera NVR, ELK security, access control, and Davis weather system.
Now, the third processor has taken over climate as well.? As you know, its a total "suck-fest" to manage infiNET and WiFi channels when you can't share gateways between Simpl and Home!!!

The main processor just chugs along at about 9% to 12% CPU usage most of the time.

Re: SWAMP - weird bug?

#239974

开云体育

Is it an option to not use input 1 for now and move it to a free input?

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of Jason Melvin
Sent: Wednesday, February 17, 2021 7:34 AM
To: [email protected]
Subject: Re: [crestron] SWAMP - weird bug?

?

Yes! I have this problem and it's pretty annoying. What's your workaround, turning on output 9 and then turning it off when the system initializes??

?

On Tue, Feb 16, 2021 at 10:07 PM FTAV <ftavinc@...> wrote:

Hi everyone - I have a project that had a SWAMP connected to a Sonance DSP on SDPIF output 9. The DSP amp never powers off it's always in standby, so whenever the output gets set to zero in programming audio ceases. I received a client complaint that this zone was turning on when zone 1 was being turned on to input 1. This makes zero sense because the pool zone on SDPIF output 9 can't turn onto this source in programming - the analog initialize symbol doesn't allow 1 as a value. The Sonnex tool would show None as a source even though the audio was clearly present.? After troubleshooting with True Blue they determined a hardware issue and authorized advanced replacement. Replacement installed - the same problem. I discovered that even though SDPIF output 10 isn't even defined in my programming, it was turning on to input 1 as well, so both SDPIF outputs are doing the same malfunction on 2 different SWAMP units. When I select an audio source for the pool on output 9 (that is defined in programming and is supposed to work) it turns on and when I turn it off it turns off. This is where I noticed a behavior- once I do this the malfunction stops. It only returns when there is a power cycle of the SWAMP. It appears that a power cycle of the SWAMP does something to cause outputs 9 and 10 to recall input 1 on zone 1 until you choose another source and shut it off. I've got a workaround completed but I've never been this before and I can create the condition consistently now that I screwed around with it today in person. Anybody else have this condition on the digital outputs? I've done a few with AVRs on these digital outputs which always turn on and off with the zone so I've never had this happen before. The fact that this DSP was remaining in a powered-up state seems to have allowed the condition to present itself.