I get "trigger map" errors trying to import then open previously working configs from 2.0.
I don't know how to fix those issues within the 2.0 tool. All the aforementioned variables are in the UserSettingsLanguageControlState state machine.

Anybody else?

If you received this message one of these things is likely. 1) You have a configuration that was build prior to the release of 2.0 Final In the early beta and engineering releases of 2.0 there was a different model for how you managed keys which was removed in later versions.

The functionality was left in place but not used in 2.0 but trigger maps were not compatible with the changes in 2.1 so they were removed.

To correct this error you will need to do a little analysis. First, find where these trigger maps are pushed and set to current. Typically this will correspond to a specific screen or state. You should then remove the calls to Push Trigger, Pop Trigger or Use Trigger from these state machines. In its place you should find the appropriate views in the page designer and assign the key definitions there. Typically this is simply taking each event in your trigger map and hooking it to the appropriate key in your Page View. Once you have done this you can delete the trigger maps. When your satisfied that it working you can upgrade to 2.1

BTW - Often you will find that the Trigger map wasn't actually being used and can simply remove the trigger map and the calls to push, pop and use. With no change in behavior.

Jake, I distilled your thorough explanation to - track those console errors down and blow away the dangling actions rename the duplicate events, etc. I think I oversimplified the process when I just went in and gutted all those issues out.

(See attachment)

I believe this approach created some quirks. Like ghost DM1s after a fault is resolved

(See attachment)

Do you agree?

I see some gradual changes to state machines as the Murphy standard config progresses from 2.0-2.1 to 2.2 and it appears the only way to incorporate that thinking into my build is to start from scratch with a 2.2 std config and rebuild my screens and functionality, trigger maps excluded. Thank you for the import/export page feature.

The good news is that I get the ghost DM1's with a PV750 in simulation mode so testing should be easier.

alb -

if you're willing to send me your .db3 file for the 2.0 version (so I can see it in a working state) via Private Message, I'd like to take a look.

I will send you a private message as well - then you can just respond. Please watch for it.

jpurdum