8.1 Programming
- Baosky IDE currently only supports programming languages LD, ST, SFC
- The difference between Baosky IDE and XIN3Plat-Control in Applications: After adding a PLC device to "Baosky IDE", the project tree will generate a unique node "Software", and the "Software" node cannot be deleted or added.
8.1.1 TASK calling
- The program PU of "Baosky IDE" can only be called by a certain TASK, but XIN3Plat-Control has no restrictions, and PRG can be called by PRG
- The TASKs of "Baosky IDE" and "XIN3Plat-Control" only support the calling of PU programs. The advantage of "Baosky IDE" is that it adds enable settings for PU
8.1.2 Namespace
- Both "Baosky IDE" and "XIN3Plat-Control" support "." as the operator of the global namespace
- Baosky IDE must define a namespace, but XIN3Plat-Control does not have this restriction
- The first-level namespace name cannot use "SYS", "SYS" is the first-level namespace name of the system library
- When a user-defined PU name is renamed with a system library instruction, the namespace cannot be defaulted
- If the namespace name of the object under the project tree software is consistent with the default namespace of the current software, the namespace is not displayed after the object name in the project tree, otherwise, the namespace of the object is displayed in the pointed brackets, as shown in the following figure, the namespace of GVS_1 is consistent with the default namespace of the software node, STD

Converting programs from XIN3Plat-Control to Baosky IDE
When creating PU,UDT in Baosky IDE, users don't need to modify the namespace, just use the default namespace. When creating GVS in Baosky IDE, there are two situations that need to be noted.
-
Corresponding to XIN3Plat-Control attribute exists

-
Corresponding to XIN3Plat-Control attribute deletion

8.1.3 Program unit
- The comparison and conversion of program units between Baosky IDE and XIN3Plat-Control is as shown in the following table:
| PU/POU | XIN3Plat-Control | Baosky IDE | Remarks |
|---|---|---|---|
| PU | PU can be called by TASK or other PUs | PU can only be called by TASK | Improves system stability |
| FB | FB instance definable area has no specification | FB instance definable area specification is as follows: 1.Globally callable FB instances can only be declared in GVS variables 2.FB nested instances can only It can be declared in FB's STATIC, but the instance can only be called locally in FB | |
| PU/FB/FC variable declaration area | The variable declaration area can be text or table | The variable declaration area is completely tabular and has powerful editing functions. It also supports IEC standard text import |