Back to top
Appendix B Parameters
Just wanted to know where to use those 'A GUI integer storage' for.
I'm using a Studio5000 PLC to communicate with AKD drive and this is my 1st time to use this drive so am trying to learn bit by bit.
What if I want to read parameter value that has no [Axis 1] on it? how am I write the logic? Is the AKD_Get_Parameter will work?
Thanks in advance for the answer.
Submitted by Autominion Mon, 07/29/2019 - 22:04
There are several ways to read a parameter in the AKD drive over Ethernet IP.
It is important to note the advantages and disadvantages of each method.
The AB Micrologix 1400 PLC supports only explicit messaging via the MSG block. For more details see the
AKD Ethernet IP RSLogix Communications manual under Appendix C: RSLogix 500 for examples and details.
Compactlogix and Contrologix PLCs support both explicit and implicit (I/O ) messaging and our Add-On-Instruction library.
The 3 methods are:
1) Using add-on-instructions such as AKD_Get_Parameter and AKD_Get_Attribute
2) Dynamic Mapping
3)Using Explicit Messaging with the MSG instruction.
The order of communication efficiency from most efficient to least is:
Dynamic Mapping->Explicit Messaging->AOI Read/Write
Dynamic Mapping and Explicit Messaging do not interfere with the execution of other AOIs ( which use
the static bytes of the command and response assemblies ) for a given axis.
The order of ease of setup from easy to difficult is:
AOI Read/Write->Explicit Messaging->Dynamic Mapping
AOI Read/Writes are easy. Look up the instance number and trigger the AOI per best practices. Using the
MSG block requires more steps. Dynamic Mapping requires mapping and byte consumption
management and turning on the data transfer ( map type=2 dynamic ).
Note the order of efficiency versus ease of setup are opposite in order so perhaps there is a trade-off.
Which method to use is application dependent.
See the following links for further support.
Submitted by toddevans01 Fri, 08/16/2019 - 13:10