Wie kann ich das in KOP machen

Keine Ahnung... nur mal das Bild in die gängigen AI Modell hoch geladen und was mit SPS gebrabbelt...


I cannot directly create an SPS program based solely on an image. Programming an SPS (Speicherprogrammierbare Steuerung - Programmable Logic Controller) requires a detailed understanding of the desired logic, including:

  1. Inputs: What signals are coming into the PLC? (e.g., button presses, sensor states).
  2. Outputs: What devices does the PLC control? (e.g., motor, lights).
  3. States/Modes: How should the system behave in different situations (e.g., open, closed, stopping, emergency stop)?
  4. Sequencing: In what order should actions occur?
  5. Safety Interlocks: What conditions must be met to prevent unsafe operation?
  6. Timers/Counters: Are there any time-based or count-based operations?
However, based on the image you provided, I can describe the components and basic functionality and then outline a conceptual SPS program structure in plain language.

Components and their assumed functions from the image:

  • Motor: Controls the movement of the rolling gate (Auf/Ab - Up/Down).
  • S1 unten (Sensor 1 Bottom): Limit switch, detects when the gate is fully closed/down.
  • S2 mitte (Sensor 2 Middle): Position sensor, indicates the gate is at a middle position (might be for obstacle detection or partial opening).
  • S3 oben (Sensor 3 Top): Limit switch, detects when the gate is fully open/up.
  • Lichtschranken (Light Barriers): Safety sensors, likely detect obstacles in the gate's path (e.g., when closing).
  • S0 NOT-AUS (Emergency Stop): Button to immediately stop all operations.
  • S4 Ab (Button Down): Button to close the gate.
  • S5 AUF mitte (Button Up Middle): Button to open the gate partially or to a specific middle position.
  • S6 AUF oben (Button Up Top): Button to open the gate fully.
Conceptual SPS Program Structure (in general terms, not specific PLC language like LAD, FBD, SCL):

Here's a breakdown of the logic for a typical rolling gate, incorporating the elements from your image.

I. Inputs:

  • I0.0 (S0) NOT-AUS (Emergency Stop) - Normally Closed (NC)
  • I0.1 (S1) unten (Gate Closed Limit Switch) - Normally Open (NO)
  • I0.2 (S2) mitte (Middle Position Sensor) - NO
  • I0.3 (S3) oben (Gate Open Limit Switch) - NO
  • I0.4 (Lichtschranke) Light Barrier 1 - NC (or NO, depends on logic, but NC is common for safety)
  • I0.5 (Lichtschranke) Light Barrier 2 - NC
  • I0.6 (S4) Ab (Button Close) - NO
  • I0.7 (S5) AUF mitte (Button Open Middle) - NO
  • I1.0 (S6) AUF oben (Button Open Full) - NO
II. Outputs:

  • Q0.0 Motor_Auf (Motor Up Direction)
  • Q0.1 Motor_Ab (Motor Down Direction)
  • Q0.2 Status_LED_Auf (e.g., green for open)
  • Q0.3 Status_LED_Ab (e.g., red for closed)
  • Q0.4 Störung_LED (Fault/Error LED)
III. Internal Flags/Memory Bits:

  • M0.0 Tor_in_Bewegung (Gate in Motion)
  • M0.1 Tor_Offen (Gate is Fully Open)
  • M0.2 Tor_Geschlossen (Gate is Fully Closed)
  • M0.3 Tor_Mitte (Gate is at Middle Position)
  • M0.4 Fehler_Lichtschranke (Light Barrier Fault)
  • M0.5 Befehl_Auf_Voll (Command Open Full)
  • M0.6 Befehl_Auf_Mitte (Command Open Middle)
  • M0.7 Befehl_Ab (Command Close)
IV. Main Logic Sections:

1. Emergency Stop (Highest Priority):* If S0 NOT-AUS is pressed (input is 0 if NC), immediately turn off Motor_Auf and Motor_Ab.* Set a Störung_LED or error flag.* No other operation should be possible while NOT-AUS is active.

2. Safety Interlocks (Light Barriers):* If Motor_Ab is active AND Lichtschranke 1 OR Lichtschranke 2 is interrupted (obstacle detected):* Turn off Motor_Ab.* Potentially activate Motor_Auf for a short duration (reversal) or just stop.* Set Fehler_Lichtschranke flag.* Prevent further closing until the obstacle is clear.

3. Gate State Management:* Tor_Offen := S3 oben AND NOT Tor_in_Bewegung (Gate is fully open and stopped).* Tor_Geschlossen := S1 unten AND NOT Tor_in_Bewegung (Gate is fully closed and stopped).* Tor_Mitte := S2 mitte AND NOT Tor_in_Bewegung.* Tor_in_Bewegung := Motor_Auf OR Motor_Ab.

4. Open Gate Logic:* Full Open (S6 AUF oben):* If S6 AUF oben is pressed AND NOT Tor_Offen AND NOT Tor_in_Bewegung AND NOT NOT-AUS:* Set Befehl_Auf_Voll.* If Befehl_Auf_Voll is set AND NOT S3 oben:* Turn on Motor_Auf.* Turn off Motor_Ab.* If S3 oben is reached:* Turn off Motor_Auf.* Reset Befehl_Auf_Voll.* Partial Open (S5 AUF mitte):* If S5 AUF mitte is pressed AND NOT Tor_Mitte AND NOT Tor_in_Bewegung AND NOT NOT-AUS:* Set Befehl_Auf_Mitte.* If Befehl_Auf_Mitte is set AND NOT S2 mitte:* Turn on Motor_Auf.* Turn off Motor_Ab.* If S2 mitte is reached:* Turn off Motor_Auf.* Reset Befehl_Auf_Mitte.

5. Close Gate Logic:* Close (S4 Ab):* If S4 Ab is pressed AND NOT Tor_Geschlossen AND NOT Tor_in_Bewegung AND NOT NOT-AUS AND NOT Fehler_Lichtschranke:* Set Befehl_Ab.* If Befehl_Ab is set AND NOT S1 unten AND NOT Fehler_Lichtschranke:* Turn on Motor_Ab.* Turn off Motor_Auf.* If S1 unten is reached:* Turn off Motor_Ab.* Reset Befehl_Ab.

6. Motor Control Logic (Final Output Assignment):* Motor_Auf output is active IF (Befehl_Auf_Voll OR Befehl_Auf_Mitte) AND NOT NOT-AUS AND NOT S3 oben (or S2 mitte for partial open).* Motor_Ab output is active IF Befehl_Ab AND NOT NOT-AUS AND NOT S1 unten AND NOT Fehler_Lichtschranke.

7. Status Indicators:* Status_LED_Auf := Tor_Offen.* Status_LED_Ab := Tor_Geschlossen.* Störung_LED := NOT-AUS OR Fehler_Lichtschranke.

Important Considerations for a Real PLC Program:

  • Debouncing: Input buttons often need debouncing (timers to filter out spurious signals from mechanical contacts).
  • Interlocks: Ensure that Motor_Auf and Motor_Ab can never be active simultaneously.
  • Timeouts: What if a limit switch fails? Add timers to detect if the gate takes too long to reach a position, indicating an error.
  • Manual Override/Maintenance Mode: Sometimes a way to manually jog the gate is needed for setup or troubleshooting.
  • Homing/Initialization: How does the gate behave on power-up? Does it need to move to a known home position?
  • Specific PLC Language: This conceptual outline needs to be translated into a specific PLC programming language (Ladder Diagram, Function Block Diagram, Structured Text, etc.) which has its own syntax and rules.
  • Edge Detection: For button presses, you often want to detect the "rising edge" (moment of press) rather than the continuous state of the button.
This description provides a solid foundation for designing an SPS program for your rolling gate system. You would then implement this logic using your chosen PLC hardware and programming software.
 
Zuviel Werbung?
-> Hier kostenlos registrieren
Heute ist Donnerstag ;)

als erstes wie bei solchen Fällen, einmal zuerst die Funktionsbeschreibung mal verbal niederschreiben und dann daraus ein Code für die PLC erzeugen. Am besten dabei Funktionsgruppen bilden und diese entsprechend beschreiben!

Heute hilft da sogar die KI und erledigt das meiste (MS Copilot und ChatGPT), wenn man dieser genug Infos eintippt!
 
Zuviel Werbung?
-> Hier kostenlos registrieren
Boxy schrieb:
Bisschen sollen die ja etwas dabei lernen ;)
Zum Vergrößern anklicken....

Gefühlt verschlechtert sich das immer weiter. Früher war es z.B. normal bei Fragen zu posten, was man bereits gemacht hat. Mittlerweile wird einer KI die Frage gestellt und der nicht funktionierende entstandene Code wird uns dann zum Fraß vorgeworfen. Der OP sagt dann aber auch nicht, dass der Code von einer KI stammt.
 

Similar threads

Jochen Kühner
TIA Gute Idee für Algorithmus zum zeichnen von KOP/FUP
Antworten
10
Aufrufe
1K
Maagic7
M
KellerIQ
Suche SPS-Projekte zur Mitarbeit neben dem Beruf
Antworten
1
Aufrufe
640
Onkel Dagobert
Onkel Dagobert
S
TIA TIA 16 Initialisierung von Startwerten mit KOP
Antworten
3
Aufrufe
619
Sepp1962
S
R
Binärlogik in SCL / ST
3 4 5
Antworten
88
Aufrufe
23K
Blockmove
B
U
TIA Pointer auf E/A-Bereich ohne AWL
Antworten
13
Aufrufe
1K
upgrayedd1
upgrayedd1
Zurück
Oben