Gambit

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)  

Probably but I would have to check but for speed and ease i would still use the ADP. Also the distance would be better between HMI and Controller   

I would add an FX3U-ENET-ADP and connect it via athernet

Which PLC will you be adding another FX3U ? Which GOT/HMI ?

Good info @mike but the FX5 support direct comm to a lot of other brand controller via ethernet.Called simple plc comm So you do not have to use modbus or write any code 

The Mitsubishi US guys did a webcast on Simple PLC with omron but canlt find it anymore. Do have this screenshot file though. It's with an RPLC but the setings would be the same  screenshots.pdf

Which Dev did you have before and into which device did you change it ?

DEBCD(P) will seperate the exponent and the mantissa part. But if you convert the Real number (2.34) to an integer value (FLT2INT) you will get an integer value (2). turn that back into a float INT2FLT and subtact that from the origional with DESUB(P). you should have your remainder (0.34)      

It's just M1 - M5 so any program will do 

here is an example. I delete the other pages but if you have any questions let me know alarm.GTX

Dan werkt de comm niet op een van de GOT1000. Waarschijnlijk is het stationsnummer van beide GOT hetzelfde dat moet je dan veranderen 

It would be good if you specify which GOT you have. You can't add another D register to show however what you can do is a pop up screen which appears when youpress the alarm woth additonal information. How to solve the alarm for instance and you can add the Register on that screen. You can have a different screen for each alarm or you can use the alarm nr for the window nr or alarm text   

Haven't checked the code but there is a space before the 10. Could be the issue. which PLC are you using and which software ? Hmm checked with GX 2 but it compiles without any problem   

No Bak-ups is the worst !!!! The yellow code usually means it's code that can't be converted to ladder in GX Developer/Works 2. Might have been programmed in IL or with Melsec medoc dos. But you can see the complete code in IL