fwlogo

List of Tutorials/Walkthroughs


 Quick Start Guide

 In-Depth Guides

 Hanger Configurations (no supplemental steel)

 Supplemental Steel

Copyright 2014 © Anvil EPS, an Anvil International Company

Troubleshooting and Error Handling in Forgeworx Pro

If this is your first time with Anvil Forgeworx Pro™, please see our Quickstart Documentation before proceeding.

All inputs will be made in the configurator screen; a walkthrough to this screen may be found here.

 Anvil Forgeworx Pro is a cutting edge application that integrates several emerging technologies into a single cloud based pipe support design system. There are many advantages to working in the cloud, however, one of the drawbacks is that more failure points have been introduced into the system beyond a simple desktop application. For example, local network traffic or heavy volume on your internet connection can slow down application performance.

There are two types of errors that can occur in Forgeworx: Application Errors

 An application error usually occurs when communication between the client and server is degraded. There are three errors of this type that are the most common: 'LoadProject' and 'SaveProject' errors prevent all mark numbers from being loaded to the UI display or mark numbers being saved to the project database. If you see these errors, confirm that you have a functioning internet connection, then logout and restart your Forgeworx session. Anvil recommends a network speed of at least 2 mbps.

Configuration Errors

 Configuration errors occur when Forgeworx cannot return a valid assembly. There are handled and unhandled errors.

Handled Errors

 A handled error takes place when the user attempts to enter an invalid input and Forgeworx cannot return a valid assembly. As an example, do the following:
    1. Enter the configurator
    2. Support type = Vertical Hanger
    3. Existing Beam = True
    4. Load = 98501
Note that when the default load of 100 lb is changed to 98501, Forgeworx removes the rod from the assembly and displays an error message at the bottom:
trouble1

This error was returned because the maximum load of a standard single rod assembly is governed by the Fig. 55 structural attachment, with a maximum load of 98500 lbs:

    1. Load = 98500
There is still an error with the clearance required to fit the components in the assembly:
    1. Existing Steel Elevation = 144
An assembly is returned:
    1. Vertical Movement = .5

The hanger components are removed because Anvil does not supply a standard spring or constant that is rated for a load of 98,500 lbs.

 This behavior is how Forgeworx deals with handled errors. It will remove components of the hanger assembly, disable outputs, and return an error message. Exiting to the project browser will save the data in the error state. A sketch or model will not be returned in a batch output for this hanger. You can change the data to a valid value in the configurator or in the project browser.

 There is no validation for values of input data in the project browser, only data type. If you enter the configurator in a handled error state, troubleshoot the configuration until a valid hanger is returned or contact Anvil for assistance here (LINK)



Unhandled Errors

 An unanticipated error inside of the configurator is an unhandled error. It is designated as unhandled because the application has not been designed to "handle" this error state. There are a near infinite number of permutations for configuration options, pipe size, component size etc... and unanticipated configurations will cause an unhandled error. As the application matures, the instances of unhandled errors will approach zero.

 Unhandled errors usually occur when the user attempts to configure a hanger at the support assembly level, and then changes a parameter at the hanger mark number level. As an example, selecting a beam clamp as a structural attachment type then increasing the load beyond the maximum allowed for that clamp is a typical workflow that could cause an error. The message "An ETO client error has occurred, returning to project browser" is displayed.

 The user is then prompted to save or cancel the hanger configuration. In most cases, the unhandled error state cannot be recovered by changing inputs because it is usually triggered by an input or series of inputs that cannot be repeated in the project browser. If the user chooses to save the hanger by hitting OK, most of the time the hanger must be deleted and re-started.

 This is why whenever possible, data should be entered into the project browser. Data entered into the project browser is automatically saved and should an unhandled error occur, it can always be retrieved. This way, only edits made in the configurator will not be saved, and the bulk of the information remains intact.


Back to top