programming – Page 4 – Kiel the Coder

NetLinx: Modules

Using and writing modules has some tangible benefits:

They are reusable code that we can polish over time
They break up large programs into smaller, testable units
They abstract away details we don’t need to worry about

Grab the code for this post from the GitHub repo.

In this post, we’ll explore the Standard NetLinx API–or SNAPI, for short. This is one of those topics I didn’t fully embrace when I started programming AMX, but over time, I grew to appreciate the benefits of adhering to a standard.

I’ve updated the touchpanel layout in this post, so if you want to grab the latest code, it’s available on GitHub.

NetLinx: Testing

This post will cover how we can use NetLinx Studio to test our program, especially in the absence of real equipment.

NetLinx: Your First Program

In the last post, we got started by making sure our tools worked and blinked some lights. In this post, we’ll dive deeper into how the NetLinx language works and write a legitimate program.

NetLinx: Getting Started

I want to write a few posts about programming AMX NetLinx controllers. While I started my career programming AMX systems, I’m lucky now if I see 1 or 2 in a year. Strangely, every time I’ve started with (or returned to) a company, I’ve been handed a NetLinx system to figure out. It’s sort of a welcoming return to AV because programming in the NetLinx language is well-suited to automation tasks and something about it brings me joy.

Setting Up the AV Programmer for Success

Nice post on rAVe Pubs from my old colleague and friend, Murphy Daley.

www.ravepubs.com/setting-up-av-programmer-success/

Thank you, Murphy!

CWS: Part 4

This post is going to be the last one covering CWS (for now). We’ve created an API that lets us view the current system settings, now we just need a way to update them. In this part, I’ll go over how to take in and apply new settings.

CWS: Part 3

In this part, we’ll build out a system configuration page that uses CWS to make changing system settings easier.

CWS: Part 2

In this part, I’m going to look at adding route handlers to our CWS server. I’ll continue adding to the program we wrote in CWS: Part 1, so grab those files from GitHub if you’d like to follow along.

CWS: Part 1

One thing that always seems to come up during the C# labs at Masters is Crestron Web Scripting (CWS). I never think about adding this to my own projects, but it is a good way to provide some level of advanced configuration (or even remote control) of the running program. I’m watching the Intermediate C# videos this morning and see that the first lab dives right into using CWS. So in the spirit of Masters, let me try to incorporate some of their teachings into my day-to-day programming.

I’m hoping in this series of posts to build out a CWS program that can:

Work on 3-series and 4-series processors
Configure a room system
Provide a REST API for external control

Let’s begin!

Category: programming