Files
generalFunctions/src/configs/valve.json

306 lines
10 KiB
JSON
Raw Normal View History

2025-07-24 13:17:10 +02:00
{
"general": {
"name": {
"default": "valve",
"rules": {
"type": "string",
"description": "A human-readable name or label for this machine configuration."
}
},
"id": {
"default": null,
"rules": {
"type": "string",
"nullable": true,
"description": "A unique identifier for this configuration. If not provided, defaults to null."
}
},
"unit": {
"default": "m3/h",
"rules": {
"type": "string",
"description": "The default measurement unit for this configuration (e.g., 'meters', 'seconds', 'unitless')."
}
},
"logging": {
"logLevel": {
"default": "info",
"rules": {
"type": "enum",
"values": [
{
"value": "debug",
"description": "Log messages are printed for debugging purposes."
},
{
"value": "info",
"description": "Informational messages are printed."
},
{
"value": "warn",
"description": "Warning messages are printed."
},
{
"value": "error",
"description": "Error messages are printed."
}
]
}
},
"enabled": {
"default": true,
"rules": {
"type": "boolean",
"description": "Indicates whether logging is active. If true, log messages will be generated."
}
}
}
},
"functionality": {
"softwareType": {
"default": "valve",
"rules": {
"type": "string",
"description": "Specified software type for this configuration."
}
},
"role": {
"default": "controller",
"rules": {
"type": "string",
"description": "Indicates the role this configuration plays within the system."
}
},
"positionVsParent":{
"default":"atEquipment",
"rules": {
"type": "enum",
"values": [
{
"value": "atEquipment",
"description": "The node is connected at the equipment level and is responsible for controlling or monitoring the equipment as a whole."
},
{
"value": "upstream",
"description": "The node is connected in a downstream position, indicating it is responsible for monitoring or controlling processes that occur after the equipment's operation, such as product flow or output."
},
{
"value": "downstream",
"description": "The node is connected in an upstream position, indicating it is responsible for monitoring or controlling processes that occur before the equipment's operation, such as input flow or supply."
}
],
"description": "Defines the position of the measurement relative to its parent equipment or system."
}
}
},
"asset": {
"uuid": {
"default": null,
"rules": {
"type": "string",
"nullable": true,
"description": "A universally unique identifier for this asset. May be null if not assigned."
}
},
"tagCode":{
"default": null,
"rules": {
"type": "string",
"nullable": true,
"description": "Asset tag code which is a unique identifier for this asset. May be null if not assigned."
}
},
"geoLocation": {
"default": {},
"rules": {
"type": "object",
"description": "An object representing the asset's physical coordinates or location.",
"schema": {
"x": {
"default": 0,
"rules": {
"type": "number",
"description": "X coordinate of the asset's location."
}
},
"y": {
"default": 0,
"rules": {
"type": "number",
"description": "Y coordinate of the asset's location."
}
},
"z": {
"default": 0,
"rules": {
"type": "number",
"description": "Z coordinate of the asset's location."
}
}
}
}
},
"model": {
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"default": null,
2025-07-24 13:17:10 +02:00
"rules": {
"type": "string",
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"nullable": true,
"description": "Product model id (e.g. 'binder-valve-001'). Required at startup: the node looks the curve up via assetResolver.resolve('curves', model). Supplier/type/units are derived from the asset registry (assetResolver.resolveAssetMetadata) — do NOT save them on the node."
2025-07-24 13:17:10 +02:00
}
},
"unit": {
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"default": null,
2025-07-24 13:17:10 +02:00
"rules": {
"type": "string",
feat(registry): AssetResolver + diffuser supplier curves (Jäger / Aerostrip / PIK / PRK) Two related changes bundled together because the diffuser curve files only make sense once the registry namespace they live in exists. src/registry — new asset-metadata resolver: - AssetResolver with synchronous resolve(namespace, id) + lazy cache, async refresh() for future remote pulls. - FileBackend (per-id or single-file layouts, case-insensitive) and a stub HttpBackend (disabled unless EVOLV_ASSET_REMOTE=1). - Namespaces: curves, menu, monsterSamples, monsterSpecs, units. Menu namespace re-keys by inner softwareType + filename so editors that pass either string resolve to the same tree. - README explains how to add a namespace. - AssetCategoryManager (datasets/assetData/index.js) becomes a thin facade over the resolver so existing consumers don't move. - 246/246 tests pass — including the 39-test registry suite. datasets/assetData — file moves + new diffuser data: - modelData/*.json deleted; curves/*.json is the canonical home. - New diffuser.json menu tree with GVA, Jäger, Aquaconsult/Entec, PIK/PRK suppliers. - gva-elastox-r.json migrated from the inline _loadSpecs hardcode, re-tagged coverageBasis="bottom-coverage-pct" (the legacy 2.4 elements/m² was a prior mis-conversion; we can't recover the original % so it's a single-point curve under key "0"). - jaeger-jetflex-td-65-2-g-epdm-1000.json — extracted from the Jäger EPDM-1000mm SSOTE/DWP chart on the data sheet (vector-PDF read). SSOTE 8.20→6.40 %/m, DWP 25→48 mbar across Q 2-12 Nm³/h. Single coverage (vendor doesn't state test conditions). - aerostrip-phoenix.json — 4-coverage SOTE family at 4.75 m water depth (DD 5/10/15/20 %, flux 10-70 Nm³/h·m²) from the Entec/de Winter 2023-11-22 dataset; DWP curve from the 21 % @ 4.05 m chart. - pik300.json / prk300.json — 5-coverage SOTE + SSOTR (DD 5-25 %) with split DWP per model variant, water depth ≈ 4.0 m inferred from the SOTE↔SSOTR ratio in the source spreadsheet. src/configs/diffuser.json: - New asset.{model, assetTagNumber} block so the editor's selected model id survives validation. - diffuser.density description corrected to "Bottom coverage [%]"; default 2.4 → 15 (typical fine-bubble install). src/configs/{rotatingMachine,valve}.json: small alignment edits that came with the registry phase. src/menu/asset.js + src/menu/aquonSamples.js: rewritten as facades over assetResolver, keeping the editor-side cascade behaviour intact. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:12:13 +02:00
"nullable": true,
"description": "Deployment unit chosen by the user. Must appear in the registry's model.units list for this model. Validated at startup."
2025-07-24 13:17:10 +02:00
}
},
"accuracy": {
"default": null,
"rules": {
"type": "number",
"nullable": true,
"description": "The accuracy of the machine or sensor, typically as a percentage or absolute value."
}
},
"valveCurve": {
"default": {
"1.204": {
"1": {
"x": [0, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100],
"y": [0, 18, 50, 95, 150, 216, 337, 564, 882, 1398, 1870]
}
}
},
"rules": {
"type": "valveCurve",
"description": "the first parameter is kg (usually according to 1 normal cubic meter per hour acc. to din norm ) and the second parameter is the diameter in mm. The x values are the opening of the valve in percent and the y values are the KV values in m3/h. The KV value is the flow rate of water at a temperature of 20 degrees Celsius through the valve when it is fully open."
}
}
},
"mode": {
"current": {
"default": "auto",
"rules": {
"type": "enum",
"values": [
{
"value": "auto",
"description": "Machine accepts setpoints from a parent controller and runs autonomously."
},
{
"value": "virtualControl",
"description": "Controlled via GUI setpoints; ignores parent commands."
},
{
"value": "fysicalControl",
"description": "Controlled via physical buttons or switches; ignores external automated commands."
},
{
"value": "maintenance",
"description": "No active control from auto, virtual, or fysical sources."
}
],
"description": "The operational mode of the machine."
}
},
"allowedSources":{
"default": {},
"rules": {
"type": "object",
"schema":{
"auto": {
"default": ["parent", "GUI", "fysical"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sources allowed in auto mode."
}
},
"virtualControl": {
"default": ["GUI", "fysical"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sources allowed in virtualControl mode."
}
},
"fysicalControl": {
"default": ["fysical"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sources allowed in fysicalControl mode."
}
}
},
"description": "Information about valid command sources recognized by the machine."
}
}
},
"source": {
"default": "parent",
"rules": {
"type": "enum",
"values": [
{
"value": "parent",
"description": "Commands are received from a parent controller."
},
{
"value": "GUI",
"description": "Commands are received from a graphical user interface."
},
{
"value": "fysical",
"description": "Commands are received from physical buttons or switches."
}
],
"description": "Information about valid command sources recognized by the machine."
}
},
"sequences":{
"default":{},
"rules": {
"type": "object",
"schema": {
"startup": {
"default": ["starting","warmingup","operational"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sequence of states for starting up the machine."
}
},
"shutdown": {
"default": ["stopping","coolingdown","idle"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sequence of states for shutting down the machine."
}
},
"emergencystop": {
"default": ["emergencystop","off"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sequence of states for an emergency stop."
}
},
"boot": {
"default": ["idle","starting","warmingup","operational"],
"rules": {
"type": "set",
"itemType": "string",
"description": "Sequence of states for booting up the machine."
}
}
}
},
"description": "Predefined sequences of states for the machine."
}
}