b.k.n.

You could probably use another vendors remote IO with their PLC. A person would have to research it.

If you want a remote Omron EIP rack you need to use NC-EIC202 that is their NX remote IO coupler for EIP. You setup the exchange in CX-One's Network Configurator. In my example 192.168.26.114 is a Omron CJ2H talking to two remote NX EIP io racks, 192.168.26.131 and 192.168.26.132. You will first need to connect to the EIC202 with USB and Sysmac Studio or the NX IO Configuration(I think they have a standalone tool so you don't need to buy the full sysmac license). This is how you add the NX io units to the coupler. When you are done with that you can use Network Configurator to set the EIC202's IP address. Once you can connect to the coupler you can upload from it and verify the number of input and output bytes. There manuals are usually pretty good. Hopefully these snips help.

1. Wouldn't you just setup the ratio as seen in the screenshot? The axis is setup with no "gearing / ratio"... From looking at how you have the axis Unit Conversion Set you are using the gear box. I would not do this if you just want to use pulses. The way you have it set in the project using the gear box your command of  12780522 would actually give 85,768,631,274,700.8 pulses. Pay attention to their formulas there in the setup it tells you what each number is doing and how to calculate how many pulses were generated.   2. I don't have experience with the NA screens. But using Weintek with NX PLC I am doing that conversion all the time. Maybe I am missing something, would be good to know if so...

I would use a normally closed contact of the Start_motor put ahead of the Motor_Off function...?

What about the GetMyTaskStatus instruction be helpful for what you are trying to do? See the snip

Have any of you run into the Non-volatile Memory Life Exceeded? I have two times now an NX102-9020. Each time we were not able to clear the error so we ended up replacing the PLC. I can connect to it with Sysmac Studio. But it does not seem to run with this fault even though it claims to be in run mode.

Have you thought about writing your data to the SD card in .csv files and then emailing the file. I can post the Email function block if you want. I am using this method and it works very well!!

In my experience power supply first then CPU then all your other cards. Like I thought the connectors on the rack are different for the CPU and power supply slots as opposed to the rest. But then again its been awhile since I have done a CS1.

I am sorry. I am not very familiar with the NSJ and when I saw it in the Sysmac thread I just assumed that it was a NJ/NX.

Hi would this solution work for you?

Not real experienced with PMCR I have used it like one time. In CX-Protocol there is an option to configure number of retries. You could play with that. Have tried setting your Peripheral Service time to a value some where in the mid range?

you are absolutely correct it will increase cycle-time overall if it needs those extra ms to process communication on the port.

The other thing you could do is increase the "Peripheral Service" time on the CJ2. This is the setting that allocates the MAX amount of time given to service the communications. Default is 10% of scan time. On some of my projects when I have problems with screens not refreshing variables from a PLC in a timely manner by setting this up I can increase performance.  

Yes thats right use your "address reference tool" to see where all it is used. And from there away you need to understand the program well enough to know what code actually will affect that output. My understanding of the "Trace" you referenced(at least for Omron) is a troubleshooting tool to track all the different values that a variable has contained. For example if they are changing so fast you can't see them real time by watching it in the program.  

That is correct D area bits are accessible on the CJ2 CPU's. W area is good for all tasks that don't need to retain their values through a power outage. In that way it is really the same as CIO. I like using them for momentary touch switches(user input) on a touch screen.