siemens/tia-portal-ai-extensions/safety-commissioning
Claude Code and agent skill by siemens/tia-portal-ai-extensions
- community
Checking that the SKILL.md file is still in the repository.
Safety commissioning for SINAMICS drives. Use when configuring PROFIsafe functions like STO and SImO, updating safety checksums, setting safety axis type, activating safety parameter bits, and managing acceptance tests.
Install
npx vskill@latest install siemens/tia-portal-ai-extensions/safety-commissioningSKILL.md
Safety Commissioning
Overview
Safety commissioning in SINAMICS drives configures PROFIsafe functions such as STO (Safe Torque Off), SImO (Safe Limited Operation), and other safety-related features. Access safety APIs through DriveFunctionInterface.SafetyCommissioning and DriveFunctionInterface.FunctionInUse. Activate safety functions by setting specific parameter bits (e.g., p9601.3 for Basic Safety, p9603.1 for PROFIsafe, p9604.0 for STO). After parameter changes, update safety checksums via UpdateCheckSums().
Required Namespaces
Required Assemblies
Siemens.Engineering.Base.dllSiemens.Engineering.Step7.dllSiemens.Engineering.Startdrive.dll
Common Patterns
SafetyCommissioning.UpdateCheckSums()
Description: Calculate and update safety checksums after safety parameter changes. This is mandatory after modifying any safety-related parameter to ensure the drive accepts the configuration.
Example:
Key Types and Methods:
SafetyCommissioning.UpdateCheckSums()— recalculates all safety checksums- Returns
boolindicating success or failure
FunctionInUse.SetSIAxisType
Description: Set the safety axis type (Rotary or Linear) via FunctionInUse. Required for safety functions that depend on axis kinematics (SImO, SLS, SMVO).
Example:
Key Types and Methods:
FunctionInUse— manages safety function activation stateSetSIAxisType(flag)— sets the axis type for safety calculationsRotaryLinearFlag.Linear/RotaryLinearFlag.Rotary— axis type enumeration
Safety Parameter Bit Activation (STO via p9604)
Description: Enable safety functions (PROFIsafe, STO) by setting specific parameter bits. This is the standard activation pattern for SINAMICS S120 safety functions.
Example:
Key Types and Methods:
p9603.1— PROFIsafe enable bitp9604.0— STO enable bitParameter.Bits[].Value— bit-level write access
Basic Safety PROFIsafe Activation (S120)
Description: Enable Basic Safety via p9601.3 bit on SINAMICS S120. This is a prerequisite for other safety functions.
Example:
Key Types and Methods:
p9601.3— Basic Safety enable bit (S120)- Must be set before activating individual safety functions
SafetyAcceptanceTestProvider
Description: Configure safety acceptance tests. The SafetyAcceptanceTestProvider exposes acceptance test parameters that must be confirmed before safety functions become active on the drive.
Example:
Key Types and Methods:
SafetyAcceptanceTestProvider— manages safety acceptance test state- Accessed via
SafetyCommissioning.SafetyAcceptanceTestProvider
Quick Reference
| Method/Pattern | Purpose | |
|---|---|---|
SafetyCommissioning.UpdateCheckSums() | Recalculate safety checksums | |
FunctionInUse.SetSIAxisType(flag) | Set rotary/linear axis type | |
p9601.3 = 1 | Enable Basic Safety (S120) | |
p9603.1 = 1 | Enable PROFIsafe | |
p9604.0 = 1 | Enable STO | |
SafetyAcceptanceTestProvider | Configure safety acceptance tests |
Related Files
- `drive-objects` — obtaining
DriveFunctionInterfaceto access safety APIs - `parameters` — parameter bit access pattern used for safety activation
- `telegrams` — safety telegram insertion (
InsertSafetyTelegram) is required for PROFIsafe - `networks-and-drivecliq` — PROFINET configuration for safety data exchange
Exception Handling
UpdateCheckSums()returnsfalseif the safety configuration is invalid. Check the return value and inspect safety parameters.- Safety parameter writes require the drive to be in an appropriate state. Writing while online may throw
EngineeringException. SetSIAxisType()may fail if safety functions are already active. Deactivate the drive before changing axis type.- Always set
p9601.3(Basic Safety) before enabling individual safety functions (p9603.1,p9604.0). The order matters. SafetyAcceptanceTestProvideroperations may require additional validation. Check the provider state before modifying acceptance tests.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingopenness_development/skills/safety-commissioning/SKILL.md
Popularity
- Repository stars
- 10
- Repository forks
- 2
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/siemens/tia-portal-ai-extensions/safety-commissioning)