Shared Runtime Logger and Calendar Groups

Use this page when runtime must collect measurement points in groups and save or send them according to a schedule.

Use groups to collect related measurement points that must be logged or sent together.
Define the group content first, then apply the required send or logging schedule to that same group number.
Keep each group small and purposeful so the resulting stored or sent data stays easy to understand.

Overview

GRPDATA# defines which measurement points belong to a group.
SENDGRPI# creates a weekly send schedule for a group.
LOGGRPI# creates interval-based logging for a group.
LOGGRPE# creates event-based logging for a group.

Group Content

GRPDATA# collects the measurement points used by a group. The group can then be used by calendar or logger functions.

Example: GRPDATA1 VR1,VRC
Up to 24 group definitions can be created.
Use the same group number across data setup and the related schedule.
Keep groups small and functional so it is clear which values are sent or logged together.

Parameter	Index	Range	Format	Default	Example
`GRPDATA#`	1..24	Measurement point list	Comma-separated list of data references	-	`GRPDATA1 VR1,VRC`

Calendar Sending

SENDGRPI# is used for weekly sending of grouped data.

The format follows D#,T#,G#.
D# is the weekday. Runtime accepts D0..D7; normal weekly use is D1..D7.
T# is the hour of day with the range T1..T24.
G# is the group number to send with the range G1..G24.
Example: SENDGRPI1 D1,T8,G1
Status from a stored rule is returned in the same format, for example D1,T8,G1.

Parameter	Index	Range	Format	Default	Example
`SENDGRPI#`	1..12	D0..D7, T1..T24, G1..G24	`D#,T#,G#`	-	`SENDGRPI1 D1,T8,G1`

This page defines when grouped data is sent. If the scheduled message must be delivered to specific recipients, configure the calendar recipient groups separately on Shared Runtime Recipients and Notifications.

Interval-Based Logging

LOGGRPI# saves grouped data at a fixed interval.

The format follows I#,T#,G#.
I# is the log definition id with the range I0..I127.
T# is the interval in minutes with the range T1..T32767.
G# is the group number to save with the range G1..G24.
Example: LOGGRPI1 I1,T60,G1
Status from a stored rule is returned in the same format, for example I1,T60,G1.

Parameter	Index	Range	Format	Default	Example
`LOGGRPI#`	1..12	I0..I127, T1..T32767, G1..G24	`I#,T#,G#`	-	`LOGGRPI1 I1,T60,G1`

Event-Based Logging

LOGGRPE# saves grouped data on defined events from digital, analog, or 1-Wire channels.

Use this only when interval-based logging is not sufficient.
The format follows <source>,S#,I#,G#.
<source> can be DR# for digital inputs, VR# for analog inputs, or OT# for 1-Wire channels.
Valid source ranges are DR1..DR127, VR1..VR64, and OT1..OT10.
S# is the event or state code. Runtime accepts S0..S3 for DR, S0..S28 for VR, and S0..S96 for OT.
I# is the log id with the range I0..I127.
G# is the group number with the range G1..G24.
Example: LOGGRPE1 DR2,S1,I10,G1
Status from a stored rule is returned as DR2,S1,I10,G1.

Parameter	Index	Range	Format	Default	Example
`LOGGRPE#`	1..24	DR/VR/OT source, S-state, I0..I127, G1..G24	`<source>,S#,I#,G#`	-	`LOGGRPE1 DR2,S1,I10,G1`

Best Practice

Create the group content with GRPDATA# first, and only then add the matching schedule or event rule.
Use consistent group numbers and keep an internal note describing what each group contains.
If there is no defined need for grouped logging or scheduled sending, leave these functions unused.