Visible to Intel only — GUID: nlx1686144027522
Ixiasoft
1. About the Drive-on-Chip Design Example for Intel Agilex® 7 Devices
2. Features of the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3. Getting Started with the Drive-on-Chip Design Example for Intel Agilex 7 Devices
4. Rebuilding the Drive-on-Chip Design Example for Intel Agilex 7 Devices
5. About the Scaling of Feedback Signals
6. Motor Control Software
7. Functional Description of the Drive-on-Chip Design Example for Intel Agilex 7 Devices
8. Signals
9. Registers
10. Design Security Recommendations
11. Document Revision History for AN 994: Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.1. Software Requirements for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.2. Hardware Requirements for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.3. Downloading and Installing the Design
3.4. Setting Up your Development Board for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.5. Configuring the FPGA Hardware for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.6. Programming the Nios V/g Software to the Device for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.7. Debugging and Monitoring the Drive-on-Chip Design Example for Intel Agilex 7 Devices with Python GUI
3.7.1. GUI Control Parameters Pane for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.7.2. GUI Main Panes for the Drive-on-Chip Design Example for Intel Agilex 7 Devices
3.7.3. Tuning the PI Controller Gains
3.7.4. Controlling the Speed and Position Demonstrations
3.7.5. Monitoring Performance
7.3.6.1. DSP Builder for Intel FPGAs Model for the Drive-on-Chip Designs
7.3.6.2. Avalon Memory-Mapped Interface
7.3.6.3. About DSP Builder for Intel FPGAs
7.3.6.4. DSP Builder for Intel FPGAs Folding
7.3.6.5. DSP Builder for Intel FPGAs Design Guidelines
7.3.6.6. Generating VHDL for the DSP Builder Models for the Drive-on-Chip Designs
Visible to Intel only — GUID: nlx1686144027522
Ixiasoft
3.7.5. Monitoring Performance
The Drive-on-Chip Design Example offers many way to monitor the performance.
- On the Trace area, under Trigger Signal, select the signal you want to trigger the trace data capture. If you select Always, the trigger is always active.
- Under Trigger Edge, select a trigger type:
- Level (trigger signal must match this value)
- Rising Edge (trigger signal must transition from below to above this value)
- Falling Edge (trigger signal must transition from above to below this value)
- Either Edge (triggers on both falling and rising edge conditions).
- Under Trigger Value, select the value that Trigger Edge uses to compare the signal value against.
- Click Update Trigger, if you update the Trigger Value.
- Under Trace Depth, select the number of samples to capture and display.
The GUI can store up to 4,096 samples. Select a lower number of samples to make The GUI update rate faster, and zoom in on the graph as the graph scale autosizes to the number of samples.
- Specify a Trace Filename.
The GUI saves the trace data saved to a .csv file.
- Click Start Trace to start the trace; click Disable Trace to stop the trace.
- Click Dump Data To CSV.