Ux Report — User Report Operations

Allows to query, execute and generate user reports previously configured with the UC Command.

What is it for?

Use case	Description
📤 Automatic sending	Generate and send custom reports by events
🔍 Local query	Verify UC report content
⚡ Dynamic execution	Execute embedded commands in the report
📊 Periodic telemetry	Send combined data at intervals

Commands

Operation	Syntax	Description
Query	`QUn`	Read UCnn report content
Execute	`SUn`	Execute report as local command
Generate	`GUn[bb][c]`	Generate and send report to server

Key difference:

QUn → Only shows rendered content
SUn → Executes embedded commands in the report
GUn → Generates report and sends it to an IP destination

Parameters

Parameter	Description	Values
`n`	Report index	`0` to `F` (UC00-UC0F)
`bb`	Associated event number (only for G)	`00`-`FF`, `XX` = no event
`c`	Sending priority (only for G)	`H` = high, `M` = medium, `L` = low

Operations in Detail

Query (Q)

QUn — Query Report

Read and display the processed UC report content.


>QUn<

Response:


rendered_content

The response to QUn is exactly the rendered content of the configured UC structure, with no RUn prefix in front: for user reports, printmsg() copies the text as-is (strcpy(str, txt)). Don’t confuse it with RUn (the response to SUn, which does carry that prefix followed by OK/ERR).

Execute (S)

SUn — Execute Report

Execute the report as if it were a device command. Useful for triggering actions configured in the UC.


>SUn<

Behavior:

Processes the UC structure
Executes embedded commands
Returns local response (does not send to server)

Ideal for use in Event Engine rules when you need to execute a dynamically configured command sequence.

Generate (G)

GUn — Generate and Send

Generate the report and send it to a configured IP destination.


>GUnbbc<

Additional parameters:

bb → Associated event number
c → Report type

Result: The device immediately responds with the literal GOK, confirming that the command was accepted and the report was queued. The actual report content (same as QUn, without prefix) is what actually travels to the destination — it is not what’s returned as the direct response to the GUn command.

Event Engine Integration

Generate report on IGN ON


>SRL60E;TRG=IGN+;ACC={GU0XXH}<

Execute macro on digital input


>SRL61E;TRG=IN02+;ACC={SU1}<

Execute UC01 content when IN02 is activated.

Generate on speed limit


>SRL62E;TRG=VL00+;ACC={GU1XXH}<

Periodic sequence with timer


>STD05E00005<
>SRL96E;TRG=TD05+;ACC={GU0XXH}<
>SRL97E;TRG=TD05+;ACC={SU1}<

Generate UC00 and execute UC01 every 5 seconds.

Compatibility

💾Firmware v1.12.05

C5Legacy

💾Firmware v1.00.00

SP-IOT

SM-IOT

ZE-IOT