Access/execute codesys menu

2020-02-27T15:02:01.346000Z

Originally created by: M.Schaber

Hi,

Please note that using the undocumented command interface is not a supported usecase. We might use it for workaorunds sometimes.

The command in question does not take any arguments. Instead, it works on the currently selected Recipe Definition Editor. If the active view is not a Recipe Definition Editor, it will throw a null reference exception.

HTH,
Markus

Access/execute codesys menu

2020-02-27T15:02:00.742000Z

I am trying to execute the command : ('Update structured variables', <system.guid 0x00000000000000f9="" object="" at="" <span="">[714fa2c5-b677-45b2-85d8-3144aba5d531]>, Arraystr)
This is a workaround for me because recipe management is not available through scripts</system.guid>

I need to update the structured variables of all the recipes from the script. I thought the argument to the execute command would be the guid of the recipe. But I get the error : object reference not set to an instance of an object. Am I missing some argument?

cmd = system.commands['{714fa2c5-b677-45b2-85d8-3144aba5d531}'] #get the update structured variables command
cmd.execute('{f992dc78-635a-4094-bcb4-56c1e53ee1de}')#execute command using recipe guid

Access/execute codesys menu

2020-02-27T15:01:59.064000Z

Originally created by: M.Schaber

Hi,

The objects in a project all have a "guid" property - so you could use projects.primary.find("DeviceName")[0].guid if the device is the only object with this name.

Access/execute codesys menu

2020-02-27T15:01:58.448000Z

system.prompt_handling |= PromptHandling.ProcessScriptPrompts # this forwards prompts to script
system.prompt_handling &= ~PromptHandling.ForwardSimplePrompts # this silences other prompts
system.prompt_answers["EnterDebugMode_Prompt"]=PromptResult.OK # you have to put it before the execute
system.commands["sil2_commands", "enter_debug_mode"].execute(str(proj_device.guid))

I had the same issue and this works fine for me but I'm still wondering, if there is an easy/easier way to find out the project device guid? I found the guid in an exported file (Project -> Export...) but i hope there is a more elegant solution (maybe another python script?).

Access/execute codesys menu

2020-02-27T15:01:57.848000Z

Originally created by: M.Schaber

Hi,

Happy you found a solution - on the other hand, you can also use the guid as key in the [index] operator - a little bit more ugly, but it should work, too.

Access/execute codesys menu

2020-02-27T15:01:56.169000Z

Never mind, i found it:

for cmd in system.commands.GetEnumerator(): 
    print("{0} - {1} - {2}".format(cmd.guid, cmd.name, cmd.tokens));

b4c6c2d3-cfda-4a01-9065-e9ad98fadfa4 - Enter debug mode... - Arraystr
37fbe729-b4ba-41fe-9f74-4987df16c487 - Create coverage info - Arraystr

Access/execute codesys menu

2020-02-27T15:01:55.587000Z

I was experimenting with this system.commands["", ""] interface and I'm trying to figure out
where did you get those strings ("sil2_commands", "enter_debug_mode").

When i list all the commands i get the same guid but with different name:
b4c6c2d3-cfda-4a01-9065-e9ad98fadfa4 - "Enter debug mode..."

Could you tell me how can I get a list of the available/searchable tokens that can be searched for
using the IScriptCommands' [] get interface?

To be more excact: I'm trying to figure out how could I set and enable a breakpoint using the script.
I'm not sure if its managable at all (or available but just with limitation e.g. script executed under GUI).

Thanks!

Access/execute codesys menu

2020-02-27T15:01:53.893000Z

Originally created by: M.Schaber

Hi,

The ProcessScriptPrompts is only about the prompts issued by the script itsself, via system.ui - it is disabled by default so a script which disables ForwardSimplePrompts can still show its own prompts.

You need to "pre-answer" the prompts for the following reason: Command execution is synchroneous[1], like any other function or method call. Control only returns back to the script after the command is finished. So when the script lines after the command are executed, all prompts have already been shown. The only way to solve this is to preload the answers for the expected prompts[2].

[1] Even if it was asynchroneous, there'd be a race condition.

[2] Or to invent a time traveling device, of course...

HTH,
Markus

Access/execute codesys menu

2020-02-27T15:01:53.279000Z

Thank you again, I think I've managed it. I had to experiment a bit but just for the others who would like to do the same:

If I got it right

system.prompt_handling |= PromptHandling.ProcessScriptPrompts # this forwards prompts to script
system.prompt_handling &= ~PromptHandling.ForwardSimplePrompts # this silences other prompts
system.prompt_answers["EnterDebugMode_Prompt"]=PromptResult.OK # you have to put it before the execute
system.commands["sil2_commands", "enter_debug_mode"].execute(str(proj_device.guid))

What I did not understand is why I had to pre-answer a prompt but its working so far so I dont mind

Access/execute codesys menu

2020-02-27T15:01:52.653000Z

Originally created by: M.Schaber

Hi,

The key for the prompt_answers dictionary neds to be the message key of the dialog in question, not the command name.

The message key for the prompt in question is "EnterDebugMode_Prompt".

There's another dialog coming up later, which is a simple info dialog. You can either catch it using the message key "EnterDebugMode_Info_PlcEnteredDebugMode", or by unsetting the ForwardSimplePrompts flag - unsetting this flag simply suppresses all dialogs with only a single OK button and no choice to the user.

In general, you can learn about unknown message keys by setting the "LogMessageKeys" flag at the beginning of your script:

system.prompt_handling |= PromptHandling.LogMessageKeys

This will log all message keys to the message view.

In your case, there are two more message keys you could get: "EnterDebugMode_Error_PlcDeniesDebugMode" and "EnterDebugMode_Exception" - they can happen when something goes wrong.

HTH,
Markus

Recent posts to Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu

Access/execute codesys menu