P367 Thermocouple Integration with Motion Perfect v5.1 and later
With the launch of Motion Perfect v5.1 and firmware updates to the P367 Thermocouple device it becomes
easier to set up and control your P367 slices.
Below is a screen shot showing the Basic Setup screen which easily allows programmers how to configure the P367 slice
that is on the EtherCat network. The P367 will automatically be detected as a recognised device and therefore users
will not require any EC_EXTEND files to be able to control the device.
Attached is a sample program bundle containing a project design with multiple P367's. It has a simple control program and associated
control screen for each Thermocouple slice. Also included is the relevant Application note for the P367 and the present P367 firmware
build of V2.200.
Related Articles
P367 Thermocouple Slice Updated Technical Note
P367 Thermocouple FlexSlice Firmware User Guide This documentation is for use with controller firmware v2.0304 and newer. With this firmware version the controller will identify the P367 module without the need for the use of an imported EC_EXTEND ...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 ...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.Can I use Motion Perfect v4 with the new MC404-Z?
The MC404-Z and other new products require the latest version of Motion Perfect to run them. At the time of writing this post, the latest version is MPv5 version 5.0.2 and that is the recommended version for programming the MC404-Z 4 axis stepper ...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. ...