Difference between revisions of "GraniteCore"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
(→Argon architecture) |
(→Argon architecture) |
||
| Line 17: | Line 17: | ||
**State of physical inputs (enable, clear faults, hall sensors etc) | **State of physical inputs (enable, clear faults, hall sensors etc) | ||
**SimpleMotion V2 commands to read/write parameters | **SimpleMotion V2 commands to read/write parameters | ||
| − | *Interface different types [[Feedback devices|feedback devices]] and [[setpoint inputs]] | + | *Interface different types [[Feedback devices|feedback devices]] and [[Setpoint signal|setpoint inputs]] |
*Handle SimpleMotion V2 communication | *Handle SimpleMotion V2 communication | ||
*Display device state via digital outputs and [[Argon LED indicators|LED indicators]] | *Display device state via digital outputs and [[Argon LED indicators|LED indicators]] | ||
Revision as of 21:30, 24 June 2013
GraniteCore a.k.a. GC is the motor control core developed for Argon (servo drive).
Argon architecture
Argon consists dual CPU architecture which run in tight synchronism and have different tasks:
- GraniteCore
- Servo control functionality for torque, velocity and position control
- High dynamic range torque control
- Dead-time distortion correction
- Control power stage directly
- Axis homing functionality
- Virtual scope to capture variables at high sample rate
- Galvanically isolated from I/O side
- Based on Digital Signal Controller
- I/O side CPU
- Feed GraniteCore with real time data consisting
- Position & velocity feedback device data
- State of physical inputs (enable, clear faults, hall sensors etc)
- SimpleMotion V2 commands to read/write parameters
- Interface different types feedback devices and setpoint inputs
- Handle SimpleMotion V2 communication
- Display device state via digital outputs and LED indicators
- Based on ARM Cortex M3 microcontroller
I/O side CPU has open source firmware allowing end users to implement additional drivers for feedback devices and/or create stand-alone servo drive applications without external Controller.
