Uploaded image for project: 'EtherCAT MainDevice V4'
  1. EtherCAT MainDevice V4
  2. PSECMV4-804

[FoE] ACK for BUSY after READ Request should be 0

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.5.0.0
    • Fix Version/s: V4.5.0.3, V4.5.1.0 (open)
    • Labels:
      None
    • Account:
      SPC EtherCat Master (SPCETHERCATMA)

      Description

      Specification mentions explicitly that FoE Write is numbered packet number 0. Since TwinCAT seems to expect that behavior according to trace, the packet Busy related to Read Req has the same numbering scheme.

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  SBormann Sven Bormann
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: