photovoltaic

Some people might find it convenient to daisy-chain several devices, and the NX terminals offer a convenient way to do it, but you'll likely melt a terminal or two if you're not careful.

I believe that's how much current you can take from the neighboring terminal which is in common with the terminal getting current provided to it. This current is usually for powering "unwired terminals". Its essentially a measure of the current capacity if you were to run current in one terminal and out of the one beside it.

I dug into this a little, I don't think what you are trying to do is possible. There are system bits you could use to detect a connection loss and then execute a clear instruction on the input data when it is lost. 1 line of code for a simple fix. In the example picture I assumed the G9SP is 192.168.250.20, yours may differ.

Instead of comparing after the subtraction you need to compare before and then perform the subtraction based on which value is higher. Example: If A < B then compare B-A If B < A then compare A-B You'll be seeing variable roll-over otherwise like pturmel said

There are a few different ways you could do this. I personally would have a global subroutine running at an interval and in this subroutine I would examine _HMI_CurrentPageIndex and if I detected a new page (Index != lastIndex) I would have an action associated with that page index value (case statement). The action would be the recipe you want to work with. You could set this up to perform an action once per page change with a sort of "run once" latching variable.  

1) This cable is not for communication between a PT and a PLC, it is for communication between a PC and a PLC. It will work for the test mode in CX-Designer. The behavior you are seeing is typical of a no communication situation.   2) NS HMIs are obsolete, the NB HMIs are affordable and widely available.

No system variables exist for communication that isn't cyclic and managed by the system itself. FINS, Modbus, MQTT, and Socket Services all fall in this category.

Are you referring to using a CJ1W-EIP21 card or using the CJ areas for FINS?

As a quick test, connect the serial cable you have, ensure the DIP switch for the Serial port is ON (cycle power if you just switched it), and in CX-Programmer choose PLC -> Auto Online -> Direct Online. Select your Serial port and choose Connect.

I just had the Test function working on my end. If you cant connect to the PLC through your serial cable then you likely have the wrong cable. Omron has a unique pinout on their DB9 connectors. Are you using a standard serial cable? To get the TEST working in CX-Designer I set the PLC DIP switch to Auto, and then in CX-Designer I set the comm port and used Toolbus. It worked fine.

Can you connect to the PLC with CX programmer via serial? This will verify the cable. I have an old project somewhere with a similar setup, I'll try and find it and share the settings.

In theory yes. However what I would do instead is pull the current program off the PLC, compare it with your backup, and then make modifications. There may be some important changes to the PLC that aren't on your backup.

For running a test HMI from CX-Designer and connecting to your PLC you can't use USB. The Test function replicates the driver the HMI uses which limits you to either Serial or Ethernet drivers in most cases. Adding an RS232 module will work with the Test function in this case.

ESI files transfer with the project, EDS and IODD files do not. The IODD files aren't relevant in this case since you are using the IFM master. Your PLC just sees a block of data coming back, it doesn't care what the bits and bytes are. You would need to add them with the IFM software I assume.