Docs
SupportCommunityAPIContact
Search…
Introduction
Motion Controllers
RMP (EtherCAT)
Getting Started
Features
Backlash Compensation
Camming
Compensator
Capture/Probe
Cartesian Robot
Configuration
Event Notification
Error Logging
Feedback
Feed Rate
Firmware Memory Allocation
Gantry
Gearing
Helper Functions
Homing
IO
Jitter
Joystick Control
Motion
Motion Controller
Network
Phantom Axes
Position Error
Motion Hold
User Limits
Streaming Motion Sync Outputs
Real Time Triggers
Recorder
Safety over EtherCAT
Settling
Status and Faults
Tuning
RapidGCode
RapidSequencer
Software APIs
Software Tools
Other
CUSTOMER TOOLS
RapidPortal
Other
Sample UIs
Powered By GitBook
Recorder

What is a Recorder?

A Recorder object provides a mechanism to collect and buffer any data (positions, velocities, etc) in the controller’s memory. After a recorder is configured and started, the controller copies the data (positions, velocities, etc) from the specified addresses to a local buffer for every “N” sample. Later, the host can collect the data by polling or via interrupt-based events.

How Many Data Objects Can a Recorder Hold?

The controller supports up to 64 data recorders, which can each record data from up to a total of 32 addresses in each sample. The buffers can be dynamically allocated. A larger data recorder buffer may be required for higher sample rates, slow host computers, when running via client/server, or when a large number of data fields are being recorded.
In case the data recording length is greater than the memory available to the recorder, the recorder can be configured to use a circular buffer and the host PC is only required to copy the recorded data to RAM faster than the recorder circular buffer rolls over. On most systems, this is not an issue.

Can I Trigger a Recorder When a Condition is Met?

A recorder can be started or stopped from the host application or from the controller by configuring a data recorder trigger. When the trigger conditions are met, the controller will automatically start or stop a data recorder. This is very useful for logging relevant variables during the period preceding a fault or error. Normally, the recorder stops collecting data when the buffer is full. It can also be configured to continuously collect data, overwriting the previous data until it is commanded to stop. This is useful for trapping a recent history of controller data.
​
Previous
Real Time Triggers
Next
Safety over EtherCAT
Last modified 2mo ago
Export as PDF
Copy link
Outline
What is a Recorder?
How Many Data Objects Can a Recorder Hold?
Can I Trigger a Recorder When a Condition is Met?
📜 Recorder Sample App (C#)