Versions Compared

Old Version 9

changes.mady.by.user Unknown User (ababbitt)

Saved on

compared with

New Version 10

changes.mady.by.user Unknown User (ababbitt)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

<chain>                                                                  

    <device type_name="EK1101" revision="0x00120000" position="0" name="C

    <device type_name="EL3202" revision="0x00100000" position="1" name="A

</chain>

 

 

To obtain the revision number for the device you will need to use the slaves ethercat command line tool on your linuxRT machine (aka the EtherCAT Master).

$ ethercat slaves -v -p0

=== Master 0, Slave 0 ===

Device: Main

State: OP

Flag: +

Identity:

  Vendor Id:       0x4c4e5449

  Product code:    0x009606e3

  Revision number: 0x00010007

  Serial number:   0x1bd200e7

 

Upon making your application, the scanner.xml file will be automatically generated in the /<top>/etc directory.  A scanner binary will be generated under /<top>/bin.  You will need to create symbolic links to both of these items under $IOC/vioc-<>-<>/bin directory as previously mentioned above.

 

NOTE: If you are using a brand new module, it may not currently exist in the EtherCAT module.  You can check whether you device is supported by looking in the following areas in the EtherCAT module area.

...

  • Who wants to be the EtherCAT module owner? (big grin)

 

 
  1. Add the scanner.xml file in a bin folder along with the scanner binary in $IOC/vioc-b34-mc23 folder.

  2. Add the script to start the scanner as a linux screen process. (ref: $IOC/cpu-b34-mc23)

  3. Start the scanner at 100Hz frequency.


Verification checks on development machines (lcls-dev3):

...