Our goal in this project is to program a simple huddle room system. We’re going to design something that looks like this:
Over time, we’ll flesh this program out into something with more features, but for this part, it’s going to remain pretty bare-bones.
Continue reading “SIMPL# Pro Primer: Part 5”Originally, I wanted to make Part 4 similar to the program in Part 3, just showing how to do it with a DMPS instead. But testing it means I have to get a DMPS setup in my lab and I don’t feel like doing that just yet. So instead, we’ll take a step back and look at how to gather information about the processor we’re running on.
Continue reading “SIMPL# Pro Primer: Part 4”We didn’t get very far in the last tutorial, but we did get all of our devices added successfully to the program. We’re going to continue using the same project and finish it by creating a user interface and adding some program logic.
Continue reading “SIMPL# Pro Primer: Part 3 (continued)”By now you should be a pro at creating new SIMPL# Pro projects. Let’s create another one, but we’re going to set this one up slightly different this time. We’ll still call it Part3, but change the solution name to Primer:
In Part 2 of this primer, we’re going to keep things simple… another Hello World program. Sorry, maybe Part 3 will cover something more exciting?
Continue reading “SIMPL# Pro Primer: Part 2”In Part 1 of this primer, we’re going to look at how to create a new SIMPL# Pro project. This series assumes you have a copy of Visual Studio 2008 SP1 installed as well as the Crestron SIMPL# Plug-In. If you need to install the plug-in, it can be downloaded from Crestron. The current version is 2.000.0058.01.
Continue reading “SIMPL# Pro Primer: Part 1”This is one part in a series of posts about my journey through the AV world. I’ve broken these up into bite-sized portions that shouldn’t take more than 10 minutes to read. I’m hoping to explore the future of systems programming in the Audio/Visual sense. Let me know if I wander off into a tangent somewhere, I tend to forget where I’m going.
I went to ITT Tech and studied subjects designed so I could land a job in IT. Instead, I took a left turn and ended up in AV. Well, joke’s on me because AV and IT ended up merging anyways. I may have traded away my knowledge about ASN.1 for the Inverse Square Law, but I think you can agree I’m the winner there.
This is one part in a series of posts about my journey through the AV world. I’ve broken these up into bite-sized portions that shouldn’t take more than 10 minutes to read. I’m hoping to explore the future of systems programming in the Audio/Visual sense. Let me know if I wander off into a tangent somewhere, I tend to forget where I’m going.
Last time, I talked about my aspirations of one day becoming a professional programmer. I hadn’t touched on the AV industry at all since it was largely unknown to me then. I had a few interviews lined up the week before graduating, and I ended up accepting an entry-level position at an AV company. They were primarily a TANDBERG reseller who also did occasional system integration work.
This is one part in a series of posts about my journey through the AV world. I’ve broken these up into bite-sized portions that shouldn’t take more than 10 minutes to read. I’m hoping to explore the future of systems programming in the Audio/Visual sense. Let me know if I wander off into a tangent somewhere, I tend to forget where I’m going.
Hi. My name’s Kiel. How you pronounce it is all on YOU, but to me it’s Kyle. I’ll accept anything with a K sound since at least you tried.
I sort of fell into AV programming 12 years ago, but let me start back at the very beginning.
This tip is going to cover Crestron modules–specifically, writing your own. As a new Crestron programmer, I shied away from doing this for years. It wasn’t the style used by the other programmers I worked with, and I never felt that I had enough time between projects to revisit how I would have done it differently. Over time, things change. Our team of programmers changed, new styles replaced the old; I became more familiar with the tool set; I could turn around new work much quicker than when I started; and I found I finally had time to apply some retrospection. Since I started incorporating my own modules into my programming, I’ve been able to increase my productivity even more and make the initial program almost bug-free.
Kiel the Coder 