> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/springs-data/toc161393906.md).

# Nodal Springs

How to enter nodal spring coefficients and non-linearity flags in a spreadsheet in ENERCALC 3D.

Tables > Springs > Nodal Springs prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-6dca9dbf181d0a7f47f063b2aba9a61715635ac3%2FFASTFR~1_img151.png?alt=media)

It allows you to enter nodal springs in a spreadsheet. Each nodal spring includes the node ID, the spring non-linearity flag and six spring coefficients Kx, Ky …, Koz. The node ID must be valid (defined).

The spring flag is a string of 6 characters representing the spring non-linearity in three translational DOFs (Dx, Dy, Dz) and three rotational DOFs (Dox, Doy, Doz). For each character in the flag, enter ‘0’ if the restrained DOF is linear, ‘1’ if compression-only and ‘2’ if tension only. For the unrestrained DOFs, just enter 0s for the corresponding spring coefficients.

An empty row is allowed if all rows below it are empty. Selected rows (whole row must be selected) may be cut by clicking the button “Cut Selected Rows”.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/springs-data/toc161393906.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
