- Posts: 446
- Thank you received: 158
Ethercat HAL driver
So the cycle time is probably in units of 1 µs?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
db1981 wrote: hello,
0x1006 is the com cycle time = 500ns this is equal to your ethercat app cycle time
0x60C2 is the interpolation time, it's also 50ms * 10^ -5 = 500ns.
is your servo_period in the ini (thread which executes lcec_read/write) also set to 500ns (2khz) ?
This is my hal line with the periods:
loadrt [KINS]KINEMATICS
loadrt motmod base_period_nsec=500000 servo_period_nsec=1000000 traj_period_nsec=100000
when i try to change the servo period linuxcnc did not start anymore.
Please Log in or Create an account to join the conversation.
In which of this threads the lcecs are called (addf)
can you attach the hal file, seems there is something strange with the bus cycle time and the dcconf.
In the Indramat manual is written, that for an position control cycle at 0,25ms (fix for this drive) the communcation period should be min. 1ms.
Please Log in or Create an account to join the conversation.
db1981 wrote: thats an servo_period of 1ms,
In which of this threads the lcecs are called (addf)
can you attach the hal file, seems there is something strange with the bus cycle time and the dcconf.
In the Indramat manual is written, that for an position control cycle at 0,25ms (fix for this drive) the communcation period should be min. 1ms.
This is my halfile where lcec is loaded
Please Log in or Create an account to join the conversation.
this does not match the drivers pdo. If this is an used device (ebay etc.. ) the card may be is configured for 16 Bit Mode. Factory standart would be 32 Bit mode (MDP511), for this the driver is configured.
Is this exactly an EL5151 or an special type EL5151-00XX ?.
Do you have acces to twincat? this would be much faster then configure the Card with sdo commands.
Please Log in or Create an account to join the conversation.