I would like to share an issue with you.

In the Translation Points section, when creating a new point, we can use uppercase letters in the name.
For example, in the image, I created “Take1” with a capital “T”.

If we use the EXISTTRANS command in the program to check the validity of a point, the software automatically shows the points, and the program compiles correctly.

However, when running on the robot, we encounter an error,
because the Kawasaki robot only works with lowercase letters.

I manually changed “Take1” to “take1”, and then the robot executed the command without any error.

It would be better if, in all sections such as Reals, Integers, Points, and other values, the system does not allow users to enter uppercase letters, in order to prevent such errors.

Hello,

that is one of the curiosities of the AS language. You are allowed to enter commands and variable names in upper- / lower- / mixed case as you like. IDEs, editors and other software needs to support it. In some rare cases, however, the AS system falls short due to its own flexibility. This is just one of a few examples where this happens, and I don’t know them all.

For me, mixed-case names are one of the advantages of K-IDE. It prevents using extra characters to split a name. This way, you don’t have to use extra characters to separate a name. You can use “PickPos” instead of “pick_pos” and thus save one of the precious 15 characters of a variable name. K-IDE goes to great lengths to ensure that case is preserved in naming. It uses a special AS program to preserve naming conventions and comments. This will most likely not be removed. Removing case-sensitive support from K-IDE will not prevent you from inserting uppercase letters into the “EXISTxxx” functions.

I also agree with you that supporting both uppercase and lowercase letters is very useful.

But this feature should not cause errors in the overall program process.

Also, when we send a program to the robot and then retrieve it again, all characters are automatically converted to lowercase.

So, the uppercase/lowercase feature is only effective if we always have access to the original program file.

If you realize that upper-case characters will make trouble in "EXISTxxx" commands, simply don't use it.

The mixed case variable names are stored in the controller and can be downloaded from the robot. If you use this feature properly, you and all other people are able to get them back from the controller. The same is true for special variable declarations (subvariables) and comments. Please see the numerous posts about "K-IDE documentation" in this forum and take a look at the manuals!