In the previous installment, MagneMotion Blog Part 11: Tuning, we discussed how to modify a system for better performance and efficiency. In this article, we’ll share details on the track graphics used by NC Host to visualize MagneMotion systems and how you can customize those graphics for your particular application.
A quick reminder: NC host is used to monitor the status of MagneMotion controllers, motors, and movers. The NC host IP address should be the node controller.
MagneMotion Guide Series
- MagneMotion Guide Part 1: Creating Configuration Files
- MagneMotion Guide Part 2: Starting up and Commissioning a Track
- MagneMotion Guide Part 3: Controlling a System with a PLC
- MagneMotion Guide Part 4: Using Path and Station AOI’s
- MagneMotion Guide Part 5: Alternative Routing Controls
- MagneMotion Guide Part 6: Track Recovery Considerations
- MagneMotion Guide Part 7: Traffic Lights
- MagneMotion Guide Part 8: Simulation
- MagneMotion Guide Part 9: Traffic Jam Prevention
- MagneMotion Guide Part 10: Moving Track
- MagneMotion Blog Part 11: Tuning
Track Graphic Files
Track graphics are files with the .mmtrk extension that are used to help visualize a MagneMotion system when using NC Host. For general information, see MagneMotion Guide Part 2: Starting up and Commissioning a Track.
Typically for MagneMotion Lite systems, track graphics are generated in the Magnemotion Configurator tool by going to File -> Export -> Create MMTRK File From Config
Below is an example of a track layout file.
Here is that same track’s corresponding .mmtrk file visualized in NC Host.
When monitoring the track graphic in NC Host, you can easily see where each vehicle is on the track. By hovering over track segments, you can also see which path of the track you are hovering over.
These .mmtrk files are simple text files which can be opened in the text editor of your choice. If needed, you can also modify the track file to better fit your system.
The track file components are simple. Each section starts with a comment describing the path that the section of the text file is defining. If you are making changes to a track file, it is advisable to include additional comments on whatever change is being made.
Next, the track file defines the path connection. The path_start #a #b line indicates that you are defining path #a that has a previous path of path #b. Note that some paths have multiple previous paths defined in the configuration file, but only one previous path needs to be defined in the track file. This is because the track file is only concerned with the physical location of the path, not how it links to the rest of the system.
Following the path definition, the file will contain information on each motor in the path. Starting from the first motor, there will be a line that contains the motor type and the motor’s direction. This direction corresponds to the orientation of the motor in the track graphic file. Everywhere the track turns, this direction should change for the next motor.
In the examples below, note that the direction changes from “left” to “right” after the “motor_r_curve” entry to ensure that the track graphic follows the actual track layout from the configuration file.
In track layout files, there are no separate definitions for switches. Instead of having a single entry for a switch on the track, there will be an entry for each path that the switch is on for both the straight and curved section of the switch.
For example, for a right switch that merges paths 3 and 4, one path will have a “motor_q_meter” entry for the straight section of the switch, and the other path will have a “motor_r_curve” entry for the curved portion of the switch.
In addition to defining the track, you can also modify the track graphic to change how vehicles are displayed in NC host. Adding a line setting the vehicle_size will change the size of the vehicle graphic displayed in NC Host to better match your system.
Note that NC Host doesn’t do any verification that the track graphic you are using lines up with the configuration file of your system. If you end up using the wrong .mmtrk file, NC Host will still display the graphic and attempt to display where vehicles would be on the track even if path lengths and orientations do not match up.
Disjointed Tracks
There are unfortunately some limits in the track graphics that can be created by the MagneMotion configurator tool. If any track is “disjointed” (i.e. completely separated from the rest of the track), then the configurator tool will be unable to generate the track file for that system. However, you are still able to create the track file for that system manually.
Let’s say we have a MagneMotion Lite track where the majority of the track is in a loop on the ground. A part of this loop is a section of track that can be raised to connect to a stretch of track that is suspended by the ceiling. So, we have one track system that is split into different sections.
You can’t get this track file directly from the configurator, but you can start by making the paths of just the ground track and creating a .mmtrk file from that partial section of track.
Now, to add additional track segments to this file, we need to create a disjointed track section. We do this by adding another line that starts with “track_start” followed by parameters that determine where in your graphic the disjointed track will appear. For each new disjointed track added, you need to input the distance and angle from the very start of the track file to the start of your disjointed track. Then you simply need to add paths/motors to the file to match your system.
If you’re having trouble calculating the position your added track can be in, you can always just display the track graphic to check the position and adjust as needed.
Now, it’s a simple matter of repeating that same process to add the ceiling track.
Note that there are other ways you can arrange your track. If you wanted to have your elevator track show up in line with the ground track loop you can tell the track graphic file to consider path 2 to immediately follow path 1 by just manually adding path 2 as a following path for path 1.
Quickstick Track Graphics
You can also manually create track graphics for Quickstick systems similar to how you’d create them for a disjointed track. The formatting of Quickstick .mmtrk files is a little different from MMLite track.
Instead of being given a cardinal direction with each motor, Quickstick motors are each assigned an angle. This allows a track graphic to properly display the curved motors sections that Quickstick can allow. After each Quickstick motor entry, you can also enter a gap distance and angle to display the larger motor gaps allowed between Quickstick motors.
Below is a straightforward example with a linear track.
If the Quickstick angles are adjusted, you can also display a nice track curve.
You can even combine methods to create disjointed tracks with Quickstick graphics to create complicated layouts involving things like rotary tables and moving path nodes.
Learn more about DMC’s MagneMotion programming expertise and contact us today to get started on your next project.