On Mon, Apr 11, 2022 at 9:27 PM Lincoln King-Cliby via <lincoln=[email protected]> wrote:
For the second scenario¡ what happens if you put the \x20 at the end of the string? It seems like it¡¯s taking the first byte of the
new command and treating it as the end of the prior command (and hence the ¡®one step behind¡¯ behavior since it¡¯s not executing the command until it gets the ¡®end¡¯ of the command)
?
What do these commands look like?
?
How wide is the programmatic trigger?
?
Is it possible multiple digitals on the SIO are high simultaneously/going high on the same wave?
I have a use case where I need to do audio breakaway switching so I'm sending custom commands from an SIO into the To_device$ input. I worked with Jay at ZeeVee and these custom commands are doing exactly what I want. The weirdness is this:
If I trigger the digital inputs to the SIO in Simpl debugger, I see the string go out, I see the ZeeVee respond and I hear my audio breakaway switch happening as expected.
If I trigger that exact same digital input but from my program, I see the string go out, but this time, no response and no audio switch.?
My faith has been rocked in believing that a digital is a digital based upon what I'm seeing. I have a case open with Crestron but no resolution yet.?
This is NOT to do with terminations. It seems to work (when it works from Simpl debugger) with either no termination, CR or CR+LF.?
Not sure if it¡¯s a clue but: I did try a separate TCP/IP symbol direct to the ZeeVee controller sending out the same commands. This gave unexpected results: when triggered from the program or Simpl debugger, every command was now
acknowledged with an error message saying it didn¡¯t recognize the command because the first character of the string was chopped off. (the first word of the string is ¡°join¡± and it was complaining it didn¡¯t know what ¡°oin¡± meant). I tried prefixing the strings
with a \x20 (blank character). This prevented error messages and every message was executed, but I noticed switching was happening ¡°1 step behind¡± and I had to send each command twice and it all felt fairly flaky and it didn¡¯t seem like the correct direction
to go.