Michael Walsh

I was trying to show you how I would set this up at least and I cannot find the EDS file.  Can you attach it and I will share how I would do it?  Of course that doesn't mean that it would work, if something is wrong with their EDS file, but I could show you how the setup should look at least. 

Sergei makes a good suggestion.  I might also set CR+LF as the end code and receive each part of the message separately (5 total messages, if I understand correctly).

I modified the PDO map for the drive to look like this for the input side: I am unsure about the ActPos_Abs being the correct selection as there are multiple options for actual position.  You may need to ask SEW.   And this for the output: I also enabled the distributed clock (right below the PDO Map Settings button).   And then I mapped them like this for the axis: When I do this, I still get the same error that you were getting.  So I kept digging.  I noticed that SEW's Control Word and Status Word were DINTs (32 bits), so instead I mapped PI0001 and PO001 to those and removed the control word and status word from the PDO map.  Then I attached those to the Axis settings like this:   When I download that, the error goes away.  Of course it will likely not work at this point, but it does show that the issue is that SEW's control Word and Status Word (both should be 16 bits as that is what WORD implies) are actually 32 bits.  So (SEW, ha!), I would ask SEW what the deal is with 32 bit Status and Control WORDs.  They may be able to somehow map one half of those 32 bits to both the PO001 and PI001 WORDs.    

Quick tip on this subject:  When searching the manuals, you will see it sometimes referred to as "PC Link" and other times as "PLC LInk".  All of the helpful information can be found searching for "PLC Link" with respect to examples and how to set it up. I think that your mistake is that you are assuming that PC Link unit 0 uses the first area (3100-3109 on CP1H and 200-209 on CP2E).  It does not.  That area is for the Master.  Node 0 starts at 3110 and 210.  So, your node #1 will actually be at 220 in the CP2E.   This example is taken from the CP2E Unit Software User's Manual:  

That is a tough one.  Do they need to be closer than 4mm (or perhaps it is 8mm if you need to account for 4mm for each axis) when jogging?  If not, just monitor the commanded position (as opposed to actual position) and don't if the difference between the two is ever less than 4mm (or 8mm) then stop them.  

Check out my response on this post:  

You can update the firmware version in CX-Motion Pro under the tools menu when you are online.  It is part of the CX-One Suite of software.  I have a attached the 1.6720 firmware (newest listed in your list from the manual above).  It is the newest that I have. MCX16720.ZIP ReleaseNote TJ1-MC__ 1.6720.pdf Trajexia TokenTable v1.6720.txt

Many instructions use that flag.  Due to this fact, the flag changes states  many times during the scan of the program. Therefore, only the last state of the flag is shown when monitoring.  This does make it difficult to troubleshoot sometimes.  You can see the state of the flag at that particular rung by adding the flag to the rung (immediately below the instruction) and have it turn on a coil for a bit that is not used.  Then look at the status of that bit to determine what state the flag is when it was executed at that rung.  There is another discussion somewhere in here that talks about these flags.  I will try to share it and provide a link for you.

NCT_V1_3_for_VB5.zip   I am not sure for which Windows version this is supported, but here you go.

I have v1.6720, as far as I know, that is the newest.  What version do you have?

One correction:  Each unit is allocated 100 words in the DM area beginning at D30000.  So, D30000 + (unit number * 100).   Each CPU Bus unit is also allocated 25 words in the CIO area, 1500 + (unit number * 25).  <--- I think @gtsuport is combining the two together.  

I just tested this and am getting the same result as @OmronOmicron: If I have this: 192.168.0.66 Subnet: 255.255.254.0 It works fine. If I change it to: 192.168.1.66 Subnet 255.255.254.0 The PLC sets the IP Address to 192.168.250.66.   So, it is not just the fact that you are using a non class C Subnet, but rather that you are using the non Class C subnet and the FINS node calculation from the IP address / Subnet combo (see link in previous comment) creates a FINS node number that does not match the FINS Node number set in the PLC settings (below Subnet Mask).  This appears to be the design. 

@IO_Rack shared a link that may help.  The controller should accept your settings and allow you to change the IP Address and Subnet to what you desire, however you may have issues connecting using FINS if you have something other than Auto (Dynamic) set for the FINS UDP conversion when you use a subnet of 255.255.254.0.   

Is this a CP1L (with an adapter) or CP1L-E with a built in port? It sounds like a CP1L-E, but I just want to make sure.

If you scroll up further in those settings, you need to make sure that Input 1 Input signal use setting = Disable.  This tells the module that you are not using Input 1 (so that it does not think it is disconnected accidentally): Make sure to download the settings to the PLC.  I think the card resets itself after this, but you may need to turn power off and back on to PLC if not.