# ConstantParameters
## `ConstantParameters` (PARAMS)
Attributes: : `qualified_only`
InOut:
| Scope | Name | Type | Initial | Comment |
| -------------------------------------------- | ----------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Constant |
gc\_iMaxAlarms
| `INT` | 300 | The number of maximum alarms; a high value can be used here because it is only used for the buffer size.
: Performance does not 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 boundary. So only the data between the boundaries will be used.
Please ensure this number is greater than or equal to your configured alarms from ALL alarm groups.
|
|
gc\_iMaxActiveAlarms
| `INT` | 300 | The number of maximum active alarms. It behaves the same 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 dynamically by using the Alarm Traversal Consumer.
Theoretically it can happen that all configured alarms become active, so for that reason the buffer should have the
same size as the maximum number 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: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://support.powerio.com/hub/codesys-hvac/en/hvac-alarm-library/datentypen/global/constantparameters.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.