Michael Walsh

Yes, that would work, but the conditions would not change as he I believe he is asking. This would only create a static configuration of the IO. Personally, I would just turn them on manually as I need them.  I don't know how to create the file for the playback mode.  

The motor needs to be tuned.  There are parameters in the drive that need to be modified according the the load, inertia and movement requirements of the system.  Often, a simple auto tune process is enough to make the motor perform well and not vibrate or hum.  Please investigate auto tune in the manuals. 

If you are in the CIO area, it is not retentive, so when you go into run / monitor, it is all reset to zeros.  The memory tool will not do what you want.  I/O Conditions and replay is the only possibility.

What I told you shows used and available.  If you need percentage, do the math.

Change the function block.  Add a second boolean input that is called Invert.  If it is true, it inverts the input if not, it does not.  Or if it always needs to be inverted, just change the FB to invert it all the time.

Use the MC_GearIn function block.

With respect to program capacity, View pulldown menu, then Memory View

Thanks for the update!

https://forums.mrplc.com/index.php?/files/file/1162-nx1p2-modbus-rtu-code-and-write-up/

NX1P2 Modbus RTU Code and Write Up. View File This code is designed to implement Modbus RTU on an NX1P2 Controller using the NX1W-CIF11, NX1W-CIF12 or NX-CIF105 module (mounted to controller or EtherCAT coupler).  Created by an Omron Engineer. Submitter Michael Walsh Submitted 05/22/20 Category Tutorials and Quickstarts

Well, that could certainly be done on the Omron side as well.  If the Fanuc needs an integer, we can do as I stated very early in this thread.  However, it seems the Fanuc has no problem sending a real to the Omron controller.  You would think it could handle a real being sent to it.  

Of course you need to be online with the controller and depending upon the memory area, you may need to be in program mode. 

Yes.  3300.00 would be the first bit in that area. Each address is a 16 bit word, so 3300.00 - 3300.15 is the first word, 3301.00 - 3301.15 is the next and so on. 

Ultimately, the data is being sent as a hexadecimal value.  It is all in how it is interpreted.  If you look at what the Fanuc is sending the NX1P2 using Wireshark or something, it is sending a value of C316 0000 (hex).  If you then tell the NX1P2 to interpret that double word of data as a real number (by making the variable that receives it a REAL), then it will use it as -150.0.   Likewise, going the other direction, the NX1P2 is sending out a double word of C316 0000 in hex and the Fanuc needs to interpret that as a real number.  This number could just as easily be interpreted as a signed double integer and would have a value of -1021968384.  This would obviously produce a non-desirable result.  In my opinion, there needs to be something done in the Fanuc controller to make it interpret this data as a REAL number.