@Rahul_Punk_ I have fixed the link in Jay's post.

I would expect that this issue is mechanical in nature.  0.02 mm variance in a mechanical system is not that much unless you have specialized actuators.  If you observe the command and the feedback from the encoder using CX-Drive and the numbers are repeatable, then you have an issue with your actuators.

@NootNoot @IO_Rack I have fixed the links in the other thread.

@NootNoot I fixed the links in PMCR's post.

This has been resolved.  See third post in this thread.

Can you provide a picture of what you are trying to do?  Complete with IP addresses.  Please show the PLC, the router and the remote PC.  Perhaps help can be provided with that information.  Also include the node # on the switches on the front of the CJ2M.

The MOVE instruction now does indeed convert data types (only certain combinations where you don't lose resolution however).  

The variable discussion made me think of this tip.  It does not address your online edit issue, but is useful for programming offline.  There is a setting that allows you to select whether a variable will be created as a global or a local variable when you add it in the ladder editor.  To do so, go to the Tools Pulldown menu and choose options.  Then check the box as shown below: Then the following dialog will shown when creating a variable as you add elements:  

There really is not much logic to it.  The temperature shows up in a register for each of the 4 inputs: Input 1 is in word n+1 Input 2 is in word n+2 Input 3 is in word n+3 Input 4 is in word n+4 n = 2000 + 10 x unit number. So if the unit number dialed in on the front of the card is 3 and you are looking for the current value of input 2, then you would look in address 2032. Explaining - n = 2000 + 10 * 3  = 2030.  Input 2 is word n+2, 2030 + 2 = 2032. then you use that number for whatever purpose that you need.   Here is the manual:  https://www.fa.omron.com.cn/data_pdf/mnu/w368-e1-10_cs1w-p____cj1w-p___.pdf?id=1644 Look in section 3-3.

The TIM instruction is not in milliseconds, it is in 0.1s increments.  So, 6000 (BCD) = 600.0 s = 10 minutes. I cannot save the picture on here, so I will have to type it.  You can use any addresses that you want, but I chose these.  My timer is T0. P_On contact to do all of this: BIN T0 D0               Convert the present value of the timer to an integer / D0 &600 D2          Divide the integer by 600.  This gives you minutes remaining as a whole number. FLT D02 D4             Convert the integer to real. D4 has the value of minutes remaining as a real number.  Display it on the screen with no decimal places. FLT D0 D10             Convert the current value of the timer (0.1s value) into a real number. /F D10 +600.0 D12   Divide the value by 600 to convert to number of minutes as a real number, so 900 (integer) would convert to 1.5 minutes. -F D12 D4 D14        Subtract the whole number of minutes remaining from the real number of time remaining.  Given the 900 example, this would be 1.5 minus 1 = 0.5.  D14 has the fractional minute value remaining. *F D14 +60.0 D16    This converts the fractional minute value in D14 to seconds.  So, 0.5 * 60.0 = 30 s.  In this example, T0 would have a BCD 900 in it, D4 would be 1.0 (whole minutes) and D16 would be 30.0 (30 seconds).  Be sure to display the D4 value on the screen with 0 decimal places.  You could display D16 with one decimal place or 0, that is up to what you want to see on the screen.   There are other ways to do this, but this is one suggestion.

From a DM: Hello Michael , I'm new here , i have doubt with the display of a timer , my boss request a count down display in the HMI but how we can display the real value? I mean i need to put  Countdown display of 5min but the TIM is in miliseconds 6000 = 5min and in the display only put 6000. i hope you can help me.  Regards. Ivan  @Ivan Fajardo

If the orange COM1 light is on all the time with nothing connected, this sounds like you have a hardware issue with that port.  This is not too surprising considering that Omron has not sold C200HS PLCs in 20+ years (my guess).