Sign In to Follow Application
View All Documents & Correspondence

Programmable Controller

Abstract: To decode a title of a file set at a PLC2 itself to the same title even if the PLC2 is connected to a plurality of external devices which use different character code sets the PLC2 is provided with a system unit (41) which uses a multiple language character code set (A) to operate a control file; a character code conversion table (44) in which a character code for a plurality of character code sets is mapped to each character; and a character code management unit (42) which when forwarding the title of the control file for an object to be accessed between the external device that uses the local character code set (A) and the system unit(41) uses the character code conversion table (44) to convert the descriptor of the title of the control file between a descriptor in the multiple language character code set (A) and a descriptor in the local character set (A).

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
28 March 2013
Publication Number
41/2014
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
patent@depenning.com
Parent Application
Patent Number
Legal Status
Grant Date
2019-09-19
Renewal Date

Applicants

Mitsubishi Electric Corporation
7 3 Marunouchi 2 chome Chiyoda ku Tokyo 1008310

Inventors

1. CHIBA Yasuhiko
c/o Mitsubishi Electric Corporation 7 3 Marunouchi 2 chome Chiyoda ku Tokyo 1008310

Specification

DESCRIPTION PROGRAMMABLE CONTROLLER Field [0001] The present invention relates to a programmable controller that controls an industrial controlled device. Background [0002] A programmable controller (hereinafter, PLC) controls a controlled device based on a user program and parameter files that define various parameters. These control files such as the user program and the parameter files are set by a programming device. Furthermore, not only the programming device but a programmable indicator or the like also refers to these control files. Conventionally, the PLC uses a fixed character-code set for communication with the programming device, the programmable indicator or the like (hereinafter, "external device"). [0003] A programmable indicator disclosed in Patent Literature 1 includes a plurality of sets of font data. Patent Literature 1 discloses a technique for switching the font data based on typeface identification information indicating a typeface of which country the characters are to be indicated. According to this technique, when an information process is performed using a common character-code set such as UNICODE, the characters can be indicated in an appropriate typeface even in a case where the typeface of the same code differs, by means of fonts of standard use depending on the countries to be used, for example. Citation List Patent Literature [0004] Patent Literature 1: Japanese Patent Application Laid-open No. 2000-227790 Summary Technical Problem [0005] However, the same character-code set is not always used for external devices connected to the PLC. It is assumed that a plurality of external devices using different character-code sets are connected to the PLC to which a usable character-code set is fixed to a specific code set. In this case, when the name of a file set by one of the external devices is to be read by another external device, so-called character corruption occurs in which the file name is not decoded into the same file name and another external device is disadvantageously unable to identify the file set to the PLC. [0006] The present invention has been achieved to solve the above problems, and an object of the present invention is to provide a programmable controller (PLC) capable of decoding the name of a file set to the PLC into the same name even if a plurality of external devices using mutually different character-code sets are connected to the PLC. Solution to Problem [0007] In order to solve the aforementioned problems, a programmable controller that controls an industrial controlled device according to one aspect of the present invention is configured to include: a storage unit that stores therein a control file for controlling the controlled device, to which a name described in character code relating to a first encoding method is assigned; a system unit that accesses the control file stored in the storage unit in response to a request from an external device; a character-code conversion table that associates character codes relating to a plurality of encoding methods including the first encoding method with one another for every character code decoded to the same character; and a character-code management unit which, in a case where an external device using a second encoding method different from the first encoding method is connected to the programmable controller and the character codes relating to the first encoding method are associated with character codes relating to the second encoding method one another in the character-code conversion table, converts an encoding method for a character code used to describe the name of a control file between the first encoding method and the second encoding method using the character-code conversion table at the time of transferring the name of the control file to be accessed between the external device and the system unit. Advantageous Effects of Invention [0008] As long as the character-code conversion table associates the character codes of an encoding method used by an external device with those relating to a first encoding method, the programmable controller according to the present invention can decode the name of a control file to the same name when an external device using different encoding method is connected to the PLC. Therefore, it is possible to decode the name of the file set to the PLC into the same name even if a plurality of external devices using mutually different character-code sets are connected to the PLC. Brief Description of Drawings [0009] FIG. 1 depicts a configuration of a PLC system configured to use a PLC according to an embodiment of the present invention. FIG. 2 is an explanatory diagram of an example of a hardware configuration of a programming device. FIG. 3 is an explanatory diagram of an example of a hardware configuration of the PLC. FIG. 4 is an explanatory diagram of a functional configuration of a PLC system according to the embodiment of the present invention. FIG. 5 is an example of a data structure of a code page table. FIG. 6 is an explanatory diagram of an example of a data structure of a character-code conversion table. FIG. 7 is an explanatory diagram of a communication procedure for setting a character-code set performed by the PLC system. FIG. 8 is a flowchart for explaining operations performed by the PLC according to the embodiment of the present invention. FIG. 9 is a flowchart for explaining the operations performed by the PLC according to the embodiment of the present invention. Description of Embodiments [0010] Exemplary embodiments of a PLC according to the present invention will be explained below in detail with reference to the accompanying drawings. The present invention is not limited to the embodiments. [0011] Embodiment. FIG. 1 depicts a configuration of a PLC system configured to use a PLC according to an embodiment of the present invention. As shown in FIG. 1, a PLC system 1 is configured so that a PLC 2 is connected to a programming device 3. The connection between the PLC 2 and the programming device 3 is not limited to a specific method, but serial connection such as USB or Ethernet®, for example, is also applicable. The programming device that sets control files such as a user program and parameter files to the PLC 2 is described here as an example of an external device. However, the concept of the external device connected to the PLC 2 according to the present embodiment also embraces a programmable indicator that refers to a state of devices of the PLC 2 and to the control files set to the PLC 2. [0012] FIG. 2 is an explanatory diagram of an example of a hardware configuration of the programming device 3. The programming device 3 has a general computer configuration in which a CPU (Central Processing Unit) 31, a ROM (Read Only Memory) 32, a RAM (Random Access Memory) 33, a communication I/F 34, an input unit 35, and a display unit 36 are connected to one another by a bus. [0013] The display unit 36, which is a display device such as a liquid crystal display, displays output information such as an operation screen for a user based on an instruction from the CPU 31. The input unit 35 is configured to include a mouse and a keyboard, and an operation of the user for the programming device 3 is input to the input unit 35. The operation information input to the input unit 35 is transmitted to the CPU 31. The communication I/F 34 is a communication interface for the communication between the programming device 3 and the PLC 2. [0014] The RAM 33 is configured by a high-speed storage device such as a DRAM (Dynamic Random Access Memory) or an SRAM (Static Random Access Memory). The ROM 32 stores therein a PLC setting program 37 and a font dataset 38. The PLC setting program 37 is a computer program for setting the PLC 1. The font dataset 38 is an aggregate of image data (font data) for each character, and the image data for each character is associated with a code for each character included in a character-code set (a local character-code set A in the present embodiment) that defines a specific encoding method. Any character-code set is usable as the local character-code set A. As Japanese local character-code sets, ISO-2022-JP (JIS), Shift-JIS, EUC-JP and the like are widely used, and one of these can be used as the local character-code set. [0015] The PLC setting program 37 and the font dataset 38 are loaded into the RAM 33 by the CPU 31 via a bus line. The CPU 31 executes the PLC setting program 37 loaded into the RAM 33. At the time of setting the PLC 1 using the PLC setting program 37, the CPU 31 uses the encoding method defined by the local character-code set A. That is, characters that constitute the name of a control file (hereinafter, simply "files") to be output are encoded by using the encoding method defined by the local character-code set A. When displaying the name of the file on the display unit 36, the CPU 31 acquires font data corresponding to the codes of the respective characters that constitute the name of the file from the font dataset 38, and displays the name of the file on the display unit 36 using the thus acquired font data. For example, when the local character-code set A defines Shift-JIS and a character code "0x82A0" in Shift-JIS is described, the CPU 31 acquires font data for "

Documents

Application Documents

# Name Date
1 2451-CHENP-2013 POWER OF ATTORNEY 28-03-2013.pdf 2013-03-28
1 2451-CHENP-2013-RELEVANT DOCUMENTS [20-09-2023(online)].pdf 2023-09-20
2 2451-CHENP-2013 PCT 28-03-2013.pdf 2013-03-28
2 2451-CHENP-2013-RELEVANT DOCUMENTS [15-09-2022(online)].pdf 2022-09-15
3 2451-CHENP-2013-RELEVANT DOCUMENTS [14-08-2021(online)].pdf 2021-08-14
3 2451-CHENP-2013 FORM-5 28-03-2013.pdf 2013-03-28
4 2451-CHENP-2013-RELEVANT DOCUMENTS [09-03-2020(online)].pdf 2020-03-09
4 2451-CHENP-2013 FORM-3 28-03-2013.pdf 2013-03-28
5 2451-CHENP-2013-IntimationOfGrant19-09-2019.pdf 2019-09-19
5 2451-CHENP-2013 FORM-2 28-03-2013.pdf 2013-03-28
6 2451-CHENP-2013-PatentCertificate19-09-2019.pdf 2019-09-19
6 2451-CHENP-2013 FORM-18 28-03-2013.pdf 2013-03-28
7 Abstract_Granted 320824_19-09-2019.pdf 2019-09-19
7 2451-CHENP-2013 FORM-1 28-03-2013.pdf 2013-03-28
8 Claims_Granted 320824_19-09-2019.pdf 2019-09-19
8 2451-CHENP-2013 ENGLISH TRANSLATION 28-03-2013.pdf 2013-03-28
9 2451-CHENP-2013 DRAWINGS 28-03-2013.pdf 2013-03-28
9 Description_Granted 320824_19-09-2019.pdf 2019-09-19
10 2451-CHENP-2013 DESCRIPTION (COMPLETE) 28-03-2013.pdf 2013-03-28
10 Drawings_Granted 320824_19-09-2019.pdf 2019-09-19
11 2451-CHENP-2013 CORRESPONDENCE OTHERS 28-03-2013.pdf 2013-03-28
11 Marked up Claims_Granted 320824_19-09-2019.pdf 2019-09-19
12 2451-CHENP-2013 CLAIMS 28-03-2013.pdf 2013-03-28
12 Correspondence by Agent _General Power Of Attorney_14-06-2019.pdf 2019-06-14
13 2451-CHENP-2013 ABSTRACT 28-03-2013.pdf 2013-03-28
13 2451-CHENP-2013-ABSTRACT [13-06-2019(online)].pdf 2019-06-13
14 2451-CHENP-2013-CLAIMS [13-06-2019(online)].pdf 2019-06-13
14 2451-CHENP-2013.pdf 2013-04-01
15 2451-CHENP-2013 FORM-3 20-09-2013.pdf 2013-09-20
15 2451-CHENP-2013-COMPLETE SPECIFICATION [13-06-2019(online)].pdf 2019-06-13
16 2451-CHENP-2013 CORRESPONDENCE OTHERS 20-09-2013.pdf 2013-09-20
16 2451-CHENP-2013-DRAWING [13-06-2019(online)].pdf 2019-06-13
17 2451-CHENP-2013-FER_SER_REPLY [13-06-2019(online)].pdf 2019-06-13
17 2451-CHENP-2013 FORM-3 19-11-2013.pdf 2013-11-19
18 2451-CHENP-2013 CORRESPONDENCE OTHERS 19-11-2013.pdf 2013-11-19
18 2451-CHENP-2013-FORM 3 [13-06-2019(online)].pdf 2019-06-13
19 2451-CHENP-2013 FORM-3 06-03-2015.pdf 2015-03-06
19 2451-CHENP-2013-FORM-26 [13-06-2019(online)].pdf 2019-06-13
20 2451-CHENP-2013 CORRESPONDENCE OTHERS 06-03-2015.pdf 2015-03-06
20 2451-CHENP-2013-Information under section 8(2) (MANDATORY) [13-06-2019(online)].pdf 2019-06-13
21 2451-CHENP-2013-FER.pdf 2018-12-20
21 2451-CHENP-2013-OTHERS [13-06-2019(online)].pdf 2019-06-13
22 2451-CHENP-2013-FER.pdf 2018-12-20
22 2451-CHENP-2013-OTHERS [13-06-2019(online)].pdf 2019-06-13
23 2451-CHENP-2013 CORRESPONDENCE OTHERS 06-03-2015.pdf 2015-03-06
23 2451-CHENP-2013-Information under section 8(2) (MANDATORY) [13-06-2019(online)].pdf 2019-06-13
24 2451-CHENP-2013-FORM-26 [13-06-2019(online)].pdf 2019-06-13
24 2451-CHENP-2013 FORM-3 06-03-2015.pdf 2015-03-06
25 2451-CHENP-2013 CORRESPONDENCE OTHERS 19-11-2013.pdf 2013-11-19
25 2451-CHENP-2013-FORM 3 [13-06-2019(online)].pdf 2019-06-13
26 2451-CHENP-2013 FORM-3 19-11-2013.pdf 2013-11-19
26 2451-CHENP-2013-FER_SER_REPLY [13-06-2019(online)].pdf 2019-06-13
27 2451-CHENP-2013 CORRESPONDENCE OTHERS 20-09-2013.pdf 2013-09-20
27 2451-CHENP-2013-DRAWING [13-06-2019(online)].pdf 2019-06-13
28 2451-CHENP-2013 FORM-3 20-09-2013.pdf 2013-09-20
28 2451-CHENP-2013-COMPLETE SPECIFICATION [13-06-2019(online)].pdf 2019-06-13
29 2451-CHENP-2013-CLAIMS [13-06-2019(online)].pdf 2019-06-13
29 2451-CHENP-2013.pdf 2013-04-01
30 2451-CHENP-2013 ABSTRACT 28-03-2013.pdf 2013-03-28
30 2451-CHENP-2013-ABSTRACT [13-06-2019(online)].pdf 2019-06-13
31 2451-CHENP-2013 CLAIMS 28-03-2013.pdf 2013-03-28
31 Correspondence by Agent _General Power Of Attorney_14-06-2019.pdf 2019-06-14
32 2451-CHENP-2013 CORRESPONDENCE OTHERS 28-03-2013.pdf 2013-03-28
32 Marked up Claims_Granted 320824_19-09-2019.pdf 2019-09-19
33 2451-CHENP-2013 DESCRIPTION (COMPLETE) 28-03-2013.pdf 2013-03-28
33 Drawings_Granted 320824_19-09-2019.pdf 2019-09-19
34 2451-CHENP-2013 DRAWINGS 28-03-2013.pdf 2013-03-28
34 Description_Granted 320824_19-09-2019.pdf 2019-09-19
35 2451-CHENP-2013 ENGLISH TRANSLATION 28-03-2013.pdf 2013-03-28
35 Claims_Granted 320824_19-09-2019.pdf 2019-09-19
36 Abstract_Granted 320824_19-09-2019.pdf 2019-09-19
36 2451-CHENP-2013 FORM-1 28-03-2013.pdf 2013-03-28
37 2451-CHENP-2013-PatentCertificate19-09-2019.pdf 2019-09-19
37 2451-CHENP-2013 FORM-18 28-03-2013.pdf 2013-03-28
38 2451-CHENP-2013-IntimationOfGrant19-09-2019.pdf 2019-09-19
38 2451-CHENP-2013 FORM-2 28-03-2013.pdf 2013-03-28
39 2451-CHENP-2013-RELEVANT DOCUMENTS [09-03-2020(online)].pdf 2020-03-09
39 2451-CHENP-2013 FORM-3 28-03-2013.pdf 2013-03-28
40 2451-CHENP-2013-RELEVANT DOCUMENTS [14-08-2021(online)].pdf 2021-08-14
40 2451-CHENP-2013 FORM-5 28-03-2013.pdf 2013-03-28
41 2451-CHENP-2013-RELEVANT DOCUMENTS [15-09-2022(online)].pdf 2022-09-15
41 2451-CHENP-2013 PCT 28-03-2013.pdf 2013-03-28
42 2451-CHENP-2013 POWER OF ATTORNEY 28-03-2013.pdf 2013-03-28
42 2451-CHENP-2013-RELEVANT DOCUMENTS [20-09-2023(online)].pdf 2023-09-20

Search Strategy

1 search_07-12-2018.pdf

ERegister / Renewals

3rd: 04 Oct 2019

From 15/10/2012 - To 15/10/2013

4th: 04 Oct 2019

From 15/10/2013 - To 15/10/2014

5th: 04 Oct 2019

From 15/10/2014 - To 15/10/2015

6th: 04 Oct 2019

From 15/10/2015 - To 15/10/2016

7th: 04 Oct 2019

From 15/10/2016 - To 15/10/2017

8th: 04 Oct 2019

From 15/10/2017 - To 15/10/2018

9th: 04 Oct 2019

From 15/10/2018 - To 15/10/2019

10th: 04 Oct 2019

From 15/10/2019 - To 15/10/2020

11th: 07 Sep 2020

From 15/10/2020 - To 15/10/2021

12th: 06 Sep 2021

From 15/10/2021 - To 15/10/2022

13th: 08 Sep 2022

From 15/10/2022 - To 15/10/2023

14th: 04 Sep 2023

From 15/10/2023 - To 15/10/2024

15th: 05 Sep 2024

From 15/10/2024 - To 15/10/2025

16th: 06 Sep 2025

From 15/10/2025 - To 15/10/2026