Technical Notes PDF

Technical Notes
MELSOFT
GX IEC Developer
GX IEC Developer 09.01.07
Technical Notes
Page 2
Technical Notes
Page 3
Content:
Topic: Page:
Technical Notes 1
Ver. 7.01 5
Wrong code / Using FB (EN and TRUE) ................................................................................................................................ 5
Out of memory during compiling ............................................................................................................................................ 5
Strange system error during compilation................................................................................................................................ 5
Compile error in ST using DUTs ............................................................................................................................................ 6
No error if special S-relays are used ...................................................................................................................................... 6
Inserting of comment field...................................................................................................................................................... 7
GID hangs after check ( OUT OF MEMORY )........................................................................................................................ 7
Online change does not work................................................................................................................................................. 8
Initial start of SFC POUs for FX series ................................................................................................................................... 8
Version conflict of user library ................................................................................................................................................ 8
Error <ES:10000019> during download ................................................................................................................................. 8
GVL instance of a DUT looses fixed addresses ..................................................................................................................... 9
Dynamically indexed addressing for an array......................................................................................................................... 9
Program crash after remote start/stop.................................................................................................................................... 9
Array of DUT, bit designation............................................................................................................................................... 10
Unable to format unformatted drive 0................................................................................................................................... 10
Array of DUT........................................................................................................................................................................ 10
Dynamic access to BOOL array with bit designation ............................................................................................................ 10
No error message after compile........................................................................................................................................... 11
Wrong compiler result with MOV instruction......................................................................................................................... 11
The compile results of CLC_M and STC_M are wrong......................................................................................................... 11
Online change and GE instruction........................................................................................................................................ 12
wrong code if negation of output EQ_M is used ................................................................................................................... 12
FX3U and 64K memory ....................................................................................................................................................... 13
GPF during update User Library .......................................................................................................................................... 13
FX modem communication using internal dialer ................................................................................................................... 13
Program crash during import of Remote I/O project ............................................................................................................. 14
Others 15
Download to PLC via MAC not possible............................................................................................................................... 15
Upload problem in transparent mode 9600 baud.................................................................................................................. 15
Start up problem with McAfee Internet Security.................................................................................................................... 15
Use of SUB_MD stops PLC................................................................................................................................................. 15
Export of closed Library with no read access ....................................................................................................................... 16
FX-plc and remote Run/Stop................................................................................................................................................ 16
Special function block setting for FX3U................................................................................................................................ 16
Wrong monitoring of String variable ..................................................................................................................................... 17
Copy/paste of variables in ST .............................................................................................................................................. 17
Program crash during import of Remote I/O project ............................................................................................................. 17
FX-Configurator-EN Opening Settings not necessary .......................................................................................................... 17
Wrong monitoring of String variable ..................................................................................................................................... 18
Memory problem with big projects on Win98........................................................................................................................ 18
Case sensitivity for identifier using "".............................................................................................................................. 18
Problem during import from Excel ........................................................................................................................................ 18
Restore of project from diskettes.......................................................................................................................................... 19
Copy/paste of variables in ST .............................................................................................................................................. 19
Boot option for Q00(J)/01 does not work correctly................................................................................................................ 19
Download to Standard ROM is not possible. ........................................................................................................................ 19
Automatic address filling for DUTs ....................................................................................................................................... 20
Library time stamp ............................................................................................................................................................... 20
Communication problems using Docking station.................................................................................................................. 20
CPU error after using SFC on a Qn PLC.............................................................................................................................. 20
Export from Device editor/EDM to Excel .............................................................................................................................. 21
System Error 6608 at FX PLC.............................................................................................................................................. 21
Temporary Variable for data type STRING too short ............................................................................................................ 21
Wrong message "Update Libraries" ..................................................................................................................................... 21
Symbolic constants for CASE in ST..................................................................................................................................... 22
Monitoring in ST................................................................................................................................................................... 22
Monitoring/tooltip problem in ST editor in Win98 .................................................................................................................. 22
Menu item "Delete Externals"............................................................................................................................................... 22
Wrong compiler error message............................................................................................................................................ 23
Problem with counter C251 FX2N........................................................................................................................................ 23
SFC transitions in Actions with TRAN.................................................................................................................................. 23
"PLC Clear-->All" works not correctly................................................................................................................................... 23
Inaccurate floating point calculation ..................................................................................................................................... 24
Use of RET_M..................................................................................................................................................................... 24
Technical Notes
Page 4
Transfer speed for A2AS-S60 is no longer supported .......................................................................................................... 24
Recommended poll rate settings.......................................................................................................................................... 25
No monitored value in dynamic arrays ................................................................................................................................. 25
PLC-Diagnostics.................................................................................................................................................................. 25
Reset of high speed counter in a event driven task .............................................................................................................. 25
Iparam file is not exported.................................................................................................................................................... 26
Sorting in declaration editors................................................................................................................................................ 26
No size check of strings connected together ........................................................................................................................ 26
Availability of MXChange ..................................................................................................................................................... 26
Code generation compared to GID 5.02............................................................................................................................... 27
MBOC availability not recognized ........................................................................................................................................ 27
FX2N interrupt problem after online change......................................................................................................................... 27
Using parameters of a macro function block ........................................................................................................................ 27
SFC editor and project navigator.......................................................................................................................................... 28
PLC keyword on QCPU ....................................................................................................................................................... 28
Monitoring MELSEC IL code................................................................................................................................................ 28
Modem connection to QnA................................................................................................................................................... 28
SFC control by special relays............................................................................................................................................... 29
Limitation example............................................................................................................................................................... 29
Verify error........................................................................................................................................................................... 30
Start-up parameter for MM+................................................................................................................................................. 30
Device Edit: C200 - C255..................................................................................................................................................... 31
Generated code for SFC start of A-series ............................................................................................................................ 31
Browser and EDM shows different variables ........................................................................................................................ 31
L devices ............................................................................................................................................................................. 31
Multiple operands in logical modules (i.e. AND) ................................................................................................................... 31
Inserting a variable twice in the EDM................................................................................................................................... 32
Pause state set by key......................................................................................................................................................... 32
Improvement: ASCII instruction............................................................................................................................................ 32
Outputs of function blocks should not be written .................................................................................................................. 32
Timer coils ........................................................................................................................................................................... 33
Curious SFC........................................................................................................................................................................ 33
Technical Notes
Page 5
Ver. 7.01
Wrong code / Using FB (EN and TRUE)
Report No.: 12248 Last revision Date: 04.12.2006
Software: GX IEC Developer
Found in Version: Ver 7.00
Description: When TRUE is used for the EN parameter of a user FB in a LD network and a TIMER_100_FB is used as
input for one of the other input parameters of the user FB, the EN of the FB does wrongly depend on the
TIMER_100_FB. Why?
Answer: It is a software problem.
Work Around: Call the TIMER_100_FB in a network before the user FB is called. Use the output of the TIMER_100_FB
in
the notation Timer100FBInst.OutputParameter as input of the user FB.
Solved in Version: Ver 7.01
Out of memory during compiling
Description: I have a POU in which I used the same name for a FB instance and another variable. I use both variables
in the body of the POU. I wanted to resolve this conflict by changing the name of the second variable,
but after the renaming the new name is used also for the FB instance in the POU body.
Answer: This is a software limitation. It happens when the Auto Update option is turned on. The Auto Update
functionality replaces all occurrences of the old name with the new name of a variable in the whole
body. In case of a naming conflict it cannot decide which occurrence to change and which to skip.
Work Around: a) Modify the body manually after changing the variable name with Auto Update turned on.
b) Turn off Auto Update and modify the body manually.
Strange system error during compilation
Description: I have declared an ARRAY [0..53] OF STRING [1] as member of a DUT. When I use an element of this
array as input for the standard function LEFT_E a message box comes up with the text "System Error
MI_SC unrecognized Typ in GetArrInfo". Why?
Work Around: Assign the element to a local variable of STRING [1] and use the local variable as input of the LEFT_E.
Technical Notes
Page 6
Compile error in ST using DUTs
Description: A FB uses an array of DUT as output. When I want to access a member of an array element with
MyFBInst.VarOutAoD [i].IntMember
in ST. Why do I get always the error F0137 during check or compile?
Answer: This is a software problem.
Work Around: Assign the array element to a local DUT variable e.g. with
LocalDUT := MyFBInst.VarOutAoD [i];
And use the member LocalDUT.IntMember in your expressions instead.
No error if special S-relays are used
Description: When a step flag is used as coil in an action of a SFC POU the POU is not executed anymore when the
step flags is set. Why?
Work Around: Don't write to step flags in actions or transitions.
Don't use step flags as direct actions in an action association list.
Technical Notes
Page 7
Inserting of comment field
Description: A GID project contains a declaration for a DUT called "VPData" that contains the following BOOL items.
- Available
- Opened
- Closed
- RequestOpen
- RequestClose
- Open
- Close
- Failed
- FailedToOpen
- FailedToClose
- StateError

The XLS file (in GVL import/export format) contains a single GVL entry, that is a VAR_GLOBAL of the
type VPData
It contains the following data for the MIT addr:
Available D2426.0
Opened D2426.1
Closed D2426.2
RequestOpen D2426.3
RequestClose D2426.4
Open D2426.5
Close D2426.6
Failed D2426.7
FailedToOpen D2426.8
FailedToClose D2426.9
StateError D2426.A

However, when the XLS file is imported into the GVL, the MIT addresses for "Open" and "Closed" in the
GVL window of GID are changed as shown below:
Available D2426.0
Opened D2426.1
Closed D2426.2
RequestOpen D2426.3
RequestClose D2426.4
Open D2426.3 <---
Close D2426.4 <---
Failed D2426.7
FailedToOpen D2426.8
FailedToClose D2426.9
StateError D2426.A

Why have the addresses for 'Open' and 'Close' not been imported correctly?
Work Around: None.
GID hangs after check ( OUT OF MEMORY )
Description: Why do I get sometimes a window with "OUT OF MEMORY" when I check a POU? Afterwards GX IEC
Developer doesn't react anymore.
Work Around: Not available.
Technical Notes
Page 8
Online change does not work
Description: Why do I get sometimes the error message "Error during STREAM copy" during Online Change, Build or
Rebuild All?
Work Around: Export the project to an ASCII file, create a new project of the same CPU type and import the ASCII file
again.
Initial start of SFC POUs for FX series
Description: Why does the code generator produce code for each SFC POU of a FX CPU to set the initial step in the
first scan even when the step flags are latched?
Work Around: Create a POU which saves the value of M8002 to a global variable and reset M8002 always. Assign this
POU to a task called MELSEC_FIRST. Create an additional POU which restores the value of M8002 from
the global variable and put this POU as first one in a task which is executed as first task after
MELSEC_FIRST.
Version conflict of user library
Description: Why do I get a version conflict when importing and replacing a library which has the status 'open'?
Answer: An open library can be set to status 'changed' during import due to several cases. For example, if the
import contains parameter or if the import contains tasks which are assigned to the library.
If a library with status changed which will be replaced, it is saved automatically. If it is assigned to the
same SUL file as the library which is currently imported and if the sul file is newer than the date of
opening the library in the project, you will get the warning that the 'old' library content might overwrite the
newer SUL-file content.
Work Around: Close libraries before replacing them.
Error <ES:10000019> during download
Description: Why do I get the error <ES:10000019> when I download a program to a QnPRH?
Work Around: Set the "Generate code as in GX IEC Developer 6.10" flag.
Or
Rename the interrupt task which uses the index registers Z0, Z1 or an array with a dynamic index to be
lexically the first task. If you have several interrupt tasks of that kind this workaround could not be used.

Or
Avoid the usage of the index registers Z0, Z1 or an array with a dynamic index in an interrupt program.
Technical Notes
Page 9
Wrong code generated for Ld-network
Description: Why is the generated code for a multi assignment in LD not correct when I use two or more S or R coils
followed by a dynamic BOOL array and have an expression as source for the multi assignment?
Work Around: Use the dynamic array as first assignment.
GVL instance of a DUT looses fixed addresses
Description: I have a DUT instance with more than 250 entries. All DUT member have been addressed automatically.
After copying the instance to another GVL (e.g. User library) the addresses of the last DUT members
are empty. Why?
Work Around: None.
Dynamically indexed addressing for an array
Description: Why is it not possible to use a member of a DUT variable or an element of an array as index for an array
in IL, LD or FBD?
Work Around: Assign the DUT variable or the element of an array to a local variable and use this variable as index.
Program crash after remote start/stop
Description: If I use several extension boards and have them defined in the I/O settings of the PLC parameters, why
does GX IEC Developer ends immediately after doing Start/Stop remotely?
Work Around: Please change the I/O setting (Base setting) in the PLC parameters so that the maximum number of used
slots is less or equal 24 if possible.
Technical Notes
Page 10
Array of DUT, bit designation
Description: Why is the address of a WORD member of an Array of DUT not the next word after an ARRAY [0..15]
OF BOOL member when 'Use bit designation' is selected?
Work Around: Use a bit address as start address for the BOOL members.
Or sort the DUT members so that all BOOL members are located at the end of the DUT
Unable to format unformatted drive 0
Description: If the drive 0 (Program Memory) of a Q PLC becomes unformatted for some reason (e.g. the PLC or its
battery has a hardware error), its not possible to open the Format Drive dialog. Its also not possible to
download the project to the PLC, even if a drive other than drive 0 is selected in the Project Transfer
Setup. An error message is displayed when attempting to use these functionalities.
Work Around: None when using GX IEC Developer 7.00 or earlier. The drive can be formatted using GX Developer.
Array of DUT
Description: Why is the generated code for an array of DUT variable not correct when I use a bit designated address
as start address for the BOOL members?
Work Around: Use a bit address as start address for the BOOL members.
Or enable the usage of bit designation by checking the check box in the array of DUT address dialog.
Dynamic access to BOOL array with bit designation
Description: I have declared a global variable as ARRAY [0..15] OF BOOL with start address D0.0. Why is the error
C9033 raised during compiling when I use a variable as index to access the elements?
Answer: It is not specified to use a dynamic index for a BOOL array with a start address which uses bit
designation.
Work Around: Use the functions TEST_MD, BSET_M, BRST_M instead to test, set, reset a bit in a word for Q and QnA
CPUs.
For FX3U only the function BON_M could be used to check a bit in a word.
Technical Notes
Page 11
No error message after compile
Description: A DINT variable/ address is accepted as index of an array. But only the lower word is used to calculate
the value for the index register. For e.g. an ARRAY [400000 .. 400005] the index is calculated wrong.
Why?
Work Around: Use only 32.767 elements in an array. Don't start a dimension smaller then -32.768 or greater then
32.767.
Wrong compiler result with MOV instruction
Description: In a LD an assignment of 0 to D0 and %MD0.10 was programmed by connecting first the D0 to 0 and
then %MD0.10 to the same 0. Why does the generated code copy D0 and D1 to D10?
Work Around: Exchange the addresses and use %MD0.10 first.
The compile results of CLC_M and STC_M are wrong
Description: Why does the function CLC_M don't reset SM700 for a Q or QnA CPU?
Why does the function STC_M don't set SM700 for a Q or QnA CPU?
Work Around: Use RST_M or SET_M with SM700 instead.
Technical Notes
Page 12
Online change and GE instruction
Description: I have modified an action in an SFC POU of my A-series project. When I try to perform Online Program
Change, an error message is displayed and the PLC gets into error state. Why?
Work Around: 1. The error can be avoided by adding a special dummy (i.e. useless) modification after the real
modifications.
Examples:
- In case of a FBD/LD action:
Create two Boolean variables: DummyBool1 and DummyBool2.
Add a new network to the end of the action, place an input variable element for DummyBool1 and an
output variable element for DummyBool2 in it and connect them.
When you modify something in the action, also modify the dummy network by exchanging DummyBool1
with DummyBool2.
- In case of an IL action:
Add a new network to the end of the action, add the following code to it:
LD DummyBool1
ST DummyBool2
with DummyBool2.
- In case of a MELSEC IL action:
Add a new network to the end of the action, add the following code to it:
LD DummyBool1
OUT DummyBool2
with DummyBool2.
- In case of a ST action:
Add a the following code to the end of the action:
DummyBool2 := DummyBool1;
When you modify something in the action, also modify the dummy code by exchanging DummyBool1 with
DummyBool2.
2. The error can be avoided if the modification makes the action shorter or longer. For example you can
add dummy code to the beginning of the action when you modify it, and remove it at the next modification
of the action (and so on). However, please be very careful, because if your original modifications make
the code smaller exactly by the size of the added dummy code, then the resulting code is still of the
same size and the problem can happen.
3. Dont use online program change to apply SFC action modifications on A-series. Use normal
download, whenever its possible to stop the PLC before the modifying its program.
wrong code if negation of output EQ_M is used
Description: Why does the code generator show an error in the SIC when the negated output of an EQ_E is
connected to two coils in LD?
Work Around: Use the NOT function instead of the negation of the output of EQ_E
Technical Notes
Page 13
FX3U and 64K memory
Description: I have set the memory capacity to 64000 steps in the PLC Parameter dialog of my FX3U project. I have
compiled the project and downloaded it to the PLC. When I switch the PLC to RUN mode, it gets into error
state. The System Error dialog identifies the error as 'Program sum check error'. Why?
Answer: This is a software problem. It happens if the memory capacity is set to 64000 steps, and the size of the
downloaded program is at least 32768 steps smaller than the available program capacity.
Work Around: Please dont use 64000 steps memory capacity setting if the 32000 steps setting would be enough for
your program. Please do the following to avoid the error:
- Open the PLC Parameter dialog and check the 'Program capacity' value in the middle of the 'Memory
capacity' page.
Important: 'Program capacity' is not the same as 'Memory capacity'.
- Check the total size of your program. It is displayed in the 'Compile/Check messages' dialog when you
build your project, or you can get it if you open the Options, go to the 'System Variables' page and press
the 'Display program size' button.
- Subtract the total size of the program from the program capacity. If this value is at least 32768, then the
memory capacity must be lowered to 32000 steps or less.
GPF during update User Library
Found in Version: Ver 7.00 (30.09.2005)
Description: Why does GID 7.00 sometimes crash when I update a user library which was created with GID 6.10?
Work Around: Adjust the user library by executing the following steps:
- Create a new project with GID 6.10
- Install the user library and open it
- Remove all VAR_EXTERNAL from all POU headers of the library
- Save the library
- Use the adjusted library in GID 7.00 and up
FX modem communication using internal dialer
Description: Why isn't it possible to communicate with the FX PLC using the internal dialer to start modem
communication?
Answer: This is a limitation of the software.
Work Around: Use the standard terminal program from Windows (e.g. Hyperterminal)
Technical Notes
Page 14
Program crash during import of Remote I/O project
Description: When I try import an export file of a complete Remote I/O project via the menu command 'Project-->Other-
->Import', the program crashes. Why?
Work Around: There are two ways to prevent the program crash:

1. Import the ASCII file via the context menu of the navigator window.
2. Import the ASCII file via the menu command 'Object-->Import'
Technical Notes
Page 15
Others
Download to PLC via MAC not possible
Description: Why isn't it possible to download a Q PLC program including SFC via MAC terminal in MAC transparent
mode if I use a baud rate of 9600 bit/sec. The used operating system is Windows 98.
Answer: It is a timing problem in the MAC terminal.
Work Around: Open E-Designer and open the "System Signals" dialog. Enter the line "T5000" to the edit field
"Commands".
Download the E-Designer project to the MAC terminal once again. After this additional timeout setting of 5
seconds the download works correct.
Upload problem in transparent mode 9600 baud
Description: Why isn't it possible to upload big files with GID using the MAC transparent mode with 9600 baud?
Answer: This is a timing problem within E-Designer.
Work Around: Enter the dialog 'System Signals' from the E-Designer menu and enter the value 'T5000' in the field
'Commands'.
With this setting it should work without problems
Start up problem with McAfee Internet Security
Description: GX IEC Developer will not start up if McAfee Internet Security Suite 8.0 is installed. Why?
Work Around: De-Install the 'Privacy Service' of McAfee Internet Security Suite.
Use of SUB_MD stops PLC
Description: Why is the data type of some SUB_MD and similar one not REAL for a Q CPU?
Answer: All functions with the ending "_MD" are "Mitsubishi Dedicated" functions introduced in the beginning for
the A series. They are available for Q and QnA CPUs as part of the MLIB for compatibility reasons only.
They should support customers to easy convert a program written for an A series CPU to a Q or QnA
CPU type.
Work Around: While the A series does not support the data type REAL variables of data type DINT or DWORD has to be
used. So when you need to use the functions SUB_MD etc. you have to initialize the used variables
correct.
Technical Notes
Page 16
Export of closed Library with no read access
Description: Why can I not export the bodies of a closed library without read access?
Answer: To protect the hidden content, the export function exports only the accessible items. In case of closed,
read protected libraries, the POU bodies are therefore not exported.
Work Around: Open the Library before exporting.
FX-plc and remote Run/Stop
Description: I started to download a new program to my FX-series PLC, which was in RUN mode. When asked, I
chose to stop the PLC. During download the communication line got broken, and the download failed. At
the next attempt I successfully downloaded the program, and tried to switch the PLC to RUN mode via
the menu command Online->Start/Stop PLC, but it did not work. The PLC stayed in STOP mode. Why?
Answer: FX-series PLCs have either a built-in RUN/STOP switch or a RUN-terminal (through which the PLC can
be switched to RUN by applying power to it). The described error can happen if the PLCs RUN/STOP
state is operated remotely, but the PLCs built-in RUN/STOP switch is in RUN position or there is power
applied to the PLCs RUN-terminal.

For remote RUN/STOP setting to work correctly with FX-series PLCs:
- the PLCs built-in RUN switch (if it has one) must be in STOP position
- there should be no connection to the PLCs RUN-terminal (if it has one)

Please refer to the document "FX Series Programmable Controllers - Programming Manual,
JY992D48301", section 10.3.2 for details.
Special function block setting for FX3U
Description: I want to set the special unit initialization parameter in an FX3U project. In the "I/O assignment" page of
the parameter it is not allowed to edit the "Unit Name" field of any unit, and it is not allowed to press the
"Read PLC Data" button. When I open the detailed setting page of a unit, it is not allowed to edit the "Unit
Name" field nor the "Comment" field of any address. Why?
Answer: This is a software limitation. The unit names and address comments are stored in the device comment
area of the PLCs memory, but GX IEC Developer does not support reading or writing the device comment
area. The fields and buttons related to device comments are disabled in GX IEC Developer.
Technical Notes
Page 17
Wrong monitoring of String variable
Description: If I change the value of a STRING type variable during monitoring to a string that contains an ANSI
character that doesnt have an OEM equivalent such as the Euro () symbol, its replaced by an
underscore (_) character.
Answer: String variables are represented in different character sets in Windows applications and on the PLC. GX
IEC Developer uses the ANSI character set, while the PLC program uses the OEM character set. Its
necessary to convert the strings between the two character sets when writing and reading strings
to/from the PLC. However, some ANSI characters like the Euro () symbol have no OEM equivalent;
therefore they cant be displayed properly with the OEM character set.
Work Around: None.
Copy/paste of variables in ST
Description: If I paste the text "if x1 and x2 then" in a ST body of my project, the text is converted to "IF x1 AND X2
THEN". Why is x1 not converted to upper case?
Answer: x1 is declared as local or global variable. Variables are not converted to upper case during paste in ST.
Work Around: Choose a color for ST Variables which is different from the text color. Then you can distinguish
variables hiding a Mitsubishi device or constant by their color.
Program crash during import of Remote I/O project
Description: When I try import an export file of a complete Remote I/O project via the menu command 'Project-->Other-
->Import', the program crashes. Why?
Work Around: There are two ways to prevent the program crash:

1. Import the ASCII file via the context menu of the navigator window.
2. Import the ASCII file via the menu command 'Object-->Import'
FX-Configurator-EN Opening Settings not necessary
Description: I have set up the necessary parameters of FX3U-ENET in FX Configurator-EN, and written the parameter
to the module. I verified that the IP address is correct by using Windows Ping functionality. I have set up
the communication in GX IEC Developers Transfer Setup to use Ethernet as interface, but I cannot
communicate with the PLC in GX IEC Developer.
Answer: If you want to communicate with the PLC via Ethernet in GX IEC Developer, you will have to change the
'Open settings' in FX Configurator-EN:
- Click the 'Open settings' button in the 'Ethernet settings' page
- Set the 'Protocol' value in the first row to 'TCP'
- Set the 'Open system' value in the first row to 'MELSOFT connection'

Afterwards write the parameter to the module.
Technical Notes
Page 18
Wrong monitoring of String variable
Description: If I change the value of a STRING type variable during monitoring to a string that contains an ANSI
character that doesnt have an OEM equivalent such as the Euro () symbol, its replaced by an
underscore (_) character.
Answer: String variables are represented in different character sets in Windows applications and on the PLC. GX
IEC Developer uses the ANSI character set, while the PLC program uses the OEM character set. Its
necessary to convert the strings between the two character sets when writing and reading strings
to/from the PLC. However, some ANSI characters like the Euro () symbol have no OEM equivalent;
therefore they cant be displayed properly with the OEM character set.
Work Around: None.
Memory problem with big projects on Win98
Description: What is the reason for GX IEC Developer to run out of memory when working with big projects under
Windows 98?
Work Around: Increase the virtual memory of the operating system.
Case sensitivity for identifier using ""
Description: Why can't I use a symbolic variables including special characters like "" in lower case
notation instead of upper case notation in a POU like it was declared in the GVL/local header? This is
possible for symbolic variable names without special characters.
Example:

GVL declaration: TEST; BOOL
POU usage: TEST (if the variable is used that way it will bring up compiler errors!)
Answer: This is limitation of the software.
Work Around: Identifiers including special characters should only be used in the same way as they were listed in the
local headers or the GVL.
Problem during import from Excel
Description: GX IEC Developer crashes during the import of my Excel file (last saved in Microsoft Excel) that contain
certain types of formatting into Device Edit, Entry Data Monitor or a Declaration Editor.
Work Around: Open the file in Excel and remove the following formatting before attempting to import the file:
Cell borders
Cell background colors
Cell text colors that were not created by GX IEC Developer
Technical Notes
Page 19
Restore of project from diskettes
Description: When doing a project restore from floppy discs, I get a message "This is not diskette #2" after inserting
the second disc and clicking ok. What is the reason for this message?
Answer: This is a problem caused by the Virus Scan software.
Work Around: 1. Press retry and the disc should be recognized correctly.
2. Disable the Virus Scan software and the restore should work as expected.
2. Update your Virus Scan software. E.g. McAfee 4.51 -> 7.00
Copy/paste of variables in ST
Description: If I paste the text "if x1 and x2 then" in a ST body of my project, the text is converted to "IF x1 AND X2
THEN". Why is x1 not converted to upper case?
Answer: x1 is declared as local or global variable. Variables are not converted to upper case during paste in ST.
Work Around: Choose a color for ST Variables which is different from the text color. Then you can distinguish
variables hiding a Mitsubishi device or constant by their color.
Boot option for Q00(J)/01 does not work correctly
Description: I am using a GX IEC Developer project with a Q00(J)/01 PLC. The parameter 'Do boot from Standard
ROM'
is active and I have downloaded my program and the parameters to the PLC. Additionally I have
transferred the content of the Program memory to the Standard ROM. When I now don't want to boot
from Standard ROM anymore I have to disable the flag 'Do boot from Standard ROM' in the parameters
and download it to Program memory and transfer it to Standard ROM.
But the PLC is still booting after powering on. Why?
After disabling the flag 'Do boot from Standard ROM' in the parameters and downloading it to Program
memory the boot file "AUTOEXEC.QBT" is not deleted in the Program memory. If you now transfer the
content of the Program memory to the Standard ROM the boot file is still copied. The existence of the
boot file in the Standard ROM is the cause of booting after powering on.
Work Around: Delete the file "AUTOEXEC.QBT" from Program memory and transfer the content of the Program memory
to Standard ROM with the menu 'Project-->Transfer-->Copy Program Memory to Flash ROM'.
Download to Standard ROM is not possible.
Description: Downloading a project to drive 4 (Standard ROM) of a Q PLC via Ethernet connection using the UDP
protocol sometimes fails.
Answer: This problem is caused by slow and/or unreliable connection to the PLC, especially when using local and
/ or multiple hubs.
Work Around: Please try the following:
Check the cables between the PC and the PLC.
Use a faster Ethernet hub.
Use the TCP protocol instead of UDP (other restrictions apply).
Technical Notes
Page 20
Automatic address filling for DUTs
Description: Why are addresses double assigned after using automatic address filling for DUTs which are used in a
in GVL?
Answer: Automatic address filling for DUTs handles only unassigned variables. Variables which are already
addressed, will be skipped. Furthermore, the start address for automatic address filling is increased for
all assigned variables without checking already existing variables. The user has to take care that there
are no overlapping ranges.
To avoid overlapping ranges by a complete reassignment, the existing addresses have to be cleared.
Work Around: A workaround is not possible. By using Excel via Export/Import, more operations are possible.
Library time stamp
Description: Why is the time stamp of an open library changed after Rebuild All?
Answer: The reason is, that compiler stores the compiled code together with the used POUs. If POUs in open
libraries are used for compilation, the code will be added and saved.
Work Around: A workaround is not available.
Communication problems using Docking station
Description: Why do I have communication problems with my serial interface (communication timeouts) if I use a Dell
notebook on a docking station?
Answer: This is an electrical problem caused by the docking station.
Work Around: Please use the serial interface directly without the docking station.
CPU error after using SFC on a Qn PLC
Description: Why does a Q PLC goes into error " SFCP FORMAT ERR: " when a huge POU SFC is used?
Work Around: Check, whether you have used not more then 512 transitions.
Technical Notes
Page 21
Export from Device editor/EDM to Excel
Description: It is not possible to create a diagram in Excel using the files created by the 'Save to File' functionality in
Device Edit and Entry Data Monitor. Excel doesnt find any numeric values.
Answer: This is a software problem, caused by the cell formats in the exported files.
Work Around: Try one of the following:
- Save and re-open the exported file in CSV format.
- Select the whole range of values in Excel, copy to a text editor (e.g. Windows Notepad) and copy back
from the text editor to Excel.
System Error 6608 at FX PLC
Description: In a project for a FX1N a task with "M10" as event is used. "Timer/ Output Control" is activated for this
task. If it is the first task in the compilation order and a SFC POU is assigned as first POU to this task the
PLC goes into system error 6608 after a Rebuild All and a download to the PLC. Why?
Work Around: Create a dummy task without any POUs assigned. Set the priority of this task to e.g. 0 so that it is
compiled first.
Temporary Variable for data type STRING too short
Description: An array of STRING [32] is used in a Q project. When a dynamic index is used and MOVE_E e.g. as ST
statement:
MOVE_E (Condition, ArrayOfString [Index], AnotherString); the compiler uses a temporary variable with
too few addresses. Only one device is allocated and all following addresses are overwritten. Why?
Work Around: Use the function STRING_MOV_M instead.
Wrong message "Update Libraries"
Description: Why do I get a library update request when opening a new created or already updated project?
Answer: This is a problem with the Windows Operating System if "Automatically adjust clock for daylight saving
changes" is enabled. The file time settings are modified by this setting depending on the summer/winter
time by one hour. As a result, GX IEC Developer reports a new available library.
Work Around: Disable "Automatically adjust clock for daylight saving changes".
If this is not working please disable the flag "Automatically adjust clock for daylight saving changes".
Then remove and reinstall GX IEC Developer.
Technical Notes
Page 22
Symbolic constants for CASE in ST
Description: Why is it not possible to use VAR_CONSTANT or VAR_GLOBAL_CONSTANT for a CASE in a ST body?

Example:
CASE D0 OF
MyConst:
D3 := D4;
END_CASE;
Monitoring in ST
Description: When monitoring of an ST POU is started, the first visible line of the editor changes. Why?
Answer: This is s software problem.
Work Around: None.
Monitoring/tooltip problem in ST editor in Win98
Description: When monitoring a large ST POU body under Windows 98, no values are displayed for the bottom
section of the POU. For this section, tooltips are also not displayed.
Answer: This is a Windows 98 OS problem.
Menu item "Delete Externals"
Description: A global variable is declared as MyGlobArray with the data type ARRAY [0..31] of BOOL. It is used in a
POU as K4MyGlobArray only. When the menu Extras\ Delete Externals is used, the VAR_EXTERNAL
declaration of MyGlobArray is also deleted from the POU header. Why?
Work Around: Copy the global declaration to the header again.
Technical Notes
Page 23
Wrong compiler error message
Description: In a project the message 'C9017 (Lex failure) SIC - line 6: Token (-1) '' invalid. Try to isolate the error
cause, create an example project with 'Extras\Project Backup' and send it with a short description to
your distributor.' is shown. Also some other error messages are shown because to few system
addresses where defined. Why do I get the error C9017?
Answer: The code generator continues the compilation even when not enough system addresses are defined
and the addresses for global or local variables could not be allocated to show as much errors/ warnings
as possible in one compilation run.
Work Around: Correct all other errors and repeat the compilation. If C9017 is still shown without any other error
message please send the project backup to your distributor to help us to correct the problem.
Try to use a different way to program your logic until C9017 is no longer displayed to continue with your
project.
Problem with counter C251 FX2N
Description: I am using a high speed counter in my program for a FX CPU. To reset the counter, I have written a LD
POU and assigned it to an interrupt driven task. But once the counter is reset, it does not start to count
again. Why?
Answer: It is a hardware problem.
Work Around: The RST instruction, which was used to reset the high speed counter, must once be called with FALSE
as EN condition to be able to activate the high speed counter again.
SFC transitions in Actions with TRAN
Description: It is possible to use the TRAN keyword outside of a transition body or with a read access in a transition
body. Why do I not get an error or a warning during check, build or rebuild all for it?
Work Around: Use the keyword TRAN as destination of a transition expression only.
"PLC Clear-->All" works not correctly
Description: When I use the "Online->PLC Clear->All" functionality there is a message displayed that also forced X
devices will be cleared. But the forced devices will not be cleared. Why?
Answer: This is a PLC hardware problem. Newer versions of the QnA PLC don't have this problem. Please
consider upgrading your QnA PLC, if it has this problem.
Work Around: After "Online->PLC Clear->All" please also use the "Online->PLC Clear->Forced Inputs" functionality.
Technical Notes
Page 24
Inaccurate floating point calculation
Description: Sometimes the exponent function shows inaccurate floating point calculations. Why?
Answer: The PLC causes the inaccuracy. The PLC doesn't have a n-based exponent function, only an e-based
exponent function. So when using n-based exponent in ST (like "Result := Data ** 2.0;"), it is
translated to the following MELSEC code:

LD SM400
LOG D0 D2
E* D2 E2 D2
EXP D2 D2

And since the inaccuracies of all floating-point operations get accumulated,
in the end we get a result that is a bit inaccurate, which is then
(correctly!) displayed by monitoring.
Work Around: There is a setting on the PLC Parameter -> PLC System tab named "Perform
internal arithmetic operations in double precision". If this option is
checked, floating-point calculations are performed with a higher precision
by the PLC and the problem described below can be minimized or doesn't happen. This setting also
affects the performance of the PLC.
Use of RET_M
Description: I am using the RET_M function inside a FB instance. If the "Use Macrocode" property of the FB is not set I
don't get any error after a "Rebuild all" and a download to the PLC. But when I enable the "Use
Macrocode" property and make a download or online change I get the error "4212 CAN'T EXECUTE (P)".
The RET instruction was before the FEND instruction in the main program.
Work Around: Use the return operator in LD/ FBD or the operator RET in IL or ST instead of the RET_M. Then the code
generator handles it and generates a RET instruction for functions or called FB instances. For FB macros
and program a jump to the end of the FB macro or of the POU is generated.
Transfer speed for A2AS-S60 is no longer supported
Description: For A2AS-S30 and A2AS-S60 PLCs it is only possible to select 9.6Kbps in the Serial Port's Transmission
Speed in Transfer Setup. In GID 5.02 it was possible to select 19.2Kbps as well.
Answer: For GID 6.00 and higher only 9.6Kbps is allowed for compatibility reasons with older CPUs.
Work Around: None
Technical Notes
Page 25
Recommended poll rate settings
Description: What is the recommendation for the poll rate settings?
Answer: Connection Count of monitored devices Qn(H) QnA(S) AnS FX2N(C) FX0N
Fast Few 100 100 200 100 -
Fast Many 100 100 400 500 -
Slow Few 200 200 200 200 500
Slow Many 400 400 400 500 500
Work Around: None
No monitored value in dynamic arrays
Description: I have a POU body in which I access an element of an array by addressing it with a variable. E.g.
MyArray[MyVariable]. If I monitor this body, the current value of the array element is not displayed. Why?
Answer: It is not possible to monitor the current value of such an expression. Only array elements addressed by
a constant index are monitored.
PLC-Diagnostics
Description: Sometimes when I work with my A2S I get strange error message saying that the PLC type set by the
project differs from the connected PLC type. But both, my project and connected PLC is A2S.
Answer: This is a PLC hardware problem. We know these issues for A2S PLC version "AB".
Work Around: Please upgrade your A2S PLC to version "CE".
Reset of high speed counter in a event driven task
Description: I reset the high speed counter C238 of a FX2N in an event driven task in GX IEC Developer with the
event M8002. Why does the counter not count even when I have enabled it in an always running
program?
Answer: It is a handling problem.
Work Around: The RST instruction of a high speed counter must be executed once with the EN evaluates to FALSE.
This could be ensured in GX IEC Developer for an event triggered task by setting the "Timer/ Output
Control" check box in the task information dialog.
Technical Notes
Page 26
Iparam file is not exported
Description: The export of projects does not export the intelligent function utility setting file. The project backup
function does not backup these settings either. Why?
Answer: It is a software limitation.
Work Around: The file "IPARAM.WPA" is a binary file generated by the "Intelligent Utilities". You have to copy this file in
the new project directory manually.
Sorting in declaration editors
Description: Declaration editors can only be sorted in ascending order. Why?
Work Around: None.
No size check of strings connected together
Description: Why is there no support for checking the string size by the code generator?
Answer: For a variable of data type STRING the string size is not checked whether it is large enough or not when
a value is assigned to the variable. E.g. when a STRING (8) variable is concatenated with another
STRING
(8) variable the destination could be declared as STRING (15) variable when it is ensured that the sum
of the length of the source variables are not greater then 15. For safety reasons always the maximum
possible string length should be calculated.

Please remember that the terminating character is not included in the string size of a variable. E.g. if it is
declared as STRING(6) it occupies 4 words, 3 for the 6 characters and the lower byte of the next word
for the terminating character. A variable declared as STRING(9) occupies 5 word devices. The
terminating character is written into the upper byte of the 5th word.
Work Around: None
Availability of MXChange
Description: MXChange is no longer available in GX IEC Developer 6.01.
Answer: You need a new PAK from your dealer for the installation of GX IEC Developer 6.01 and future versions
to enable MXChange.
Work Around: Install GX IEC Developer 6.01 again with the new PAK.
Technical Notes
Page 27
Code generation compared to GID 5.02
Description: When I open a project from GX IEC Developer 5.02 with disabled project specific option "Code
Generation - Generate code as in GX IEC Developer 5.02", the generated code is too big for the available
memory of my PLC. Why?
Answer: The code generation in GID 6.00 has been changed for several reasons. Details can be found in the
chapter "Project specific options - Code generation" of the help file.
Work Around: - Enable the project specific option "Code Generation - Show warning for different coding of GX IEC
Developer 5.02 / 6.00" and disable "Code Generation - Generate code as in GX IEC Developer 5.02".
Rebuild the project and check the generated code for the compiler warnings C9132, C9134, C9136,
C9138, C9140 and C9142.
- Enable the project specific option "Code Generation - Show warning for different coding of GX IEC
Developer 5.02 / 6.00"and "Code Generation - Generate code as in GX IEC Developer 5.02". Rebuild the
project and check the generated code for the compiler warnings C9135, C9137, C9139 and C9141.
MBOC availability not recognized
Description: My QCPU is formatted to support MBOC for Online Change. Sometimes I get an error message during the
Online Change that the changed block size is too big for SBOC. Why is the MBOC availability not
recognized?
Work Around: Repeat the Online Change after the aborted procedure.
FX2N interrupt problem after online change
Description: Why is my task with the interrupt I301 not working after an online change for a FX2N?
Answer: The interrupt is disabled during the online change.
Work Around: Ensure that the EI instruction or the EI_M function is executed after the online change. We
recommend to use the EI_M function in a POU, which is executed every scan.
Using parameters of a macro function block
Description: Why is it not possible to use a parameter of a macro function block before calling the macro
function block?
Answer: The parameters of a macro function block have no addresses. If the macro function block is
called, the actual given parameters are used. A system address is assigned to all parameters,
which have no assignment to a value or a variable. After calling the macro function block, the
parameters can be used with the values or addresses of the last call.
Work Around: Call Project -> Build after the failed compilation of the project.
Technical Notes
Page 28
SFC editor and project navigator
Description: When I close the SFC editor without saving the last changes, I get sometimes different
transition
Work Around: Rename the transitions in the SFC editor to the original name.
PLC keyword on QCPU
Description: What is protected when I register a PLC keyword on a QCPU?
Answer: Only the program files: MAIN.QPG (if existing) and SFC.QPG (if existing) on drive 0.
This means, that a user can make a symbolic upload or an upload from a drive different from
drive 0 without entering a keyword.
Work Around: To achieve a protection of a program, make only a download without symbolic information to
drive 0 and register a PLC keyword.
Monitoring MELSEC IL code
Description: I use a DMOV instruction in a MELSEC IL POU. When I monitor this POU the destination
register is monitored as a 16-bit device. How can I see the value as 32-bit device?
Answer: The monitoring uses only the used devices, addresses or symbolic variables and takes the
according type for display. Mitsubishi direct devices are always taken as 16-bit devices
regardless with which instruction they are used.
Work Around: If you want to monitor 32-bit in a MELSEC IL network you must use a 32-bit IEC direct device or
a local or global variable of a 32-bit data type. You can also monitor D100 and D101 in the EDM
as 32-bit value, if you enter "D100+D101" as address.
Modem connection to QnA
Software: Melsec Medoc plus
Found in Version: MM+ AE 2.50
Description: It is not possible to communicate with the QnA series via modem. Why?
Answer: Make the following modem settings at both modems (PLC side and PC side):
- Software flow control must be disabled (Hayes code: &H0 &I0 or &H1 &I0)
- Recommended communication parameters are: 9600 Baud, no parity, 8 data bits, 1 stop bit

Make the following modem settings at the PLC side:
- Auto answer mode should be enabled (Hayes code: S0=1)
Technical Notes
Page 29
SFC control by special relays
Found in Version: MM+ AE 2.3a
Description: SFC control by special relays:

a) I use a special function relay SM321 of the QnA series to reset an SFC. This does not seem
to work. The SFCs are activated by a SET BLn instruction.
b) If a cyclic SFC task is off, the SFC is still active.
Answer: SFC control by special relays:

a) The SFC part of MMP.INI is not valid for the QnA series. The special relay for resetting an
SFC (SM321) controls all SFC POUs. The first SFC (BL0) is active in MM plus 2.31a and MM
plus 2.32 permanently; the other blocks BL1, BL2... can be controlled. If all SFCs have been
switched off with SM321 it is not enough to switch SM321 on afterwards; all SFCs have to be
switched on individually (either block wise, eg BL1 or stepwise eg BL1\S0). This is allowed
earliest one cycle after switching off SM321; otherwise a PLC error occurs.
b) This depends on the task realization concept of MM plus; cyclic task control of an SFC must
be realized manually by the PLC program.
Work Around: a) If SFCs are intended to be controlled individually, the first one should be a dummy; then all
others can be controlled.
Limitation example
Description: If you make a change offline and then execute "Project/Online program change", MM plus does
not jump back to the original code, if the changes made were too extensive.
Answer: This is the definition of the functionality "Project/Online program change". You can edit as many
elements (POUs, Tasks, GVL) as you like. It is even possible to leave and store the project.
After a period of modifications you can execute "Project/Online program change". This will build
the PLC code for the current status of the project and will compare this PLC code with the PLC
code from the last compilation/build. The differences are checked, and if they fit into the range
which is supported by the operating system of the PLC, the online change will be executed.
If the change is bigger than supported by the operating system of the PLC, there is no way to
execute online changes and the project will remain as it was before the attempt of online
change.
So, there is no way back to the original status of all editors, because this would cause that the
entire project had to be stored when a project is downloaded to the PLC. For capacity reasons
this implementation is not realized.
Work Around: There is the "Online change mode" which allows to go back to the original code in case the
online change fails. According to the needs of an application one or the other way of online
change can be executed.
Technical Notes
Page 30
Verify error
Description: When I perform an online change an error message is returned reading that I do not have the
same version in PLC and PC. MM plus returns that the code is generated at different times.
This occurs even if I only moved one contact sideways. I did not change the function.
Answer: There are two different options in MM plus to execute an online change.

"Project/Online program change"
> Used to make several changes in advance, then execute them at one time.

Online change mode
> Must be activated first. If the projects are consistent, this mode will be activated and online
changes can be performed network-wide.

Please refer to the following scenarios and descriptions:

a) After an editor was modified it is not possible to identify whether this will really result
in different binary code. Therefore, it is not allowed to start online change mode. Executing
"Project/online program change" however works fine. It builds the project (which means
only the affected POU). This may lead to 2 different results:

>b1) Binary difference is found. Then online change at PLC will be executed.
>b2) No binary differences found. No action to PLC is necessary.

After b1 as well as after b2, activating online change mode is possible again

b) Alternative to the process in a) there is another way to allow the online change mode after
"dummy" modifications in an editor again.
Simply execute "build". MM plus will build the project again but will not find any binary
differences. The editor will internally be set to "Compiled" but the time stamp will not be altered
because there are no binary differences.
After taking these steps, it is also possible to enter the online change mode again.

c) If the program in MM plus has "really" been modified and built, MM plus will set a new time
stamp because there are differences in binary code. If the code is modified and built again so
that it will result in the same binary code from the starting point, MM plus must set a new time
stamp.
At the following attempt to activate the online change mode MM plus will display the different
generation times. At this time you can select the option "Verify". MM plus will compare the
program in the PLC and the binary code in MM plus.
If they are identical, the online change mode will be activated automatically. If they are different,
online change mode will not be activated. This is correct.

d) "Really" modify a POU. The following build process will generate different binary code. In this
case MM plus sets a new time stamp. A following attempt to start online change will be
refused.
This is absolutely correct because online change cannot be started when the code in MM plus
and in the PLC are different.
After downloading the program to the PLC online change is possible again.

CONCLUSION:
Based on these descriptions you can see that online change can be done as long as the
projects in MM plus and PLC are consistent (identical binary code). MM plus provides the
means to ensure that MM plus and PLC ARE consistent.
Start-up parameter for MM+
Description: Is it possible to open a GX IEC Developer project by appending a project name to the MMP.EXE
file like:
Answer: Yes. You can also use "MMP.EXE C:\MMPPRO\myproj /NOLOGO" - this is more convenient.
Technical Notes
Page 31
Device Edit: C200 - C255
Found in Version: MM+ AE 2.31 ES (SP 3.0)
Description: When inserting the counter device by the "all" option in the dialog 'Device Edit', 32-bit counters
(C200 - C255) of FX2N CPUs will not be inserted.
Answer: The dialog 'Device Edit' specifies that only 16-bit devices can be inserted and edited. This
means that all 32-bit devices (e. g. C200 - C255 for FX2N, FX2C) can not be used.
Generated code for SFC start of A-series
Description: Why is my SFC program still being executed, even if I have removed the POU from the task?
Answer: In the following cases code is generated automatically to enable/disable SFC execution:
- In the section "[SFC]" of the INI file the entry "GenerateSfcStartupCode" is set to "TRUE".
- The section or the entry do not exist at all

If the entry is set to FALSE, 0, or NO no automatic startup code is generated. See the
description in the INI file for more information.
Browser and EDM shows different variables
Found in Version: MM+ AE 2.31 ES
Description: Why does the browser not work in a case sensitive way according to variable identifiers?
Answer: The background is the standard IEC 61131-3. This standard defines that there is no case
sensitivity. The browser works according to this fact. Therefore, the browser does not
differentiate between m3 or M3 in the body.
L devices
Description: Why are latched relays represented by an M instead of an L?
Answer: This is a consequence of the free editors and the internal concept of GX IEC Developer.
Multiple operands in logical modules (i.e. AND)
Description: Why is no error returned, if in an Instruction List statements like the following ones are
included:

LD op1
AND op2, op3...., op28, op29
ST output

Answer: There is no limit checked for the number of extensible inputs of the standard operators in
Work Around: Check this limit manually.
Technical Notes
Page 32
Inserting a variable twice in the EDM
Description: If I insert a variable twice in the Entry Data Monitor and change the value of one of them, the
other display of this variable is not updated. Why?
Answer: The monitor mode is switched off. In this case you can enter several values which are not
overwritten by the actual values off the PLC. All or selected values could be written to the PLC.
Work Around: If your monitor mode is switched on, the value of the variable entered twice should be the
Pause state set by key
Description: Why does the Start/Stop PLC dialogue not display a pause setting by key switch?
Work Around: Not available. Please, refer to the key setting for this function, not to the MM plus display.
Improvement: ASCII instruction
Found in Version: MM+ AE 2.31 SP 0.2
Description: Why is it not possible to use the ASC instruction in IEC editors?
Answer: The ASC instructions needs a string constant as input parameter. The IEC data type STRING is
not supported for the A and FX series.
Work Around: Use the ASC instruction in MELSEC IL only.
Or replace e. g.

ASC_M "ABCDEFGH" D9

with

DMOV_M H44434241 %MD0.9
DMOV_M H48474645 %MD0.11.
Outputs of function blocks should not be written
Found in Version: MM+ AE 2.31 SP 0.2
Description: Why are the outputs of a function block written if EN is FALSE ?
Answer: This is the specification of MM plus.
Work Around: Do not connect the output parameter directly to the FB in LD/FBD. In IL do not use the output
parameter with the call of the FB. Use MOVE_E to assign each output of the FB.

Example in IL:
CALL FBInst (EN:=M0,VarIn:=D0, VarOut1:=D2, VarOut2:=D4)

Use instead:
CALL FBInst (EN:=M0,VarIn:=D0)
LD M0
MOVE_E FBInst.VarOut1, D2
MOVE_E FBInst.VarOut2, D4
Technical Notes
Page 33
Timer coils
Description: I programmed an LD TC0, ST Y10 in IL. But the value of Y10 is set according to TS0. What
must I do to show in Y10 that the timer T0 is started?
Answer: The generated code for TN5, TS5, TC5 is always T5. It depends on the instruction what part is
used. All bit writing instructions use TC, all bit reading instructions use TS, and all word/double
word instructions use TN. For TS5 an error is displayed, if it is used for writing.
Work Around: Also if TC is read no error is displayed in MM plus because it must be used with read access
as input parameter of the TIMER_M etc. functions.
Curious SFC
Description: I do not get an error message when I write an incorrect SFC although this SFC does not run on
Answer: Like in other editors MM plus cannot check whether the application program will work correctly
as long as the specified syntax of the language is correct. In case of SFC also an error
message "Unsafe SFC" is returned, if the editor finds a construct which might lead to
problems. But only some cases are found, so be sure your SFC structure is correct.
Work Around: Do not use unusual SFC structures.

Technical Notes PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Technical Notes PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Technical Notes

Anda mungkin juga menyukai