This article is intended to aid a user of the MachineMetrics platform that wants to track PMC Parameters or Signals from a Fanuc machine. This is an extension of the guide to configure Fanuc machines through the Machine Settings.
While there are technical details under the hood separating PMC Parameters and Signals in a Fanuc machine, this distinction is not carried over into the MachineMetrics configuration for Fanuc adapters. Both PMC Parameters and Signals are treated very similarly by the platform and so we configure both of them in the same way.
Note: The old Signals config block is being deprecated. Users should strongly prefer configuring registers under the PMC configuration block. As a general rule, all PMC addresses, be they PMC Parameters or Signals, should be configured under the PMC configuration object for the best performance and experience. If you have questions about this functionality, please reach out directly to your customer success manager or contact email@example.com.
Topics covered in this article
PMC’s are emitted from the adapter as a key/value data item for each PMC. The name of the PMC specified in the app configuration will be the key name used and observed by App and the value in the configuration is the PMC address. It is common to just use the same value for both, although it is not strictly required.
This is the preferred way to configure both PMC Parameters and Signals.
Note: On older Fanuc installations, there is a maximum limit of 32 total PMC addresses that could be monitored. This limit has been removed on later versions. If you are experiencing problems with this configuration, please reach out directly to your customer success manager or contact firstname.lastname@example.org to ensure you are on a supported version.
Signals are also PMC addresses, they share the address format and share the same configuration setup. There used to be a signals configuration section that is no longer being supported moving forward. If your installation is using the signals section, migrate to the PMC installation above.
Note: The Signals config block is being deprecated. All installations should be migrating to configuring all PMC Registers under the PMC configuration block.If you have questions about this functionality or migration process, please reach out directly to your customer success manager or contact email@example.com.
PMC Data Mapping
After configuring PMC Parameters they need data mapping to be conducted in App. For more detail on mapping data see Mapping Data (Machine Settings) . Here we will focus specifically on the necessary details for understanding mapping PMC Parameters. PMC is a subcomponent of the Controller component, and the data item type is Register. This is because PMC Parameter values are Byte or Bit values.
Below is an example using just the address as the display name, however, the user may instead prefer to use the human-readable name here. In the below example G0070.5 might instead define the Display Name as “Spindle Running”.
For demonstration here only a few were mapped, these PMC addresses configured this way would render in the App diagnostics page as:
Alternatively, if the user chose readable display names corresponding to the PMC Parameters:
If you have questions about this process, please reach out directly to your customer success manager or contact firstname.lastname@example.org.
Please sign in to leave a comment.