¿ªÔÆÌåÓý

The colors are on remote central from a 722 and work

Sent from my pocket computer

Unless your parsing code has delays in it that would allow the buffer to fill up, I find that using destructive functions on the buffer does not ever require the use of a clearbuffer.
Remove() and Gather() are destructive and using them to pick off the buffer has never given me trouble to where I thought I needed to use clearbuffer. They only time I've ever used clearbuffer in the past was when I didn't get destructive functions or it was really late at night and I didn't have time to figure out where bugs were so I used it as a band aide.

JP


--- In Crestron@..., Tray Schaeffer <trayschaeffer@> wrote:

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of the solution for this problem and good coding practice. This is not just a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only 255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes in, no error is returned. Both statements above assume that the Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was received before, it is easy to see how data that is already processed but not removed could cause the buffer to be full (or full enough that an incoming data frame wont fit completely in the remaining space) when new data arrives.
Wiping the slate clean after each complete frame of data is received is not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I make a copy of a complete data frame into a temp variable and immediately clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work around, it?€?s the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use a String_Input instead. Disadvantage here is that this cannot be larger than 255 chars.
Upside is that you never have to remember to clear the input as it will clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03") is found. ie. The buffer will still be filled up with replies from other polls!
This is excactly the same issue I experienced today with the I2P "BenQ SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me.... (especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

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

Can anyone give me a compelling reason to spend extra money on the 3-series card frame and cards when I can get the same features in a slaved CP2e? Need to add Com, IR and relays to an MC3 and a Cresnet slaved CP2e seems like a pretty solid choice for less money.

Heath

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of the solution for this problem and good coding practice. This is not just a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only 255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes in, no error is returned. Both statements above assume that the Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was received before, it is easy to see how data that is already processed but not removed could cause the buffer to be full (or full enough that an incoming data frame wont fit completely in the remaining space) when new data arrives.
Wiping the slate clean after each complete frame of data is received is not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I make a copy of a complete data frame into a temp variable and immediately clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work around, it?€?s the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use a String_Input instead. Disadvantage here is that this cannot be larger than 255 chars.
Upside is that you never have to remember to clear the input as it will clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03") is found. ie. The buffer will still be filled up with replies from other polls!
This is excactly the same issue I experienced today with the I2P "BenQ SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me.... (especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

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

Try ebay?

--- In Crestron@..., "sevenstarokawari" <tabata@> wrote:

Hi, I am Japanese.
In case of Japan, ST-CS is out of discontinued model due to "PSE certification"
PSE certification is, safety basis which Japanese government defines.

Anyway ST-CS doesn't have the PSE mark.
So Crestron Japan doesn't sell ST-CS to any their distributors.
Thus there is no way to buy that product. But I would like to buy still!!
Therefore I am looking for the third party current sensor which can send the current value (I hope) via RS-232C.

Is there such a product in the world?
If I can buy from this website, I am very happy.
www.smarthome.com

Regards,

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of the solution for this problem and good coding practice. This is not just a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only 255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes in, no error is returned. Both statements above assume that the Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was received before, it is easy to see how data that is already processed but not removed could cause the buffer to be full (or full enough that an incoming data frame wont fit completely in the remaining space) when new data arrives.
Wiping the slate clean after each complete frame of data is received is not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I make a copy of a complete data frame into a temp variable and immediately clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work around, it?€?s the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use a String_Input instead. Disadvantage here is that this cannot be larger than 255 chars.
Upside is that you never have to remember to clear the input as it will clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03") is found. ie. The buffer will still be filled up with replies from other polls!
This is excactly the same issue I experienced today with the I2P "BenQ SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me.... (especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

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

As long as you guys are comparing apples and oranges (Stig's comments
on this specific module vs. Tray's grand programming concepts), let me
throw in some bananas....

This should be done with just SIMPL. No S+ moots all the buffer
size/management arguments.

Ha!



On Fri, 10 Aug 2012 14:54:17 -0000, "Stig" <ska@...> wrote:

Ted,
I agree with you that increasing the buffer sometimes is necessary, but in
this case I don't believe that's the issue and it will not alone fix the
problem as you also need to extract from/empty the buffer one way or another.
As you say, clearing the buffer once you have received the packet and
extracted it to a tempstring is one solution but my impression is that a
well written parsing routine pour contents from the buffer to a tempstring
delimiterwise, as exemplified many times before on this forum, so there
should be no need to clear the buffer at any time ?

What upsets me is that many I2P modules from the mothership is failing, and
buffer overflow's seems to be a common issue.

-Stig

--- In Crestron@..., Tray Schaeffer <trayschaeffer@> wrote:

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of
the solution for this problem and good coding practice. This is not just
a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only
255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes
in, no error is returned. Both statements above assume that the
Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was
received before, it is easy to see how data that is already processed but
not removed could cause the buffer to be full (or full enough that an
incoming data frame wont fit completely in the remaining space) when new
data arrives.
Wiping the slate clean after each complete frame of data is received is
not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I
make a copy of a complete data frame into a temp variable and immediately
clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work
around, it's the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use
a String_Input instead. Disadvantage here is that this cannot be larger
than 255 chars.
Upside is that you never have to remember to clear the input as it will
clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer
from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for
Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how
increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is
suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove
characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03")
is found. ie. The buffer will still be filled up with replies from other
polls!
This is excactly the same issue I experienced today with the I2P "BenQ
SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if
delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow
messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me....
(especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both
the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

Hi, I am Japanese.
In case of Japan, ST-CS is out of discontinued model due to "PSE certification"
PSE certification is, safety basis which Japanese government defines.

Anyway ST-CS doesn't have the PSE mark.
So Crestron Japan doesn't sell ST-CS to any their distributors.
Thus there is no way to buy that product. But I would like to buy still!!
Therefore I am looking for the third party current sensor which can send the current value (I hope) via RS-232C.

Is there such a product in the world?
If I can buy from this website, I am very happy.
www.smarthome.com

Regards,

Ted,
I agree with you that increasing the buffer sometimes is necessary, but in
this case I don't believe that's the issue and it will not alone fix the
problem as you also need to extract from/empty the buffer one way or another.
As you say, clearing the buffer once you have received the packet and
extracted it to a tempstring is one solution but my impression is that a
well written parsing routine pour contents from the buffer to a tempstring
delimiterwise, as exemplified many times before on this forum, so there
should be no need to clear the buffer at any time ?

What upsets me is that many I2P modules from the mothership is failing, and
buffer overflow's seems to be a common issue.

-Stig

--- In Crestron@..., Tray Schaeffer <trayschaeffer@...> wrote:

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of
the solution for this problem and good coding practice. This is not just
a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only
255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes
in, no error is returned. Both statements above assume that the
Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was
received before, it is easy to see how data that is already processed but
not removed could cause the buffer to be full (or full enough that an
incoming data frame wont fit completely in the remaining space) when new
data arrives.
Wiping the slate clean after each complete frame of data is received is
not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I
make a copy of a complete data frame into a temp variable and immediately
clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work
around, it's the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use
a String_Input instead. Disadvantage here is that this cannot be larger
than 255 chars.
Upside is that you never have to remember to clear the input as it will
clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer
from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for
Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how
increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is
suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove
characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03")
is found. ie. The buffer will still be filled up with replies from other
polls!
This is excactly the same issue I experienced today with the I2P "BenQ
SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if
delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow
messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me....
(especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both
the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

With respect, I have to disagree.

1. Sizing the input buffer to match the expected string length is half of the solution for this problem and good coding practice. This is not just a hack or workaround, it is essential.
If the expected string is 300 bytes long, but the input buffer is only 255 wide, an error will be returned.
However, if the buffer is sized to 350 and the same 300 characters comes in, no error is returned. Both statements above assume that the Buffer_Input is empty when the data is received which brings me to #2.

2. Since a Buffer_Input constantly appends new data to any that was received before, it is easy to see how data that is already processed but not removed could cause the buffer to be full (or full enough that an incoming data frame wont fit completely in the remaining space) when new data arrives.
Wiping the slate clean after each complete frame of data is received is not merely a workaround, it is good practice that will improve reliability.
This is why I do not parse against the Buffer_Input directly. Instead, I make a copy of a complete data frame into a temp variable and immediately clear the Buffer_Input.
Again, clearing the input buffer is not just some sort of hack or work around, it?€?s the right thing to do.

3. If, for some reason, there is an aversion to clearing buffers then use a String_Input instead. Disadvantage here is that this cannot be larger than 255 chars.
Upside is that you never have to remember to clear the input as it will clear itself each time data is received.


All of that aside, you all are right that I2P modules should not suffer from these issues.


Tray


From: Stig
Sent: Friday, August 10, 2012 6:14 AM
To: Crestron@...
Subject: [Crestron] Re: Error msg. Buffer Input overflow in S+ for Panasonic PT-AE4000U


Maybe I'm overlooking something here, but I really can't see how increasing the buffer can make the overflow msg. disappear.
A Clearbuffer can accomplish it, if it is placed right, but this is suggested only as a workaround on the real issue.

If you take a look at the code in the simpl+ module, it will Remove characters from the buffer ONLY if: Lamp_Requested is 1 AND ETX("&#92;x03") is found. ie. The buffer will still be filled up with replies from other polls!
This is excactly the same issue I experienced today with the I2P "BenQ SP920 v1.0.umc with BenQ SP920 v1.0 Processor.usp"
This module will also start Removing chr's from buffer ONLY if delimter+Lampresponse is present,
otherwise buffer get filled up to maxbufsize then gulping out overflow messages...

Had to rewrite both pollroutine + simpl+, and this really annoyes me.... (especially on a Friday afternoon. Grrr)

Back to the OP's question "What should I do?" the answer is: Rewrite both the pollroutine & the lamp hours module.

IMHO We should expect I2P modules to be better written than this.

-Stig

--- In mailto:Crestron%40yahoogroups.com, Rafael Costa <rafaelg.costa@> wrote:

Hello,
I??m controlling a Panasonic projector PT-AE4000U with CresDB module
for PT-AE1000U (Panansonic Lamp Hours v1.0) and it??s working fine.
Even so, I am receiving this error message -> "Error:
splusmanagerapp.exe [App 1] # 21:01:28 8-08-2012 # Module
S-5.1.1:S-2.4 : Panansonic_Lamp_Hours_v1_1 at line 136: Buffer Input
overflow. New = 260, Max = 255"
What should I do, change the "BUFFER_INPUT From_Device$[255];"
parameter to [260], is it possible?

Here is the S+ part:
LINE 44 DIGITAL_INPUT Lamp_Requested;
LINE 47 BUFFER_INPUT From_Device$[255];

LINE 133 change From_Device$
LINE 134 {
LINE 135 // Lamp hours are of the form "&#92;x02####&#92;x03"
LINE 136 if(iBusyFlag = 0 && Lamp_Requested = 1) // if not busy
processing and it is a valid lamp request
LINE 137 {
LINE 138 iBusyFlag = 1; // set busy to avoid re-entry into parser
LINE 139 while(find("&#92;x03", From_Device$) > 0 ) // look for the
ETX during a Lamp Request
LINE 140 {
LINE 141 sTemp$ = remove("&#92;x03", From_Device$); // build the
string
LINE 142 if (find ("ER401", sTemp$) = 0 && Len(sTemp$) = 6)
// Skip errors and unwanted strings
LINE 143 {
LINE 144 Lamp_Hours = ATOI(mid(sTemp$,2,4)); // set
lamp hours
LINE 145 }
LINE 146 }
LINE 147 iBusyFlag = 0; // clear busy
LINE 148 }
LINE 149 }

PMC3+ with firmware 1.005.0008 and all programs and database up to date.

Thank??s in advance,
Rafael Costa

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

Hi Guys,

I was wondering if you guys can shed some light on DRAM Symbol, might sound like a dumb question. What happens if I put 1 on both store and recall while the system is running? does it start acting like a buffer? what i am trying to acoomplish is I have a lutron system which is so outdated that it works on relays. they have 4 presets thus 4 relays. I want to give them the ability to assign any of those presets to any mode (VC, AC, Presentation etc) in tools menu.

Any insignt would be great.

As you say, the color commands don't exist on the 922 symbol. I have not really missed them, though, as you can use the cursor keys to select pretty much anything on the screen.

I've got one Hopper and one Joey(who comes up with these names!), and the whole system has a bit of a rough feel, with some of the features supposedly coming in future releases. Hopefully they will simplify the GUI somewhat, as my wife was complaining about all the options that are presented when setting up a recording.

From: Crestron@... [mailto:Crestron@...] On Behalf Of adks1010
Sent: Friday, August 10, 2012 8:43 AM
To: Crestron@...
Subject: [Crestron] Re: Dish Network Hopper2000



Great, I will give that a shot. What did you end up doing for the color commands (red, yellow, green, blue)?

I don't see those on the 922 driver but they are on the remote and am unsure how vital these are to the interface. Thanks for the quick reply.

--- In Crestron@...<mailto:Crestron%40yahoogroups.com>, Andrew Yalowitz <andrewy@<mailto:andrewy@>> wrote:

I just got a Hopper, and the codes were the same as the 922. The unit has some quirks, for sure, I feel like a beta tester.

From: Crestron@...<mailto:Crestron%40yahoogroups.com> [mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>] On Behalf Of adks1010
Sent: Friday, August 10, 2012 8:06 AM
To: Crestron@...<mailto:Crestron%40yahoogroups.com>
Subject: [Crestron] Re: Dish Network Hopper2000



Were you able to successfully learn the codes? Getting ready to install one and don't seem to see the codes anywhere. Thanks.

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "bradgathers" <almostastud@<mailto:almostastud@>> wrote:

Does anyone have the ir codes for the hopper yet , and willing to share?

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "DougG" <doug1369@> wrote:

Any luck learning this, the remote that came with my hopper is rf only, no switch in the remote battery compartment

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "weddellkw" <weddellkw@> wrote:

The Hopper was loose in NOLA all weekend:


--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "cyberbri24" <cyberbri24@> wrote:

Isn't it pronounced, " The Hoppa"? hahaha

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "KimberLee Mcginnis" <k_mc@> wrote:

Hi, Y'all,

Just to update you guys on this post. The Hopper remote has a switch in the battery compartment to switch the remote to IR. I will learn the remote for all and post it when I get back on site.

FYI, Kim

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, "KimberLee Mcginnis" <k_mc@> wrote:

Yes, this is a new box from EchoStar, . Whole new remote and interface. It's always something to screw things up. The setup says it can do both IR and UHF. No unit codes like the old ones. Just says IR enable and disable in the menu. I'll give them a call and see what they can do for us and let you all know. I'm sure I'm not the only one out there who will be needing the info soon.

--- In Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron%40yahoogroups.com>, Jon Spackman <fueler1@> wrote:

Sorry, just saw you said you already tried them.

If you press menu, menu on the dish remote. Does it have an IR address? Maybe default is not address 1. I have driver for 1,3,and,5 if that helps.

Jon

Sent from my iPad

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

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

Thanks for the comments.

My post was a little warning not to get carried away with the cool, expensive, tech - it's often the really mundane stuff that hooks people because it enhances their life much more than an angel-supported plasma. It's easy to get carried away and actually miss the idea that the tech has to complement the user's life and make it better - it's usually something to do with heating, lighting or security and rarely to do with having the latest and greatest mechanised plasma screen.

Your example of the pressure pads is one we've used in the past - so the homeowner would step out of bed between certain hours (at night essentially) and it would bring on the bathroom lights at a low-level so they could find their way to the WC etc. You could certainly utilise the mats further to make coffee etc. if the time is between certain hours (let's say between 6 and 8 am).

We all work with some of the very wealthiest, smartest individuals in the world - and they will be good at spotting someone just suggesting stuff because it is lots of money etc. - but find the things that irritate them, solve those issues for them and you'll be in a much more trusted position to suggest the expensive, show-off toys.

--- In Crestron@... , "Mark W" <weldywire@> wrote:

Sorry to hijack with an off-post but I just wanted to thank Marcus for hi comment...

Original reply:
[I'm sure that we've all had a few clients like this over the years and I have
found that the key is not bombarding them with dozens of ideas and concepts
(that is the second stage).

Just find the ONE thing that they don't know that they NEED in their life. Talk
to them, find out their passions, their concerns. Something will stand out -
take that and elaborate on the concept.

It might be something really simple and mundane to us, something to do with
lighting or heating for example, something that's bugged him his whole life.
Solve that issue for him, and he'll suddenly trust you a lot more when you
suggest the 103 inch plasmas in every room or whatever!

Easier said than done - but find the hook and run with it.]

...exactly


It isnt about loading a house with 60" plasmas that float down from the ceiling on the wings of porcelein skinned angels(the 'awe'(sp?) factor).Its about using the automation to suit the needs(and yes wants as well) of the client. Taking the time to 'listen' to what they do during the day,the 'activities',the 'schedules' their habits and simplifying it for them with automation.

Marcus, if I was consumer and you sat down and listened to how my life spins and what you could do for me to take some weight off,I would let you sell me on plasmas mounted into the side wall of my pool with a trained dolphin to harmonize serial signals through echo location to change the channels...


...as long as I can have a Psi mat next to my bed so when I wake up and my feet hit the floor, the light in my bathroom ramps up,coffee pot starts(lets be honest,we dont get out of bed EVERYDAY at the SAME time and my coffee pot isnt smart,hence the pressure mat) and the shower starts at a preset mix of scalding hot and insanely hot.Thats it,Im simple LOL

Marcus, once again thank you for the great words and I hope that others will follow your lead.

Can anyone give me a compelling reason to spend extra money on the 3-series card frame and cards when I can get the same features in a slaved CP2e? Need to add Com, IR and relays to an MC3 and a Cresnet slaved CP2e seems like a pretty solid choice for less money.

Heath