nexatom-downloads

Data Connection

The UTT810 manages a high-bandwidth data connection over USB, offering distinct output modes tailored for realtime analysis or bulk offline storage.

FTDI USB 3.0 transport layer

Data is streamed from the FPGA to the host via an FTDI FT60x SuperSpeed USB 3.0 controller. The native SDK owns the D3XX transport, asynchronous read buffers, decoding and shutdown. Its buffers absorb short scheduling interruptions; they cannot guarantee loss-free capture when the sustained source rate exceeds transport, processing or storage capacity.

Sustained bandwidth depends on the host USB controller and SSD write speeds (if file saving is enabled). High-count-rate applications should use direct USB 3.0 ports on the host motherboard.

Output data type modes

The hardware data shuffler can be configured into one of four output modes, defined by nexatom_output_data_type_t:

Value	Constant	Description
`0`	`NEXATOM_OUTPUT_NO_OUTPUT`	Quiet measurement output; use this before changing saver configuration or leaving raw capture.
`1`	`NEXATOM_OUTPUT_ENCODED_TAGS`	Encoded time-tag output where advertised by the resolved profile.
`2`	`NEXATOM_OUTPUT_RAW_TAGS`	Time-tag stream for the native time-tag saver: BINARY (`.nxtt`), CSV or TAB. Processed measurement callbacks are not the raw event delivery interface.
`3`	`NEXATOM_OUTPUT_REALTIME_DATA`	Processed stream: supported CPS, telemetry, TIHI, MFCO and correlation packets are decoded and routed to registered callbacks/savers.

An enum value being defined does not mean every model implements it. Check supported_output_mode_mask in the connected profile and the relevant feature flag before enabling a mode or measurement engine.

C API

/* Set the output mode */
nexatom_tt_set_output_type(device, NEXATOM_OUTPUT_REALTIME_DATA);

/* Query the current mode */
nexatom_output_data_type_t current_mode;
nexatom_tt_get_output_type(device, &current_mode);

Python

from nexatomtt import NEXATOM_OUTPUT_REALTIME_DATA

device.set_output_type(NEXATOM_OUTPUT_REALTIME_DATA)
current_mode = device.get_output_type()

State transition rule. Changing the output mode should generally be done while the system is disabled (enable_system(False)) to prevent partial packet delivery. When switching out of RAW_TAGS file-saving mode, you must set NO_OUTPUT before disabling the file saving subsystem.

Performance monitoring

set_performance_monitoring is retained for compatibility and still has no effect in this SDK. It accepts a flag and may emit a diagnostic log, but it does not activate host throughput statistics or change acquisition, communication or telemetry behavior.

Enabling monitoring

Existing applications may continue calling it through C or Python:

nexatom_tt_set_performance_monitoring(device, true);

device.set_performance_monitoring(True)

Acquisition status structure

The public headers retain nexatom_acquisition_status_t and Python exposes the matching NexatomAcquisitionStatus record. There is no public getter/callback that supplies populated host statistics. To prove that a capture reached its file, use the file-saving statistics. The fields below explain the retained record layout, not measurements made available by enabling this flag:

Metric category	Fields	Description
Timing	`start_time_ms`, `elapsed_time_sec`	Session duration.
Event Statistics	`total_events`, `processed_events`, `dropped_events`	Retained event-counter fields; not populated through a public monitoring interface.
Channel Statistics	`channel_stats[8]`	Retained `event_count`, `count_rate`, `last_timestamp` fields.
Performance	`data_rate_mbps`, `processing_rate_meps`	Retained throughput fields; no live values are exposed.
Health	`is_keeping_up`	Retained status flag; do not use an initialized record as acquisition evidence.
File I/O	`file_saving_active`, `bytes_written`, `current_filename`	Retained writer fields; inspect actual saver results/files instead.

For a real capture, check returned errors, packet quality/error flags, saved-file contents and the instrument’s telemetry. Those are separate evidence sources: hardware CPS can remain nonzero even when a host capture is incomplete. See File Saving and Data Export for recording and checking individual time tags and processed packets.