Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Crestron
- Messages
Search
|
Re: Newbish serial questions...
Chip
For MSPs - while there are other uses, it is primarily handy if you have a touch panel that ever goes offline in the case of Ethernet, or any wireless panel, or Xpanels. By putting a signal onto an MSP as well as a touch panel definition, you're ensuring that if/when the touch panel comes back online, the last string that was sent to it will be refreshed. (Even if that string was sent while the panel was offline)
toggle quoted message
Show quoted text
Many touch panels include a permanent string size definition in SIMPL Windows now, but since there are also many that *don't*, I wind up using MSPs anyway by default. Now - if you have a touch panel that is awake and online and you believe you're sending text to it and that text doesn't appear - then you have other issues. Time to fire up debugger and really focus on what is going to that serial join... Analog to Serial - this symbol expects you to provide individual *characters* to build a string. If you have an analog signal that can go from 0 to anything larger than 9 and you're trying to display the value on a touch panel - then what you have won't do it. (Not to mention that an analog value in the range 0-9 needs to be transposed to the ASCII chart's equivalent value in order for even a single character to appear as text) Easiest solution here, if you're just trying to display a simple number, is to draw a Digital Gauge object on your page and just supply the analog value to the touch panel. If you absolutely want that value displayed as text via serial join, you need to do a conversion. Quickest way is using S+, where a one-line S+ program can use the S+ function "ITOA" to convert an analog value to ASCII text. There are other approaches, depending on how much time you want to spend on it. For something like projector lamp hours that won't change any more often than once an hour, I'd just go with the S+ approach. (Assuming you can't use the digital gauge for some reason) - Chip --- In Crestron@..., "jmacd2918" <jmacd2918@...> wrote:
|
|
Re: Newbish serial questions...
Serials are transient by default, as you said, only existing at the moment
toggle quoted message
Show quoted text
they change. If you send one to a touchpanel, it will display it "permanently" until the panel reboots. When it reconnects, if the signal wasn't permanent, there won't be any data to send to the panel until the signal changes again. Connecting it to a Make String Permanent (MSP) marks it as permanent so its value is retained by the program. Note that almost all the touchpanel symbols automatically make all of their serial signals permanent, that's why there's a parameter for string size on the touchpanel symbol itself. One notable exception is the XPanel, along with some older panels you're not likely to run into. MSP also affects signal propagation through crosspoints and ABUFs in the same way: a changed signal always propagates. After changing, though, if a crosspoint gets connected or an ABUF enabled, the signal can only propagate if it's marked permanent. Analog to Serial builds a string up from individual bytes and static string parts. If you wanted to use it, you would need 4 or so analog inputs, each between 0x30 and 0x39 to indicate an ASCII digit. The simplest way to show lamp hours on the TP is to just leave the value as an analog and use an Analog Gauge on the touchpanel to display it. If you really want it as serial text for some reason, you can use DIVMOD, ASCALEL, and ATOS as described above to build up a string, or build a tiny SIMPL+ module to use ITOA() or MAKESTRING() to do it for you. Be sure to read the help files on the symbols (like Analog to Serial) as the behavior is not always what you would expect. The help files may be confusing, but they are accurate and sometimes contain useful examples. On Thu, Aug 15, 2013 at 11:21 AM, jmacd2918 <jmacd2918@...> wrote:
I'm having issues/questions with a few serial items in a current project, --
Jeremy Weatherford |
|
Re: Newbish serial questions...
jmacd2918
Ok, changed the trigger and now I get something. I think I just need to find the right format because a value of 1076d comes up as either 3 or 4 on 0d and 256d. Back to the help file
toggle quoted message
Show quoted text
--- In Crestron@..., "jmacd2918" <jmacd2918@...> wrote:
|
|
Re: Comparing VTPro projects
Wow Chip, you're easily satisfied.
I'm disappointed with my 1920x1080 17" laptop and 1920x1200 24" monitor and am looking for a 2560x1600 30" for a decent price ... I'm doing TSW-1050s as we speak and I can barely see all my tools at 1920x1080 :( On 2013-08-15, at 7:53 AM, "Chip" <cfm@...> wrote:
[Non-text portions of this message have been removed] |
|
Re: NVS 200 PTZ Control
Chip
Wow - and that's an I2P module that does that????
toggle quoted message
Show quoted text
- Chip --- In Crestron@..., "jaeger_pdigm" <fasteddy@...> wrote:
|
|
Newbish serial questions...
jmacd2918
I'm having issues/questions with a few serial items in a current project, my first "big" one.
First one, "make string permanent". Can someone give me a better explanation than what is on Crestron tutorials? Where would one use this? I'm mainly concerned with feedback making it to the touch panel/xpanel, some serial feedback seems to make it, some doesn't. Could the transient nature of serial be the culprit? Should I, as a matter of practice, make all serial feedback to the touch panel permanent? Second one, analog to serial. I've never used this symbol before, so I'm not sure if I'm doing this correct. I'm trying to convert analog projector lamp hours to serial because I'm hoping to display indirect text and use a digital signal to change indicator color when lamp hours reach a certain threshold (that part works). What doesn't work is the analog to serial conversion. Here is what I have: <trig>1 <ain1>my lamp hours analog (this same signal is working elsewhere) <out$> out to touchpanel (I've tried it with and without msp) <format>256d <string1>blank (also tried ") When I look at the $out signal in debugger, all I get is \x00. I'm thinking maybe I need a different format or trigger?? Any ideas? Sorry if I'm missing something simpl here (lame pun intended). Thanks -Jeff |
|
Re: Complaints
John,
toggle quoted message
Show quoted text
I think all of us understand that this will be a long process. The major frustrations seem to come out of miscommunications with marketing -- for instance, you just said "Studio [is] probably not of any interest to this group". Yet only a few months ago, CTI changed all their classes to be Studio only, completely dumping the "old stuff", and marketing is heavily pushing use of Studio saying how much development time it's going to save. Fortunately CTI went back to the "old stuff" classes AFAIK, but the point remains that the message from Crestron is very thoroughly mixed. I'm not ready to jump onboard with Core3 graphics at this point. I've heard all the arguments pro and con, and it looks a little too bleeding edge for what we're doing right now. That's fine with me. We stay a few firmware revisions behind what Crestron considers "stable" as well. I'd rather deal with known "known issues" than unknown "known issues". What's not fine with me is Crestron discontinuing "Core2" panels and pushing everything to be Core3 only. You have something that works, you need to keep supporting it (both in engineering AND with marketing AND tech support) until there's a viable replacement for it. Beta-testing stuff is great, and it needs to happen, but not involuntarily. On Thu, Aug 15, 2013 at 7:57 AM, John Pavlik <jpavlik@...> wrote:
Sounds like I'd better show up at Master's class this year - because none --
Jeremy Weatherford |
|
Re: NVS 200 PTZ Control
Hi Artur,
toggle quoted message
Show quoted text
We tried using NVS-200 RS-485 for camera control a few months back, and ended up ditching that idea and connecting the cameras straight to control processors. First of all, you'll find that the IP table entry will always show up as 'offline', even when the communications are alive and well. This is due to the way the Crestron module communicates with the NVS-200; it uses simpl+ direct sockets rather than traditional CIP. The IP table entry is not used to establish a CIP connection, but is simply parsed by the simpl+ module to determine the IP address of the NVS. It's an odd use of the IP table to be sure. The real show stopper for us was that the communication with the NVS-200 simply wasn't reliable. It kept disconnecting at random intervals (and for long periods of time), and we'd get piles of "array out of bounds" errors on the processor. This was on a 3-series processor, so Chip's recent revelation about what happens with out-of-bounds errors on 3-series processors might explain some of the problems. Ultimately, just hooking the camera up to the control processor was the right answer for us. - Edward --- In Crestron@..., Artur Zabludovsky <artur.triton@...> wrote:
|
|
Re: Complaints
Chip
Really nicely put, John - thanks! And yes, seeing you at masters would be great!
--- In Crestron@..., John Pavlik <jpavlik@...> wrote: - I lost track of who updated the splash screens in the software but I thought that was classic. I still think mine would have been the best, though it never got past the "conceptual" phase. :) KAD's were awesome... "Y U No Go Away?!?" - Chip |
|
Re: Comparing VTPro projects
Chip
I'm not hurting for real estate - main display is a nice 1920x1080 unit, and I have a 1680x1050 to plug in and extend to when I need it. (And yes, I've had VTPro stretched across both a few times)
toggle quoted message
Show quoted text
Unfortunately the problem has nothing to do with available screen space... - Chip --- In Crestron@..., Nick Mitchell <nick@...> wrote:
|
|
Re: Complaints
Seth Olle
Thank you John. We appreciate it.
I think most of us are in the same boat, gave up completely on studio, frustrated beyond believe with the TSW panels and just hoping for fixes. It does seem the feedback to what is going on in labs is lacking or possibly we are just not seeing it. Personally I gave up on labs. For now I guess patience is our only option, screaming no longer works. We do appreciate it you listening though. From: John Pavlik <jpavlik@...<mailto:jpavlik@...>> Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>> Date: Thursday, August 15, 2013 7:57 AM To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>> Subject: RE: [Crestron] Re: Complaints Sounds like I'd better show up at Master's class this year - because none of that feedback made it back to me. Look, we can't do everything and we can't do it all immediately. And yes, inertia sometimes comes into play. The bottom line is that Fred and I do very much care what you have to say and please don't stop telling us what you want and need. In a lot of cases of course, everyone wants something different and so "make a product that is this" sorts of comments are good but of course will take the longest to gel. In other cases, there may be infrastructure shifts that we've made (and in some cases those shifts are still looking years down the road) and so the request is backtracking from the bigger picture. We have made a lot of changes in engineering over the last year to improve quality and change some of the direction - but it takes months and months for those efforts to show up at your doorstep. To address a few things that I've seen recently... - I lost track of who updated the splash screens in the software but I thought that was classic. I am sorry that it was done out of frustration but thanks for giving me a chuckle. - No engineering resources were harmed in updating the icons. Frankly, I was surprised as you were to see them changed. That doesn't go through Architecture review! - Rebooting the TSW nightly is a stopgap. Creating an embedded product these days is much more complicated than it was years ago and has all sorts of operating system and supplier nuances (and legalities on source code, etc). But we have been actively pursuing solutions for some time now. I am a frustrated as you are that we are still doing this. - Crestron Studio - well, I think the answer is that it isn't ready for anybody on this forum. I'll be honest, my team doesn't use it either. But as someone pointed out, if we don't get the feedback from everyone here it will never be what you want. But, the database thing has been well discussed and there is agreement that what is there is not appropriate for what many of you are doing. So, there will be changes. But not soon enough - that nasty priority thing again. The immediate goal it to improve upon on the program generation aspects of the system to allow more automatic system generation. I wouldn't call it System Builder but maybe System Builder re-imagined, where logic is generated but not untouchable, and customizations and mix and match code really work. Probably not of any interest to this group, but we need it in the market as a whole. - Meanwhile, we have been investing heavily in SIMPL Windows and VTPro. For example, SIMPL Windows is going to be getting the automatic CED File management that it so very sorely needs. - And for those about to jump on why do we even have CED files, I do have a skunk works project to try and produce at least a flat view dpad and number pad. Haven't quite figured out the best way to release it yet. So, while we don't necessarily share back what we've heard and what we are doing about it, we do listen and it does cause change. Probably not as fast as you want it and probably not everything you want but don't stop sharing. I want Crestron to be the best that it can be. And to do that we need the continued support of all of you. You all are a big part of what Crestron has become and I need you to continue to do that. I know its frustrating at times. As I lie awake at 3am staring at the ceiling I think about these things too! But I think together we can continue to make strives and be a mutual success. I will see many of you at CEDIA so that you can complain in person! And I think most of you know how to get it touch with me one way or another so feel free. John Pavlik Crestron Electronics, Inc. Director, Architecture & Design This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. |
|
Re: Comparing VTPro projects
I've only needed to do this a few times but I switched my monitor
toggle quoted message
Show quoted text
configuration from multiple desktops to stretch the first monitor across the second so VTPro takes up both screens and then I had the real estate to open up all the pages I wanted at the same time. I dont know if all video cards support stretch but it was a function of windows so maybe its more dependant on the version of windows. Im pretty sure I did it on windows xp and 7 tho. Nick Sent with AquaMail for Android On August 14, 2013 10:03:16 AM "Chip" <cfm@...> wrote:
|
|
Re: Wow Prodigy
The. Issue you'll have with a PMC3 is that it can only run one program (unlike the MC3 that can run 10). You'll have to choose either SIMPL or D3, but not both. (At the end of the day D3 generates a SIMPL program anyway)
The only thing I'm not sure about is if D3 will let you specify a PMC3 as the control processor. If not you may be able to define the processor as an MC3 and load the program manually. Never tried but the PMC3 and MC3 are identical hardware wise. It's only a firmware limitation that prevents running 10 programs. On 2013-08-15, at 6:45 AM, Nick Mitchell <nick@...> wrote: Excellent. Thats exactly what I wanted to hear. I've never dealt with [Non-text portions of this message have been removed] |
|
Re: Complaints
Sounds like I'd better show up at Master's class this year - because none of that feedback made it back to me.
Look, we can't do everything and we can't do it all immediately. And yes, inertia sometimes comes into play. The bottom line is that Fred and I do very much care what you have to say and please don't stop telling us what you want and need. In a lot of cases of course, everyone wants something different and so "make a product that is this" sorts of comments are good but of course will take the longest to gel. In other cases, there may be infrastructure shifts that we've made (and in some cases those shifts are still looking years down the road) and so the request is backtracking from the bigger picture. We have made a lot of changes in engineering over the last year to improve quality and change some of the direction - but it takes months and months for those efforts to show up at your doorstep. To address a few things that I've seen recently... - I lost track of who updated the splash screens in the software but I thought that was classic. I am sorry that it was done out of frustration but thanks for giving me a chuckle. - No engineering resources were harmed in updating the icons. Frankly, I was surprised as you were to see them changed. That doesn't go through Architecture review! - Rebooting the TSW nightly is a stopgap. Creating an embedded product these days is much more complicated than it was years ago and has all sorts of operating system and supplier nuances (and legalities on source code, etc). But we have been actively pursuing solutions for some time now. I am a frustrated as you are that we are still doing this. - Crestron Studio - well, I think the answer is that it isn't ready for anybody on this forum. I'll be honest, my team doesn't use it either. But as someone pointed out, if we don't get the feedback from everyone here it will never be what you want. But, the database thing has been well discussed and there is agreement that what is there is not appropriate for what many of you are doing. So, there will be changes. But not soon enough - that nasty priority thing again. The immediate goal it to improve upon on the program generation aspects of the system to allow more automatic system generation. I wouldn't call it System Builder but maybe System Builder re-imagined, where logic is generated but not untouchable, and customizations and mix and match code really work. Probably not of any interest to this group, but we need it in the market as a whole. - Meanwhile, we have been investing heavily in SIMPL Windows and VTPro. For example, SIMPL Windows is going to be getting the automatic CED File management that it so very sorely needs. - And for those about to jump on why do we even have CED files, I do have a skunk works project to try and produce at least a flat view dpad and number pad. Haven't quite figured out the best way to release it yet. So, while we don't necessarily share back what we've heard and what we are doing about it, we do listen and it does cause change. Probably not as fast as you want it and probably not everything you want but don't stop sharing. I want Crestron to be the best that it can be. And to do that we need the continued support of all of you. You all are a big part of what Crestron has become and I need you to continue to do that. I know its frustrating at times. As I lie awake at 3am staring at the ceiling I think about these things too! But I think together we can continue to make strives and be a mutual success. I will see many of you at CEDIA so that you can complain in person! And I think most of you know how to get it touch with me one way or another so feel free. John Pavlik Crestron Electronics, Inc. Director, Architecture & Design This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. |
|
Re: Problems with Carrier Infinity Module
I think the Carrier Infinity modules have been a problem for a long time. Or should I say, the Carrier Infinity control boards.
toggle quoted message
Show quoted text
Here's a thread from a couple years ago where I was able to capture some erroneous serial strings coming off the integration panel. You might try to duplicate these results, if possible. I gave up on it at the time. And another thread that didn't really go anywhere, but explains the real problem with the modules is that they aren't handling the NAK responses correctly. --- In Crestron@..., "Jeff" <jeff@...> wrote:
|
|
Re: Wow Prodigy
Excellent. Thats exactly what I wanted to hear. I've never dealt with
toggle quoted message
Show quoted text
prodigy and this is a take over job and I didnt want to have to learn systembuilder to do it. What about a pmc3, can I run a D3 lighting project on there along with my simpl program just like I typically do? Does D3 work with prodigy? Thanks for the info Stephen. Sent with AquaMail for Android On August 14, 2013 11:09:55 PM "stainbow1" <stainbow1@...> wrote:
I just did a PMC3 the other day, all Simpl. I've done a bunch of prodigy, |
|
Re: Denon AVR-X2000
Sorry, Russound MCA-C5
toggle quoted message
Show quoted text
--- In Crestron@..., "rogiervs" <rogier@...> wrote:
|
|
TCP/IP & LG Smart TV
esturiano
Hi ALL!
Can anyone control the LG Smart TV LA-series (f.e., 47LA644V) via TCP/IP (Ethernet)? I've interest only to Power OFF (because, Power ON impossible) and POWER ON/OFF feedback. COMMAND: ka 00 00\r (Power OFF) But I can't correctly connect my TCP/IP Client to the TV. I don't know port number for the connection. Port 8080 making connection Client-TV (Connect-F is high), but Client can't correct transfer/get commands/answers to the TV. What I have to do? Thanks for the help. |
Edward Wright
to navigate to use esc to dismiss