> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/codesys-hvac/hvac-alarm-message-library/datentypen/global/constantparameters.md).
# ConstantParameters
## `ConstantParameters` (PARAMS)
Attributes: : `qualified_only`
InOut:
| Scope | Name | Type | Initial | Comment |
| -------------------------------------------- | ----------------------------- | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Constant |
gc\_iMaxAlarms
| `INT` | 300 | The amount of maximum alarms, a high value can be used here because it’s only used for the buffer size.
: Performance doesn’t depend on this parameter. It depends on the size of configured alarms in the alarm group.
There is a Pointer to the lowest and the highest border. So only the data between the borders will be used.
Please make sure, this number is higher or equal to your configured alarms, from ALL alarm groups.
|
|
gc\_iMaxActiveAlarms
| `INT` | 300 | The amount of maximum active alarms. It has the same behaviour as the parameter “gc\_iMaxAlarms”.
: The difference between them is, that this parameter defines the max size of active alarms. But we fill the
Buffer dynamicly by using the Alarm Traversal Consumer.
Theoretically it can happen, that all configured alarms will be active, so in fact of this the buffer should have the
same size as the maximum amount of active alarms.
| |
|
gc\_xAlarmFloodPortal
| `BOOL` | TRUE | Flood alarm suppression (activates when FIFO memory is full
for the portal)
| |
|
gc\_iMaxAlarmsPortal
| `INT` | 5 | Number of alarms to be transmitted to the portal | |
|
gc\_iChangeTimeAlarmsPortal
| `TIME` | TIME#3s0ms | Switchover time for portal string (alarm and pause time) | |
|
gc\_iMaxPolicyRules
| `INT` | 4 | Max Policy Rules | |
|
gc\_iMaxGroupRules
| `INT` | 4 | Max Group Rules | |
|
wsDefaultPolicyName
| `WSTRING` | “Policy 1” | Default Policy Name | |
|
wsDefaultGroupName
| `WSTRING` | “Group 1” | Default Group Name | |
|
xActivateAlarmByDefault
| `BOOL` | TRUE | Activate Alarm By Default | |
|
gc\_sHVACInstanceStaticString
| `STRING` | ‘HVAC-Mail-ID: a102101a-cb2b-44e8-a483-8e9185217659’ | HVAC Instance Static String | |
|
gc\_iMaxBodyMessageSize
| `INT` | 4096 | Max Body Message Size | |
---
# 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://support.powerio.com/hub/codesys-hvac/hvac-alarm-message-library/datentypen/global/constantparameters.md?ask=&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.