Webbs

ifm AL1322 Ethernet/IP

14 posts in this topic

I am trying to set up a ifm AL1322 EtherNet/IP IO Link Master to communicate with a NX1P2 or CS1 PLC.

When using Network Configurator I have added the EDS file and added the AL1322 to the network and set its IP address.  It shows all the parameters in the device but if you make a change it says it has downloaded but nothing on the unit changes.  If you make a change to a parameter and then verify it says there are no difference even though there are.  I have set up the communication with the PLC but there is an error 

Establishing a tag data link connection failed.

This is the same for both the CS1 and NX1P2.

I have also tried setting it up using Sysmacstudio for the NX1P2 and get the same result.

 

I have had the unit back to ifm and there is no issue with it running with an AB PLC.  I can also communicate with the unit using the ifm LR software.

Any ideas why the Omron software is unable to read from or write to the unit?

ifm_IOL_Master_AL1322.eds

Share this post


Link to post
Share on other sites
13 hours ago, Webbs said:

It shows all the parameters in the device but if you make a change it says it has downloaded but nothing on the unit changes.

Typically if there are any settings for the remote device (AL1322), they will be made either by manual switch or the manufacturer's software. Network Configurator or Sysmac Studio will not download to it. 

Use the manufacturer's methods to set the IP address. Network Config and Sysmac Studio will get the information from the EDS file. Double check the tag sizes match.

Share this post


Link to post
Share on other sites

If you share a wireshark capture of the traffic, I can help diagnose the problem.  While I haven't put these two together, there's nothing special about either's EtherNet/IP implementation--this should "just work".  When using the NX1P2, I strongly recommend using a structured type in CJ format to map the data elements and verify their byte offsets.

Share this post


Link to post
Share on other sites
4 hours ago, IO_Rack said:

Typically if there are any settings for the remote device (AL1322), they will be made either by manual switch or the manufacturer's software. Network Configurator or Sysmac Studio will not download to it. 

Use the manufacturer's methods to set the IP address. Network Config and Sysmac Studio will get the information from the EDS file. Double check the tag sizes match.

I have been able to configure the IP address and that all works as expected.  There are no jumpers on this unit and the only setting that can be changed via the ifm software is the Port Process Size.  The documents from ifm for setting this up show you can also change this also with Network Configurator.

 

I have had devices where there are no parameters to configure in Network Configurator and understand that.  This one offers settable parameters but then won't allow them to be set.

I have set it up using the default tag size settings and it doesn't work.

 

I also set up a NX-EIC202 on the same network to make sure that side was all working ok and that happily worked but the AL1322 still had the issues.

ifm.JPG

Share this post


Link to post
Share on other sites

According to the EDS file, this device expects a 98-byte configuration assembly, which carries the parameters to set up the profile and I/O sizes, etc.

Share this post


Link to post
Share on other sites

It appears you can select from multiple assemblies. Network Configurator was used for NJ/NX EIP setup early on before Sysmac Studio had a configuration utility. Try using this utility instead of Network Configurator. 

1) Create tags. Don't forget to set your 'Network Publish' attribute to Input and Output.

Mr_PLC_AL_03.JPG.67dc4fc348303e2094d8b6c

2) In Sysmac Studio, goto Tools > Ethernet/IP Connection Settings. Right click in the upper right pane and choose Display EDS Library then install your EDS file.

Mr_PLC_AL_02.JPG.828ac266145522091d32c83

3) Create Tag Sets for your inputs and outputs. I usually just name my tag set the same as the variable it will contain.

Mr_PLC_AL_04.JPG.2a07d1222131d1fcab88575

4) Set the connection. Add the Target Device (AL1322) then populate with your new variables and the Target Variable from the EDS information.

Mr_PLC_AL_05.thumb.JPG.b71d13937b399f815

Mr_PLC_AL_01.JPG

Share this post


Link to post
Share on other sites
4 hours ago, pturmel said:

If you share a wireshark capture of the traffic, I can help diagnose the problem.  While I haven't put these two together, there's nothing special about either's EtherNet/IP implementation--this should "just work".  When using the NX1P2, I strongly recommend using a structured type in CJ format to map the data elements and verify their byte offsets.

This is the first device i have had trouble with setting up Ethernet/IP.  Yes once you have the data sizes the same it should just work.....  ifm have a downloaded setup tutorial which i followed (and also online with an ifm tech) and still had the same issue.  There is an example program which has a tag set that matches the structure of the data coming back and this also has no joy.

I haven't used wire shark before so not 100% sure on how it works.  I did install it and found this in the log.  192.168.94.246 is the AL1322 and 192.168.94.50 is the PLC

35    19.650259    OmronTat_bb:80:55    Broadcast    ARP    60    Who has 192.168.94.246? Tell 192.168.94.50

Attached is the error i get.  If is set the data transfer size to be in correct i still get the same error.

 

Error.JPG

Share this post


Link to post
Share on other sites
4 hours ago, pturmel said:

If you share a wireshark capture of the traffic, I can help diagnose the problem.  While I haven't put these two together, there's nothing special about either's EtherNet/IP implementation--this should "just work".  When using the NX1P2, I strongly recommend using a structured type in CJ format to map the data elements and verify their byte offsets.

I have tried the setup via network configurator and in sysmac studio.  The ifm setup examples for Omron show both methods.  I have tried 100 & 150 and also 101 & 151 with the same result.

Share this post


Link to post
Share on other sites

Here is the wireshark capture when i used network configurator to download and upload the parameters from the AL1322 (192.168.94.246) from my laptop (192.168.94.241).

Network Config.pcapng

Share this post


Link to post
Share on other sites

Try updating the IP addresses in this export I've been poking around with.  You shouldn't need anything preconfigured on the IFM except IP address stuff.

If this doesn't work, try getting a wireshark capture from the Omron to the IFM.

MrPLC IFM AL1322.smc2

Share this post


Link to post
Share on other sites

Note that I picked assemblies 102 and 151 to test--they have the simplest layout.  I had to update those assembly sizes separately in the parameters.

I created structures for all of the possible combinations of assemblies and port data sizes for you to play with.

Share this post


Link to post
Share on other sites

I tried your program and i get all the same errors.  I have attached the wire shark for the download and then a power cycle.

I have tried a different IP address for the AL1322 (192.168.94.2) and still get the same result.

Download.pcapng

Restart.pcapng

Restart.pcapng

Share this post


Link to post
Share on other sites

Your wireshark captures have no meaningful content.  (Try a display filter of "ip.addr == 192.168.94.0/24" to see what I mean.)  Probably because your network isn't showing you packets that go between the PLC and the IFM.  You need a mirror port on a smart switch or your laptop needs to be the bridge itself.

Anyways, I was looking for the EtherNet/IP "Forward Open" packet and the IFM's response to that.  I'm not sure precisely where you are going wrong, but the starter kit for this family of products from IFM for Omron strongly suggests it should work.

Share this post


Link to post
Share on other sites

I don't have a smart with this setup.  I will see if I can do anything to make my laptop a bridge and see if i can get in between the coms from the PLC to the AL1322. 

All the info i from ifm points to this as simple and there isn't anything that should cause any problems. I have the EtherCAT version and it works as expected.

I will post any update if i can get the traffic between them.

Thanks for your suggestions.

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