开云体育

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@...>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

You are correct Matt. The "tick" increment is much smaller in the 3-series
which is why we were encouraged to use logic waves for timed event
management rather than ticks.

On Fri, Apr 13, 2012 at 4:13 PM, matt_rasmussen_2000 <mjrtoo@...>wrote:

**


I was told in the last masters the smallest timeslice in 3 series is
.000000000001s rather than the .01s in 2 series. Is that not true?


--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron

programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not

sure if that's going to really get in your way. Most pure SIMPL solutions
work the same. There have been some SIMPL+ gotchas since it's a new
platform, but they have endeavored to make most of it the same (and if you
do have access to the labs, you CAN post a message to them saying that XXX
works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is

variable to begin with.

--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can

tell

you is that if you are using anything that uses ticks for timing it

will

cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it

works

fine with my Cp2E processor in the office. - However - when It got

sent out

to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes

like it's

supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

That might be the smallest nonzero value you can enter, but I have a
hard time believing it will really trigger the next signal a
thousandth of a nanosecond later, especially when a 1GHz processor
only has a clock pulse once every nanosecond.

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

Since that is less than a single processor cycle I think it is safe to say that it's not true. With the current programming tools the shortest time-able period is still 0.01 seconds. With new tools that is likely to change. However, timing in Crestron is not guaranteed. Timed events are executed on the first available S+ or logic slot AFTER the elapsed time. If the time required to process core tasks takes longer, length of time 'after' can be considerable. In fact, I used this attribute to demonstrate the time taken for various tasks in the demonstration program that I wrote a couple of years ago (still in the files section I think).

Lindsay

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

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

That might be the smallest nonzero value you can enter, but I have a
hard time believing it will really trigger the next signal a
thousandth of a nanosecond later, especially when a 1GHz processor
only has a clock pulse once every nanosecond.

On Fri, Apr 13, 2012 at 6:13 PM, matt_rasmussen_2000 <mjrtoo@...> wrote:

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. ?Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. ?That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. ?Most pure SIMPL solutions work the same. ?There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 ?but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? ?Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. ?This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

------------------------------------



Check out the Files area for useful modules, documents, and drivers.

A contact list of Crestron dealers and programmers can be found in the Database area.
Yahoo! Groups Links

--
Jeremy Weatherford

You are correct Matt. The "tick" increment is much smaller in the 3-series
which is why we were encouraged to use logic waves for timed event
management rather than ticks.

On Fri, Apr 13, 2012 at 4:13 PM, matt_rasmussen_2000 <mjrtoo@...>wrote:

**


I was told in the last masters the smallest timeslice in 3 series is
.000000000001s rather than the .01s in 2 series. Is that not true?


--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron

programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not

sure if that's going to really get in your way. Most pure SIMPL solutions
work the same. There have been some SIMPL+ gotchas since it's a new
platform, but they have endeavored to make most of it the same (and if you
do have access to the labs, you CAN post a message to them saying that XXX
works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is

variable to begin with.

--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can

tell

you is that if you are using anything that uses ticks for timing it

will

cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it

works

fine with my Cp2E processor in the office. - However - when It got

sent out

to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes

like it's

supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

**



I remember being told the same thing, and that "1t" in a 2 series is
longer than 1t in the 3...

- Chip


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

I was told in the last masters the smallest timeslice in 3 series is

.000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of

crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not

sure if that's going to really get in your way. Most pure SIMPL solutions
work the same. There have been some SIMPL+ gotchas since it's a new
platform, but they have endeavored to make most of it the same (and if you
do have access to the labs, you CAN post a message to them saying that XXX
works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave"

is variable to begin with.

--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can

tell

you is that if you are using anything that uses ticks for timing it

will

cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device,

it works

fine with my Cp2E processor in the office. - However - when It got

sent out

to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes

like it's

supposed to.. Has anyone else had this happen - on any IP module

that

worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

Actually a processor cycle is not a set time. So 1 logic wave can be shorter then .01s or then .01s because of the way it works.

Also is the SIMPL+ direct socket or does it run through a tcp/ip client?

If direct, the condition for the send may not be correct.

If you are using SOCKETSTATUS with the simpl+
and you are saving the status as a variable (ex CurrentStatus)
with CurrentStatus = SOCKETGETSTATUS();
i have found that is the most reliable. That way when it shows a 2 you can set the string to send.

The other problem i came across is that when the CurrentStatus = ( 4 || 5), i needed to make sure to SOCKETDISCONNECTCLIENT(socketname)

else sometime it would think it was connected and not really be.


--- In Crestron@..., "l_codd" <lindsayc@> wrote:

Since that is less than a single processor cycle I think it is safe to say that it's not true. With the current programming tools the shortest time-able period is still 0.01 seconds. With new tools that is likely to change. However, timing in Crestron is not guaranteed. Timed events are executed on the first available S+ or logic slot AFTER the elapsed time. If the time required to process core tasks takes longer, length of time 'after' can be considerable. In fact, I used this attribute to demonstrate the time taken for various tasks in the demonstration program that I wrote a couple of years ago (still in the files section I think).

Lindsay

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

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]

It's direct socket control, just point the module at the right IP/Port combo and it works. I have two flavors of the module at the moment, one is full features (still working on it) and one is stripped down to accomplish one task - mute/unmute...

In the stripped down version, I have the packet built, and then open the port with socketClientConnect. When the socket has been properly established, I have the send of the packet going out on the SOCKETCONNECT. After it connects, I wait for the response on the socketreceive and if the response is right (in this case - I got any response) - shut the port.

Like I said works great on the 2-series. TB thinks is may be a timing error, I am playing with it today to try and really fix it - hopefully I can..

On a side note - what is the longest string that can be output either from a S+ Module to Simple - or Simple to a TCP/IP client - cause I thought about going that route, but I have really large packets to send..

Thanks for the help guys!

--- In Crestron@..., "Witmarquzot" <tdurrant420@> wrote:

Actually a processor cycle is not a set time. So 1 logic wave can be shorter then .01s or then .01s because of the way it works.

Also is the SIMPL+ direct socket or does it run through a tcp/ip client?

If direct, the condition for the send may not be correct.

If you are using SOCKETSTATUS with the simpl+
and you are saving the status as a variable (ex CurrentStatus)
with CurrentStatus = SOCKETGETSTATUS();
i have found that is the most reliable. That way when it shows a 2 you can set the string to send.

The other problem i came across is that when the CurrentStatus = ( 4 || 5), i needed to make sure to SOCKETDISCONNECTCLIENT(socketname)

else sometime it would think it was connected and not really be.


--- In Crestron@..., "l_codd" <lindsayc@> wrote:

Since that is less than a single processor cycle I think it is safe to say that it's not true. With the current programming tools the shortest time-able period is still 0.01 seconds. With new tools that is likely to change. However, timing in Crestron is not guaranteed. Timed events are executed on the first available S+ or logic slot AFTER the elapsed time. If the time required to process core tasks takes longer, length of time 'after' can be considerable. In fact, I used this attribute to demonstrate the time taken for various tasks in the demonstration program that I wrote a couple of years ago (still in the files section I think).

Lindsay

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

I was told in the last masters the smallest timeslice in 3 series is .000000000001s rather than the .01s in 2 series. Is that not true?

--- In Crestron@..., "RobK" <fooguy89@> wrote:

A "tick" (i.e. 1d in a time based symbol) is 0.01s in terms of crestron programming. That's the same for both 3 series and 2 series.

Gates run faster on the MC3 than they do on the 2 series, but I'm not sure if that's going to really get in your way. Most pure SIMPL solutions work the same. There have been some SIMPL+ gotchas since it's a new platform, but they have endeavored to make most of it the same (and if you do have access to the labs, you CAN post a message to them saying that XXX works on a 2 but not on a 3 series).

But there never was a "time" for a logic wave, anyway, since a "wave" is variable to begin with.


--- In Crestron@..., stranded <strandedyahoo@> wrote:

Is the module completely Simpl+? Having not used a MC3 yet all I can tell
you is that if you are using anything that uses ticks for timing it will
cause timing issues. This is because a tick in the MC3 is much much
shorter than in a 2 series.

On Fri, Apr 13, 2012 at 10:29 AM, waltonad0283 <waltonad0283@>wrote:

**


Hi All,

I have a Simpl+ module that I wrote for an IP controlled device, it works
fine with my Cp2E processor in the office. - However - when It got sent out
to a client site that has an MC3 in it - it doesn't work.

I am trying to switch audio/video sources - on my Cp2E - everything
happens fine. On the MC3, toolbox shows making a successful socket
connection, but the switch never happens. Then the socket closes like it's
supposed to.. Has anyone else had this happen - on any IP module that
worked on a 2 series and not on a 3 series - and if so what was the
resolution?

Thanks

[Non-text portions of this message have been removed]