wcQueue.sim

RF event ingestion & report-trigger console

SIM T+ 00:00.0

wcQueue depth

0/ 256
threshold
near full
Arrived0
Dropped0
Reports0
Since last report
Published0
Buffered0

Gateway PSRAM EXT_RAM_BSS_ATTR

0 KB of 8 MB
within budget

    All seven buffers scale with WC_QUEUE_CAP above — the base64 switch traded hex's larger text buffers for extra raw-byte scratch space (see mNodeEventsRawBytes). CONFIG_SPIRAM_TYPE_AUTO detects the populated module at boot; 8 MB is this board's known module size.

    Azure D2C payload azureIotSendD2cMessage

    0 KB of 256 KB
    within limit
    Last report
    Worst case at current cap
    Oversized reports 0

    Azure IoT Hub hard-caps device-to-cloud messages at 256 KB regardless of tier. The firmware's own MESSAGE_PAYLOAD_CAP (24 KB) is declared in nexa.c but isn't currently checked anywhere before send.

    Telemetry buffer /ext/buf

    tmp.raw 0 KB of 660 KB
    External flash used 0 KB of 16 MB
    min free
    Upload idle
    Chunks queued0
    Rotations0
    Uploaded0
    Evicted0
    • No finalized chunks yet.

    Finalized chunks name as {startTime}_{endTime}_{uuid}.gz and upload to {deviceId}/telemetry/{uuid}.gz in blob storage. Only one chunk uploads at a time, and it's protected from eviction while reserved — see the "chunk reservation" logic in telemetryBuffer.c. telemetryBufferFlush() also force-rotates whatever's in tmp.raw — even under the size threshold — on every connect and disconnect, not just when it fills up.

    Depth over time

    • threshold
    • interval
    • near full
    • queue full
    • exception

    Report log

    Waiting for the queue to reach a report trigger…