Main zone front, 'C' = main zone center, etc.). If the string is related to volume, it specifies the speakers ('F'= Third char is 'E', it breaks down into additional surroundeffects. The P1 means Zone 1, the next char can be S for Source, V forVolume,Į for Effect (surround effect), Q for encoding applied, etc. The data that comes back looks like: P1S6\x0a P1E60\x0a P1ET62\x0aP1VC I'd like to capture all of this data and save each piece in avariable. Of information is delimited by an '\x0a' and the transmission ends Material, the surround effects mode currently selected for theĮncoding of the source material, whether THX is on, etc. Variables, including the new source, main volume, volume forfront,Ĭenter, surround, rear and subs, the surround encoding of thesource One source to another, the D2 responds by sending data on 20different The D2 is rich in features and rich in feedback. When it comes to receiving and parsing data into something I can Transmitting data is going well, but I don't know where tostart
I'm (still) trying to create a user module for an Anthem Statementĭ2. If you're not skilled in S+ and you'reĭetermined to roll your own from scratch, give the above methods a Variable number of bytes, it probably won't work.Īnother popular way is to use a SIO and create exact parameters forĮvery possible value (not too bad when you use the advanced editingįeatures), this would be simulating your lookup table.īut, most would probably still use some type of S+ 'engine' to parse Problem with the STOA is that when you define one, the number ofīytes must match or it will be ignored, so for volume that has a Value, but a scaler and ASUM could help you out with that. Returned in ASCII representations of what you want as a single analog This gets moreĬhallenging depending upon your skill level when several bytes are Match/ignore/extract the bytes that you need. STOA (serial to analog), setup the parameters of the STOA to With a length of your longest string, say 20d for starters, and then
If anything, they will give you some ideas on howīut, from what it looks like try using a serial gather on the rx$ I believe there is a module at the Crestron site, as well as here in
This SIMPL Windows approach doesn't seem that bad, assuming it works, but I wonder if Crestron has a symbol or feature similar to a lookup table? Is there an easier or more straight-forward approach I'm missing? I'd also like to store the results in variables that can be accessed by an IP Client. a little like peeling the layers off of an onion.). I also thought about using SIMPL Windows with a Serial I/O symbol for each level (in other words, the first Serial I/O would determine which zone we're talking about, with parameters for P1, P2 and P3, the second level of Serial I/O would determine whether we're looking at Volume, Source or Effect, the third level would look at which type of effect, etc. I thought about using SIMPL+ and writing a really long switch case function with lots of embedded switch cases, but that seems pretty ugly, both to write and to debug. If the string is related to volume, it specifies the speakers ('F' = main zone front, 'C' = main zone center, etc.). If the third char is 'E', it breaks down into additional surround effects. The P1 means Zone 1, the next char can be S for Source, V for Volume, E for Effect (surround effect), Q for encoding applied, etc. The data that comes back looks like: P1S6\x0a P1E60\x0a P1ET62\x0a P1VC +0.0\x0a P1QAL-Cinema, etc. I'd like to capture all of this data and save each piece in a variable.
Each piece of information is delimited by an '\x0a' and the transmission ends with two '\x0a's. When changing from one source to another, the D2 responds by sending data on 20 different variables, including the new source, main volume, volume for front, center, surround, rear and subs, the surround encoding of the source material, the surround effects mode currently selected for the encoding of the source material, whether THX is on, etc. Transmitting data is going well, but I don't know where to start when it comes to receiving and parsing data into something I can display on the touchpanel. I'm (still) trying to create a user module for an Anthem Statement D2.