Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
Nächste ÜberarbeitungBeide Seiten der Revision
embedded_systems:ethercat:start [2021-11-26 08:44] Urs Grafembedded_systems:ethercat:start [2024-01-25 11:22] Urs Graf
Zeile 35: Zeile 35:
   * Acyclic messages, so-called SDOs (service data objects), are not discussed in this documentation.   * Acyclic messages, so-called SDOs (service data objects), are not discussed in this documentation.
  
-At its lowest level, ethercat uses an ethernet frame to send EtherCAT datagrams containing commands to read or write data, or both ('r', 'w', 'rw'). Each Datagram consists of a header, its data and the **working counter**, which servers as a status indicator or checksum. Depending on the operation, the counter is either not incremented at all (+0), by 1, 2 or 3, if data was read, written or both. (TODO: which is read and which is write?)+At its lowest level, ethercat uses an ethernet frame to send EtherCAT datagrams containing commands to read or write data, or both ('r', 'w', 'rw'). Each Datagram consists of a header, its data and the **working counter**, which servers as a status indicator or checksum. Depending on the operation, the counter is either not incremented at all (+0), by 1, 2 or 3, if data was read, written or both.
  
 The data that is actually read or written is accessed using a 4Gbit address space using byte.bit addressing. EtherCAT technically bit alignment, though in practice most  things seem to be byte aligned. This address space is called the **Process Data Image** or **PDI**. The data that is actually read or written is accessed using a 4Gbit address space using byte.bit addressing. EtherCAT technically bit alignment, though in practice most  things seem to be byte aligned. This address space is called the **Process Data Image** or **PDI**.
Zeile 63: Zeile 63:
 In this example workflow a Linux based master with Acontis stack and EEROS is used.  In this example workflow a Linux based master with Acontis stack and EEROS is used. 
  
-We build our system with Yocto. The necessary recipes and resources can be found in the private repository [[https://gitlab.ost.ch/tech/inf/projects/yocto/meta-ntb-ethercat|meta-ntb-ethercat]] together with information about acquired licenses. This repository must be private as it contains the licensed runtime libraries. +We build our system with Yocto. The necessary recipes and resources can be found in the private repository [[https://gitlab.ost.ch/tech/inf/projects/yocto/meta-ost-ethercat|meta-ost-ethercat]] together with information about acquired licenses. This repository must be private as it contains the licensed runtime libraries. 
  
   - [[embedded_systems:ethercat:choose_linux_master|Choose Linux master]]   - [[embedded_systems:ethercat:choose_linux_master|Choose Linux master]]