Gambit

 OUT_C_32  is needed to activate the high speed counter Dmov is for the values  

There is a difference between C250 and C251. 1-phase 2-count input & 2-phase 2-count input To activate the counter use OUT_C_32 instruction As for the monitoring keep in mind that the program is running much faster then you are monitoring.  So many scan have been processed which changed some values. Active open or closed is only what you programmed the depending on the value of the bit it will be filled blue. So a normally closed which bit is off will be blue filled p.s. For real production i would not use a clone !!!!!

You should use labels than you would have gotten an error,  Some instructions Like multiplcation the result is 32 bit so it uses 2 Registers. So if you enter D120 (it's also D121) When you use labels you have to define the type so you would have gotten a notification when building the project

During installation you didn't set start automatically when booting the PC. So it looks like the OPC server has't started. Have you started the server ? Basicallly your screencapture is already providing the correct steps   

Which Firmware are you running ?   As for Dianostics:

https://www.mitsubishielectric.com/fa/document/technews/got/got-a-0160/gota0160ac.pdf You need a USB -A on the GOT. The mini USB is only for data transfer

Then I expect there is something in the code on start-up. chianging the values

Just Change M to an L device. Those are latched 

Then D2842  should be lachted, So it's either overwritten in the program (maybe an inital program) somewhere after a reboot  or the  battery has died. Is there a yellow LED lit on the CPU? Can you check the parameters if the battery detection is disabled 

You'll need to Latch  D2842 in the PLC parameters. which controller are you using ?

Okay In GX works 3 goto the CPU parameters. Service processing settings and give more time for communication

Maybe you should start in steps and get network running with the stations. after that refresh the correct Registers/adresses. And than the need programming  There is an e-learnig for CC-Link. you should follow this first https://www.mitsubishielectric.com/fa/service-support/global/e-learning/pdf/eng/1-CC-Link_iQ-R_na_eng-A.pdf  

Did you use different stationnumbers for the connections ? Do you communicate large amounts of data  ? What is the scan time of the PLC's ?    

Why ??? you can do this easlly with the simple PLC comm settings. Ypu don't need any programming   OR if the FX5 is just the server just create a modbus port in the port settings and you're done

You mean comm software like Mx components so you can make something in C#?

The servo amplifier was switched on when power to the servo system controller is off. The axis No. set to the servo system controller does not match the axis No. set with the axis setting switch (SW1) of the servo amplifier. A servo amplifier fault occurred or an error took place in communication with the servo system controller. In this case, the indication changes. "Ab" "AC" "Ad" "Ab" The servo system controller is faulty.

Those are modbus modules which can be master and slave / server client.  Do youn want to use the to communicate with eachother or with a modbus Client ?   Also wich PLC programming software are you using ? GX Works 2? 

Hmm Sorry don't know but i would convert the project to iQ-R\. It's not that difficult. The AnS series is pretty old.    

The AnS series is eol. You should consider replacing it with a newer series (system Q or the current iQ-R) it's quite simple.  

if you don't know the old paswords just change to operator and then back again to level

The FX3G doessn't support this. You can either mov to an array of bits or use an instruction to get the bit value.

Should be part of the installer of GX Works 2. But you shouild be able to install it maually. GX Works 2 installer DVD :\\ GXW2\Disk2\GXD1\setup.exe

2nd post with the same question

Looks like it is  not a default mitsubishi Error but one programmed into the HMI. I would readout the project and see which PLC device generates this error 

Just reinstall the BootOS it's the easiest So just go to => Communication => Write to GOT => comms settings => Select BootOS from thje drop down and press GOT Write button