|
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
|
If I can add to the "be more resourceful"
Every programmer should have or have access to an IR Learner whenever they're programming, onsite or off.
The new learner is tiny and cheap, and there's really no excuse, IMO, not to just have one in your laptop bag. Sure, learning remotes is not the most glorious thing -- when necessary I typically take it/them back to the hotel with me and learn with my feet up on a coffee table watching TV -- but it's usually a heck of a lot faster & more reliable than waiting for someone to reply with something that "might" "be close"
Yeah, sometimes the remote gets lost but the majority of the time it's right there with the manuals...
Lincoln
--
Lincoln King-Cliby, CTS
Sr. Systems Architect | Crestron Certified Master Programmer (Silver)
ControlWorks Consulting, LLC
V: 440.449.1100 x1107 | F: 440.449.1106 | I:
Crestron Services Provider
toggle quoted message
Show quoted text
-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Nathan Hesson
Sent: Monday, May 20, 2013 9:25 AM
To: crestron
Subject: [Crestron] Helpful hints to not get flamed
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
------------------------------------
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
|
Wow, I missed the fun post. Yeah, cert specific questions are touchy, I am more upset with crestron for giving more time to get the test done and using the old test with passing it out before some people made it to cert class. Isn't that part of the test is to meet a deadline?
The repetitive ir/SB questions get a little annoying (I wish they would stop), and the cert specific questions I may read and will try to help, but there is NO WAY I will give you a direct answer to solve your problem. I had several people point me in the right direction and I would figure it out. Learning takes time and mistakes, but you have to put the effort in. No one is going to know all the answers, but you do need to be able to take a ball and run with it. I mean I still ask you guys questions because many of you know a lot more than I do. So all I can say is thanks for helping and I will try to do the same.
It is also good to carry an old URC remote with you to learn codes from. I carry an mx-700. Old/cheap but if I have to have codes and it is not in the Crestron, RTI database the I have a fall back.
toggle quoted message
Show quoted text
--- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
If I can add to the "be more resourceful"
Every programmer should have or have access to an IR Learner whenever they're programming, onsite or off.
The new learner is tiny and cheap, and there's really no excuse, IMO, not to just have one in your laptop bag. Sure, learning remotes is not the most glorious thing -- when necessary I typically take it/them back to the hotel with me and learn with my feet up on a coffee table watching TV -- but it's usually a heck of a lot faster & more reliable than waiting for someone to reply with something that "might" "be close"
Yeah, sometimes the remote gets lost but the majority of the time it's right there with the manuals...
Lincoln
--
Lincoln King-Cliby, CTS
Sr. Systems Architect | Crestron Certified Master Programmer (Silver)
ControlWorks Consulting, LLC
V: 440.449.1100 x1107 | F: 440.449.1106 | I:
Crestron Services Provider
-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Nathan Hesson
Sent: Monday, May 20, 2013 9:25 AM
To: crestron
Subject: [Crestron] Helpful hints to not get flamed
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
[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
|
This is a good thread, should be a "sticky" or a "read, inwardly digest and be prepared to answer questions on it" for all new members. It's always worth trawling the manufacturers "Support" or "Custom Installation" (if they have one) sections as the stuff tucked away there usually doesn't turn up on any search engine Pioneer, Denon, Marantz, Arcam, Naim, Linn�.etc etc etc all rock in this respect). I have also had success contacting the supplier to ask for information (a driver, a protocol document�). Being one of those nasty unwashed diy types and knowing what a valuable resource this group is and how unwise it is to p1ss off the cognescenti here, I am super cautious about asking the dumb question. The odd one slips through but it probably grates with the likes of me more than others when I see the lazy questions being asked. I am thinking "oh no, don't ask them that!!!!" The last thing we need is for you guys to take you bat and ball and go elsewhere�.. On 20 May 2013, at 15:08, eagrubbs <eagrubbs@...> wrote: Wow, I missed the fun post. Yeah, cert specific questions are touchy, I am more upset with crestron for giving more time to get the test done and using the old test with passing it out before some people made it to cert class. Isn't that part of the test is to meet a deadline?
The repetitive ir/SB questions get a little annoying (I wish they would stop), and the cert specific questions I may read and will try to help, but there is NO WAY I will give you a direct answer to solve your problem. I had several people point me in the right direction and I would figure it out. Learning takes time and mistakes, but you have to put the effort in. No one is going to know all the answers, but you do need to be able to take a ball and run with it. I mean I still ask you guys questions because many of you know a lot more than I do. So all I can say is thanks for helping and I will try to do the same.
It is also good to carry an old URC remote with you to learn codes from. I carry an mx-700. Old/cheap but if I have to have codes and it is not in the Crestron, RTI database the I have a fall back.
--- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
If I can add to the "be more resourceful"
Every programmer should have or have access to an IR Learner whenever they're programming, onsite or off.
The new learner is tiny and cheap, and there's really no excuse, IMO, not to just have one in your laptop bag. Sure, learning remotes is not the most glorious thing -- when necessary I typically take it/them back to the hotel with me and learn with my feet up on a coffee table watching TV -- but it's usually a heck of a lot faster & more reliable than waiting for someone to reply with something that "might" "be close"
Yeah, sometimes the remote gets lost but the majority of the time it's right there with the manuals...
Lincoln
--
Lincoln King-Cliby, CTS
Sr. Systems Architect | Crestron Certified Master Programmer (Silver)
ControlWorks Consulting, LLC
V: 440.449.1100 x1107 | F: 440.449.1106 | I:
Crestron Services Provider
-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Nathan Hesson
Sent: Monday, May 20, 2013 9:25 AM
To: crestron
Subject: [Crestron] Helpful hints to not get flamed
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
[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
[Non-text portions of this message have been removed]
|
+1 Very well said.
Especially #2 - I remember even before there was a Remote Central, using a Crestron learner and pulling discreet power codes off of a Sony receiver remote for every Sony device. Allot of trial and error but it was worth it.
TB
toggle quoted message
Show quoted text
--- In Crestron@..., Nathan Hesson <nhesson@...> wrote:
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
|
I had the Pronto software installed for quite a while, was handy to grab the hex for Deal during that 'era'.
toggle quoted message
Show quoted text
--- In Crestron@..., "Ted" <ted_brincka@...> wrote:
+1 Very well said.
Especially #2 - I remember even before there was a Remote Central, using a Crestron learner and pulling discreet power codes off of a Sony receiver remote for every Sony device. Allot of trial and error but it was worth it.
TB
--- In Crestron@..., Nathan Hesson <nhesson@> wrote:
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
[Non-text portions of this message have been removed]
|
I do want to add some points here that are not only applicable to the new guys/beginners.
Never assume somebody else is in the same position as you are and by that I mean:
1) Work setup - self employed (meaning you do everything from sales to support), working at a big company with lots of programmers, just doing corporate or residential projects
2) Personal situation - might have just started his or her own business and things are tough. Remember the days, way back when, when you started on your own. Your mind is in 10 different places and you do find yourself asking stupid questions, because all you need to do it get the job done.
3) Experience - somebody might not have had a programming background, but it is not to say that they cannot become a great programmer. Let's not put them off before they've even started.
I do agree that when you read some of the posts that you can immediately see that no effort was put in to find the information, files, ext, but I also see people responding with posts that cause 20 extra unnecessary responses when a single helpful one liner could have done.
Sometimes a little more patients is all that is needed.
toggle quoted message
Show quoted text
--- In Crestron@..., "matt_rasmussen_2000" <mjrtoo@...> wrote:
I had the Pronto software installed for quite a while, was handy to grab the hex for Deal during that 'era'.
--- In Crestron@..., "Ted" <ted_brincka@> wrote:
+1 Very well said.
Especially #2 - I remember even before there was a Remote Central, using a Crestron learner and pulling discreet power codes off of a Sony receiver remote for every Sony device. Allot of trial and error but it was worth it.
TB
--- In Crestron@..., Nathan Hesson <nhesson@> wrote:
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
|
--- In Crestron@..., "Etienne" <etienne@...> wrote:
I do want to add some points here that are not only applicable to the new guys/beginners.
I do not want to add some points here, for fear of being flamed ... :) Chris K
|
I understand that finding IR codes can certainly be difficult at times. I've used MakeHex a few times to actually make the hex codes for IR devices, but that was definitely not easy and not something for newbies to try.
Had a friend of mine tell me, he used a Logitech Harmony remote (one of the cheaper ones) and programmed it for any device which was difficult to find. Then he used the Crestron IR learner to learn the IR codes he needed. He said he found discrete codes for devices he didn't even know had discrete codes and so far hasn't been stumped on any device. Haven't tried this myself yet, but certainly a handy way to get IR codes for those hard to find devices!
Chris Cates, CSP
Creative Programming Inc.
www.creativeprogramming.ca
toggle quoted message
Show quoted text
--- In Crestron@..., "matt_rasmussen_2000" <mjrtoo@...> wrote:
I had the Pronto software installed for quite a while, was handy to grab the hex for Deal during that 'era'.
--- In Crestron@..., "Ted" <ted_brincka@> wrote:
+1 Very well said.
Especially #2 - I remember even before there was a Remote Central, using a Crestron learner and pulling discreet power codes off of a Sony receiver remote for every Sony device. Allot of trial and error but it was worth it.
TB
--- In Crestron@..., Nathan Hesson <nhesson@> wrote:
I've seen some threads getting rather testy lately and I thought I would
post some helpful hints to help others avoid feeling internet wrath.
1. Do NOT post with questions or requests for help on tests. The tests mean
something. They are an indication of your skills. They are supposed to be a
measurable baseline that we ALL get judged upon. If a person gets a
certification and is undeserving of it, it tarnishes the reputation of the
certification that the rest of us have. Your certification does not just
apply to programming ability, it also has underlying implications that you
can search for information (see item 2), understand protocols, build your
own modules and IR drivers, etc...
2. Be more resourceful. There is a wealth of knowledge to be had. Search
engines do a lovely job trying help you find that information. If you're
looking for an IR driver, do the following BEFORE posting a "Does anyone
have this?"
a. Look in the Crestron DB
b. Try drivers for other models of similar devices. Chances are, the
codes are similar.
c. Search the files here (hint, your browsers search feature works
really well for this).
d. Search remote central. Even if you have to download pronto software
and grab hex codes and then dump them into DEAL, you should be doing this
before asking if anyone has a driver.
e. Look at other companies IR databases. There's a tool out there
somewhere that can convert AMX drivers to Crestron (Vert?). Look at RTI.
You can pull hex codes out of their IR database and put them into DEAL. Go
through every available resource you know.
Similarly, the same effort should go into finding ethernet and serial
protocols. There are a TON of modules here and if you spend more than 30
minutes with any search engine, you'll probably get close to what you're
looking for. Try multiple search engines, they don't always pull the same
results. Try different search terms, get creative. Other options available
include picking up the phone and calling support to find that information.
Remember, when members of the group post responses for peoples questions,
they are actively taking time out of their days to offer assistance. Don't
waste that time if you can do some searching on your own. As a bonus,
you'll be a better programmer for honing your search skills more.
3. Start your own archive for this groups content. I can't recommend this
enough. Gmail works really well, the storage is free and you have a better
(IMHO) search engine than the one that yahoo uses for the groups. Create a
new account and change your email preferences for the group so you get each
message as a single email. If you already have gmail, just use an incoming
filter to put everything in a label and skip your inbox. Sure, you'll need
to use the web interface to find information older than your archives start
date, but it's better than nothing.
4. Remember that tone is a tricky thing when reading and writing messages.
Do NOT post in all caps. It is the internet equivalent of shouting (how I
wish the caps lock key were never invented). If someone prefaces their post
with, "Don't take this the wrong way" or "Not to be rude" chances are, they
know what they are saying is going to be difficult to swallow. It doesn't
mean that they are instantly a jerk for saying what they did. It's the
internet, thick skin required.
My $0.02
-Nathan
[Non-text portions of this message have been removed]
|
