Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: RBPLC on February 23, 2023, 08:20:32 AM
-
BRX in RUN mode. Configuring a remote EBC that is currently not online. When I make stop-mode edits I get the warning dialog box about the CPU being unable to switch to RUN mode. CPU shows RUN mode and is executing when I close dialog box. EBC is setup in configuration to keep BRX in RUN mode on slave error and not required to be online to enter RUN mode. The operation of the CPU appears to be correct, it just looks like the warning dialog is being called incorrectly.
-
I think the warning is telling you that when you tweak the System Configuration, you are unable to do a RUN MODE EDIT - i.e. in order to update the System Configuration on the next Write to PLC, Designer will put the PLC in Program mode, then put it back in RUN mode.
When a PLC goes to PROGRAM mode, all Outputs go to OFF/0. For many installations, this is not an issue, especially during development. But some installations, this is CRITICAL, hence the user needs to figure out a good time to update the PLC (i.e. when the machine's outputs can all go OFF).
You can typically do RUN MODE EDITs by tweaking the PROGRAM and/or DOCUMENTATION. However, System Configuration changes cannot be "bumpless".
-
On program to run, the PLC waits (in program) for up to 15 seconds for remote I/O to come online, even when it's set to stay in run on slave failure. My guess is that the dialog is concluding that the PLC didn't ever go to run mode, because it isn't waiting that long. Yeah, technically a bug, but I'm not super offended in this case.
-
I think the warning is telling you that when you tweak the System Configuration, you are unable to do a RUN MODE EDIT - i.e. in order to update the System Configuration on the next Write to PLC, Designer will put the PLC in Program mode, then put it back in RUN mode.
When a PLC goes to PROGRAM mode, all Outputs go to OFF/0. For many installations, this is not an issue, especially during development. But some installations, this is CRITICAL, hence the user needs to figure out a good time to update the PLC (i.e. when the machine's outputs can all go OFF).
You can typically do RUN MODE EDITs by tweaking the PROGRAM and/or DOCUMENTATION. However, System Configuration changes cannot be "bumpless".
This isn't what I was referring to. It's what BobO described below. I can live with it as long as it's actually going to RUN mode.