[etherlab-users] DC sync1 shift time

[Gavin Lambert]

Ah, ok.  That setting actually modifies the SYNC1 cycle time (which is a parameter of ecrt_slave_config_dc) based on your actual cycle time – similarly you need to fill in the “real” cycle time values for those that have Factor=”1” in the XML.

 

The appropriate calculations are given in ETG2000, section Types -> DeviceType -> Dc -> OpMode.  Your application will need to calculate this itself based on your target cycle interval; the master library doesn’t do this for you.

 

Also note that only the Cycle Times are written to the slaves, not the Shift Times.  (The Sync0 shift time is however used to calculate the DC Start time.)  For most slaves this is ok but for some you might need to explicitly configure 0x1C32/33 as well.  You could try configuring it in TwinCAT and see what settings it uses for confirmation.

 

From: Philippe Leuba [mailto:pleuba at swissonline.ch] 
Sent: Tuesday, 14 March 2017 01:18
To: Gavin Lambert <gavin.lambert at compacsort.com>
Cc: etherlab-users at etherlab.org
Subject: Re: [etherlab-users] DC sync1 shift time

 

Hello,

 

I probably misunderstood something, but I take these inputs from the Beckhoff EL2522 XML file:

 

<OpMode>

    <Name>DC</Name>

    <Desc>DC-Synchron</Desc>

    <AssignActivate>#x700</AssignActivate>

    <CycleTimeSync0 Factor="1">0</CycleTimeSync0>

    <ShiftTimeSync0 Input="0">0</ShiftTimeSync0>

    <CycleTimeSync1 Factor="1">0</CycleTimeSync1>

    <ShiftTimeSync1>140000</ShiftTimeSync1>

</OpMode>





So I assumed that the sync1 shift time should be configured somewhere. 





Philippe Leuba


On 13 Mar 2017, at 00:01, Gavin Lambert <gavinl at compacsort.com <mailto:gavinl at compacsort.com> > wrote:

According to the documentation that I can find for the EL2522, it only uses
SYNC0, so I'm not sure what you're referring to here.  (Granted I only
glanced through so I might have missed something.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20170314/a0014625/attachment-0003.htm>