yau-plant-assistant/db/seed/scada-source/his_group.qli
Claude 24afc51672 Take delivery of the corrected CI Server configuration
The point list handed over in August named the points PS_STN_WET_WELL_LEVEL
and the like. Those were never CI Server names. They came from
gen_scada_points.py on the PLC side, which describes its own output as "a
starting point for CI Server configuration, not a CI Server import file",
and the CI Server generator ignored them entirely - it names points from
its own address-keyed table. The names appear in no .qli export, and
nowhere else in the WRPS project at all.

This is the corrected delivery. ci-server-points.csv is keyed on the CI
Server ITEM each point feeds, with the Modbus station and the point name
beside it, so all four namespaces are visible in one row:

  LIT-101              instrument tag
  %QW0                 PLC symbol and address
  WRPS_PLC:STN_LEVEL   CI Server point - station, colon, point name
  AID.WRPS.STN.LEVEL   CI Server item - what the historian is keyed on

The 49 rows were joined onto the .qli exports by function code and Modbus
address: 49 matched, 0 unmatched. The item and point names are read from
the exports, not invented here.

The six .qli files come too, unchanged. gen_historian_items.py needs them,
and until now they existed only on one laptop behind a --wrps path - so
the one file the rules say must never be hand-edited could be regenerated
by exactly one person. 84 KB buys the team that back.

These are uncontrolled documents: no revision, no effective date, no
approval. The README says so, says how to ask for a fresh set, and records
the two things that bite - that PS_ survives legitimately as four poll
group names, and that his_group.qli and the live export disagree about the
sample rates, with the live one winning.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-01 19:00:20 +10:00

44 lines
1.3 KiB
Text

@LANGUAGE
ENGLISH
@VERSION
1.03.00
!==================================================================================================================================
@FIELDS
NAME,DESCRIPTION,START_TIME,STOP_TIME,FIRST_ROLLOVER
LIFE_TIME,WARN_TIME,ROLLOVER_INT,FORCE_ROLLOVER,FILL_OLD,STORE_QUALITY
SAVE_TIME,SCAN_INTERVAL,CORRECT_DAYLIGHT,EXCLUDE_ARCHIVE,DATA_COMP,AGG_PERIOD_HOUR
AGG_PERIOD_SHIFT,AGG_PERIOD_DAY,AGG_PERIOD_WEEK,AGG_PERIOD_MONTH,AGG_PERIOD_YEAR,AGG_PERIOD_30MIN
AGG_CORRECT_DAY_DST,AGG_CORRECT_SHIFT_DST,NUMBER,NODE,NODE_NAME,NEXT_UNIT_SEQ
NEXT_DATA_SEQ,AVERAGING_INTERVAL,PRIORITY,SAMPLES_RECORD,TYPE,AVERAGING_METHOD
COL_STOR_TYPE,AGG_SHIFT_LENGTH,AGG_WEEK_START,AGG_SHIFT_START,AGG_DAY_START,AGG_COMP_NOT_ITEM
@HIS_GROUP_DF
"WRPS_ONE_SEC","","","","21-08-2026 00:00:00",\
"7 days","","1 hours",0,0,1,\
0,1,0,0,0,1,\
0,0,0,0,0,0,\
0,0,50,1,"",1,\
2,0,8,0,"Item","",\
"Scan/Time","8 hours","Monday","00:00","00:00",""
"WRPS_ONE_MIN","","","","21-08-2026 00:00:00",\
"7 days","","6 hours",0,0,1,\
0,60,0,0,0,1,\
0,0,0,0,0,0,\
0,0,51,1,"",1,\
2,0,5,0,"Item","",\
"Scan/Time","8 hours","Monday","00:00","00:00",""
"WRPS_EVENT","","","","21-08-2026 00:00:00",\
"7 days","","1 days",0,0,1,\
0,0,0,0,0,1,\
0,0,0,0,0,0,\
0,0,52,1,"",1,\
2,0,11,100,"Item","",\
"Event/Item","8 hours","Monday","00:00","00:00",""