SCL-Templates fuer alle Typen mit Referenz-Aufrufstelle (Schritt 5)
- neue Templates: FB_ILS_MTRO_1Sep (TRO100), _Vario (TRO115), _Vario_workStation (TRO421), _1Sep2Swi (TRO267), _1Sep_SSCC (TRO105), _PinStore_Auto (TRO208); zusammen mit dem Pilot 1Sep1Swi 7 von 11 Typen. 2Sep1Swi, EmptyCarrBuffer, LoadingBoom, 2Sep2Swi bleiben generisch (keine reale Aufrufstelle) - scl_context: Felder nur fuer die Templates - Cognex-Verdrahtung je Scanner, part_sensor, carriers/data je Staubereich, jam_in/jam_out (dieselben Objekte wie erster Ein-/Ausgang), error_quit, automatic, is_border, correction_station, Bloecke sscc/work_station/store (PinStore: eine Linie je Speicherbahn aus dem Layout statt der 19 aus dem Katalog) - _macros: cognex_in/cognex_out/cognex, correction, todo_mehr - tests/test_scl_templates.py: Rundlauf je Template gegen seine Referenz (PinStore: von der Referenz abgekuerzte Teile ausgenommen); Normalisierung vereinheitlicht ":="/"=>"-Abstaende - Golden-Files *_templates neu geschrieben (gewollt: mehr TROs aus Templates); generische Golden-Files unveraendert - Doku: SCL_Templates.md (§6 Entscheidungen je Template, §11 Schritt 5, §13 offene Fragen 9-12), Python_Scripts.md, CLAUDE.md, README.md Zeilenentscheidungen sind Vorschlaege, noch mit den SPS-Kollegen zu bestaetigen. Geprueft: 39 Tests gruen, jede Rundlauf-Pruefung erkennt eine geaenderte Zeile; tro_flow --json + scl_skeleton --templates auf allen 8 CSVs ohne Fehler. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
5764df1ac8
commit
41df841317
@@ -485,11 +485,13 @@ per-project naming rules described in [`SCL_Templates.md`](SCL_Templates.md).
|
||||
**Templates (opt-in, `--templates [DIR]`).** With this switch every TRO whose FB
|
||||
has a template in `lib/scl_templates/<fbType>.scl.j2` (Jinja2) is rendered from
|
||||
it; the others keep the generic text above. The header and the console summary
|
||||
name which FB types came from a template. Today only the pilot
|
||||
`FB_ILS_MTRO_1Sep1Swi` exists — it follows the real call site of TRO107 line for
|
||||
line (priority manager `Dir2`, `stInSenJam<n>`, `xInCarouselRun1`, reference
|
||||
times 100/50 ms), and every value that is still open carries
|
||||
`TODO(E-Planung)`. `--strict` stops (exit `1`, no SCL) if any FB type has no
|
||||
name which FB types came from a template. Templates exist for the seven types
|
||||
with a real reference call site (`1Sep`, `1Sep1Swi`, `1Sep2Swi`, `1Sep_SSCC`,
|
||||
`Vario`, `Vario_workStation`, `PinStore_Auto`); each follows its call site in
|
||||
`doc/TRO_Katalog/scl_templates/` line for line, and every value that is still
|
||||
open carries `TODO(E-Planung)`. The line decisions are proposals to be confirmed
|
||||
by a PLC engineer (`doc/SCL_Templates.md` §6). `2Sep1Swi`, `EmptyCarrBuffer`,
|
||||
`LoadingBoom` and `2Sep2Swi` have no call site yet and stay generic. `--strict` stops (exit `1`, no SCL) if any FB type has no
|
||||
template. Without `--templates` the output is unchanged.
|
||||
|
||||
Tests: `tests/test_scl_context.py` (the derivations one by one),
|
||||
|
||||
Reference in New Issue
Block a user