If you are doing basic systems like a stand alone theater programming in simpl is very easy. A simple theater or one room system should take no longer than an hour or two if you are using decent equipment with RS -232 or discrete IR control. you simply name the signal coming from the touchpanel button press and drag it to the appropriate input signal on the device. Using other logic such as conditionals and creating all scenario covering logic does take some time. An IPad and qmrmc to control a display, AVR, and basic videos sources should take less than a day provided that you have existing network infrastructure and vt pro templates to use for the gui. System builder is a great tool but it applies alot of logic and is difficult to trace sgnals through. It also does not compile cleanly so when opened in Simpl there are many compile notices. I prefer to have a clean compile when in Simpl so I can debug easier. Systembuilder is good for large multiroom projects with small inferfaces like APads. Systembuilder can create some very large projects with many interfaces and crestron devices such as lighting, Tstats, XM, IPod, IPads, ADMS, etc. in less than an hour start to finish and be pretty complete. there are some systems that I have done entirely in one or the other, depends on the equipment.

An IPad and qmrmc to control a display, AVR, and basic videos sources should take less than a day provided that you have existing network infrastructure and vt pro templates to use for the gui. System builder is a great tool but it applies alot of logic and is difficult to trace sgnals through. It also does not compile cleanly so when opened in Simpl there are many compile notices. I prefer to have a clean compile when in Simpl so I can debug easier.

Systembuilder is good for large multiroom projects with small inferfaces like APads. Systembuilder can create some very large projects with many interfaces and crestron devices such as lighting, Tstats, XM, IPod, IPads, ADMS, etc. in less than an hour start to finish and be pretty complete. there are some systems that I have done entirely in one or the other, depends on the equipment.


Great post, I fixed for you =)

So do you normally start by having the GUI first and all the joins in the GUI assigned, then work from the button press backward for make the events occurs that you want based on that button press?

My programmer builds one interface then writes logic.

Bruce,
thank for the feedback and positive support. I have 3 processors on hand (so I don't ruin the main system that my wife uses). The QM-RMC I have been using as a Bitwise type solution and an MC3.

I have a few different interface solutions and want to get single zone proficient. I lost my self when I added multiple interfaces around the house.

I am fairly new to the Simpl programming but I have my interfaces built first but don't assign joins. Then I move over to Simpl and start creating the logic and through the logic my joins are created, which then get assigned to my VTPro project.

I may not be doing this as recommended/efficiently but find that it works the best for me as it allows me to work in sections and ensures me that my joins are assigned properly, and my program compiles cleanly.

I almost always do the simpl side first and then create a gui. Reason for this is in simpl I connect all possible device commands yet on the gui side I generally only include the buttons pertinent to the installation for simplicity to the end user. More advanced users get more buttons

I put a little stand alone system together for my wife so I can play and not bother her!

I "storyboard" the system first, meaning I write out a design layout of how I want the system and UI's to present and flow.  Based on this, Simpl logic comes next, and this is particularly important on larger projects.  The UI is the last piece that gets done, with tweaks to both at the end.
I believe that to write a good program, you have to mentally see the code work first as your write it, then design the graphics at the end.

I'm surprised no one has mentioned the idea of setting up a 'template' SIMPL program and using it for most of your systems. The more systems you do, the more refined your system becomes, and the faster you get. Most of the systems I had to do were similar enough that I was able to re-use much of my programming. I was also able to simply re-skin my gui projects if someone had an issue with the color/look of my main gui set. All different gui sets used the same joins for everything.

If you are talking about simple one-room systems, you should be able to rock them by your third. Just try not to sell a completely different set of equipment every time...

Food for thought.

Norm

It's pure logic. The difficult part is knowing the symbol names and what each one of them do, the rest is ifs and thens. Watch some tutorials, and refer to the help files. they are very self explanatory. in my opinion, the most time consuming part is VTpro. it's nearly impossible to do it without an extended desktop with 2 monitors. it will take you forever to link join numbers.

The beauty of it is that once you understand how it works, you can do whatever the hell you want. No other system (other than savant) will let you do that level of customization.

Where do you find tutorials? I dont see anything on the site (dealer login access)

Programming is a language. How long did it take you to learn a language to the point that you could say anything that came into your mind? I would say that a single room system consisiting of display, screen, lighting, shades, AV components would take less than a day.

A multi-room system between 1-3 days. But this depends on having the graphics already done. If not, it might take longer.

I build the GUI first as that determines the logic flow. I don't think it matters how you code the back end. Secondly, adding additonal driver for some source is much simpler than altering the GUI logic. Telling me after the fact t add 3 sources is going to take longer as I have to adjust logic in mulitple places.

Knowing all in the beginning makes a very big difference

Well, if you are a dealer you really should take their training. you will not regret.
But, if you google Crestron Simpl Tutorials you can find a lot of stuff. Even in youtube. Check this one out:

http://crestron.davidcamerondesign.com/

I am a dealer. I have taken the essentials class once but need to go back. I have a stretch target of making it through intermediate with in the next 12 months.

Thank you for the link.

The primer that comes with the Essentials programming course should have all the information you will need to make your program work. I would start at that, and you will be amazed at how quickly your system comes together just using the logic within the primer. Although it may not be a very clean looking program it will work and over time you will find ways to make it cleaner.

I have done those programs. I am looking to import modules and start adding more interfaces to my programs.