Crossbow

Do a build on the project (hit F8), then synchronize the project, and check if it goes away.  

Modbus TCP works over an Ethernet connection... Copper or fiber has no bearing on the communication protocol.

The safety project in the open project has to match the one in the controller, and the controller must be in its validated state.  The safety data in the HMI is tied to a validated safety controller. If you're trying to upload, then don't pick the safety data, that is a download thing...

Encoders are input data.  You can use standard instructions to look at this data. Standard instructions like math and compare work with LREAL data, which is how the encoder axis position would be stored. Encoders are not output data, so motion function blocks have no control of an encoder axis.  You can't jog an encoder...

You shouldn't have to change the program.  The new FX3U has other ways to access the data besides TO and FROM.  But the old method still works.  What module was attached on the right side of the old PLC?  And did you move it to the new PLC?

The encoder can be configured as an input motion axis.  Then you can look at the position of that axis for verification.

The only PLC that requires validation is the NX Safety CPU.  Did you enable the Safety Monitor in the HMI Settings?  In order to use this, the safety CPU must be in a validated state.  This will add a check box on the Synchronize screen for Safety Data.

There must have been a special function module on the AX2N that you did not move onto the FX3U...  Those TO and FROM instructions are trying to talk to the first special function module.

MOVD can be told the number of digits to move if I recall correctly, so it can move 8 bits...

Sounds like a hardware failure...

Those addresses were listed for FX, so it was D, not SD.  FX did not have SD, that did not come about until Q Series...

Be careful with your moves... clock data is in BCD, not integer.  I would swear there is a command that can copy digits from one register into another, but I cannot think of it right now.  It's been a while since I worked in CX-Programmer, mostly use Sysmac Studio anymore...

What is the status of the error lights on the front of the CPU?  Without that info, we would be guessing...

https://automation.omron.com/en/us/search?query=IAG&pageSize=10  

I use them all the time.  The Omron US website has the latest version of the Standard IAGs.  The Omron standard IAGs haven't changed in a long time, i think the archive name was 114B.  You can make your own as well.  Also Omron France has a bunch on their website as well.

NX1P2 will need an NX-PF0630 card to add power for the I/O.  And then you can add an NX-PG module for the pulse outputs.  Then you can control as a motion axis using the built in motion function blocks.

What do you mean by 'operational technology'?  And what networks?  There are literally dozens of network types used in factory automation.  For better responses, provide more detail...

It's an IEC software, so the TON instruction always counts up.  And I am not sure you are allowed to write to the current value. You do not need the AND on the second timer, because the moment TON_2 finishes, TON_1 becomes false and that would reset both timers.  Putting it on TON_2 is redundant. As for your extra input, add it as input condition on the second timer.  Will it stay on?  If not, you need to write a latch to keep it on while the second timer runs and reset it when the second timer ends.  The timer needs a true signal for the whole time it is timing.

Back when I worked for a Modicon distributor we had the software, I upgraded a few of them.  I don't still have a copy.  Do you have the proper programming cable?  Because those were nearly impossible to find, and not something that is easily made from what I remember... had electronics inside the cable.  I would think a long-term Schneider Electric distributor would have the capacity to get your program out for you... might want to look who sells Schneider Electric in your area.

GX Works2 is NOT shareware.  You need to purchase it from an authorized Mitsubishi distributor.  The older software GX-Developer had an FX-only version that was lower cost, not sure if GX Works2 offers the same or not. So there is nothing wrong with the PLC.  If that output is the fault, that's based on the program inside the CPU turning that on.  If there was a PLC problem, the error light on the right would be on, and the run light would typically be off...

The manual for the hardware will indicate what the error means.  Sometimes the light is solid, sometimes flashing.  The manual will indicate what each means.   The battery may have gone dead and the program may be lost.

PLC time is stored into registers in the controller, I don't have the list handy.  But you would simply do a compare to those registers in your code.

If you click in the Initial Values column, a black box appears, and when you click it, you will see each member of the structure and can enter data that way too, if it doesn't need to be changed. Also keep in mind the IP address is a string, so it needs to be in single quotes '192.168.250.10'

Likely your MR Configurator is out of date.

Contact Mitsubishi technical support for the software.  Those are long obsolete, but that doesn't mean the software is free...