Saving VR from MC206x to MC4N

AN-409 Saving VR from MC206x to MC4N

When converting from some of the older controller like MC2xx series, the VR(s) from the project have to be transferred to the new controller for the program to work.

In this document, it explains how to copy over these VR(s) from MC206x to MC4N

This document can be also applied to any MC2xx series using Motion Perfect 2

    • Related Articles

    • MC_CONFIG vs Flash parameters

      All Motion Coordinators store the IP_ADDRESS, IP_NETMASK and IP_GATEWAY in Flash memory.  So there is usually no need to add them to the MC_CONFIG. There are some differences with other system parameters. MC4N-ECAT, MC4N-RTX, MC6N-ECAT, Flex-6 Nano ...

    • Motion Perfect problem when SCOPE command is used

      When running the SCOPE command in a program, I think Motion Perfect doesn't like the SCOPE command being issued over and over when I run it. It seems more stable when I comment the SCOPE command out after it's ran once. ...

    • Will processes change with Motion Perfect 5?

      Process numbering is controlled entirely by the firmware so nothing should change when you update Motion Perfect.  For example, process numbers for MC405 are 0 to 9.

    • MC202 controller and Motion Perfect

      For the MC202 you must use Motion Perfect 2. Motion Perfect versions 3, 4 and 5 are for the later generation of Motion Coordinators that connect using Ethernet. I am running this version of Motion perfect 2 on my Windows 10 PC. You need a COM port on ...

    • What is the life of Flash Data?

      In the MC206 and MC206X, the TABLE is in battery backed RAM. In the MC4/5/6 Flash memory is used but like a USB Flash-stick. The firmware creates a file store area on the Flash and maintains an index to the contents. The Flash memory used is much ...