Re: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error)

2015-06-01 Thread Graeme Foot
Hi, 1) If your cycle time is 4ms, I think it should instead be: 0x60C2, 0x01 = 4 0x60C2, 0x02 = -3 Eg: ecrt_slave_config_sdo8(dev-slaveConfig, 0x60C2, 0x01, (uint8_t)4); ecrt_slave_config_sdo8(dev-slaveConfig, 0x60C2, 0x02, (int8_t)(-3)); Where the first parameter is the significand and the

Re: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error)

2015-06-01 Thread Gavin Lambert
@etherlab.org Subject: Re: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error) Hi, 1) If your cycle time is 4ms, I think it should instead be: 0x60C2, 0x01 = 4 0x60C2, 0x02 = -3 Eg: ecrt_slave_config_sdo8(dev-slaveConfig, 0x60C2, 0x01, (uint8_t)4

Re: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error)

2015-06-01 Thread Gavin Lambert
Subject: RE: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error) Hi, Good comments to make. Yes, the DC reference slave should be the first capable slave and definitely before (or at least the first) DC enabled slave. However, I had some EK1100 modules (which

Re: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error)

2015-06-01 Thread Graeme Foot
. To: Graeme Foot Cc: etherlab-users@etherlab.org Subject: RE: [etherlab-users] Twincat communicate with yaskawa SGDV alarm A12 (Sync Error) FWIW, while I could be wrong about this, as far as I know it’s generally a bad idea to explicitly set the reference clock slave. It defaults to being