Upload
dominh
View
223
Download
0
Embed Size (px)
Citation preview
產 品 通 報 Newsletter
1/53
Purpose:
Release information about the application software DOPSoft 2.00.06 for DOP series products.
Latest firmware for the DOP-B series: 3.0096
Latest firmware for the DOP-W series: 3.0083 Latest OS for the DOP-W series: 1.028 Latest firmware for the HMC: 3.0179
Latest DSP for the HMC: 1.0029 Description:
Applicable models: DOP-B / DOP-W / DOP-H / HMC series
1. Software / firmware revisions:
1.1 Fix the DOP-B series HMI crash occurring when you enter the system menu and
return to general screens if IP conflict occurs.
1.2 Fix the DOP-B series HMI crash occurring when it reads from or writes to devices with
allocation unit size over 4K.
1.3 Fix the issue of exporting older history data in non-volatile memory in HMI.
1.4 Fix the DOP-B series HMI crash occurring when you insert an external device and set
to save the non-volatile data in the external device.
1.5 Fix the communication setting error occurring when cycling the power to
DOP-B07S410 HMIs.
1.6 Fix the continuous error of auto-detection window when the communication setting
between DOP- B07S410 HMI and Delta ASDA-A2 is correct.
1.7 Fix the communication error between DOP-W series HMIs and the controller using
Modbus TCP/IP when the communication is lost for 16 times or more.
Technical Announcement
Issued by IMSBU
HMI Author(s) Daisy, Huang
Security
Classification
General
Confidential
Issue No. HMI17070700 Released
Date July 07, 2017
Recipient Product Manager, BU Sales Representative, Global Service Partners
產 品 通 報 Newsletter
2/53
1.8 Fix the copying failure occurring when the DOP-W series HMI screen data file contains
alarm data.
1.9 Fix the execution error of the momentary button with user security level settings for
DOP-W series HMIs.
1.10 Fix the execution error of the control section occurring when the DOP-W series HMI
enables the communication optimization function.
1.11 Fix the DOP-W series HMIs with no response for a short time when you trigger the bit
for saving as multiple files in history buffer.
1.12 Fix the DOP-W series HMIs with alarm clearance error when the number of alarms
exceeds the savable range in the history buffer.
1.13 Fix the screen download failure when DOPSoft is in Windows 10 environment.
1.14 Fix the DOPSoft crash issue when exporting multi-language texts in Windows 10.
1.15 Fix the calculation error (repeat calculation) when you compile projects in DOPSoft.
1.16 When HMI connects with eRemote, fix the HMI crash occurring if you go to the system
menu and return to general screens.
1.17 Fix the connection error between eRemote and the HMI when GridBox element is set
with an After Execute macro.
1.18 Fix the HMI with no response due to users' not removing the external device safely
before re-plugging in the device.
1.19 Fix the HMI crash occurring when it reads from or writes in NTFS-formatted storage
devices.
1.20 Fix the reading error occurring when the enhance recipe imported to the HMI is edited
with Excel.
1.21 Fix the HMI crash occurring if you plug in the external device to auto import the recipe
when HMI screen shows the message that the USB Disk does not exist.
1.22 Fix the HMI crashing error occurring when the alarm message contains more than 56
characters.
1.23 Fix the alarm number recording error that occurs when you set to save the non-volatile
data (alarm history) in the HMI.
1.24 Fix the issue of being unable to open the file by computer while you use “Save as
Multiple Files” function in the history buffer.
1.25 Fix the result error occurring when you use Modbus to access 16-bit recipe values.
1.26 Fix the reconnection error occurring when communication failure occurs for over 16
times between the HMIs and some network type PLCs.
產 品 通 報 Newsletter
3/53
1.27 Fix the issue that the HMI keeps showing the alarm window when booting if the HMI
cannot automatically obtain the IP address.
1.28 Fix the HMI crash occurring when HMI updates the RTC (real-time clock) through
PLC.
1.29 Fix the HMI crash occurring when the barcode reader connecting to the HMI is
interfered.
1.30 Change the controller name Omron CJ2M TCP to CJ/NJ Series FINS TCP.
2. New functions of the software / firmware:
2.1 Add the FTP Client function.
2.2 Add operation log for DOP-W series HMIs.
2.3 Add the sorting function to the Alarm Frequency Table for DOP-B series HMIs.
2.4 Add internal system parameter KEY_CHAR for DOP-B and DOP-H series HMIs to
capture the keyboard input characters.
2.5 Add the ascending/descending sorting function in alarm history list for DOP-W series
HMIs.
2.6 Screen display becomes faster when DOP-W series HMIs connect to PLCs.
2.7 Add network type PLC information when you obtain the firmware version in DOPSoft.
2.8 Add the supporting MC protocol for FX3U Ethernet controllers.
2.9 Add the function for re-obtaining the Ethernet address (DHCP) during screen
operation.
2.10 Add a new macro EXALARMGROUP that exports the alarms based on groups for
DOP-B series HMIs.
2.11 Add the USB host waiting time setting in the [System Menu] for DOP-B series HMIs.
2.12 More controllers (listed below) can now connect with the Delta HMI.
Delta 15MC
Delta 15MC TCP Delta 10EMC TCP Delta CNC Controller ASCII
Fatek FBseries TCP LS XBM/XBC/XGK CPU Direct Mitsubishi FX5U
Mitsubishi FX5U Ethernet Mitsubishi QnA Series CPU Port Moeller EasyPLC 800/MFD
Siemens S7 1500 (ISO TCP)
產 品 通 報 Newsletter
4/53
2.13 New models: B07SS411
3. Website to download the software:
http://www.deltaww.com/services/DownloadCenter2.aspx?secID=8&pid=2&tid=0&CID=06&ite
mID=060302&typeID=1&downloadID=DOP-B,&title=DOP-B&dataType=8;&check=1&hl=zh-TW
產 品 通 報 Newsletter
5/53
1. Software / Firmware revisions
1.1. Fix the DOP-B series HMI crash occurring when you enter the system menu and return to
general screens if IP conflict occurs.
Before
If the DOP-B series HMI detects a device using an identical IP address, the IP
conflict alarm occurs. Then, when you enter the system menu, the HMI crashes.
After When the HMI detects a device using the same IP address and the IP conflict
alarm pops up, you can still go to the system menu.
1.2. Fix the DOP-B series HMI crash occurring when it reads from or writes to devices with
allocation unit size over 4K.
Before When the DOP-B series HMI continues to read from or write to devices with
allocation unit size over 4096 bytes, the HMI crashes.
After
When the DOP-B series HMI detects a device with allocation unit size over 4096
bytes, it prompts an alarm message and a reminder for formatting the memory
device by HMI. See the example below.
產 品 通 報 Newsletter
6/53
Step 1: when plugging in the USB Disk which allocation size is over 4096 bytes, a
message showing “Allocation unit size is over 4k.” pops up. (If you are using the
previous DOPSoft version (not 2.00.06), the HMI displays “Error Cluster over 4K
size”.)
Step 2: press OK and the HMI prompts a window to ask whether to format the
storage device. Please press YES.
Step 3: press YES to start formatting the device. It takes some time, so please wait
and do not remove the storage device or switch off the HMI.
Step 4: if you press NO in Step 2 (not to format the device), then the storage
device is unavailable and the HMI prompts you that the device is not supported.
產 品 通 報 Newsletter
7/53
Step 5: after the initialization, a message “Please re-insert the device” displays.
Please press OK and re-plug in the device to start using the storage memory.
If you use Windows system to format the storage device instead of the HMI, select
the allocation size below 4096 bytes.
產 品 通 報 Newsletter
8/53
1.3. Fix the issue of exporting older history data in non-volatile memory in HMI.
Before
If you keep the history buffer in non-volatile memory in the DOP-B series HMI, the
exported history data might contain old data as well as new data as shown in the
figure below.
After In the DOP-B series HMI, the history data exported from non-volatile memory is
correct and sorted by date and time.
1.4. Fix the DOP-B series HMI crash occurring when you insert an external device and set to
save the non-volatile data in the external device.
Before
To import the recipe file automatically, you must set the non-volatile data (recipe)
location to an external storage device first before exporting to the device. When
the storage device is plug into the HMI, the recipe file is automatically imported.
Old data
產 品 通 報 Newsletter
9/53
If you used Excel to edit the recipe file, then the HMI crashes when it is imported to
the HMI.
After
In DOP-B series HMIs, if you set to save the non-volatile data (recipe) in an
external device before exporting the recipe to the device, you can use Excel to edit
the recipe. When you plug in the external device to the HMI, the edited recipe is
automatically imported to the HMI.
產 品 通 報 Newsletter
10/53
1.5. Fix the communication setting error occurring when cycling the power to DOP-B07S410
HMIs.
Before
When connecting a DOP-B07S410 HMI with a Delta device, you can use
auto-detection to complete the communication setting if communication is off.
However, when you cycle the power to the HMI, the communication setting is in
error.
After
When connecting a DOP-B07S410 HMI with a Delta device, you can use
auto-detection to complete the communication setting. When you cycle the power
to the HMI, the previous communication setting remains and you can use
auto-detection to complete the communication setting.
1.6. Fix the continuous error of auto-detection window when the communication setting
between DOP- B07S410 HMI and Delta ASDA-A2 is correct.
Before
If you use DOP-B07S410 HMIs with Delta ASDA-A2 servo drives, when power-on,
the detection window pops up even when communication setting is correct.
After
When connecting DOP-B07S410 HMIs and Delta ASDA-A2 servo drives with
RS-485, no detection window displays during power-on if the communication
setting is correct. If incorrect, the detection window displays when power-on and it
can detect the communication setting for A2 servo drives. If you use RS-232 for
communication between DOP-B07S410 and ASDA-A2 and the communication
setting is correct, the detection window displays when power-on.
產 品 通 報 Newsletter
11/53
1.7. Fix the communication error between DOP-W series HMIs and the controller using Modbus
TCP/IP when the communication is lost for 16 times or more.
Before
When the DOP-W series HMI and controller use Modbus TCP/IP for connection, if
the connection between the controller and HMI is lost for 16 times or more, then
the controller cannot connect to the HMI successfully anymore.
After
When the DOP-W series HMI and controller use Modbus TCP/IP for connection, if
the connection between the controller and HMI is lost, you can always connect
them again.
1.8. Fix the copying failure occurring when the DOP-W series HMI screen data file contains
alarm data.
Before
When there are more than two DOP-W series HMIs, if HMI A has the alarm data saved, go to [System Menu] > [System Setting] > [File Manager] > [Copy File] to copy the screens to an external storage device, then copy this screen data file to
HMIB, a message “Copy fail” shows on HMI B and HMI B is restored to the
default.
After When there are more than two DOP-W series HMIs, whether HMI A has the alarm
data or not, the screen data file can be successfully copied to HMI B.
1.9. Fix the execution error of the momentary button with user security level settings for DOP-W
series HMIs.
Before
If you use a momentary button with user security level settings in DOP-W series
HMI, after entering the password, the momentary button remains in ON state and
does not switch to OFF. See the example below:
Step 1: create a momentary button on the screen. Go to [Details] and set the [User
Security Level] to 6.
產 品 通 報 Newsletter
12/53
Step 2: for this momentary button, set $1 = 1 for the ON macro and $2 = 1 for the
Off macro. Then, set two numeric entry elements which memory addresses are $1
and $2 to see whether the ON macro and OFF macro for the momentary button
are executed.
Step 3: download the project to the DOP-W HMI, when the user security level is
not high enough, execute the momentary button and enter the password.
產 品 通 報 Newsletter
13/53
Step 4: after you enter the password, please press OK and then the momentary
button stays in ON state without the OFF macro being executed.
After
When you execute a momentary button with user security level settings in DOP-W
series HMI, after entering the password, the momentary button is ON and then
goes OFF, which means both ON macro and OFF macro are executed.
ON state OFF macro not executed
產 品 通 報 Newsletter
14/53
1.10. Fix the execution error of the control section occurring when the DOP-W series HMI
enables the communication optimization function.
Before
When you enable the communication optimization function for the project in
DOP-W series HMI and use PLC address for the control, the execution result in
the control section is in error (unable to switch screens).
產 品 通 報 Newsletter
15/53
After
When you enable the communication optimization function for the project in
DOP-W series HMI and use PLC address for the control, the execution result in
the control section is correct.
Control with PLC address
產 品 通 報 Newsletter
16/53
1.11. Fix the DOP-W series HMIs with no response for a short time when you trigger the bit for
saving as multiple files in history buffer.
Before
In the DOP-W series HMIs, after you trigger the “Save as Multiple Files” bit for the
history buffer and execute the elements for screen change or numeric entry, there
is no response from the HMI lasting 10 – 20 seconds.
After After you trigger the “Save as Multiple Files” bit for the history buffer, there is no
problem with executing elements for switching screens or inputting values.
Step 1 Step 2
產 品 通 報 Newsletter
17/53
1.12. Fix the DOP-W series HMIs with alarm clearance error when the number of alarms
exceeds the savable range in the history buffer.
Before
In DOP-W series HMIs, when the number of alarms exceeds the savable number,
you cannot clear the alarms by clearing the buffer. The alarms to be cleared are
still in the active alarm list. See the example below:
Step 1: set the maximum savable alarms (Max Records) to 5.
Step 2: trigger Alarm 1 – 5.
產 品 通 報 Newsletter
18/53
Step 3: trigger Alarm 6 and the total alarms are 6, which exceeds the maximum. In
the alarm history, you can see that Alarm 6 overwrites Alarm 1.
Step 4: clear the alarms in the buffer.
產 品 通 報 Newsletter
19/53
Step 5: clear Alarm 1. It cannot be cleared. The list still shows Alarm 1.
產 品 通 報 Newsletter
20/53
After
In DOP-W series HMIs, when the number of alarms exceeds the maximum
savable number, after you clear the history buffer, the list does not display the
alarms that are cleared.
1.13. Fix the screen download failure when DOPSoft is in Windows 10 environment.
Before You cannot download screens when DOPSoft is in Windows 10 environment.
After You can download screens when DOPSoft is in Windows 10 environment.
1.14. Fix the DOPSoft crash issue when exporting multi-language texts in Windows 10.
Before
When using DOPSoft in Windows 10, you export the multi-language texts by going
to [Edit] > [Export Multi-language Text], but DOPSoft crashes and shows the
Exception window.
After When using DOPSoft in Windows 10, you can export the multi-language texts by
going to [Edit] > [Export Multi-language Text] without error.
Alarm 1 is not cleared
產 品 通 報 Newsletter
21/53
1.15. Fix the calculation error (repeat calculation) when you compile projects in DOPSoft.
Before
If you compile the project in DOPSoft, the memory calculates repeatedly and so an
error message “Memory is not enough to open (page name)” displays when there
is still memory available.
After The compiling results are correct and DOPSoft correctly calculates the available
memory.
1.16. When HMI connects with eRemote, fix the HMI crash occurring if you go to the system
menu and return to general screens.
Before
In the HMI project, if you set the [System Error Display Time] to 0 by going to
[Configuration] > [Default] and enable the offline alarm window in [Configuration] >
[Network Application], the HMI crashes if you go to the system menu and return to
the HMI screen by using eRemote to connect the HMI.
產 品 通 報 Newsletter
22/53
After When you use eRemote to connect the HMI and then go to the system menu and
return to the HMI screen, you can continue to control the HMI with eRemote.
1.17. Fix the connection error between eRemote and the HMI when GridBox element is set
with an After Execute macro.
Before
If the GridBox element on the screen is set with the After Execute macro, the
eRemote cannot connect with the HMI and the message "Parsing…." stays on the
screen.
產 品 通 報 Newsletter
23/53
After eRemote can connect with the HMI and you can use the GridBox element without
error.
1.18. Fix the HMI with no response due to users' not removing the external device safely
before re-plugging in the device.
Before
When you set to save the history buffer in an external storage device and you
directly remove the external storage device without executing “Remove Storage”
button, the file written in the external device may be in error. If you remove the
power from the HMI, re-plug in the external device, and cycle the power, the HMI
stays at the reading screen.
After
If you directly remove the external storage device without executing the “Remove
Storage” button, the file written in the external device is in error. Meanwhile, if you
remove the power from the HMI, re-plug in the external device, and cycle the
power, the HMI shows the general screen, ignoring the previous error and reading
the content that is correctly written in the history buffer.
1.19. Fix the HMI crash occurring when it reads from or writes in NTFS-formatted storage
devices.
Before The HMI currently only supports storage devices in FAT32 format. If the HMI reads
from or writes in NTFS-formatted devices, it crashes.
產 品 通 報 Newsletter
24/53
After
If the HMI reads from or writes in NTFS-formatted storage devices, the HMI
prompts a message showing the device is not supported.
Go to [System menu] > [System Setting] > [File Manager] > [Format Removable
Disk] to format the device. Or, you can format the device and convert it to FAT32
format by Windows.
產 品 通 報 Newsletter
25/53
1.20. Fix the reading error occurring when the enhance recipe imported to the HMI is edited
with Excel.
Before If you use Excel to edit the recipe, after you import this recipe to the HMI, the HMI
shows the CSV file reading error message.
After You can use Excel to edit the recipe file and no error occurs when you import this
recipe to the HMI.
1.21. Fix the HMI crash occurring if you plug in the external device to auto import the recipe
when HMI screen shows the message that the USB Disk does not exist.
Before
To automatically import the recipe file, you must set to save the non-volatile data
(recipe) to an external device. Then, export the recipe so that the external device
has the recipe file saved. After the external device connects to the HMI, the recipe
is imported automatically.
However, if the HMI prompts you that the USB Disk does not exist and you plug in
the external device, the HMI crashes when importing the recipe.
產 品 通 報 Newsletter
26/53
After
If you set to save the non-volatile data (recipe) in the external device, when the
HMI prompts you that the USB Disk does not exist and you plug in the external
device, the HMI automatically imports the recipe file.
1.22. Fix the HMI crashing error occurring when the alarm message contains more than 56
characters.
Before
If the non-volatile data is set to be saved in the external device and the alarm
message contains over 56 characters, the HMI crashes when the alarm is
triggered.
產 品 通 報 Newsletter
27/53
After The HMI alarm message can contain up to 61 characters. The HMI displays the
message properly and you can also export the CSV file to an external device.
1.23. Fix the alarm number recording error that occurs when you set to save the non-volatile
data (alarm history) in the HMI.
Before
When you set to save the non-volatile memory for the alarm history in the HMI and
the number of alarm occurrences is over 255, the number showing on the alarm
frequency list is incorrect. If the alarm occurrence time is 255, the HMI displays
255; but if it is 256, it shows 0.
After The HMI can correctly display the number of alarm occurrences when you set to
save the non-volatile data for alarm history in the HMI.
56 characters
產 品 通 報 Newsletter
28/53
1.24. Fix the issue of being unable to open the file by computer while you use “Save as
Multiple Files” function in the history buffer.
Before
If you use the “Save as Multiple Files” function in the history buffer, after the buffer
accumulates some files, you cannot open these files by the computer and the
computer shows file access failure.
After If you use the “Save as Multiple Files” function in the history buffer, you can access
all files through the computer.
1.25. Fix the result error occurring when you use Modbus to access 16-bit recipe values.
Before
When two HMIs communicate through Modbus, HMI B reads the 16-bit recipe
values from or writes the 16-bit recipe values to HMI A by Modbus TCP/IP. If HMI
A’s recipe group number (RCPNO) changes to a non-first group recipe, the recipe
value read by HMI B is incorrect.
After
If two HMIs communicate through Modbus, the reading result is correct when HMI
B reads the 16-bit recipe values from or writes the 16-bit recipe values to HMI A by
Modbus TCP/IP.
1.26. Fix the reconnection error occurring when communication failure occurs for over 16 times
between the HMIs and some network type PLCs.
Before
When the HMI connects to the following network type PLCs and communication
failure occurs over 16 times, the HMI cannot connect to the PLC again unless you
reboot the HMI.
PLCs with connectivity issues to the HMI:
Manufacturer Series
Delta Delta RTU-EN01 (Ethernet)
Modbus TCP/IP (6 Digitals)
FUJI Electronic MICREX SX Series TCP
XINJE XINJE XC series PLC (Modbus TCP)
Yaskawa SIO UDP
產 品 通 報 Newsletter
29/53
After The HMIs and PLCs can always re-connect after communication failures occur.
1.27. Fix the issue that the HMI keeps showing the alarm window when booting if the HMI
cannot automatically obtain the IP address.
Before
If you set the HMI to automatically obtain the IP address when booting, but the HMI
fails to get the IP address due to problems such as loose connection cable or
DHCP Server error, the screen shows “DHCP can’t be started!!”. Then, you have
to press OK to enter the screen.
After
When the HMI cannot automatically obtain the IP address and shows the alarm
message, you can go to the HMI screen without pressing OK.
After the HMI boots, if you need to obtain the IP address, use bit 10 in the control
block to get the IP address. For more information, please refer to 3.9 Function for
re-obtaining the Ethernet address during screen operation (DHCP) in this
document.
產 品 通 報 Newsletter
30/53
產 品 通 報 Newsletter
31/53
1.28. Fix the HMI crash occurring when HMI updates the RTC (real-time clock) through PLC.
Before
When the HMI enables the RTC (real-time clock) and you update the RTC through
PLC, the HMI crashes after some communication time.
After The HMI can update the RTC through PLC. You can update the HMI time to the
PLC or update PLC time to the HMI.
1.29. Fix the HMI crash occurring when the barcode reader connecting to the HMI is interfered.
Before If the barcode reader connecting to the HMI is being interfered for a while, the HMI
crashes.
產 品 通 報 Newsletter
32/53
After If the barcode reader connecting to the HMI is being interfered, the HMI does not
crash and you can continue to use the barcode reader.
1.30. Change the controller name Omron CJ2M TCP to CJ/NJ Series FINS TCP.
Before
In the HMI project, you can set the controller Omron CJ2M TCP to connect Omron
CJ and Omron NJ series network type PLC, but these names are confusing.
After Now the controller name is changed to Omron CJ/NJ series FINS TCP which can
產 品 通 報 Newsletter
33/53
connect Omron CJ and Omron NJ series network type PLC. In DOPSoft 2.00.06,
when you open the project file created by DOPSoft 2.00.05 or earlier versions, the
controller changes to Omron CJ/NJ Series FINS TCP.
2. Software / Firmware new functions
2.1. Add the FTP Client function.
For details about the FTP setting, please refer to the technical announcement for FTP Client.
2.2. Add operation log for DOP-W series HMIs.
For more information, please refer to the technical announcement for the operation log.
2.3. Add the sorting function to the Alarm Frequency Table for DOP-B series HMIs.
The Alarm Frequency Table of DOP-B series HMIs sorts based on “alarm number”, and now it
can also sort by “number of alarm occurrences” and you can use the variable to trigger this
new sorting function.
產 品 通 報 Newsletter
34/53
You can enable the sorting function in the property list as well as by triggering the variable
using the memory address. When you set the value to 1, the sorting function is enabled and
the list sorts by number of alarm occurrences. When you set to 0, the sorting function is
disabled and the list sorts by alarm number.
Variable
Type
Internal
memory
PLC
register Constant
Sorting trigger bit ◎ ◎
產 品 通 報 Newsletter
35/53
See the example below. The figure on the left shows the list with the sorting function
enabled. The list sorts the number of alarm occurrences in descending order. The figure on
the right shows the list sorting the alarm number in ascending order.
2.4. Add internal system parameter KEY_CHAR for DOP-B and DOP-H series HMIs to capture
the keyboard input characters.
The HMIs provide internal system parameter KEY_CHAR to capture the characters input by
external keyboard and enables you to see whether the conditions are met for the macro.
Number of the alarm occurrences
sorting in descending order
Alarm number sorting in
ascending order
產 品 通 報 Newsletter
36/53
Please refer to the example below:
Step 1: create a character entry element in the project and set the write address to
KEY_CHAR.
Step 2: download the project to the HMI and connect the keyboard using the USB connector.
產 品 通 報 Newsletter
37/53
Step 3: enter the text to display on the character entry element in the project by keyboard.
Enter character “A”, the character entry element displays “A”.
2.5. Add the ascending/descending sorting function in alarm history list for DOP-W series HMIs.
The Alarm History Table in the DOP-W series HMI can sort the display order using the control
address based on options such as triggering time and alarm counts. Before the revision, the
table can only sort in ascending order. Now the control address for ascending and descending
sorting is added to the HMI. Setting 0 means ascending sorting while setting 1 means
descending sorting. If you do not set this sorting control address, the Alarm History Table sorts
in ascending order (default).
See the following example.
Step 1: please set the sorting order control address. $3006 is used in the example below.
產 品 通 報 Newsletter
38/53
Step 2: create a numeric entry element and set the write memory address to the
ascending/descending sorting control address. Take $3006 as a setting example.
產 品 通 報 Newsletter
39/53
Step 3: download and execute the project after the alarm occurs. Select “Sorting by Alarm
Number” and set $3006 to 1 to sort in descending order.
產 品 通 報 Newsletter
40/53
Step 4: set $3006 to 0, the list sorts in ascending order.
Alarm number sorts in
descending order
產 品 通 報 Newsletter
41/53
2.6. Screen display becomes faster when DOP-W series HMIs connect to PLCs.
Before the revision, when DOP-W series HMIs connect to PLCs, the communication element
updates only after a communication cycle finishes. Now, the elements update their statuses
right after you trigger the button or update values. The HMI display becomes smoother with very
little display lag.
2.7. Add network type PLC information when you obtain the firmware version in DOPSoft.
Before the revision, when you obtain the firmware version by going to [Tools] > [Get Firmware
Information], DOPSoft only shows information about PLCs that connect through COM ports.
Now, DOPSoft shows the information about PLCs connecting through COM ports and Ethernet.
As shown in the figure below, Driver 4 shows the settings for all network type PLCs. This
example uses two network-type PLCs, one is Modbus TCP/IP which is displayed as
MODTCPIP and its version is VER1.7; the other is Delta DVP TCP/IP which is displayed as
Alarm number sorts in
ascending order
產 品 通 報 Newsletter
42/53
DELDVPTCP and the version is 2.4. Contents in the square brackets represent the connection
number using this controller. In the example below, 0 means connection No. 0 uses Modbus
TCP/IP, and connection No. 1 and No.2 use Delta DVP TCP/IP.
2.8. Add the supporting MC protocol for FX3U Ethernet controllers.
The PLC Mitsubishi FX3U Ethernet uses MELSOFT protocol for communication. When using
the MELSOFT protocol, the port has to be 5556 so that the HMI can connect with Mitsubishi
FX3U network type PLC.
Now, MC protocol is provided for communication between HMIs and Mitsubishi FX3U network
type PLCs. The MC protocol can work with the PLC software based on the user-defined
communication port.
產 品 通 報 Newsletter
43/53
2.9. Add the function for re-obtaining the Ethernet address (DHCP) during screen operation.
In the past, if the HMI is set to automatically obtain the IP address, the HMI can only obtain the
IP address when booting. Now, you can set a control bit so that the HMI can automatically get
the IP address during screen operation. See the example below.
Step1: go to [Options] > [Configuration] > [Control Block] and check [Recipe Control].
產 品 通 報 Newsletter
44/53
Step 2: create a button to trigger the bit for “Enable DHCP again” on the screen. For this
example, please create a button with the write address as $7.10.
Step 3: create the elements for displaying the IP address, SUBMASK address, and Gateway
address on the screen.
產 品 通 報 Newsletter
45/53
Step 4: download the screen to the HMI. Do not connect the DHCP server when the HMI boots.
The HMI displays an alarm message “DHCP can’t be started!” while booting, meaning it cannot
obtain the IP address. Meanwhile, the IP address, SUBMASK address, and Gateway address
are all 0.
產 品 通 報 Newsletter
46/53
Step 5: connect the HMI with DHCP server and then press the button for “Enable DHCP again”
so the HMI can obtain the IP address immediately.
2.10. Add a new macro EXALARMGROUP that exports the alarms based on groups for
DOP-B series HMIs.
You can export all alarm data by using the macro EXALARM, and now you can specify the
alarm groups and export them by macro EXALARMGROUP.
Expression Definition of the variable Note
Var1 = EXALARMGROUP(Var2,
Var3,Var4)
Var 1
Return value
Failed 0
Successful 1
Var 2 Alarm group number
Var 3 Exported file name
Var 4
External
storage
device
USB Disk 2
SD Card 3
Command description
Export the alarm data to the external device
產 品 通 報 Newsletter
47/53
Variable Type
Internal memory PLC register String Constant
Var 1 ◎ ◎
Var 2 ◎ ◎ ◎
Var 3 ◎ ◎
Var 4 ◎ ◎ ◎
Example
Step 1: complete the alarm setting as follows. Set the reading address to $1000, select the
“output to CSV file”. Set Alarm 1 - Alarm 3 to Group 1, Alarm 4 – Alarm 6 to Group 2, and Alarm 7
– Alarm 9 to Group 3.
based on the specified groups
Note:
1. You must select “output to CSV file” in the alarm setting.
2. Automatically adds the filename extension “-group number” and “.csv” after exporting.
Filenames cannot contain the following characters: \, /, :, *, ?, ”, <, >, and |.
x00 means the end of the filename string.
產 品 通 報 Newsletter
48/53
Step 2: create a maintained type element for the alarm triggering bit on the screen to trigger the
alarm. Set the write address respectively to $1000.0, $1000.1, $1000.2…$1000.9.
Step 3: create an alarm history element on the screen for displaying the current alarm history. Set
the group number to a variable which reading address is $302.
產 品 通 報 Newsletter
49/53
Step 4: create a value display element which address is $304 and string length is 20. Create two
numeric entry elements which addresses are $302 and $301. Create a drop down menu which
address is $303 and the total state number is 2. In State 0, the State Index is 3 and the text is SD.
For State 1, the State Index is 2 and the text is USB.
Step 5: create a maintained type button which address is $300.0 with the addition of an On
macro.
產 品 通 報 Newsletter
50/53
The macro instruction is as follows:
Line 1: set to record the system time at $200 - $206 (Year, Month, Day, Day of the Week,
Hour, Minute, Second)
Line 2: set the file name as “Alarm” with the addition of
“_year_month_day_hour_minute_second” and “_Group” and specify the start
address as $304.
Line 3: export the history buffer to the specified external device based on the specified
group number and filename.
Step 6: download the edited screens to the HMI and plug in the USB Disk to the HMI.
Step 7: trigger Alarm 1 – Alarm 10. Input “1” to the Group No. and select “USB” for the external
storage device on the screen.
Step 8: press the “EXALARMGROUP” button. After the execution, the filename displays and the
return value changes to 1.
產 品 通 報 Newsletter
51/53
Step 9: this step is the same as Step 8. Carry on to set Group No. 2 and No. 3 and then press the
“EXALARMGROUP” button respectively.
Step 10: after removing the USB Disk, the exported files in the USB Disk are shown as below:
2.11. Add the USB host waiting time setting in the [System Menu] for DOP-B series HMIs.
Sometimes the HMI cannot detect the USB device when booting and the screen auto-update
does not work properly. It is because the reading speed differs with the USB device
manufacturers. To solve this problem, Delta has added a new function for you to set the waiting
time for USB Disk detection when booting. You can set it by going to [System Menu] > [System
Setting] > [MISC.] > [USBH Insert WaitTime]. In this case, the HMI can execute the auto update
function when booting even if the reading time for the USB Disk is longer. The parameter setting
range is 400 ms – 2500 ms.
產 品 通 報 Newsletter
52/53
This parameter setting restores to the default only when you go to [Tools] > [Reset HMI].
Otherwise, the setting remains during HMI screen update and firmware update. For the four
models, DOP-B03S211, DOP-B03S210, DOP-B03E211, and DOP-B05S111, the default value
is 1000 ms. For other models, the default is 400 ms.
產 品 通 報 Newsletter
53/53
2.12. More controllers (listed below) can now connect with the Delta HMI.
Manufacturer Connection
method Series
Delta
COM Delta 15MC
Ethernet Delta 15MC TCP
Ethernet Delta 10EMC TCP
COM Delta CNC Controller ASCII
Fatek Ethernet Fatek FBseries TCP
LS COM XBM/XBC/XGK CPU Direct
Mitsubishi
COM FX5U
Ethernet FX5U Ethernet
Ethernet QnA Series CPU Port
Moeller COM EasyPLC 800/MFD
Siemens Ethernet S7 1500 (ISO TCP)
2.13. Add model B07SS411.