Gambit

Did you try reinitializing the module  SH081976ENG-6E2 G(P).UINI, Z(P).UINI

I don't think it is possible. You can set an inpu for run/stop.  So you would be able to do that from the HMI. alternatvily you could set an output which breaks te power to the plc. But why do you need to rst the PLC ? Isn't it better to solve the problem ? 

It's probably the symbolic info which is taking up space.  You don't need it. and if you want it change the program memory to SD card  

The program size in calculated in steps. you should use the check program size in the options

You probably have a older version of GX Works 3. The latest one is 1.096 In NL the updates have been free so far  

yes you can just click the alarm itself and have a pop up screen come up. I think i have an example somewhere where i use the alarm number for the comment number so i only need one pop up screen/ took the other pages out but it should still work or give you an idea how to recreate it I took the comment number instead of the alarm number but both are possible Example_Alarm.GTX

post your demo project and ill have a look  

The DSCL2 instrucion is scaling with the option to have multple ranges. However this is only for intger values (16 or 32 bit)> You would either convert your real to intger values do the scaling and then make them floats again.  or just multiply the reals with the Gain and add the offset In you case (0-1200) to (0-100) the gain would be 0.0833333 and the offset 0.  

M8000 are the old FX special. The FX5 is more like the system Q/iQ-R SM400 etc. As for mofbus there is an example program in your e-manual See PAGE ID: JY997D56101-6B in your e-manual viewer   I expect you want serial modbus because you don't need any porgramming for modebus TCP/IP

If you  replaced an FX5 with another FX5 than the porgram schould be the same and the GOT should be able to comm. Have you checked the diagnostics from the HMI and Ethernet diagnostic in the FX5 ?  

Have a look at the example program on page JY997D56101-6B You will get an abnormal completion of processing if the communiaction is not oke     

Uxxx\G501 or use the label below

DMOV K8M100 K8Y0

Taka a look at page JY997D56101-31 of the e-manual viewer  

The RS485 protocol seems to support mobus so this would be easiest to use. page 11: RS485 Communication RS485 is an industry standard for defining serial communication. Due to its balanced signalling, RS485 is effective over distances, even if other electrical signals are present. Its stability makes it well suited to connect multiple receivers to a single network. You can operate RS485 in half-duplex mode and it is well suited for use with the Modbus protocol. On the 25-pin connector, RS485+ and RS485- pins are present.

Yuo can use the latch data backup function - or you can create device memeory files to store or send the values

RT Visualbox is limited and intened for operators, You could go to the position list and just copy the original position and change the X or Y with a 100 mm or you use panel and use the inching method to jog 100mm.   This is RT toolbox  

What do you need to know ? There is a Webcast about RT visualbox. If you want to go deeper you can use RT Toolbox which has Visualbox programming inside 

GX Works 2

Use melsecnet diagnostic 

Use Uxxxx\G1900024.0 for an open contact where xxxx is the I/O number of the Ethernet module. (If the ethernet module is on IO nr 20 use U2\G.....

This is what @AndreasW is writing about  In this eaxmple 5 x 16 bits starting from M1 alarmBit.gx3 But pref. you don't want to use devices in your programs but labels Define the MyStartAdress as aan array of Bool   

See The + on the bottom of the OR block. You can extend the inputs   Also If you alll the  bits are sequential you can put them in a couple of Dwords and check if they are not 0 Or create an array and create a for next loop wich checks each bit /

For the Mitsubishi Drives you could also use  CC-Link IE Field basic ofc but i Guess you woudl like to be able to choose wiichi drive, So modbus TCP/IP is usually supported by most brands and you would have accees to all hardware remotely via ehternet if needed. As for your parameters. I would create my own (companion spec) So my list of params I would to like to use.  Once created I would then only write a program which send this list to the correct modbus locations depending on the brand(s). (reorder the list so to speak) Then have a universal program again to send all the data to the drive if possible. (maybe a different modbus starting adress is needed)