Know-How Protection prek API

Avtomatizirajte Know-How Protection v velikem obsegu

Know-How Protection v Siemens TIA Portal zaklene izvorno kodo bloka z geslom. Blok ostane viden v projektnem drevesu (ime, tip, javni vmesnik), vendar njegove notranje logike ni mogoče brati, izvoziti ali spreminjati brez gesla. T-IA Connect vam omogoča programsko uporabo te zaščite prek REST API, MCP orodij za AI asistente ali vgrajenega Copilot - vključno s serijsko zaščito za celotne projekte v nekaj sekundah.

1. korak: Identificirajte nezaščitene bloke

Seznam vseh blokov v vaši PLC napravi. Vsak blok vključuje polje isKnowHowProtected, ki prikazuje trenutni status zaščite.

curl http://localhost:9000/api/devices/PLC_1/blocks \
  -H "X-API-Key: your-api-key"

{
  "Success": true,
  "Data": [
    {
      "Name": "FB_Fill",
      "Type": "FB",
      "Number": 1,
      "Language": "SCL",
      "IsKnowHowProtected": false
    },
    {
      "Name": "FB_Drain",
      "Type": "FB",
      "Number": 2,
      "Language": "SCL",
      "IsKnowHowProtected": false
    },
    {
      "Name": "FC_Recipe_Manager",
      "Type": "FC",
      "Number": 10,
      "Language": "SCL",
      "IsKnowHowProtected": false
    },
    {
      "Name": "FB_SafetyMonitor",
      "Type": "FB",
      "Number": 3,
      "Language": "LAD",
      "IsKnowHowProtected": true
    }
  ]
}

2. korak: Prevedite napravo

Bloki morajo biti prevedeni, preden jih je mogoče zaščititi. Prevedite celotno napravo, da zagotovite, da so vsi bloki v veljavnem stanju.

curl -X POST http://localhost:9000/api/devices/PLC_1/actions/compile \
  -H "X-API-Key: your-api-key"

{
  "Success": true,
  "Message": "Compilation completed.",
  "Data": {
    "Errors": 0,
    "Warnings": 2
  }
}

3. korak: Uporabite Know-How Protection

Zaščitite blok tako, da navedete ime naprave, ime bloka in geslo. Geslo se prenaša varno in ga T-IA Connect nikoli ne shrani.

curl -X POST http://localhost:9000/api/devices/PLC_1/blocks/FB_Fill/actions/protect \
  -H "X-API-Key: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "password": "MySecretPassword123"
  }'

{
  "Success": true,
  "Message": "Block 'FB_Fill' is now know-how protected.",
  "Data": {
    "BlockName": "FB_Fill",
    "IsKnowHowProtected": true,
    "IsProtectable": true
  }
}

4. korak: Preverite status zaščite

Potrdite, da je bila zaščita pravilno uporabljena, tako da preverite podroben status bloka. Odgovor vam pove, ali je blok zaščiten in ali ga je mogoče zaščititi.

curl http://localhost:9000/api/devices/PLC_1/blocks/FB_Fill/protection \
  -H "X-API-Key: your-api-key"

{
  "Success": true,
  "Data": {
    "BlockName": "FB_Fill",
    "IsKnowHowProtected": true,
    "IsProtectable": true,
    "Reason": null
  }
}

curl -X POST http://localhost:9000/api/devices/PLC_1/blocks/actions/protect-batch \
  -H "X-API-Key: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "blockNames": ["FB_Fill", "FB_Drain", "FC_Recipe_Manager", "DB_Config"],
    "password": "MySecretPassword123"
  }'

{
  "Success": true,
  "Message": "3/4 blocks protected successfully.",
  "Data": {
    "TotalRequested": 4,
    "Succeeded": 3,
    "Failed": 1,
    "Details": [
      { "BlockName": "FB_Fill", "IsKnowHowProtected": true, "Reason": null },
      { "BlockName": "FB_Drain", "IsKnowHowProtected": true, "Reason": null },
      { "BlockName": "FC_Recipe_Manager", "IsKnowHowProtected": true, "Reason": null },
      { "BlockName": "DB_Config", "IsKnowHowProtected": true, "Reason": "Already protected." }
    ]
  }
}