sdstiller

IAI (MSEP) ETHERNET/IP

6 posts in this topic

Hello all 

this may be dumb is so I am sorry. However I have come from Mitsubishi and am accustom to CC-Link and this is my first time using Ethernet/IP and I am having trouble.

I am adding a MSEP-C controller to  1769-L30ERM PLC. I have read several manual and have got the module to be satisfied. However I have imported an AOI to use and this is where my trouble begins. I am loosing my data someone. I am unsure of where. I have the subroutine talking to the AOI however the AOI is not talking to the MSEP-C controller. I should be receiving MAP_AXIS_INPUTS.CONTROLLER_READY signal and I am not. I have added a couple CPS instructions to move data to and from the input/outputs. I think somewhere in this area is my issue. I feel like I have not specified correct areas for the data to move to and from but do not know the correct way.

Capture.PNG

Capture1.PNG

Share this post


Link to post
Share on other sites

Two quick things to check.

First the IAI must be in the IO Tree.  Find and read the manual and sample programs.  Generally, its a Generic EtherNet Module.

Next, obviously you have configured logis in a sub routine.  Make sure the sub routine is called (JSR) from the MainRoutine.

 

Lastly, my IAI distributor is execellent and if he can't help me he has three IAI engineers available in an hours and sitting next to me to help.

1 person likes this

Share this post


Link to post
Share on other sites

I used IAI for a linear actuator. IAI is pretty good in support. @pcmccartney1 is making a valid point and the correct one. In your IO tree, under generic ethernet module, browse to the tag definition (online of course with the plc) and see if you are seeing any values. if you are not seeing any values, that means that you are not pointing to the correct IP address, or you messed up in your generic module definition (such as DINT, INT, SINT, ...) make sure that your generic ethernet module matches with their datasheet. It is something that most people overlook. 

Share this post


Link to post
Share on other sites

Thank you for the input. I do have the module setup as a generic ethernet module and seems to be happy. I did reach out to IAI they were indeed extremely helpful. However they just gave me a sample project that I was able to use to get the servo to be operational thru the PLC. They were unable to explain to me where I messed up. This will be an issue when I add my second controller to the tree. They did give me different AOIs. I presume that the AOI can be used for both controllers and is determined by the CPS instruction (the data allocated for each controller). As in copy the logic and change tags. They showed me that when having more then one axis to just lengthen the array and repeat the logic structure. So I presume I can do the same for the second controller (with the new tags)?  

Share this post


Link to post
Share on other sites

When you setup your generic Ethernet module, make sure you select the correct data type.  This has snagged me more than once (sorry to admit).  It's very easy to forget and use the defaults and just fill out the number of input/output and config words.  I believe it will show a valid connection on many devices, but the data transfer will be messed up.

Edited by PLCMentor.com

Share this post


Link to post
Share on other sites

I haven't used the MSEP. generally we use the PCONs.  There are some settings in the PCON that change the data structure, sizing of tables and what can/cannot be accessed.  The manual will then tell you how to setup your generic ethernet module for correct data type, instances and sizes.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now