CiA 402 Folder Missing

About the cia402.0.pos-scale, I wrote 100 000 to just start with some value. My encoders are 23bit, therefore 8 388 608 pulses per motor revolution. On my current plasma machine I have a 1:10 planetary gearbox that I plan to use when I upgrade the machine motors to servo motors and LinuxCNC. The rack gear pitch diameter is 50 mm, therefore the circumference is 157.07963267949 mm. This the linear distance that the axis will travel for 1 revolution of the rack gear or 10 revolutions of the motor.

Therefore the cia402.0.pos-scale = ((encoder res * gear ratio)/distance per rev). I am not sure what value I should use for distance per rev - is it the linear distance per the rack gear revolution or the linear distance per motor revolution(that is linear distance per rack gear revolution / gear ratio)?

It is encoder pulses per mm, maybe your value isn't far off then.
It is suspicious if it start moving very fast. Use halshow to look at the
variables between cia402 and lcec and see if they look ok in size,
moves when they should etc.

The topic was not updated for a long time. I was trying to get the servo drives work with LinuxCNC and at one point I decided to start from scratch. Now my configuration is with only one servo drive. I managed to get the homing on index pulse working to a certain extent. The problem is when the servo is far from the index pulse, LinuxCNC gives "joint 0 following error". The servo keeps moving but LinuxCNC is disabled. For a successful homing, the motor should close to the index pulse. What is causing the following error? I attached the configuration files. By the way, the homing components used is the standard "homemod".

The "sudo dmesg" command shows warnings about datagram unmatched, time out and slave sync. The tried writing to 1C12:001 and 1C13:001 from the command line but it returns an unknown error "SDO transfer aborted with code 0x06010003". Using the attaced .xml file, when reading 1C12:001 and 1C13:001 from command line, it returns that the PDO mapping is flexible.

Your ethercat.xml file is completely wrong.
The errors are pointing that out to you.
[290201.755307] EtherCAT ERROR 0-0: SDO upload 0x1A01:00 aborted.
[290201.755312] EtherCAT ERROR 0-0: SDO abort message 0x06020000: “This object does not exist in the object directory”.
[290201.755314] EtherCAT ERROR 0-0: Failed to read number of mapped PDO entries.
[290201.755315] EtherCAT ERROR 0-0: Failed to read mapped PDO entries for PDO 0x1A01.

You had already created the correct XML file. Take another look at your pdos.txt and compare it with the ethercat.xml.
This is what should be in your XML:
RxPDO 0x1701 “RxPDO”
    PDO entry 0x6040:00, 16 bit, “ControlWord”
    PDO entry 0x607a:00, 32 bits, “Target position”
    PDO entry 0x60b8:00, 16 bits, “Touch probe function”
    PDO entry 0x6060:00, 8 bits, “Modes of operation”
  TxPDO 0x1b01 “TxPDO”
    PDO entry 0x603f:00, 16-bit, “Error Code”
    PDO entry 0x6041:00, 16-bit, “statusWord”
    PDO entry 0x6064:00, 32-bit, “Position actual value”
    PDO entry 0x6077:00, 16 bits, “Torque actual value”
    PDO entry 0x60f4:00, 32 bits, “Following error actual value”
    PDO entry 0x6061:00,  8 bits, “Modes of operation display”

You can start by setting it up for one axis.
Once you no longer see any errors in dmesg, you can continue.

@andrax
I figured it out, my mistake, I wrote the SDO object wrong and after trying many different ways to get it working. Now I just want to verify that my "sudo dmesg" is ok. What I did is I rebooted the computer and the drive. Attached is the last output and the lines after 64.544984 were shown after LinuxCNC was started.
I observe two error but do not know if they affect LinuxCNC and EtherCAT: The problem is that I do not know how the "sudo dmesg" output is supposed to look when no errors.
The .xml file is fixed and I decided to use the variable PDO mapping object - 0x1600 and 0x1A00. I check with "ethercat upload" and it seems that the SDOs are set as intended. Attached are the .xml and .hal files. 

EDIT: I want to add that when I close the LinuxCNC and open it again there is a different output after "sudo dmesg". Attached is a file. An error appears:

That looks good.
The error is normal; it happens when LinuxCNC shuts down.
Can you move the axis in jog mode without any problems?
If so:
You now have two options. Connect the remaining axes and use the CIA402 homing.
Note: Prone to errors with gantry setups
or
Use the LinuxCNC homing. However, this is significantly less accurate.

If there are battery-powered encoder cables available for your servos,
install them, and you’ll save yourself the homing process and avoid any further trouble.