1.) Version of Configuration Tool being used: 2.8.10546
2.) Model Number of Unit: PV750T
3.) Operating System: Windows 7
4.) When attempting to set the real time clock in a configuration that was imported from v2.7, the module reboots after the update clock command but the clock comes up at 00:00 rather than at where it was set. This feature works in V2.7 using the same PV780T.

I can send the configuration privately if needed

Hello jclark,

Thank you for mentioning this. I'm not sure when the requirement was put into PowerVision Configuration Studio, but the RealTimeClock.Set.{variable} (sorry, I'm too lazy to type out all of the variable names, but you know what they are} need to all be set to the value required.

For example, if only the Hour is being changed, the other RealTimeClock.Set.{variables} will need to be set to the RealTimeClock.{variables} prior to sending the UpdateClock action.

In the standard configurations, all of the RealTimeClock.Set.{variables} are initialized to the RealTimeClock.{variables} when the settings page gets shown, the user changes what they need which sets the particular RealTimeClock.Set.{variables}, and the UpdateClock action is sent.

If this does not fix your problem, jclark, I'll be glad to help if you have additional questions.

Thank you Sara Talley, as usual, you are correct.