Otasuke Pro! Technical Resource > Otasuke FAQ's Book

GP Pro-EX and GP-PRO/PBIII C-Pakage Compatiblity

Restriction Comparison

The differences of restriction for creating a logic program with GP-PRO/PBIII C-Package and GP-Pro EX are introduced here.

01	Comparison of Performance Specifications of GP-PRO/PBIII C-Package and GP-Pro EX

Differences of Settings

The differences of settings for creating a logic program with GP-PRO/PBIII C-Package and GP-Pro EX are introduced here.

01	The interval for the scan time can be set by 1ms
02	The controller auto start setting can be set to either RUN or STOP
03	The storing order of character string data is different between GP3000 and GLC
04	The types of symbol variables used in a command should be identical

Settings required to be changed

When converting a project file from GP-PRO/PBIII C-Package to GP-Pro EX, you may need to modify the data depending on the setting contents of the logic program. Points to be modified and precautions for these modifications are introduced here.

01	The ladder Monitor function is converted into the Logic Monitor function
02	When an error occurs in the logic program, the project file cannot be converted
03	About logic file (*.WLL) conversion
04	DIO drivers for GLC100/300 series are converted to Flex Network drivers
05	About bit performance of an integer variable in D-Script
06	To set an initial value to a variable
07	About conversion of variables to be undefined addresses
08	About restriction of array elements
09	About conversion when assigning array variables via Configure I/O
10	About a project file with no drivers assigned
11	Precaution for the conversion when the system variable "#Screen" is used for switching screens
12	For Integer Array, when accessing a bit
13	LS and LSS variables become LS devices

Variable/ Instruction Conversion

When converting a project file from GP-PRO/PBIII C-Package to GP-Pro EX, the contents may be changed depending on the setting of variables or instructions. Changed contents and precautions for these changes are introduced here.

01	Device address names of the Fix Variable Mode are converted to fixed names
02	LS and LSS variables become LS devices
03	Temporary variables are created automatically
04	Control block variables of the PID instruction are converted to PID variables
05	About system variable conversion
06	About instruction conversion
07	If the second operand of the PID instruction if an integer constant, an error will occur
08	About values of variables LS and LSS used in a project file

Comment/ Label Conversion

When converting a project file from GP-PRO/PBIII C-Package to GP-Pro EX, the contents may be changed depending on the setting of comments or labels. Changed contents and precautions for these changes are introduced here.

A program comment is converted to a program title

1.	Up to 128 characters can be in a rung comment. The character strings over 128 will be disposed.
2.	Rung comments including [START], [END], [SUBSTART], or [SUBEND] will be disposed.
3.	In case that the value of [the number of a Rung Comment multiplied by 260] exceeds 14K, the comments over the value will be disposed.

1.	Up to 32 characters can be in a variable comment. The character string over 32 will be disposed.
2.	In case that the value of [the number of a variable comment multiplied by 68] exceeds 14K, the comments over the value will be disposed.

In case that a variable name and a comment are same, the comment (variable name. x [0], variable array name [0], etc.) will be disposed.

A user label is converted to a fixed label name (Label-**)

A subroutine label is converted to a fixed label name (SUB-**)

About conversion of a project file including comments entered in the OS in another language

↑Back to page top

← Return to the previous page

FAQ for use | Protection of Personal Information | Trademark Acknowledgments | About Intellectual Property Rights | Terms of Use