So it goes both ways I see. :)
Though buffers have their place, there are many times when buffers are so much easier than breaking out crosspoints that it makes sense to use them. It depends upon the circumstance, 'going back to buffers' is a little generic. If you're saying that people don't use crosspoints when you're connecting multiple panels to devices with all signal types in play, then I'd agree that not using crosspoints, and not even looking at them, is an issue.
toggle quoted message
Show quoted text
--- In Crestron@..., "jgreenink16" <jgreenink16@...> wrote:
I just yesterday sat with one of the other programmers here for an hour to try to standardize things here and basically got nowhere, and we're just three programmers. It drives the owner nuts, but we're programmers and almost if it goes hand in hand, have egos. I once worked at a company for just two weeks: Try telling someone who's been programming for 12 years (self taught, not a single class) that there's a better way to do things. Resentment doesn't even begin to describe it. I quit because (among other things) there was no way in hell I was going to go back to buffers after doing crosspoints.
/rant
--- In Crestron@..., Barry Newton <barry@> wrote:
You know, this really gets at programming technique which is something Crestron has always stayed out of. They offer best practices for specific situations sometimes, but overall architecture is absent. So like most programmers with experience, I have my own approach I use over and over. There are a lot of unpaid hours that went into it, but that time is recovered in being able to produce finished programs more quickly.
I suspect most programmers eventually abandon timed logic for the most part and begin thinking in terms of logic wave pulses and wave delays where that sort of thing is needed. I know I spend an unhealthy amount of time tweaking logic just to reduce the number of symbols.
I have wondered if there is interest in the community in creating a standard architecture for program design, something like an open source project. In my mind the focus would be creating an overall architecture with cut-and-paste-ready logic modules with well defined standard interfaces. There are a lot of device modules in the files section, but I haven't seen a lot other than that, and there is no standardization at all really.
Maybe most of you have too much invested in your own approaches to want to share techniques, even I'm not sure I want to do that, but it won't hurt to discuss it.
Sorry to hijack the thread.
Barry
On Apr 12, 2012, at 6:54 PM, Steve Kaudle wrote:
To some extent that's dependent on the display's in question (or more
specifically, the completeness of their control API's). Lets assume
that the displays can either be queried and/or will provide unsolicited
feedback for the current power state (off, warming, on, or cooling).
Given that, I'd write a module that would always tell me the current
power status, and if either of the display's 'warming_fb' outputs were
high, activate the subpage.
On 4/12/2012 6:32 PM, avsystemdesign wrote:
Thanks Steve,
Then how would a person create the following condition?
Display A + B can be powered up separately, but depending on what source has been selected they both may or may not need to be powered up at the same time. And here is the kicker, they both have different warm up times, and the "system is warming up" page needs to be held high during the power up cycle.
So if A takes 10s to warm up, but has been powered up at the same time as B (which takes 20s), the warm up page needs to be high for 20s.
--- In Crestron@..., Steve Kaudle<crestron@> wrote:
From a more abstract/best practices standpoint, you should try to keep
the amount of timed events (steppers, delays, one-shots, etc...) you use
to a minimum. That said, I'd bet you'd need to use a>lot< of steppers
before the burden they put on system would be perceived by the
operator. Lots of variables at play and the real world threshold will
likely vary (greatly) from system to system. Note that the previous
statement(s) should most defiantly not be translated into anything like
'stop using timed events if you want your systems to work right'.
From a logical/program flow standpoint, I prefer to avoid timed events
and build logic that is condition dependent. Example: I don't
necessarily want to send an input swap command to a projector based on a
specific amount of time having passed, but rather based on real-time
conditions like the (actual) power state and current input selection.
On 4/12/2012 5:56 PM, avsystemdesign wrote:
I know there are several ways to skin a cat in Crestron world, and I am always looking at improving and following best practices. Having said that I have a question.
Is it bad to have 2 or 3 steppers running concurrently? Depending on the device being used, I like to have a stepper handle the procedure.
For example, source is selected, stepper for projector 1 is triggered, this fires up the proj and sends down the screen, whilst indicating the system is warming up.
If a different source is selected, it might be destined for other displays, which in turn will trigger their respective steppers.
So there might be a few steppers running at the same time.
------------------------------------
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
------------------------------------
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
------------------------------------
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
|
I seem to have had more IR problems with the DVR versions than the non-DVR
ones. Gaffer's tape + a pinhole helped.
toggle quoted message
Show quoted text
On Apr 13, 2012 9:29 AM, "Heath Volmer" <hvolmer@...> wrote: The only trouble I've ever had with these is placement and type of IR
emitter. Some of them were really finicky.
Also, do you have the remote settings on "IR" instead of "RF"?
Heath Volmer
Digital Domain Systems
(303) 517-9714
On Apr 13, 2012, at 6:50 AM, Jeffrey wrote:
Has anyone had trouble getting IR control to work with a DirecTV box.
I believe the model is H20. I have tried learning commands, using crestron module so far nothing. Any help would be greatly appreciated.
Thanks
Jeff
------------------------------------
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
|
Best way to widen my programming ablility
I have been programming for a few years but have not been in a position to do it full time, I am really a lead install tech that can also program. I would like some input from the group on how to widen my programming abilities. It would seem like most of the things learned would come necessity. what i mean by that is that I learn how to program code for a specific piece of gear because I need to for a job. But what are some thing I could do to basically prep myself for upcoming needs? Any input would be appreciated.
|
Thank you for all the help, the IR emitter had to be moved a couple of inches away from the eye
________________________________
From: Jeffrey <binkyangela@...>
To: Crestron@...
Sent: Friday, April 13, 2012 7:50 AM
Subject: [Crestron] DirecTV IR Control
听
Has anyone had trouble getting IR control to work with a DirecTV box.
I believe the model is H20. I have tried learning commands, using crestron module so far nothing. Any help would be greatly appreciated.
Thanks
Jeff
|
Does anyone have an RS-232 or IP module to control this unit?
Thanks
Don
|
Re: Simple + Guru Question - Differences for IP modules between 2 and 3 series
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]
|
Re: Dish Network Hopper2000
Any luck learning this, the remote that came with my hopper is rf only, no switch in the remote battery compartment
toggle quoted message
Show quoted text
--- In Crestron@..., "weddellkw" <weddellkw@...> wrote:
The Hopper was loose in NOLA all weekend:
--- In Crestron@..., "cyberbri24" <cyberbri24@> wrote:
Isn't it pronounced, " The Hoppa"? hahaha
--- In Crestron@..., "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@..., "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@..., 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
|
Re: PTX-3 and Buffers for Hardkeys
Jesus @ Audio& Net Artist
If I have more time on a next project with this remote I will give it a tried again within SIMPL side, but this project is not in time frame to test. On Fri, Apr 13, 2012 at 11:52 AM, Tony Golden <mrgolden@...>wrote: **
I also prefer to keep stuff like this in Simpl, because it's easier to make
changes later - especially if there are multiple remotes or touchpanels.
--- On Friday, April 13, 2012 at 11:33 AM, Jeremy Weatherford wrote:
Use either one you want, there's no functional difference. I prefer buffers
personally because I'm used to hardbuttons always sending the same joins,
and when I reassign them I tend to forget about the hard button manager --
I'd rather have those differences in the code where I can see them. Stuck
in a rut, I guess...
On Fri, Apr 13, 2012 at 9:31 AM, gsusmood <audioandnetartist@...>
wrote:
Hey Guys, been working on this control, but the way I learned with
older
models or a TPS-6X for use hard keys between sources was true a buffer,
called to crestron and they told me that was the older way, with new
controls use hard button manager, am doing this right now gonna test it in
few minutes, any comments regarding this that can shine!!!
-- *Jesus Tossas* * * *Technology Architect, Audio Engineer, Programmer* * * *787-460-1223* * * Contact Info <>
|
Except there is no vcbutton command and the camera command doesn't have a for-content option in the QDX. On Fri, Apr 13, 2012 at 9:38 AM, Raph Paf <raphael.thiffault@...>wrote: **
For the content issue you need to assign the correct camera for the content
in hdx7000 the content camera is input 3, just sent those command:
vcbutton map 3\r
camera for-content 3\r
if the QDX is input 5, it would be probably these command:
vcbutton map 5\r
camera for-content 5\r
--- In Crestron@..., "stranded" <strandedyahoo@...> wrote:
Here's the scoop. To control it via RS232 you need to have a crossover
cable with pins 4 and 6 tied together on the Polycom side like so:
QDX Crestron
Pin 2 Pin 3
Pin 3 Pin 2
Pin 5 Pin 5
Pin 4 tied to Pin 6
No other pins required.
I used the VSX series crestron moodule and found that the content play
button does not work. You have to send the graphics button followed by the
input to send content. In my case it was graphics then 5. To turn off
content you send the same command. So of course you have to monitor when
content is being turned on and off with the "notify vidsourcechange"
command. The feedback to the command didn't make a lot of sense to me, but
it may be because it was a long day getting this thing working yesterday.
If you send the "camera near 1" command it will toggle the camera on and
off. It seems most of the feedback from the unit has changed so don't
expect to get much in the way of feedback from the stock modules.
Good Luck and I hope that helps
--- In Crestron@..., Mark Conde <mcjaran@> wrote:
I am � programming a QDX6000 tomorrow. I was researching the how to
control it part. TCPIP/RS232.
The only thing i found so far is the HDX9000, i was wondering if the
commands will work on it.
Have you tried that yet?
________________________________
From: Raph Paf <raphael.thiffault@>
To: Crestron@...
Sent: Thursday, April 12, 2012 8:21 AM
Subject: [Crestron] Re: Polycom QDX6000
�
Have you try if you connect you pc direct to the com port are you able
to use a console program to talk to the unit ?
Have you try to connect with telnet to check if your able to control
it ?
--- In Crestron@..., "stranded" <strandedyahoo@> wrote:
Has anyone been able to control a QDX6000? It's definitely supposed
to be RS232 controllable after firmware 4.0, but I haven't been able to get
it to work. It will not respond to anything on its com port at all. I have
set the com port for control and hooked up to the thing like any other
Polycom and no joy. I am thinking I might have a bad unit. I talked to tech
support and was told I needed a special cable as referenced in the API. we
made that cable on-site only to find out it had actually come with the
unit. The cable made no difference. Plus, according to the documentation
that cable is only for "pass thru" mode.
I'm going to call tech support again today but I was hoping someone
here could push me in the right direction.
Thanks
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
|
Re: PTX-3 and Buffers for Hardkeys
I also prefer to keep stuff like this in Simpl, because it's easier to make
changes later - especially if there are multiple remotes or touchpanels.
toggle quoted message
Show quoted text
--- On Friday, April 13, 2012 at 11:33 AM, Jeremy Weatherford wrote:
Use either one you want, there's no functional difference. I prefer buffers
personally because I'm used to hardbuttons always sending the same joins,
and when I reassign them I tend to forget about the hard button manager --
I'd rather have those differences in the code where I can see them. Stuck
in a rut, I guess...
On Fri, Apr 13, 2012 at 9:31 AM, gsusmood <audioandnetartist@...>
wrote:
Hey Guys, been working on this control, but the way I learned with older
models or a TPS-6X for use hard keys between sources was true a buffer,
called to crestron and they told me that was the older way, with new
controls use hard button manager, am doing this right now gonna test it in
few minutes, any comments regarding this that can shine!!!
|
I want to see the commands been sent from a controller, then copy those strings to use from Crestron.
You suggesting running the controller through the com ports on a processor (QM-RMC, connect A to B), and look at the traffic?
toggle quoted message
Show quoted text
--- In Crestron@..., "Raph Paf" <raphael.thiffault@...> wrote:
What do you mean ?
a nice qm-rmc :P
--- In Crestron@..., "avsystemdesign" <avsystemdesign@> wrote:
Can anyone recommend a good serial port sniffer?
|
Re: PTX-3 and Buffers for Hardkeys
Jesus @ Audio& Net Artist
Well, I just updated the PTX-3, with the hard button manage assigned the joins to proper command EX: join 10= Cable box #1. and work OK, so far, the only problem is that takes time to goo true all the pages you build for each device and assign, Crestron told me that doing it with buffer will cause sometime weird behaviors, but Hey I did it. On Fri, Apr 13, 2012 at 11:32 AM, Jeremy Weatherford <xidus.net@...>wrote: **
Use either one you want, there's no functional difference. I prefer
buffers personally because I'm used to hardbuttons always sending the
same joins, and when I reassign them I tend to forget about the hard
button manager -- I'd rather have those differences in the code where
I can see them. Stuck in a rut, I guess...
On Fri, Apr 13, 2012 at 9:31 AM, gsusmood <audioandnetartist@...>
wrote:
Hey Guys, been working on this control, but the way I learned with older models or a TPS-6X for use hard keys between sources was true a buffer,
called to crestron and they told me that was the older way, with new
controls use hard button manager, am doing this right now gonna test it in
few minutes, any comments regarding this that can shine!!!
------------------------------------
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
-- *Jesus Tossas* * * *Technology Architect, Audio Engineer, Programmer* * * *787-460-1223* * * Contact Info <> [Non-text portions of this message have been removed]
|
Re: PTX-3 and Buffers for Hardkeys
I started out using the hard button manager but have switched to buffers. I have found it makes it easier to transition between different remotes or touch-panels and not have to redo all of the code.
Nate L
toggle quoted message
Show quoted text
On Apr 13, 2012, at 9:32 AM, Jeremy Weatherford <xidus.net@...> wrote: Use either one you want, there's no functional difference. I prefer
buffers personally because I'm used to hardbuttons always sending the
same joins, and when I reassign them I tend to forget about the hard
button manager -- I'd rather have those differences in the code where
I can see them. Stuck in a rut, I guess...
On Fri, Apr 13, 2012 at 9:31 AM, gsusmood <audioandnetartist@...> wrote:
Hey Guys, been working on this control, but the way I learned with older models or a TPS-6X for use hard keys between sources was true a buffer, called to crestron and they told me that was the older way, with new controls use hard button manager, am doing this right now gonna test it in few minutes, any comments regarding this that can shine!!!
------------------------------------
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
TODAY(Beta) 鈥� Powered by Yahoo!
Funny pickup lines that actually work
Privacy Policy
|
|
|
Can anyone recommend a good serial port sniffer?
|
Re: PTX-3 and Buffers for Hardkeys
Use either one you want, there's no functional difference. I prefer buffers personally because I'm used to hardbuttons always sending the same joins, and when I reassign them I tend to forget about the hard button manager -- I'd rather have those differences in the code where I can see them. Stuck in a rut, I guess... On Fri, Apr 13, 2012 at 9:31 AM, gsusmood <audioandnetartist@...> wrote: Hey Guys, been working on this control, but the way I learned with older models or a TPS-6X for use hard keys between sources was true a buffer, called to crestron and they told me that was the older way, with new controls use hard button manager, am doing this right now gonna test it in few minutes, any comments regarding this that can shine!!!
------------------------------------
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
|
Simple + Guru Question - Differences for IP modules between 2 and 3 series
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
|
For the content issue you need to assign the correct camera for the content
in hdx7000 the content camera is input 3, just sent those command:
vcbutton map 3\r
camera for-content 3\r
if the QDX is input 5, it would be probably these command:
vcbutton map 5\r
camera for-content 5\r
toggle quoted message
Show quoted text
--- In Crestron@..., "stranded" <strandedyahoo@...> wrote:
Here's the scoop. To control it via RS232 you need to have a crossover cable with pins 4 and 6 tied together on the Polycom side like so:
QDX Crestron
Pin 2 Pin 3
Pin 3 Pin 2
Pin 5 Pin 5
Pin 4 tied to Pin 6
No other pins required.
I used the VSX series crestron moodule and found that the content play button does not work. You have to send the graphics button followed by the input to send content. In my case it was graphics then 5. To turn off content you send the same command. So of course you have to monitor when content is being turned on and off with the "notify vidsourcechange" command. The feedback to the command didn't make a lot of sense to me, but it may be because it was a long day getting this thing working yesterday. If you send the "camera near 1" command it will toggle the camera on and off. It seems most of the feedback from the unit has changed so don't expect to get much in the way of feedback from the stock modules.
Good Luck and I hope that helps
--- In Crestron@..., Mark Conde <mcjaran@> wrote:
I am 脗听programming a QDX6000 tomorrow. I was researching the how to control it part. TCPIP/RS232.
The only thing i found so far is the HDX9000, i was wondering if the commands will work on it.
Have you tried that yet?
________________________________
From: Raph Paf <raphael.thiffault@>
To: Crestron@...
Sent: Thursday, April 12, 2012 8:21 AM
Subject: [Crestron] Re: Polycom QDX6000
脗听
Have you try if you connect you pc direct to the com port are you able to use a console program to talk to the unit ?
Have you try to connect with telnet to check if your able to control it ?
--- In Crestron@..., "stranded" <strandedyahoo@> wrote:
Has anyone been able to control a QDX6000? It's definitely supposed to be RS232 controllable after firmware 4.0, but I haven't been able to get it to work. It will not respond to anything on its com port at all. I have set the com port for control and hooked up to the thing like any other Polycom and no joy. I am thinking I might have a bad unit. I talked to tech support and was told I needed a special cable as referenced in the API. we made that cable on-site only to find out it had actually come with the unit. The cable made no difference. Plus, according to the documentation that cable is only for "pass thru" mode.
I'm going to call tech support again today but I was hoping someone here could push me in the right direction.
Thanks
|
Re: Beyerdynamic MCW-D 50-9 control unit module?
They have a conference software suite to control the microphone system, which can link up by either com or lan.
Is there a way I could see what commands are being sent? That way it would help my figure out which strings I need and which ones I don't.
toggle quoted message
Show quoted text
--- In Crestron@..., "avsystemdesign" <avsystemdesign@...> wrote:
I need to be able to put the unit into the following modes: (normal, push to talk, voice on activation & request to talk - with a next speaker button).
I have read through the horrible documentation and think the below is what I need, but still having a tough time figuring out how to write this out in order to achieve the above.
If anyone has worked with one of these units and cares to throw a dog a bone here, that would be much appreciated.
set_mu_global(a,b,c,d,e,f,g,h,i,j,k,l,m,n)
a 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
b 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
c 鈥� {0..50} 鈥� voice activation sensitivity (max sensitivity = 0);
d 鈥� {0..255} 鈥� MU hold time;
e 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
f 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
g 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
h 鈥� {0..255}:
鈥� low nibble = allocation mode (1 鈥� normal, 2 鈥� PTT, 3 -VOAC) ;
鈥� bit 4 = manual power off enabled (1) / disabled (0); j 鈥� {0..8} 鈥� priority mode;
j 鈥� {} 鈥� reserved / unused (write nothing 鈥� next comma);
k 鈥� {on, off} 鈥� enable / disable the auto-lock feature of the MU;
l 鈥� {on, off} 鈥� enable / disable override;
m 鈥� {0..9} 鈥� NOM;
n 鈥� {on, off} 鈥� enable / disable NOM mode;
This command changes the global parameters of the MU.Considering the large number of reserved / unused parameters this command will be sent as:
set_mu_global(,,c,d,,,,h,i,,k,l,m,n)
--- In Crestron@..., "avsystemdesign" <avsystemdesign@> wrote:
Not on their website, not on Crestron's website. The API is not very clear.
Anyone programmed one of these before?
--- In Crestron@..., "avsystemdesign" <avsystemdesign@> wrote:
Does anyone know if there is a module for the Beyerdynamic MCW-D 50-9?
|
Never program a QDX Unit but i've done some hdx7000 thru tcp/ip with success. Using port 24 work great. (Need to sent the password to be able to control it via tcp)
toggle quoted message
Show quoted text
--- In Crestron@..., Mark Conde <mcjaran@...> wrote:
I am 脗听programming a QDX6000 tomorrow. I was researching the how to control it part. TCPIP/RS232.
The only thing i found so far is the HDX9000, i was wondering if the commands will work on it.
Have you tried that yet?
________________________________
From: Raph Paf <raphael.thiffault@...>
To: Crestron@...
Sent: Thursday, April 12, 2012 8:21 AM
Subject: [Crestron] Re: Polycom QDX6000
脗听
Have you try if you connect you pc direct to the com port are you able to use a console program to talk to the unit ?
Have you try to connect with telnet to check if your able to control it ?
--- In Crestron@..., "stranded" <strandedyahoo@> wrote:
Has anyone been able to control a QDX6000? It's definitely supposed to be RS232 controllable after firmware 4.0, but I haven't been able to get it to work. It will not respond to anything on its com port at all. I have set the com port for control and hooked up to the thing like any other Polycom and no joy. I am thinking I might have a bad unit. I talked to tech support and was told I needed a special cable as referenced in the API. we made that cable on-site only to find out it had actually come with the unit. The cable made no difference. Plus, according to the documentation that cable is only for "pass thru" mode.
I'm going to call tech support again today but I was hoping someone here could push me in the right direction.
Thanks
[Non-text portions of this message have been removed]
|
