Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
etherlabmaster
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ICS Control System Infrastructure
etherlabmaster
Commits
150b0e51
Commit
150b0e51
authored
16 years ago
by
Florian Pose
Browse files
Options
Downloads
Patches
Plain Diff
Updated features.
parent
5c79e4f7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
FEATURES
+54
-38
54 additions, 38 deletions
FEATURES
with
54 additions
and
38 deletions
FEATURES
+
54
−
38
View file @
150b0e51
...
...
@@ -4,64 +4,80 @@ This is the FEATURES file of the IgH EtherCAT Master.
$Id$
vim: spelllang=en spell
-------------------------------------------------------------------------------
General Features:
* Runs as kernel module for Linux 2.6.
* EtherCAT master implementation conforming to IEC/PAS 62407.
- Runs as kernel module for Linux 2.6.
- Multiple masters possible on one machine.
*
Comes with
EtherCAT-capable
network
driver for
serveral network interface
card
s.
- Interrupt-less
network driver operation
.
- Easy implementation of additional
network
drivers through common device
* EtherCAT-capable
versions of standard Linux
driver
s
for
wide-spread
Ethernet device
s.
- Interrupt-less
operation of Ethernet devices
.
- Easy implementation of additional
Ethernet
drivers through common device
interface of the master.
- Runs even with PCMCIA cards.
* Supports multiple EtherCAT masters on one machine.
* Supports any realtime extension through independent architecture.
- RTAI, IPIPE, ADEOS, etc.
- Runs well even without realtime extension.
* Common kernel interface for realtime modules using EtherCAT functionality.
- Synchronous transmission and reception of EtherCAT frames.
- Operation possible with any device supported by the standard drivers,
including PCMCIA devices.
* Supports any realtime environment through independent architecture.
- RTAI, Xenomai, RT-Preempt, etc.
- Operation possible even without any realtime extension.
* Common API for Realtime-Applications in kernel- and userspace.
- Requesting and releasing masters.
- Dynamic slave configuration, even for slaves that are offline.
- Detailed configuration of the slaves' Pdos and Sdos.
- Creation of process data domains (see below). Registration of Pdo entries
for exchange within a domain.
- Monitoring the states of masters, slave configurations and domains.
- Sdo handlers for application-triggered CoE transfers (see below).
- VoE handlers for Vendor-specific mailbox protocols (see below).
- Similar userspace implementation of the kernel API via a C-library.
- Avoidance of unnecessary copy operations for process data.
* Separating slave groups through domains.
- Handling of multiple slave groups with different sampling rates.
- Automatic calculation of process data mapping, FMMU- and sync manager
configuration within the domains.
- Process data exchange can be monitored via a per-domain mechanism.
* Master finite state machine (FSM).
- Bus monitoring during realtime operation.
- Automatic reconfiguration of slaves on bus power failure during realtime
operation.
- Setting slave states during realtime operation.
* Special IDLE mode, when master is not in use.
- Automatic scanning of slaves upon topology changes.
- Bus visualisation and EoE processing without realtime process connected.
- The same state machine runs when the master is idle and also when an
application is connected.
- Bus monitoring. Slave states are read cyclically. Automatic scanning of the
bus on a topology change.
- Automatic configuration of slaves, if a application-layer state change is
requested.
* Implementation of the CANopen-over-EtherCAT (CoE) protocol.
- Configuration of CoE-capable slaves
via Sdo interface
.
- Configuration of CoE-capable slaves.
- Sdo information service (dictionary listing).
- Sdo
acces
s via the
realtime interface
.
- Sdo
transfer
s via the
application interface and the command-line tool
.
* Implementation of the Ethernet-over-EtherCAT (EoE) protocol.
- Creates virtual network devices that are automatically coupled to
EoE-capable slaves.
- Thus natively supports either a switched or a routed EoE network
architecture with standard GNU/Linux tools.
* User space interface via a command-line tool 'ethercat'.
- Detailed information about master, slaves and the bus configuration.
- Slave SII reading and writing.
* Seamless integration in your favourite GNU/Linux distibution.
- Master and network device configuration via sysconfig files.
- Creates a virtual network interface for any EoE-capable slave.
- Natively supports either a switched or a routed EoE network
architecture.
* Userspace command-line tool 'ethercat'.
- Detailed information about master, slaves, domains and bus configuration.
- Reading/Writing alias addresses.
- Listing slave configurations.
- Viewing process data.
- Sdo download/upload; listing Sdo dictionaries.
- Access to slave registers.
- Slave SII (EEPROM) access.
- Requesting application-layer states.
- Generation of slave description XML from existing slaves.
* Seamless integration in any GNU/Linux distribution.
- Master and Ethernet device configuration via sysconfig file.
- "Linux standard base"-compatible init script for master control.
* Virtual read-only network interface for debugging
purposes and for
monitoring the EtherCAT traffic (through Wireshark, or others)
.
* Virtual read-only network interface for debugging
and traffic monitoring
purposes (using Wireshark, etc.). No additional hardware necessary
.
-------------------------------------------------------------------------------
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment