Output

This function block shows a human-readable, serialized view of the data coming into it. It is intended for inspecting runtime values, quick debugging, and lightweight on-screen logging of data produced by other function blocks.

📥 Inputs

Generic This input socket accepts any data (numbers, text, lists, dictionaries, image metadata, detection results, etc.) from other function blocks.

📤 Outputs

This function block does not produce any output sockets. It is a display-only block.

🕹️ Controls

Output Display A resizable text area that shows the serialized representation of the incoming data. It collects and appends entries during each run and updates the view for easy inspection.

⚙️ Running mechanism

• At the start of a run the block clears its internal display buffer so each run shows only that run's entries.

• During the run each incoming value is converted into a readable, indented text representation and appended to the buffer.

• At the end of the run the combined text is shown in the Output Display so you can review all collected entries in sequence.

This makes the block useful to monitor how data changes during a scenario without saving files.

✨ Features

• Human-readable, indented serialization for quick inspection of complex data structures.

• Converts non-display-friendly values into readable text so the display remains informative.

• Accumulates entries during a run, showing a timeline of values produced.

• Resizable display area for long records or multiple entries.

📝 Usage Instructions

1. Connect a producing block (for example, a detection or processing block) to the Generic input.

2. Run the scenario. The Output Display will populate with a readable representation of the incoming data for the current run.

3. Use the display to verify data structure, counts, coordinates, and other metadata before wiring data to persistent storage or network blocks.

💡 Tips and Tricks

• Use this block together with detection or analysis blocks to inspect their outputs:

  • Connect outputs from Object Detection, Object Detection - Custom, Mask Detection, Pose Estimation, Object_Detection_Tracker or Find Object into this block to quickly view counts, positions and other result details.

• When you want to persist or transmit the data you inspected here, pair it with:

  • CSV Export to write tabular data to files,

  • Data to JSON to assemble structured JSON logs,

  • REST API - Post or MQTT Publish to send the inspected data to servers or message brokers,

  • Image Logger or Image Write when you also need to save visual evidence.

• For quick debugging alongside visual checks, use Show Image in parallel: inspect images while viewing detection metadata in this block.

• Use Debug Input to cross-check what is logged vs. what appears in your program logs.

🛠️ Troubleshooting

• Nothing appears in the display:

  • Ensure a producing block is connected to the Generic input and that it outputs data during the run.

• Very long records are hard to read:

  • Consider saving structured data using CSV Export, Data to JSON or sending it to a server with REST API - Post for post-run analysis.

• Data looks abbreviated or not as expected:

  • Confirm the producing block's output type (for example, counts, lists, dictionaries) and inspect that block (e.g., Object Detection, Mask Detection) to ensure it is producing the expected fields.