Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
embedded_systems:ethercat:understanding_ethercat:understanding_sync_with_dc [2019-02-13 11:22] mgehrig2embedded_systems:ethercat:understanding_ethercat:understanding_sync_with_dc [2019-02-13 11:32] (aktuell) mgehrig2
Zeile 26: Zeile 26:
 The slaves then do not receive the data sufficiently early before the next Sync0 even is triggeredt. The slaves then do not receive the data sufficiently early before the next Sync0 even is triggeredt.
  
-TODO: corresponding error message+The coresponding error message will be something like: 
 +<code> 
 +082039 : eUsrJob_ProcessAllRxFrames - not all previously sent frames are received/processed (frame loss)! 
 +</code>
  
 ==== DCM Bus Shift Mode ==== ==== DCM Bus Shift Mode ====
Zeile 37: Zeile 40:
 After the Sync0 event, the received data from the Ethernet driver are first copied into the buffer of the Acontis stack on the master. After the Sync0 event, the received data from the Ethernet driver are first copied into the buffer of the Acontis stack on the master.
 Then the application can evaluate the received data and set the outputs. Then the application can evaluate the received data and set the outputs.
-As soon as the cyclic job of the application is completed, the EC Frame is sent from the stack.+As soon as the cyclic job of the application is completed, the EC Frame is sent from the master to the slaves.
  
-The period between the frames is only deterministic to a limited extent. +==== Cycle time ==== 
-In this mode only the period between the Sync 0 events is deterministic!+The cycle time between the EtherCAT frames is only deterministic to a limited extent. 
 +If the application needs in one cycle more time to calculate the results, the frames are sent later than in the cycle before. 
 + 
 +The time between two consecutive inputs measurements is very constant, because they are synchronized with the Sync0 event. 
 +The same is true for writing outputs. 
 + 
 +For calculations in control applications, the period duration (setpoint!) must be used, not the measured time between two EtherCAT frames.