ecattypedsdo issue

[jhenning]

Hi,

We have a mature project developed on UMAC 465 fw 2.1.1.3 and IDE 2.1.0.107.  The ecattypedsdo command worked as advertised on that project.

We are now porting the project to CK3E fw 2.6.1.1 and IDE 4.6.0.14.  Anytime I issue ecattypedsdo in this environment I get an error message:

L0=ecattypedsdo(0,22,1,$361a,0,0,4)
requested data size: 4 and received data size: 20 do not match

This happens regardless of the slave and object size requested.  When I change the requested size to 20 bytes the command succeeds, but the results appear to be the command parameters with no useful data.  The following should return DC bus voltage for a Kollmorgen AKD:

L0=ecattypedsdo(0,22,1,$361a,0,5000,20)
sys.cdata[5000]
Sys.Cdata[5000]=0
sys.cdata[5001]
Sys.Cdata[5001]=0
sys.cdata[5002]
Sys.Cdata[5002]=0
sys.cdata[5003]
Sys.Cdata[5003]=0
sys.cdata[5004]
Sys.Cdata[5004]=22
sys.cdata[5005]
Sys.Cdata[5005]=0
sys.cdata[5006]
Sys.Cdata[5006]=1
sys.cdata[5007]
Sys.Cdata[5007]=0
sys.cdata[5008]
Sys.Cdata[5008]=26
sys.cdata[5009]
Sys.Cdata[5009]=54
sys.cdata[5010]
Sys.Cdata[5010]=0
sys.cdata[5011]
Sys.Cdata[5011]=0
sys.cdata[5012]
Sys.Cdata[5012]=20
sys.cdata[5013]
Sys.Cdata[5013]=0
sys.cdata[5014]
Sys.Cdata[5014]=0
sys.cdata[5015]
Sys.Cdata[5015]=0
sys.cdata[5016]
Sys.Cdata[5016]=0
sys.cdata[5017]
Sys.Cdata[5017]=0
sys.cdata[5018]
Sys.Cdata[5018]=0
sys.cdata[5019]
Sys.Cdata[5019]=100    // not valid

Any suggestions?

Thanks,

John

 

 

 

[steve.milici]

What is the returned "L0" value?

[steve.milici]

What does the Kollmorgen AKD documentation say for this SDO?

[Sangmo]

Hi

I suggest you to use version 2.7.0.0 firmware.

[jhenning]

L0=nan.  If I request 20 bytes, then LO=22 (slave number).

Index 361A:0 is 4 bytes in size, per AKD documentation.  This command worked before in the the old project, returning a 32-bit integer representing bus voltage.

Is fw 2.7.0.0 available for CK3E?  If so, how do I get it?  (Haven't gotten any new fw in a long time.)

 

[steve.milici]

Please contact ODT's direct technical support for FW update files:

ODT-Support@Omron.com

[jhenning]

Upgrade to FW 2.7.0.0 fixed this problem.  Thanks!