开云体育

Take the following senario:
Main zone SIO contains the parameter: Cable\x0D
Secondary SIO zone contains the parameter: Zone 2 Cable\x0D

Now of course both these events will fire if I send: Zone 2 Cable\x0D
This is the expected behaviour from a serial I/O.

Is there a way to make the SIO more choosy? So if I send Zone 2
Cable\x0D it does not trip the main zone event.

Thanks

gary

--- In Crestron@..., "slip.cougan" <slip.cougan@...>
wrote:

Take the following senario:
Main zone SIO contains the parameter: Cable&#92;x0D
Secondary SIO zone contains the parameter: Zone 2 Cable&#92;x0D

Now of course both these events will fire if I send: Zone 2

Cable&#92;x0D

This is the expected behaviour from a serial I/O.

Is there a way to make the SIO more choosy? So if I send Zone 2
Cable&#92;x0D it does not trip the main zone event.

Thanks

gary

What's the concept of using the SIO? Are you using serial strings
into the SIO to switch sources from the outputs? Maybe look at using
analog init's instead?

Sorry, these are returned strings from the device, I was simulating
the strings in debugger.

All my modules use analogs for source selects (I don't do digitals
anymore :) )

g

Assuming you mean strings coming into the SIO, have you tried removing
spaces in the string and/or replace them with other characters i.e.
"Cable&#92;r" & "Zone2-Cable&#92;r"... this effectively makes the second
string one word so the other parameter (or other SIO) cant match it.

ChipG

An incoming "Zone2-Cable&#92;r" will trigger BOTH "Cable&#92;r" and
"Zone2-Cable&#92;r" parameters. "Cable&#92;r" is still a subset of the
incoming string and a valid match...

- Chip


--- In Crestron@..., "lunarteq" <lunartech@...> wrote:

Assuming you mean strings coming into the SIO, have you tried removing
spaces in the string and/or replace them with other characters i.e.
"Cable&#92;r" & "Zone2-Cable&#92;r"... this effectively makes the second
string one word so the other parameter (or other SIO) cant match it.

ChipG

--- In Crestron@..., "slip.cougan" <slip.cougan@> wrote:

Sorry, these are returned strings from the device, I was simulating
the strings in debugger.

All my modules use analogs for source selects (I don't do digitals
anymore :) )

g

--- In Crestron@..., "Matt" <mjrtoo@> wrote:

--- In Crestron@..., "slip.cougan" <slip.cougan@>
wrote:

Take the following senario:
Main zone SIO contains the parameter: Cable&#92;x0D
Secondary SIO zone contains the parameter: Zone 2 Cable&#92;x0D

Now of course both these events will fire if I send: Zone 2

Cable&#92;x0D

This is the expected behaviour from a serial I/O.

Is there a way to make the SIO more choosy? So if I send Zone 2
Cable&#92;x0D it does not trip the main zone event.

Thanks

gary

What's the concept of using the SIO? Are you using serial strings
into the SIO to switch sources from the outputs? Maybe look at

using

analog init's instead?

How about making "Cable" into "Zone 1 Cable" instead? Valid option?

- Chip

At the risk of sounding stupid, it would seem like a simple truth
table would take care of this. When the string is received, both will
go high (or low) on the same wave.

Zone 1 = 'cable' H and 'zone 2 cable' low
Zone 2 is fine right out of the SIO. If you want it to go high on the
same wave, just put it in the truth table as 'zone 2 cable' h with X
for 'cable'

or you could detect the &#92;r and use it to clear a SR. Then detect
the 'Zone 2 ' and set the SR. Then detect the cable and use the SR's
output to route the pulse. The pulse will be one save long because
the incoming &#92;r will clear the 'cable' output. I might do this if
there were a lot of Zone 2 commands and use two buffers (one each on
the output of the SR) to send the commands where you want them.

I apologize if I'm missing something tricky.



--- In Crestron@..., "Chip Moody" <cfm@...> wrote:

An incoming "Zone2-Cable&#92;r" will trigger BOTH "Cable&#92;r" and
"Zone2-Cable&#92;r" parameters. "Cable&#92;r" is still a subset of the
incoming string and a valid match...

- Chip


--- In Crestron@..., "lunarteq" <lunartech@> wrote:

Assuming you mean strings coming into the SIO, have you tried

removing

spaces in the string and/or replace them with other characters

i.e.

"Cable&#92;r" & "Zone2-Cable&#92;r"... this effectively makes the second
string one word so the other parameter (or other SIO) cant match

it.

ChipG

--- In Crestron@..., "slip.cougan" <slip.cougan@>

wrote:

Sorry, these are returned strings from the device, I was

simulating

the strings in debugger.

All my modules use analogs for source selects (I don't do

digitals

anymore :) )

g

--- In Crestron@..., "Matt" <mjrtoo@> wrote:

--- In Crestron@..., "slip.cougan" <slip.cougan@>
wrote:

Take the following senario:
Main zone SIO contains the parameter: Cable&#92;x0D
Secondary SIO zone contains the parameter: Zone 2 Cable&#92;x0D

Now of course both these events will fire if I send: Zone 2

Cable&#92;x0D

This is the expected behaviour from a serial I/O.

Is there a way to make the SIO more choosy? So if I send

Zone 2

Cable&#92;x0D it does not trip the main zone event.

Thanks

gary

What's the concept of using the SIO? Are you using serial

strings

into the SIO to switch sources from the outputs? Maybe look

at

using

analog init's instead?