"Engage Preset" message type not toggling states across banks

Morningstar Software Bug Reports and Feature Requests
1

“Engage Preset” message type is not toggling states across banks. However, when engaging presets within the current bank (ie. preset A engaging preset B) the states are toggled.

I reverted back to v3.13.3 which is the last version I had before I skipped to .6. Engage preset works fine with .3 locally and across banks. I uploaded .4 and the problem starts with that version.

This bug was reported in January.

2

Card created

This is an automatically generated message

A Trello card has been created for this request: “Engage Preset” message type not toggling states across banks

3

Do you have “Remember Toggle States” turned on?

4

Yes. That’s one of the first settings I checked. Again, it works fine with v3.13.3.

5

can you upload your controller backup either here or via email ( jason@morningstarfx.com )?

6

Two e-mails have been sent. First one explaining the presets and the second one with the actual files.

Thanks

7

Jason have you been able to take a look at the presets I e-mailed last week?

If not, at the very least see if you can replicate the problem.

Thanks

8

Sorry for the delay! I just checked now. The presets you sent have Set Toggle Presets, but nothing is checked:

image
image2160×1476 221 KB

Though I did go and select the appropriate one and try again, and it looks like they can’t set themselves when triggered across banks. This works though (if I’m just needing a preset to toggle itself on command, it’s what I prefer):

image
image2178×172 23.2 KB

Also, you can use Set Toggle in other switches, just not the one calling. I can’t currently confirm if the behavior was different in earlier firmware, but I can see what you’re talking about now.

So the good news is you’ll be able to program whatever behavior you’re looking for, with the caveat that if you’re setting multiple toggles, you’ll need a command for the receiver itself and a separate one for any others it sets. I’ll discuss the possible bug with engineering as well.

9

Thanks for the reply.

The unchecked boxes was purposely done. It doesn’t make sense, but oddly enough it worked correctly that way in v3.13.3. However, in the new version I did try a multitude of methods to engage across banks and could not get it to work. It seems to be a position 2 bug. But I can’t confirm.

So yes, if you can bring it to the attention of engineering and have them test it in the new version and most importantly in v3.13.3 that would be great. The “engage preset” message is the core of my workflow.

Thanks

10

Okay, just to make sure we’re on the same page.

  • The only confirmed bug I see is that when trying to use Engage Preset to set toggles across banks, the target of the Engage Preset command would set the toggles of other switches but not itself. I have alerted engineering, but in the meantime, there is a functioning workaround, which is to use Toggle Preset (pos:1) to set the switch’s own position to 2 and Toggle Preset (pos:2) to set it to position 1.
  • Here’s the correct way for the Set Toggle Presets to work:
    • Other than “Set Toggle” (command) → “Set Toggle” (sub-type), all the others only work on the items checked e.g. “Set Toggle” → “Engage Toggle” will set the checked switches to position:2
    • Set Toggle → Set Toggle is the only one where everything is affected and the check determines the position (checked= pos2, unchecked=pos1)

The way your commands are currently programmed, using Set Toggle → Engage Toggle and Set Toggle → Disengage Toggle, currently don’t do anything because nothing is checked. If a command like that previously did something, that’s bugged logic and it was probably fixed. I’d suggest updating your commands to the correct logic if you’re using the new firmware.

11

Yes, that’s correct and it’s what I’ve observed myself. I’ve been using the workaround without any problems. But, something definitely changed with the set toggle message type starting in v3.13.4.

It’s not a huge problem. I could continue using the “toggle preset” message type in addition to “set toggle”. My purpose for the combination of engage preset and set toggle message types is to imitate IA linking. The “toggle groups” feature has some built-in limitations with that workflow.

Thanks for looking into it.

12

Is the primary limitation the number of Toggle Groups? I don’t see a functional difference otherwise (I’m just basing that observation on a skim of the RJM documentation).

13

In the interest of not rehashing the subject , I posted this very topic 2 years ago with an explanation here: