AVS › AVS Forum › A/V Control & Automation › Home Automation › Starting a crestron system
New Posts  All Forums:Forum Nav:

Starting a crestron system

post #1 of 87
Thread Starter 
Just not happy with what I can do with my logitech harmony 1100.

Wanting to pick up a used control system off ebay to play with and practice programming to hopefully integrate into my theater. All I want to start out with is HVAC control and lighting but would later like to add full AV control of the theater and distributed audio throughout the house with ipod and the other 2 HVAC zones. After that, maybe more.

What control system would you recommend starting with that I could grow with?

What's the differences in the AV2 and the Pro? Is the compact systems enough to start with and expand from there?
post #2 of 87
It is not impossible to do a Crestron system DIY, but do you do realize that there is no end user support and that the programming software (~ 10 different programs) is only available to dealers?
post #3 of 87
Quote:
Originally Posted by Leifashley27 View Post

Just not happy with what I can do with my logitech harmony 1100.

Wanting to pick up a used control system off ebay to play with and practice programming to hopefully integrate into my theater. All I want to start out with is HVAC control and lighting but would later like to add full AV control of the theater and distributed audio throughout the house with ipod and the other 2 HVAC zones. After that, maybe more.

What control system would you recommend starting with that I could grow with?

What's the differences in the AV2 and the Pro? Is the compact systems enough to start with and expand from there?

FYI - Search "Crestron+DYI" on AVS and you will see that Crestron is not a DYI system. You can buy the hardware on eBay, etc but you will have to somehow acquire all the different software applications & pieces, SIMPLWindows, Product Database, VTPro, Toolbox, etc. Then you will have to learn how to program a Crestron system.
post #4 of 87
If you are not controlling too many systems, I would recommend going with the MC2E. You will not need a lot of processing power if you are just doing a couple local video zones, audio, and hvac. If you plan on expanding, the next step would be the AV2 and finally a PRO2 with a lot of sub systems.
post #5 of 87
David, A bit off topic here,but enjoyed your response on theCE article. I too believe the clients should own the code..they paid for it didn't they.
post #6 of 87
Thread Starter 
Yes I understand that crestron is not fully DIY... I'll do what I can and will have a programmer (probably someone from this forum) do the rest.
post #7 of 87
Thank you Mr. Goodcat, much appreciated. It's a very contentious issues in the CI community but it's something I feel strongly about.
post #8 of 87
Personally I would look at something that is a little more DIY friendly - like CQC or Homeseer. You can put together a very capable system with a whole lot less heartache that trying to DIY a Crestron system.

I suspect that you would actually be able to do more with CQC than trying to figure out a Crestron system as a DIYer.
post #9 of 87
Just a quick comment here. To the thread starter, I recommend doing a search on the term Crestron for other discussions of the issue of DIYing a Crestron system. Most people end up giving up because they can't get all the software they need and/or can't get support either, other than from newsgroups. And it's not an easy product to program unless you are comfortable with computer programming. Personally I believe Brian's advice is best for most people.

That being said, the thread starter has indicated that he understands the situation and the risks. So let's please answer his questions and not just keep telling him not to do it.
post #10 of 87
If you look back on my posts, you will see that I was on the same boat as you are. Contrary to what most people told me, getting the software was not as difficult as they made it out to be. I got each and every program they have, but for me it was a matter of time. I did not want to spend allot of time learning something that I would not regularly use, I decided to go with an automation with a smaller learning curve. Good luck to you!
post #11 of 87
"learning curve" LEARNING CURVE, is that anything like..... bumps in the road
post #12 of 87
There's a few folks here, including myself, that are not "professionals" and do our own Crestron programming. All of the obstacles noted above can be worked around if you're willing and motivated to learn the system.

Note: Post edited my moderator.
post #13 of 87
Multiple posts edited and deleted. There is absolutely no need for every single thread where someone wants to learn to program a professional product turn into a 3-page flame on the issue. Let's move on.
post #14 of 87
Thread Starter 
I absolutely expected such responses and respect the work and dedication the crestron guys put into their work. I simply love tinkering and learning new and challenging things (from programming and electronic repair) and tend to change things way too often for someone to come in and do everything to our system.

I appreciate everyone's time and replies and will continue doing my homework to see what direction I'm going to. I had searched through this forum nearly all day before posting this so I knew what kind of responses I was going to get.

My main question was what control unit to start with.
post #15 of 87
Quote:
Originally Posted by Leifashley27 View Post

I absolutely expected such responses and respect the work and dedication the crestron guys put into their work. I simply love tinkering and learning new and challenging things (from programming and electronic repair) and tend to change things way too often for someone to come in and do everything to our system.

I appreciate everyone's time and replies and will continue doing my homework to see what direction I'm going to. I had searched through this forum nearly all day before posting this so I knew what kind of responses I was going to get.

My main question was what control unit to start with.

The Pro2 has a front display which can be very helpfull when trying to figure out things.

I would make sure the unit had an ethernet port and is a 2 Series.

That being said please be aware that the software is not freely available to the public.
post #16 of 87
Thread Starter 
Guys... please keep the conversation civil for the sake of answering a legitimate question for both my use and future use.

That would do more for the community than a bunch of bickering.
post #17 of 87
Go with the pro2. We use it on small and large scale projects because it's rock solid and robust. Buy the pro2 now and u won't find yourself buying it in a year when you start upgrading and adding things.

The tip about the Ethernet card is a good one. There are three other card slots for u to add in com or relay or whatever else u might need.
post #18 of 87
Quote:
Originally Posted by Leifashley27 View Post

I absolutely expected such responses and respect the work and dedication the crestron guys put into their work. I simply love tinkering and learning new and challenging things (from programming and electronic repair) and tend to change things way too often for someone to come in and do everything to our system.

I appreciate everyone's time and replies and will continue doing my homework to see what direction I'm going to. I had searched through this forum nearly all day before posting this so I knew what kind of responses I was going to get.

My main question was what control unit to start with.

You should really steer far away from crestron as a DIY unless you have a "friend" who can help you. There are more hurdles you'll encounter than you can possibly deal with without having someone on the inside. aside from software there's also firmware and will be more than challenging it will be more along the lines of frustrating.

However if you do have someone on the inside. I would recommend the Pro2 if you are buying used you can get a good price. Hopefully in good working order.

EDIT: oh yes and as said above make sure it has an ethernet card/port

EDIT2: And yes you may be able to get the software as someone said but without someone helping you keep it up to date your system can soon fall out of date. Get help... everyone needs it
post #19 of 87
Quote:
Originally Posted by 39CentStamp View Post

Go with the pro2. We use it on small and large scale projects because it's rock solid and robust. Buy the pro2 now and u won't find yourself buying it in a year when you start upgrading and adding things.

The tip about the Ethernet card is a good one. There are three other card slots for u to add in com or relay or whatever else u might need.

I'm going to disagree with the above. If all you need is an ethernet capable control system and your requirements are an IR emitter or two and a couple of serial ports why would you need to go for a PRO2? A QM-RMC would do the job perfectly and be significantly cheaper.

If, however, you're looking at using the Crestron system to do more then obviously that's where the larger systems come into play. the CP2E would be more than adequate for a home theatre and a bit of HVAC and lighting control, assuming it has enough serial ports for your requirements. Up from the CP2E is the AV2, which is basically a PRO2 but without the front panel and the 3 extra card slots (the card slots can be added with the use of a CAGE2 though). If you need the front panel then go for the PRO2 and this comes with the CAGE2 already installed so you have 3 expansion slots from the outset.

As for trying to DIY a Crestron control system I would say the follow (I might get in a bit of trouble from others for this one):

1. Crestron programming is not rocket science, anyone with a bit of common sense, past programming experience or the desire to learn could easily program up a system.

2. Programming a Crestron system well takes a bit more skill and experience.

3. Designing the UIs is not particularly hard either but again, making them functional and uncomplicated takes a little insight.

4. The biggest hurdle will be getting all the software you need. The software tools are only available to dealers, CAIPs and a few others (integrated partners etc).

5. If you can manage to get the software tools that you need then I am sure there will be people here and other places who would be willing to get you going...
post #20 of 87
Syphon, did u miss the part about hvac lighting whole house AV and "maybe more"?
post #21 of 87
One of the reasons I point to the Pro2 is the front panel. For a new guy getting his feet wet it might save them hours of fustration. Gee, why is the clock stopping everytime I press this button. Oh! I there is a loop in there. Why is toolbox not talking to the controller...Stuff like that.
post #22 of 87
Quote:
Originally Posted by 39CentStamp View Post

Syphon, did u miss the part about hvac lighting whole house AV and "maybe more"?

But without knowing the OPs exact requirements you can't quantify what "maybe more" means. It could just be an extra IP controlled device or a couple of RS-232 devices?

Why go PRO2 when an AV2 would cover most (if not all) bases unless he was doing a pretty large system? Depending on the OPs needs a CP2E might even be enough. I'm not saying NOT to use a PRO2 but it's not the only processor out there that could meet the OPs needs.

Quote:
Originally Posted by David Richardson View Post

One of the reasons I point to the Pro2 is the front panel. For a new guy getting his feet wet it might save them hours of fustration. Gee, why is the clock stopping everytime I press this button. Oh! I there is a loop in there. Why is toolbox not talking to the controller...Stuff like that.

I take your point David but the front panel isn't that much use if you ask me. Looking at the front panel and the stopped clock tells you about as much as Toolbox not being able to connect. The processor being "stuck" doesnt immediately tell you anything and using Simpl Debugger (as horrid as it is) is a much more useful way of seeing where things are going wrong.

To the OP, if you can get hold of the software tools etc I would be willing to help you get going.
post #23 of 87
Quote:
Originally Posted by David Richardson View Post

One of the reasons I point to the Pro2 is the front panel. For a new guy getting his feet wet it might save them hours of fustration. Gee, why is the clock stopping everytime I press this button. Oh! I there is a loop in there. Why is toolbox not talking to the controller...Stuff like that.

I have been doing this for years and have never once troubleshot a system based on the front panel of a PRO2.
post #24 of 87
Quote:
Originally Posted by Blowne30M3 View Post

I have been doing this for years and have never once troubleshot a system based on the front panel of a PRO2.

And the number #1 reason is because you have been doing this for years. Congrats!

I personally don't spec Pro2s on this but hey I'm trying to help the OP out and like to think out of the box.

And I've seen toolbox not connect over IP before,, um like last week at a business when the IT guys changed the gateway at some point. I'm trying to think what issues a new guy might come upon and what easy things might help over come them.

Blowne, In your many years and vast experience you must have some suggestions.
post #25 of 87
Quote:
Originally Posted by Syphon Filter View Post

But without knowing the OPs exact requirements you can't quantify what "maybe more" means. It could just be an extra IP controlled device or a couple of RS-232 devices?

Why go PRO2 when an AV2 would cover most (if not all) bases unless he was doing a pretty large system? Depending on the OPs needs a CP2E might even be enough. I'm not saying NOT to use a PRO2 but it's not the only processor out there that could meet the OPs needs.



I take your point David but the front panel isn't that much use if you ask me. Looking at the front panel and the stopped clock tells you about as much as Toolbox not being able to connect. The processor being "stuck" doesnt immediately tell you anything and using Simpl Debugger (as horrid as it is) is a much more useful way of seeing where things are going wrong.

To the OP, if you can get hold of the software tools etc I would be willing to help you get going.

While I don't use the front panel much, I have used it to check com settings, see what Cresnet stuff is online and at one clients home have a front panel button reset the Pro2 and 5 racks of gear.

I'm looking at it from a new guys point of view who needs every bit of advantage they can get.....
post #26 of 87
Quote:
Originally Posted by David Richardson View Post

And the number #1 reason is because you have been doing this for years. Congrats!

I personally don't spec Pro2s on this but hey I'm trying to help the OP out and like to think out of the box.

And I've seen toolbox not connect over IP before,, um like last week at a business when the IT guys changed the gateway at some point. I'm trying to think what issues a new guy might come upon and what easy things might help over come them.

Blowne, In your many years and vast experience you must have some suggestions.

I just don't think a front panel display should be a real factor in which type of processor he gets. He should be buying one based on the needs of his system, not whether he needs to figure out bugs or not.

With PRO2's you can always establish a hardwire 232 connection. When the IP connection fails, which is fairly common on some applications, reboot the processor and try again. If that doesn't work, hardwire in with a serial connection and verify your settings. I was on a job last week and had all kinds of issues with IP connectivity with a PRO2. The cause was a jacked up network, but the processor would randomly drop. Sometimes just giving it time would clear up the issue, but for the most part this is rare.

As for the OP, I still stand by my initial post. I'm not sure why this thread is getting so sidetracked.
post #27 of 87
While trying to avoid getting back to work on my Crestron Cert exam,,,, I remember a few times where the clock saved me hours of troubleshooing time. There were about 25 devices on the cresnet side and the system would lock for few a few seconds then come back to life, lock up then come back to life. Toolbox showed up three flags on 3 devices. Upon messing with those three I decided to pull each cresent device off one by one watching the clock on the front panel. Well turned out to be a roombox causing the whole thing which was not of the the three items flagged by toolbox or testing the waves to/from the device.

BTW, you can't connect even with 232 if the unit is locked up with any processor.

An entry level unit would be fine, If I was a new guy just might be saved some hassle with someting to look at.

OK, back to working on my vacation...
post #28 of 87
This is a debate about nothing . Any processor from an MC2E to a PRO2 will work fine. However if budget permits the PRO2 is a great processor, he can grow with it in the future, and the front panel display and lights can come in very handy for someone learning since you can see if commands are being sent and received.
post #29 of 87
Quote:
Originally Posted by Syphon Filter View Post

But without knowing the OPs exact requirements you can't quantify what "maybe more" means. It could just be an extra IP controlled device or a couple of RS-232 devices?

Why go PRO2 when an AV2 would cover most (if not all) bases unless he was doing a pretty large system? Depending on the OPs needs a CP2E might even be enough. I'm not saying NOT to use a PRO2 but it's not the only processor out there that could meet the OPs needs.

I take your point David but the front panel isn't that much use if you ask me. Looking at the front panel and the stopped clock tells you about as much as Toolbox not being able to connect. The processor being "stuck" doesnt immediately tell you anything and using Simpl Debugger (as horrid as it is) is a much more useful way of seeing where things are going wrong.

To the OP, if you can get hold of the software tools etc I would be willing to help you get going.

A $500 difference when you compare an AV2 with card cage vs a PRO2. The front panel is worth the $500 IMO. Maybe you can pad that into your labor for him?
post #30 of 87
Thread Starter 
Loving the info... thanks for the chatter.

I'm back from christmas vacation and will start planning out a system this week.

I have a couple of leads on getting software now... we'll see if anything pans out.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Automation
AVS › AVS Forum › A/V Control & Automation › Home Automation › Starting a crestron system