But I’m not sure what it is supposed to do. I’ve experimented and I can see that when I disable a port it removes it from the channel assignment. But when I try to enable a port I’m not exactly sure what it’s doing.
I guess what I would envision is one field in the action to select the port and then another field to select a channel. The value field would either enable or disable that connection.
It would be great if you could disable a port from all channels with one action. Then the next action could assign that port to a channel and you wouldn’t have conflicting assignments.
Is that considered a cross point? I’m not sure exactly the language to use.
I’m sure it’s not the last “What the heck does this action do” questions, since all of the commands come directly from the base station, along with the odd naming conventions.
Obviously I haven’t tested many of them, and likely lots of them are of no use to a companion module, but for now I’m keeping as many in as possible until we figure out exactly what they do!
But… I would suggest you DON’T try this particular command. Just toggling it from false to true and back and then adding that port to a channel was enough to crash my Arcadia. I’ll send the report to CC and see if they have an idea what that command is for, but I expect I need to get rid of that one until further notice!
Safe call. I am anxious to get a solution for assigning (2 Wire) ports to channels to make this baby really the center of our Control Room comms with huge flexibility. If it works I can eliminate a switchboard power supply (SB-704). Those things are notoriously buggy when the slider switches start getting dirty.
Okay. This is working, but we need a way to learn what channels are joined to a port. Because if I try to join more than one channel to a port I crash the Arcadia (using companion or CCM). And If I’m actively joining channels to a port I don’t necessarily know which one is already joined so I don’t know which one to unjoin before I join a new one.
Great progress so far! I definitely owe you a lovely beverage.
Okay, so this fault is not because of the module. I can reliably crash my Arcadia by joining more than one channel to a 2W port using the CCM alone. I’ll call CC and put in a bug notice.
It’s because of that other multichannel command which never should have been possible. Since it’s not a command that can be done with the CCM, it’s really not their fault, it’s more of an oversight by me for allowing a command that the Arcadia can’t handle. Unfortunately, you’ll have to reset your Arcadia to clear the error. Sorry for the trouble!
Hopefully there isn’t more like that, or if there are that they get found quickly.
Once you get it reset, try the port join command and see if it works as expected.
Andy, is there a way to unjoin a port to all currently assigned channels without a blanket stack of unjoin actions?
Use case, I’d like to join a port to a different channel but need to unassign to whatever it is currently assigned at the moment, which could be any number of channels.
perhaps a checkbox to remove existing assignments before making a new assignment. I can also think of a need to simply clear assignments without making another assignment, so perhaps two nested checkboxes. Or perhaps a wildcard variable in the list of unassign options.
Ok, I added an “All” to the dropdown, just going to test it and then I’ll let you know when it’s built.
Might change the dropdown to a multi select so you can select several endpoints to disconnect from. We’ll see if that’s difficult or not.
Thank you for reporting that. The error shouldn’t have caused any issues, it was simply trying to leave a connection that was already left, likely because of a timing issue. Now it tries to check before leaving to make sure the connection still exists, but it also just warns rather than errors if you for some reason try to leave a connection that’s already disconnected.
Try v0.4.7 and let me know if you find any other issues!
