Changing Languages for Localization

Description
Getting to know how to deal with language traslations in FactoryTalk Optix. Display also alarm messages and create a new language dictionary! This is putting into practice the instructions from the ASEM video on Localization.

Contributed by Xavier Florensa – YouTube – LinkedIn – GitHub

Transcript
(00:01) Hi everyone. In this video, I will show you how to work with languages change in your HMI in your machine. So, let me show you an example. This is the boiler demo taken for from automation repository in GitHub. And when we go to the ARMS page, I have added some flags to change language. There were only English and Italian languages.
(00:33) Here I have added more languages. And let’s take a look at this message concerning the alarm that you want to have translated in some languages. Not everything will be translated version. For instance, if we change to Italian, sound words are translated, but only one alarm is translated. When we change to Catalan, only one alarm is changed.
(01:08) We’re missing this translation for the Ethernet message. So to fix this, well, you can learn how to deal with languages in this great video by ASM concerning localization. So let’s go to our application here. We have to locate the alarm that we are missing. It’s this one. The Ethernet IP station alarm message. And here we can copy this value and search on our dictionary.
(01:55) Can go to the dictionary. Let me make this. You have the dictionary in your translations. Okay. Let me make this a little bigger. Yeah. And here we can see all what will be translated. Only what you have marked here will be translated. But you have the list of everything. You can search for this text. Yeah, we have it here.
(02:34) We see that it’s not synchronized and there’s no key. First we have to do is synchronize it. Now we have the key and we can switch back to the dictionary here. When we look again for this message, we see that the language are missing here. So we can copy it to translate this way. And I could do something like this. for instance.
(03:41) Okay, we have it right. I will do this later. So we can go back to our application. First you have to stop the application and start again. Okay, we can go to the arms page and make the message a little bigger. And if we try now the message is translated. And now imagine you want to have a new language here.
(04:43) You have to go to your dictionary. and add a new local. We will add this Spanish. But look, it’s in blank. So, we can do something to fix this. You can go to your optics studio to the libraries. Let me put this here. Okay, you can go to the libraries and you can look for exports. Here you will find translations. Exactly.
(05:47) You drag and drop. You will have here this script. Then you can execute. Well, take a look at this. You have to be aware of the path. Where will you store this? this file. Then let me change. Well, we can use this this name. This is the last one. So, you can execute export translations. Then you can go to your directory and you will find here the file
(06:58) exported. So you can go to JP to do this for you. For instance, can change the instructions. Now say I want to change to Spanish. Spanish. and you can insert the file. Let’s be sure that we will use this path. So, we add Oh, I have it here. So this is the dictionary and let’s make
(08:03) chibity work for you. We’ll take a little when you finish you’ll have your file ready to import. When you’re going to report once it’s finished, you only have to go here and execute import relation and you will have this column filled for you. Let’s see if this is finished. Yeah, you can download this file. have it here.
(09:02) And you can also go to the other project file. So we will take this one here. Have to change Let’s open it to see if there is something here. Yeah, we have the Spanish translation here. Okay, close this and we can go to our optics to first of all you have to change the path since the file is another one.
(09:59) The file has changed a little and it’s this one. this one. Okay, let me be sure that Yeah. Okay. So, we can just let me execute import relations. We have to update update this table. Yeah, we have now Spanish here. Okay. So if we go to our application in the pages of alarm lists, I mean
(11:03) arms pages where the pages here arms page and we can go to this. Let me put the properties here. Yeah, we can go to this button. Here we have a button. Not yet. Let’s copy this button. This will be Spanish. Okay, we have to copy the method. Here we have a method. Can copy this method. I know the method is already copied when copying the button.
(12:05) But you only have to change the language. Yes, this one. Okay. So we have it. Now each time you change the language, we will see the new ports. Excuse me. Front. Okay, now we can test this. First of all, let me restart the program. Go to the arms page
(13:18) and not the arms but some boards will be changed. Yeah, you have done it. So, I hope you enjoy. Thank you very much.

Tutorial List

• Linking pushbuttons to a Logix tag
• Dynamic Link Key-Value Converter
• Create reusable graphics
• Object model alias
• Alias with Logix a UDT
• Dynamic alias index with Logix UDT
• Popup Dialog Box
• Build a faceplate
• Create Variables with Structured Data Types
• Rockwell Automation Device Libraries for Optix
• Optix Presentation Engines
• New Windows for Web Presentation Engine
• Changing Languages for Localization
• ComboBox to Change PLC Tag