1.) Version of Configuration Tool being used: 2.7.10324 (Release Build)
2.) Model Number of Unit, PV750, Pv450, etc: PV450
3.) Operating System: Windows 7 Professional 64-bit
4.) Clear and accurate instructions so we may recreate and troubleshoot the issue.

I don't have the exact text from the exception/error but it just happened for a 5th time.

Originally it appeared if I left PowerVision Configuration Studio 2.7.10324 open for >24 hours, that the error would show up. However, this time it was only open for 20 minutes, and while I had been saving rigorously -- that doesn't matter when the error makes the configuration unusable.

The error that pops up states something along the lines of "Cannot create new gaurd page on the stack" (again, not exact text in front of me). Pressing OK will imediately close PowerVision. Upon re-opening, the configuration you last used will not be in the list of configurations, and if you browse to import it, nothing will happen when you select the file(and the file size of the last used configuration is considerably smaller than the others, ~350kb smaller.)

The only other thing to note is that the error usually pops up when I'm alt tabbed in another program. I very often have Visual Studio 2012 open alongside PowerVision.

Another item to note: In regards to this issue I've been trying to make backup configurations to resort to as this error has occured several times, but having to make a completely new configuration for each back-up is beginning to use a lot of space, is there anyway to look into a more backup friendly form of saving the configurations?

Any help would be appreciated.

Update: The actual text of the error is: "A new guard page for the stack cannot be created." (I opened powervision and left my computer for 2 hours for meetings, came back and the error was up)

If you save your configuration after the error has popped up, and prior to hitting "okay" (since the program is going to close when you do) - it corrupts the configuration from what I can tell.

It sounds like a bug we found in test just a few days ago. We have a fix that will be incorporated into the first patch. The bug occurs when PowerVision is not able to contact a display for a LONG period of time. It's error condition can cause an abnormally large call stack and crash (or other behaviors) PowerVision.

There are also two workarounds.

1) Keep a display connected. Connecting a display will prevent the stack overflow condition that your seeing.

2) When not connected to a display, turn off Hardware Device Checking in the About Window. This stops the polling interval and prevents the overflow.

We will get this corrected very soon.

For now I have disabled the "Hardware Connection Checking" (which i had to expand the about window to find), that I know of we don't connect to a display through powervision period, and at least from what i've read and/or been taught by the previous HMI programmer here, we have not tried to do so or been introduced to the benefits of doing so?

Is there information about connecting to the displays through powervision available?

Thank you for the help by the way!!

There are a lot of benefits... mostly in productivity. Also, compiling Scripts to find errors requires a unit connected, also you can directly load the display and not shuffle files onto USB drives. Also there are some new tools such as Remote Diagnostics and Debug Console that require a connection. For more details the Core manual has info on how to connect to the display and details on features that use the connection.

I guess I need further details regarding the "Core Manual" -- no literature was shipped with our recent purchase of the PV780's and I can't find it in the .pdf's available on the product page here: http://www.fwmurphy.com/products/displays/pv780

Sorry, I didn't' mean to confuse. Here is a link to a post which points to the latest Documentation and Examples as well as the final release version of PowerVision 2.7.

viewtopic.php?f=3&t=870

This is where we post all releases and patches as they are available. The links on the main site often lag as the marketing folks work through their press releases and verbiage etc. This forum is intended to provide the fastest way to get our customers the software and we are allowed to bypass a number of normal processes (such as burning CD's) to get our releases out here quickly.