10.1" cMT3102Xv2 and M02 Wi-Fi Enabling Package

RFID, which stands for radio frequency identification, is a form of wireless communication that uses radio waves to identify and track objects. There are a number of forms of RFID technology on the market today. The most recognizable include low frequency (LF), high frequency (HF), and ultra-high frequency (UHF).

Ultra-High Frequency RFID readers are devices that communicates with RFID tags in the 860–960 MHz range, allowing for long-distance, high-speed, simultaneous reading of many items for efficient inventory, logistics, and tracking, offering longer read ranges (up to 12m) and faster data transfer than other RFID types.

Yes, all our HMIs and cMT HMIs support RFID card authentication via the use of a USB RFID card reader. We also have one 10.1″ HMI with a radio frequency identification scanner built into the front bezel.

You will have to maintain separate projects. Once your project is converted from HMI series to cMT series, it cannot go back to HMI. If project updates are needed, make sure to update the HMI project first, save it, then convert that to cMT, and save that separately.

Yes. The EBPro software includes simulation modes that you can use to test every aspect of your project before buying anything. There are two types of simulation modes available in EBPro: online and offline.

Online simulation will run your HMI project on a PC as if it were an HMI. This enables you to test device communication and preview program behavior without an HMI present. For cMT Series models, online simulation can be used for up to an hour at a time, while HMI Series models are limited to 10 minutes of online simulation. You must connect your external devices to the PC for online simulation; otherwise a connection error will display.

Offline simulation will allow you to preview everything except for the external device communication. This can be helpful when adjusting the logic, layout, and window behavior for your HMI project. This can be run on the PC at any time and does not require your other devices to be connected.

Build & Test Drive your HMI with Project Simulation

To convert a Standard/Advanced project to a cMT Series project, open the System Parameters and click on the Model tab. Select the cMT Series model you want to use and click OK to close the System Parameters window. If the screen resolution of the selected cMT Series is different than the original Basic/Advanced HMI, the “Resize Pop-up Windows/Objects” dialog will pop up. It is recommended that all the check boxes are selected and then click OK.

When converting a Standard or Advanced HMI project to a cMT Series project, there are some possible issues you may need to contend with due to the differences between the Advanced/Basic HMIs and the cMT Series HMIs.

Note: It is not possible to convert a cMT Series project to a Standard/Advanced Series project.

Here is a short video showing how easy it is to convert an HMI to a cMT device.

 More information and troubleshooting tips:

Basic Security vs. Enhanced Security

Only Enhanced Security can be selected when creating a new cMT Series project. However, if using Basic Security in the Standard/Advanced project, the converted project will retain the
Basic Security settings. Nevertheless, if you will be using cMT-Viewer, it is recommended that you switch to Enhanced Security for the reasons outlined in the next paragraph.

When using Enhanced Security, only PLW registers can be used for the Control Address. Since the cMT Series have a built-in cMT Server, a cMT Viewer can connect to a cMT Series HMI and run the project locally. PLW (Private Local Word) registers are used locally in the cMT Viewer to allow a user to log in and out of the HMI without affecting the actual physical HMI. This way, one user can be logged in locally to the HMI while a different user can be logged in independently using cMT-Viewer.

Stacked Objects

In a cMT Series project, you cannot stack objects one on top of the other and trigger them all by pressing the top button. Only the top button will activate.

In most cases, the Combo Button can be used to recreate the functionality of the stacked objects. For example, if several Toggle Switches are stacked one on top of the other to
simultaneously turn on multiple bits with the push of a button, the Combo Button can be configured to turn on multiple bits with a single press of the button.

Under the Tools menu in EBPro, there is a tool to “Find Overlapping Objects.” Right next to it is an option to “Convert to Combo Button.” This can be used to automatically convert stacked objects to a single Combo Button.

System Keypad

cMT Series HMIs have a built-in System keypad that can be used to enter numbers in a Numeric Object and ASCII characters in an ASCII Object instead of the Custom keypads on Windows 50 – 65.

The Custom keypads for the Basic/Advanced Series will not work in a cMT Series project because of the issue with stacked objects described above. The Custom keypads on Windows 50 – 65 for the cMT Series have been modified so they do not have stacked objects.
Therefore, it is recommended that any Numeric or ASCII objects in the converted project be
modified so they use the System keypad.

Another option is to copy the keypads on Windows 50-65 from a cMT Series project of the same model into the converted project. Then the “Custom keypad” option can be used.

Capacitive Touchscreen

Since the cMT-Series HMIs have
capacitive touchscreens instead of resistive touchscreens, some objects like
the Trend Display work differently in a cMT Series project. For example, in a
Standard/Advanced Series project, the Trend Display has a scroll bar at the bottom
that can be used to scroll back and forth on the X-axis. In a cMT Series
project, there is no scroll bar. Instead, you can simply swipe your finger left
and right on the Trend Display to move back and forth on the X-axis.

Data Sampling with cMT Series

Data sampling is implemented a little differently in the cMT Series. Here is a brief description of how it works. For more information, refer to “Chapter 8 – Data Sampling” in the “EBPro-Programming Manual”:

History file Disabled

With History file disabled, data is stored in HMI RAM memory. When 10,000 records are reached, the oldest 1000 are deleted from the HMI memory, with 9000 remaining. When 10,000 records are reached again, the next 1000 oldest record are deleted from HMI memory, so that at any one time the number of records in memory and being displayed on a Trend Display is between 9000 and 10,000 data points.

If the HMI is rebooted, data is erased and starts recording new data.

History file Enabled (All records in one file)

Save to HMI memory (10,000 limited)

With History file enabled, data is stored in a data log file in HMI memory. When 10,000 records are reached, the oldest 1000 are deleted from the HMI memory. When 10,000 records are reached again, the next 1000 oldest record are again deleted such that the
number of records will always range from 9000 to 10,000.

Control Register:

1 (Clear): Clears the data in HMI memory

2 (Sync): N/A

3 (Sync and Clear): Clears the data in HMI memory

Save to HMI memory (until space full)

Data is saved in the data log file (cMT_log000.db) in HMI memory until the memory is full.
Note: When converting the cMT_log000.db file to XLSX, Excel creates a new tab
at 60,000 records.

Save to USB disk or SD card

Creates a *.db file on USB disk initially but it is empty. After 10,000 samples, the data is written to the USB disk. The Trend Display continues to show all the data, as does the History Data Display. Every 1000 samples, the data log is updated with the most recent 1000 records.

If “Auto sync. Periodically” is selected, the data is automatically backed up to the USB disk or SD card each designated time period.

Control Register:

1 (Clear): Clears the data in HMI RAM memory

2 (Sync): Copies data from HMI RAM memory to USB flash drive

3 (Sync and Clear): Copies data from HMI RAM memory to USB flash drive, then clears data in HMI RAM memory

If data has already been sync’d to USB flash drive, that data will still appear in the Trend Display. Subsequently, there will be a hole where the data was deleted from HMI memory
if it didn’t get sync’d to USB.

History file Enabled (Customized file handling)

Save to HMI memory (until space full)
Data is stored in a data log file in HMI memory. When 10,000 records are reached, the oldest 1000 are stored in the designated data log folder in a separate file. When a new file is created according to the customized file handling settings, all the data for the previous session is stored in the data file in the data log folder and a new data log file is
created in HMI memory for the new session.

Data is saved in HMI memory until the memory is full. The Preservation limit applies according to the number of files selected.

Writing a 1 to the Control Register clears the data log in the temporary HMI memory but not the data files in the data log folder. The data log files in the data log folder can be cleared in the System Settings window History tab.

                Save to USB disk or SD card

Every time a new file is created, the Trend Display and History Data Display refresh and only display the data from the new data file.

History
Data Display (Clear, Sync; how does it work with backing up data files)

“Clear” clears the data from the current datalog file in HMI memory or external memory (USB/SD card). Older datalog files are not affected.

Preservation Limit

Number of days selected plus the partial current day. At midnight, the oldest day is deleted as the new day starts.

Option List

With the cMT Series, the Option List is not used to select history files for a Trend Display or History Data Display. Rather, an Option Button (“gear” icon) can be enabled in the Display Object Properties, which allows you to select the date for the history file you want to view.

Event/Alarm Logging with cMT Series

Event/Alarm logging is implemented a little differently in the cMT Series. Here is a brief description of how it works. For more information, refer to “Chapter 7 – Event Log” in the
“EBPro-Programming Manual”:

History files Disabled

With History file disabled, events are stored in HMI RAM memory. When 10,000 events are reached, the oldest 1000 are deleted from the HMI memory, with 9000 remaining. When 10,000 events are reached again, the next 1000 oldest events are deleted from HMI memory, so that at any one time the number of events in memory and being displayed on an Event Display is between 9000 and 10,000 events.

If the HMI is rebooted, all events are erased and the HMI starts recording new events.

History files Enabled

                Save to HMI memory (10,000 limited)

With History file enabled, events are stored in an event log file in HMI memory. When 10,000 events are reached, the oldest 1000 are deleted from the HMI memory. When 10,000 events are reached again, the next 1000 oldest events are again deleted such that the number of
events will always range from 9000 to 10,000.

                Save to HMI memory (until space full)

Events are saved in the event log file in HMI memory until the memory is full.

                Save to USB disk or SD card

Events are initially stored in HMI RAM memory. Creates a *.db file on USB disk/SD card initially but it is empty. When 10,000 events are reached, the first 10,000 are written to the USB disk or SD card. Subsequently, with each additional 1000 events, the events are
written/appended to the event log file on the USB disk or SD card.

If “Auto sync. Periodically” is selected, the events are automatically backed up to the USB disk or SD card each designated time period.

Option List

With the cMT Series, the Option List is not used to select history files for an Alarm Display or Event Display. Rather, an Option Button (“gear” icon) can be enabled in the Display Object Properties, which allows you to select the date for the history file you want to view.