Ken K.

Maybe you can try to use the Omron ethernet IP modules. These seem to work well communicating between CJ series PLC using datalinks. You should also use ethernet IP to communicate with the NS12s if you get the ethernet port on those units. I have three CJ2 PLCs with the built in ethernet IP port talking to each other (using the datalinks) and talking to NS10 HMIs through a network switch.

I managed to get the Beckhoff slave communicating and working. I didn't have to edit the .eds file. I was getting a 'd6' error on the 7-segment display on the EIP21 card. It turns out the Beckhoff unit has 5 bytes in and 5 bytes out by default in the parameter setting. The Omron system only likes a 'even' number of bytes. So I got the units to 'talk' after I changed the in/out bytes in the Beckhoff to 6 bytes in and 6 bytes out (the Beckhoff also uses 5 as the minimum number of bytes so I had to set it to 6) and changed the Omron to 6 as well. I also found that the first 4 bytes in the Beckhoff unit seem to be 'status and control' bytes. I have to trigger the 5th and 6th bytes to turn on outputs for the Beckhoff -B905. Not sure what the setup is for this as the Beckhoff documentation isn't too clear on this part.

I have a love / hate relationship with function blocks. In my experience: function blocks are good for: 1. math (conversions, scaling, floating point math, etc.) 2. loops (I find it much easier to code loops in structured text) 3. repetitive tasks such as door logic, cylinder logic, stopper logic, etc. function blocks are bad because: 1. takes a lot of memory 2. adds scan time 3. hard to troubleshoot if you don't know how the FB works 4. more work up front to test and document 5. can be dangerous if you try to online edit and 'accidentally' change all instances of the block

Thanks for the responses. I have been pulling my hair out trying to setup a Beckhoff EIP coupler (IL2301-B905) with the Omron CJ1W-EIP21 card. I got the EDS file from the Beckhoff site and 'installed' it in the EIP network configurator but I cannot communicate with it. I have read in other posts that you have to 'edit' the EDS file to make it work. This seems rather inconvenient. Anybody have experience connecting these two devices and what I have to edit in the EDS file? I am going to do more research in the meantime but this is rather discouraging.

We have been using Devicenet with Omron CS1 PLCs for a few years now but have realized it's too slow for simple discrete I/O's. We are moving onto the new CJ2 series PLCs with built in ethernet IP ports (which allows us to network all the line PLCs together and saves us from buying control link cards). So we have been trying to decide which fieldbus is better: CompoNet or Ethernet IP? We do not have any experience with either systems so we are open to any suggestions. Our local Omron distributor is pushing CompoNet but I cannot find many third party devices that support this bus system. Many of our equipment supplier have not even heard of CompoNet. We are a little concerned about going to Omron all the time for interface devices. Ethernet IP seems to be another good option. There seems to be a lot of devices can interface with an EIP network. Beckhoff, AB and some other suppliers already build interface boxes/couplers to interface with EIP systems so it seems there will be more choices with equipment selection. Is there any reason why Omron isn't focusing more on EIP for discrete I/O? Another advantage I seem with EIP is we can use regular ethernet switches and cables to build our network. We are already buying CJ2 PLCs with built in EIP ports so it kind of makes sense. Thanks in advance for your feedback.