This mesage seems unclear to me

[Henryp]

I'm not sure if I need to go to program mode manually and then back to run?

[BobO]

I'm not sure if I need to go to program mode manually and then back to run?

It's just warning you that you've made changes that cannot be downloaded in run mode. Designer won't let you do it wrong, we just didn't want you to be surprised that you can't do a run mode update.

[BobO]

Sorry, first response was from my phone over lunch. I always miss the details when I do that.

Not manually. When you attempt to download, Designer knows what needs to happen and handles it automatically.

[Henryp]

I still think this message is unclear and should be reworded
I'm in run mode and edit my serial configuration.
The message comes up and says can't write the change in run mode
Accepting these change requires switching to program mode.
 It appears that the message is telling me I need to take additional action other than the edit of my configuration , clicking ok, and acknowledge an advisor message.
The advisor message sounds like the change won't occur until I cycle the  run mode but does really say that and  then it say select yes to continue with your changes.
Maybe the message box should  have three choices
Apply the change now (this will switch to program and back to run mode)
Apply the change on the next cycle to runtime
Cancel the changes

[BobO]

This is clearly in the "no good deed goes unpunished" category.

The whole intention of the message is to make you aware that you have made a change that cannot be applied through a run mode update. Is has nothing to do with when and how the update is applied, just that run mode update is now no longer an option, and if that is critical to you, you may wish to cancel the change.

Since you cannot update the system configuration without also writing the program, it is really not possible to offer the update now option, without going into further details that will probably only confuse the matter further. Since it has caused so much confusion with so many people, I am inclined to remove it completely. Of course then we will start hearing from the folks that are mad that they can't do a run mode update after changing their serial config...

[rlp122]

Perhaps it just needs to say; "The PLC will need to stop the program cycle to complete this change.  All outputs will be turned off."  or some such message.

[BobO]

Yeah...but who needs to make that happen? ...and when does it happen? ...now? ...later?

We initially had a shorter message...and surprise, it got complaints. At least a couple wanted it removed completely. We felt that it was important to help folks know the significance of the change, and the current text was an effort to make it clearer. I am inclined to remove it and see how many folks complain.

[franji1]

We need to keep it in.  The ability to make RUN mode changes is HUGE in the applications that care about that capability.  Change the message/wording, but definitely do NOT remove it.

[Controls Guy]

I think the message is pretty good right now.  Might be slightly better to say "If you proceed, blah, blah, blah will happen" or something like that.

[ATU]

I agree, with Darth. I vote on keeping the text, but changing the last line to "Select YES to switch to PROGRAM MODE and update the PLC or NO to cancel.

[BobO]

I agree, with Darth. I vote on keeping the text, but changing the last line to "Select YES to switch to PROGRAM MODE and update the PLC or NO to cancel.

You would be writing everything to the PLC...program included...which requires a program check and all of the junk that goes along with it..and assumes that the changes you just made didn't break the program. I'm not sure that is the best choice.

[Controls Guy]

(1) I'm not suggesting you DO anything different, just proposing wording that might alleviate what seems to be some confusion on the part of users when they see the warning, so I don't see where any danger comes in there.

(2) If you're going to make one of these high-impact changes that requires a switch to program mode, rewrite the config and program, and restart, how ELSE can you do it but by doing that?  Are you suggesting it would be better to do a reload first, leaving the PLC in program mode, then require an explicit switch by the engineer from program to run mode?

I guess I'm not following your last comment.

[BobO]

It isn't complicated. The system config can only be downloaded in program mode. If you change it, on your next write to the PLC, DmD will automatically go to program instead of doing a run mode update. That's it.


My resistance to doing the download in the sys config dialog itself, is just that any time you update the sys config we also must update the program. Since the sys config changes can affect the program, possibly breaking it, it may be awkward to handle the many possible failures at that time, so I think it is best to not do so.

[plcnut]

Please don't remove the warning.
Alternate text idea:

You have just made changes to the System Configuration.
If you click "Yes", then the CPU will automatically go to program mode the next time you download the program.
If you click "NO" then the changes you made to the System Configuration will be discarded.