MP2310iec

One common cause of the CPU load being higher than expected is caused by using a custom Function Block that uses a large structure connected as a VAR_INPUT instead of a VAR_IN_OUT.

When a variable is declared as a VAR_INPUT, the MPiec Controller copies the entire contents of the structure into the Function Block every scan. Other programming languages refer to this technique as “Passing by Value.”  In this situation, the Function Block does not have the ability to alter the contents of the original data. When declaring a variable as VAR_IN_OUT, the MPiec Controller passes a pointer to the original location of the variable rather than a copy of the data. Other programming languages refer to this technique as “Passing by Reference.” The pointer is an internal 32 bit value, which is significantly more efficient than copying the entire contents every scan. This method also gives the Function Block the ability to alter the contents of the structure variable.

To show this example in practice, the attached document shows two scenarios. The first scenario scans a Function Block with a large structure as a VAR_INPUT and results in a high CPU load. The other scenario shows the same structure as a VAR_IN_OUT and has no impact on the CPU load.

The large structure is an array of an array creating 500,000 LREAL’s. There is nothing else in the program, the custom Function Blocks have no code.

If the Vipa Ethernet coupler was previously configured and then modules are added or changed, you must perform an online save through its web page before they will function correctly.  If the new configuration is not saved, the Vipa Ethernet coupler will flash the SF and MS red LED’s when the controller connects.  The I/O status variable in the MotionWorks IEC project will show a status of 0x1000 (connected) or 0x320 (deleted configuration) but the I/O will not update.

To save the configuration on the Vipa Ethernet coupler:

Open the Vipa web page by typing the IP address into the browser’s address bar.

Note:  Disconnect or stop any MPiec controller Ethernet connection to the Vipa bus coupler.

Navigate to the Configuration tab and press the Save button.

After saving the configuration, the Vipa Ethernet coupler must be powered down for at least 20 seconds, and then powered back up.  If the power is short cycled, the Vipa Ethernet coupler will not power up.

See attached document for a screen shot of the web page’s Configuration tab

The controller counts all configured axes and any axes it discovers when the CNFG switch is on. To avoid adding discovered axes to this count, set the CNFG switch to off before the controller is powered on, or disconnect the additional axes.

There is an error in older firmware versions that cause analog output channels with a negative offset to only output the maximum voltage. Use firmware version 3.1.1.1 for all MP2300 type controllers and firmware version 3.5.0 and higher for all other controllers to correct the issue. The 3.5.0 release will be available in April 2018.  Please contact customer support with help in resolving this issue before then.

IF YOU SEE THE “Firmware Update Failed!” SCREEN DO NOT REBOOT or the controller can become unusable.

Click on “update the firmware” and select the same firmware file that was on the controller.

Version 3 firmware for the MP23xxiec controllers contains extra code to present a modern web interface. This has caused the version 3 firmware to consume more memory than the version 2 firmware. Some users will find that they cannot upgrade the firmware if a project is stored on the controller. Also, we have found that some archives created in version 2 cannot be loaded onto version 3 controllers.

To upgrade your MP23xxiec controller to version 3:

1. Make sure you have a copy of the project. You may need to load this project manually.

2. Create an archive of the project and save it.

3. Delete all user files (the project) from the controller.

4. Upgrade the firmware.

5. Install the archive.

6. If the archive installation fails, load the project manually, by opening the project, opening Hardware Configuration, saving the configuration to the controller and rebooting, and compiling and downloading the project.

See attached document

There are two cases when this may occur. If the library cannot be found on the PC or if the library is marked as open.

See attached document for instructions.

The MPiec controllers have evolved over their lifespan. The first versions only supported Internet Explorer with the classic interface. A modern interface was added and fully supported in firmware release 3.2.0 to conform to more modern browsers. The classic interface is the only interface supported by Internet Explorer and is available in all firmware versions. The attached chart shows the supported interface - firmware version combinations.

See document MTN-97XRJ3 “Using Web Server Classic on the MPiec Controllers” for more information on using the classic interface.

There are two ways to reset the controller to factory defaults, one using the web browser and the other through Hardware Configuration.

See attached document for specific instructions.

Please open the pdf for a look at the Controller Memory for the MPiec Controllers.

The controller was unable to load a configured axes group is indicated by the error 440C 1003 with the description: Unable to add axes group to groupIODriver. Check the validity of the handle. The most likely cause is that the INIT switch of the controller is ON. The INIT switch disallows the loading of any saved configuration.

To fix this alarm, turn the INIT switch off and reboot the controller.