MADE 3.9.1 User Manual > Warnings & Errors
Errors
MADE displays errors in the Problems viewer to indicate inconsistencies in the
system model that would prevent simulation or module-related analyses from being
carried out correctly. The same type of error can appear multiple times in the problem
viewer but with different items associated with each.
[Image: problemView0.png]
Each warning is shown in a single row a description followed by its location in the
"Model" column. The same type of warning can appear multiple times in the
Problems viewer but with different items associated to each.
Error Types
The types of errors in the Problems viewer are listed in the table below:
| Error | Description |
|---|---|
| Incompatible bond graph type | Occurs on an energy connection when the source component and the target component of the connection have incompatible bond graph types. For example, if a component of type 0-C is connected to another component of type 0-C. When this error happens, it requires changing the bond graph type of one or both the components see dynamic modelling). |
| Invalid dynamic model | Occurs when the system diagram can not be converted into a valid dynamic model. This might be caused by assigning incorrect bond graph type to one or more dynamic components, or invalid energy connections among dynamic components. There is no such a simple way to solve this error. Users need to review their system diagram to fix the error. |
| Dynamic component functionally incorrect | Occurs on a dynamic component when one or more of the following causes happen in the dynamic function of the dynamic component: 1. There is zero or more than one out energy flows defined; 2. There is zero or more than one activated energy flow properties; 3. The nominal functional failure mode of this dynamic component has no incoming connections. To resolve the error, users need to make sure that they have one and only one out energy flow for a dynamic function. And that energy flow has be to activated either through making a flow connection or manual activation via the context menu. At last users need to connect the dynamic energy flow to another in energy flow within the same dynamic component. |
| Flow properties mismatched | Occurs on flow connection when the source flow from a component does not match the target flow from another component. A flow connection is the connection between functions of two components, the colour of such connection comes in red (energy), green(material) or blue(signal). An example will be connecting a non-dynamic function flow to a dynamic function flow. To resolve the error, users need to ensure that the source and target of a flow connection both have to be either dynamic or non-dynamic. |
| Invalid crossover function flow connection | Occurs when a "flow properties mismatched" error is triggered by switching dynamic functions; as a result of that, a flow properties of dynamic function is automatically crossed over to connect to another flow properties of a non-dynamic function from within the parent component of the given system diagram. |
| Missing function flow connection | Occurs when there is an energy connection between two dynamic components, but missing the corresponding flow connection which represents the function flow through them. |
| Orphan component | Occurs when a component has a valid bond graph type assigned to it (i.e. Not set as "undefined") but without any incoming or outgoing energy connection connecting from/to another dynamic component. |
| Missing Energy Connection | Occurs when there is no energy connection connecting to the port in the mux-bar of an assembly component. |
| Missing Dynamic Function | Occurs when a component has no dynamic function defined in its function definition. (See dynamic modelling guide). |
Source: Local MADE 3.9.1 installation: com.phm.made.help.plugin/documents/help/html/MADeHelp/16-WarningsErrors/16-02-Errors.html · retrieved 2026-07-09