Managed device

Abstract

A managed device 1 that is provided in a local area network 4 including an access point accessible by a mobile information terminal 2 includes a server unit 13 running a Web application for displaying a Web page 7 including at least one of a confirmation item 15 and an operation item 16 of the managed device, by using a Web browser 6 of the mobile information terminal, and a read unit 19 including URL information 18 that is generated on the basis of a host name fixedly set in the managed device in advance so as to enable communication using a predetermined protocol which can be searched from a host name 17 in the local area network, and that enables access to the Web page, the read unit 19 also being read by using a reading function of the mobile information terminal.

Description

Managed Device

[0001] The present disclosure relates to managed devices.

[0002] Conventionally, devices to be managed (operated), such as molding machines, molding-related devices around the molding machines, and other machine tools installed in various factories, are each equipped with a display unit, an operation unit, etc. To enable a mobile information terminal such as a smartphone to display items to be checked, such as the operating status of the managed device, and items to be operated, such as various setting operation units, instead of the display unit of such managed devices, it is necessary to grasp and manage identification information, such as the IP address of the managed device, so that it can be connected via a network. For example, Patent Document 1 below discloses a wireless operation system including multiple control controllers that control the operation of multiple electric actuators and a teaching device that wirelessly inputs teaching content related to the operation of each electric actuator to each control controller by operating the operation unit. The control controllers have a pre-set SSID. The teaching device has a built-in access point that can wirelessly communicate with the control controllers and has the same SSID pre-set as the control controllers, and a built-in DHCP server that automatically assigns IP addresses to control controllers located within the wireless communication area. If the response information transmitted from the control controller is a pre-set character string, the teaching device registers the IP address of the control controller as a wireless communication target.

[0003] Japanese Patent Application Laid-Open No. 2022-169262

[0004] However, in the wireless operation system described in Patent Document 1, when an operator operates the operation unit of the teaching device, the operator must select the electric actuator to be operated on the operation unit, which raises concerns that it may be difficult to identify the actual electric actuator.

[0005] The present disclosure has been made in consideration of the above-described situation, and aims to provide a managed device that can display at least one of the items to be confirmed and the items to be operated of the managed device on a mobile information terminal, without requiring the identification information of the managed device to be known or managed, and while making it easy to identify the managed device to be managed.

[0006] In order to achieve the above-mentioned object, configuration 1 of the managed device according to the present disclosure is a managed device provided within a local area network including an access point accessible by a mobile information terminal, and is characterized by comprising: a server unit that operates a web application that displays a web page including at least one of items to be confirmed and items to be operated of the managed device using a web browser of the mobile information terminal; and a readable unit that includes URL information that enables access to the web page and is generated based on a host name that is fixedly set in advance in the managed device so that communication using a predetermined protocol that can be searched from a host name within the local area network is possible, and that is read using the reading function of the mobile information terminal.

[0007] The following embodiments disclose that a managed device according to the present disclosure may include the following subordinate configurations. <Configuration 2> In Configuration 1, the managed device may be connected to a network device that constitutes the access point. <Configuration 3> In Configuration 1, the managed device may constitute the access point. <Configuration 4> In any one of Configurations 1 to 3, the readable unit may be provided so as to be readable on the outer periphery of the managed device. <Configuration 5> In any one of Configurations 1 to 4, the readable unit may be a two-dimensional code. <Configuration 6> In any one of Configurations 1 to 4, the readable unit may be an NFC tag. <Configuration 7> In any one of Configurations 1 to 6, multiple readable units may be provided, each containing URL information that enables access to a different web page. <Configuration 8> In any one of Configurations 1 to 7, the managed device may be a molding-related device installed in association with a molding machine.

[0008] The managed device according to the present disclosure has the above-described configuration, which makes it possible to easily identify the managed device to be managed without having to know or manage the identification information of the managed device, while still being able to display at least one of the items to be confirmed and the items to be operated of the managed device on a mobile information terminal.

[0009] 4A and 4B are schematic system diagrams illustrating an example of a communication system incorporating an example of a managed device according to an embodiment of the present disclosure. (a) is a schematic flowchart illustrating an example of pre-setting items for the managed device, and (b) is a table illustrating an example of setting items for the managed device. (b) is a schematic block diagram of the communication system. (a) is a partially cutaway schematic front view illustrating an example of a read unit provided in the managed device, (b) is a partially cutaway schematic front view illustrating another example of the read unit, and (c) is a schematic front view illustrating an example of a web page displayed on a mobile information terminal. (a) is a partially cutaway schematic front view illustrating a read unit similar to that of FIG. 4A, (b) is a partially cutaway schematic front view illustrating a read unit similar to that of FIG. 4B, and (c) is a schematic front view illustrating another example of a web page displayed on a mobile information terminal. FIG. 10 is a schematic system diagram illustrating an example of a communication system in which an example of a modified example of the same managed device is incorporated.

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In some drawings, some of the detailed reference numerals used in other drawings are omitted. In Figures 1, 3, and 6, electrical connections and communication connections are schematically indicated by solid lines and two-dot chain lines.

[0011] 1 to 6 are schematic diagrams illustrating an example of a managed device according to the present embodiment, a modified example thereof, and an example of a communication system incorporating the same. As shown in FIG. 1 , the managed device 1 according to the present embodiment is provided within a local area network (LAN) 4 including an access point accessible by a mobile information terminal 2. As shown in FIGS. 3 and 4(c), the managed device 1 includes a server unit 13 that runs a web application that displays, using a web browser 6 of the mobile information terminal 2, a web page 7 including at least one of a confirmation target item 15 and an operation target item 16 of the managed device 1. As shown in FIG. 4(a), the managed device 1 includes a readable unit 19 that includes URL (Uniform Resource Locator) information 18 enabling access to the web page 7 and that is read using the reading function of the mobile information terminal 2.

[0012] With the above-described configuration, by reading the readable portion 19 of the managed device 1 using the reading function of the portable information terminal 2, it is possible to view the web page 7 including at least one of the confirmation target items 15 and the operation target items 16 of the managed device 1 on the portable information terminal 2. This web page 7 is displayed by a web application on the server unit 13 provided in the managed device 1, so there is no need to install a dedicated application (app) or the like in advance on the portable information terminal 2. Furthermore, because the readable portion 19 is provided in the managed device 1, it is easy to identify the managed device 1 to be managed (the target of confirmation or operation), and there is no need to select from a list of devices connected to the LAN 4, which makes it possible to prevent misidentification of the managed device 1 that should be managed.

[0013] The URL information 18 included in the readable portion 19 is generated based on a host name 17 that is fixedly set in advance for the managed device 1 so that communication using a predetermined protocol that allows search from the host name 17 (see FIG. 2B) within the LAN 4 is possible. With this configuration, the URL information 18 generated based on the fixed host name 17 is included in the readable portion 19, so the user operating the portable information terminal 2 does not need to know or manage the identification information, such as the IP address, of the managed device 1. Furthermore, for example, if name resolution is performed by a DNS server, complex network settings are required, and if URL information including identification information is assigned after LAN connection, the readable portion needs to be generated, configured, or rewritten after LAN connection. However, this is not necessary. This eliminates the need for complex network settings, for example, when a managed device 1 is newly installed or added to the LAN 4 in a factory, for example, and allows the user to easily browse a web page 7 including at least one of the confirmation target item 15 and the operation target item 16 using the portable information terminal 2 without the need for complex network settings. Furthermore, since it is possible to view the web page 7 including at least one of the items to be confirmed 15 and the items to be operated 16 on the mobile information terminal 2 in this manner, it is also possible to configure the managed device 1 without providing a display unit or the like, or to provide only a simple display function.

[0014] In this embodiment, the managed device 1 is provided with a plurality of readable sections 19a, 19b, each including URL information 18a, 18b that enables access to a different web page 7 (8, 9). This configuration makes it possible to quickly access different web pages, for example, a user web page 8 and an administration web page 9. As will be described in detail later, in this embodiment, the managed device 1 is provided with a user readable section 19a that enables access to the user web page 8 and an administration readable section 19b that enables access to the administration web page 9.

[0015] In the example of FIG. 1 , the managed device 1 is connected to a network device 3 that constitutes an access point. The network device 3, together with the managed device 1 and the mobile information terminal 2, constitutes a LAN 4, and together with these constitutes a communication system. This network device 3 constitutes an access point so that the mobile information terminal 2 can connect to the LAN 4 via wireless LAN. Such network device 3 may be a wireless LAN router having a hub function and an access point function. Such network device 3 may further include an ONU (Optical Network Unit), a modem, etc. The network device 3 is not limited to a configuration that can connect to other networks outside the LAN 4 or the Internet, but may also be a hub or switch having an access point function, or may have various other configurations.

[0016] The network device 3 is provided with multiple connection sections (LAN ports) to which LAN cables or the like connected to the managed device 1 are connected. The example in FIG. 1 shows an example in which multiple (three in the example) managed devices 1 (a first managed device 1A, a second managed device 1B, and a third managed device 1C) are connected to the network device 3. These managed devices 1 have similar configurations, and therefore will be referred to as the managed device 1 below unless distinction is required. The number of managed devices 1 connected to the network device 3 is not limited to three, but may be one, two, or four or more. Furthermore, the managed devices 1 provided within the LAN 4 are not limited to the same type of device and may be various devices. The managed device 1 may also be a molding-related device installed in association with a molding machine. This configuration makes it easy to identify the managed device 1 to be managed in a molding factory where multiple models with similar appearances are often installed. Furthermore, since molding-related devices may be added or replaced relatively frequently within a molding factory, the device 1 is suitable for installation within a molding factory.

[0017] The managed device 1 is a mold temperature control device that circulates a temperature-control medium through a medium flow path of a mold 5 incorporated in a molding machine. As shown in FIG. 3 , this managed device 1 is provided with a temperature control function unit 11 that controls the temperature of the temperature-control medium. Such a temperature control function unit 11 may include a pump disposed in a circulation path connected to the inlet and outlet of the medium flow path of the mold 5 to circulate the temperature-control medium, a temperature sensor that detects the temperature of the mold 5 and the temperature of the temperature-control medium, various sensors that detect the flow rate and pressure of the temperature-control medium, a heat exchanger that controls the temperature-control medium to a preset temperature, and the like. The managed device 1 is not limited to a mold temperature control device equipped with such a temperature control function unit 11, but may also be a device that transports, dries, or blends molding materials, or other molding-related device. Furthermore, the managed device 1 is not limited to molding-related device, but may also be a processing machine installed in various processing factories or other factories, or a device installed in connection with the processing machine, or various other devices.

[0018] The managed device 1 includes a control unit 10 that controls a temperature adjustment function unit 11 and a server unit 13 connected via signal lines or the like, and a storage unit 12 that stores various programs such as control programs, various preset operating conditions, various data tables, and the like, and is configured from various memories such as ROM and RAM. The control unit 10 may be configured to include a control circuit such as a CPU (Central Processing Unit) or an MCU. The managed device 1 includes a communication unit 14 that is connected to the control unit 10 via signal lines or the like and controlled by the control unit 10. The communication unit 14 is connected to a LAN 4 via a network device 3 and has a transmitter and a receiver that enable data transmission and reception between the managed device 1 and the mobile information terminal 2. The communication unit 14 can communicate with the mobile information terminal 2 using a predetermined protocol that enables search using a host name, and has a function of responding to a search using the host name from the mobile information terminal 2. The communication unit 14 may be connected to the network device 3 via a LAN cable or the like. The communication unit 14 may be connected to the network device 3 in accordance with a wired communication standard such as Ethernet (registered trademark). The managed device 1 may be connected to the LAN 4 via a wireless LAN instead of being connected via a wired LAN.

[0019] The server unit 13 has a function of running a web application that causes the mobile information terminal 2 to display a web page 7 using the web browser 6. The server unit 13 is appropriately configured to be able to send and receive files and data that constitute the web page 7 in response to a request from the mobile information terminal 2 via the web browser 6. The files that the server unit 13 sends to the mobile information terminal 2 may be static files stored in the server unit 13, or dynamic files that the server unit 13 generates in response to a request from the mobile information terminal 2. In this embodiment, the server unit 13 stores, as files that constitute the web page 7, an index.html file that constitutes the user web page 8 and an admin.html file that constitutes the management web page 9 (see FIGS. 4(c) and 5(c)). The server unit 13 may also store HTML files that constitute other web pages 7, as well as other files that constitute the web page 7, such as CSS files and JavaScript (registered trademark) files.

[0020] The confirmation items 15 displayed on the web page 7 may be various items necessary for managing the managed device 1, such as the operating status of the managed device 1, including the ON (operating) / OFF (stopped) state, measurements and settings from various sensors, etc. Such confirmation items 15 may include dynamic data. In this case, the server unit 13 may transmit the dynamic data to the mobile information terminal 2 periodically, whenever the dynamic data changes, or in response to an update operation on the mobile information terminal 2. In the example of FIG. 4( c), the user web page 8 displays, as confirmation items 15, the measured temperature and operating status of the mold 5, the presence or absence of an alarm indicating an abnormality, the output of the heating unit (heater) constituting the heat exchanger, the flow rate and pressure of the temperature control medium, the time required to reach the set temperature, etc. These may be data acquired by the temperature adjustment function unit 11, or may be data calculated based on the acquired data. The items to be confirmed 15 are not limited to the dynamic data described above, but may be data stored in advance in the storage unit 12, or other items appropriate depending on the functions of the managed device 1, etc.

[0021] The operation target items 16 displayed on the web page 7 may be various items necessary for managing the managed device 1, such as the ON (operating) / OFF (stopped) status of the managed device 1, various setting values, and information required for login authentication. Such operation target items 16 may be input and operated on the web browser 6 of the mobile information terminal 2. In a web application run by the server unit 13, when the operation target items 16 are input and operated on the web browser 6 of the mobile information terminal 2, corresponding operations are performed on the managed device 1 side. The example of FIG. 4( c) shows an example in which a target set temperature change operation section for the mold 5, an ON (operating) operation section, an OFF (stop) operation section, and the like are displayed as operation target items 16 on the user web page 8. The target set temperature is displayed as the temperature that has been changed, and is also a confirmation target item 15.

[0022] 5(c) shows an example in which the management web page 9 displays, as operation target items 16, an input form for a login ID and password constituting information required for login authentication of a user (administrator) and a login button. The operation target items 16 are not limited to the items exemplified in FIGS. 4(c) and 5(c) and may be other appropriate items depending on the functions of the managed device 1. Furthermore, the confirmation target items 15 and operation target items 16 are not limited to being displayed on a single web page 7 as shown in FIGS. 4(c) and 5(c). For example, all or some of the confirmation target items 15 and operation target items 16 may be switched and displayed by moving to another page. Furthermore, as in the example of FIG. 1, when multiple managed devices 1 are provided within the LAN 4, it may be possible to display web pages 7 including the confirmation target items 15 and operation target items 16 of each of the multiple managed devices 1. In this case, it may be possible to use the tab function of the web browser 6 of the mobile information terminal 2 to switch and display web pages 7 containing items 15 to be confirmed and items 16 to be operated for each managed device 1 on each tab (web page 7).

[0023] If the managed device 1 is provided with an operation display unit, all or some of the confirmation target items 15 and operation target items 16 described above may also be displayed on the operation display unit of the managed device 1. In this case, when input or operation is performed on the operation display unit of the managed device 1, the target temperature setting and the like on the user web page 8 will also be changed. Furthermore, when input or operation is performed on the user web page 8 displayed on the web browser 6 of the mobile information terminal 2, the target temperature setting and the like on the operation display unit of the managed device 1 will also be changed. Furthermore, if the web browser 6 of the mobile information terminal 2 is capable of displaying web pages 7 including confirmation target items 15 and operation target items 16 for multiple managed devices 1 as described above, a notification may be sent to the managed device 1 displayed as a managed device in the web browser 6 of the mobile information terminal 2 to facilitate identification. For example, confirmation data or the like may be sent from the mobile information terminal 2 to the managed device 1, and the display unit or the like of the managed device 1 may light up or blink in an appropriate manner, or specific numbers or the like sent from the mobile information terminal 2 may be displayed.

[0024] The readable portion 19 is provided on the outer periphery of the managed device 1 so as to be readable (see FIG. 1 ). This configuration allows the readable portion 19 to be easily read using the mobile information terminal 2. The readable portion 19 may be provided in the managed device 1 in advance, such as before shipping or installation of the managed device 1, as follows. For example, as shown in FIGS. 2( a) and 2(b), first, a host name 17 is set in the managed device 1 (step S100). This host name 17 may be set so as not to overlap with the host names 17 of other managed devices 1 within the same LAN 4. Preferably, the host name 17 may be set specifically for each managed device 1. For example, the host name 17 may include a model and serial number uniquely determined for each managed device 1 by the manufacturer of the managed device 1. With this configuration, no matter which LAN 4 the managed device 1 is installed in, or when the managed device 1 is added or replaced to the LAN 4, there is no concern that the host name 17 will overlap with the host name 17 of another managed device 1. Information including such host names 17 is stored in the managed device 1 so as to enable communication using a predetermined protocol, which will be described later. In the illustrated example, the host name 17 of the first managed device 1A is "XXX_123", the host name 17 of the second managed device 1B is "XXX_456", and the host name 17 of the third managed device 1C is "XXX_789".

[0025] Next, URL information 18 is generated based on the host name 17 set as described above (step S101). This URL information 18 is generated so as to enable communication using a predetermined protocol that enables search from the host name 17 within the LAN 4. This predetermined protocol may be mDNS (multicast domain name system). The managed device 1 and the mobile information terminal 2 are configured to support search protocols such as mDNS. According to the mDNS protocol, if the inquiring device (mobile information terminal 2) multicasts information including the host name 17 within the LAN 4, a device (managed device 1) matching the host name 17 will respond with information including its IP address, enabling two-way communication. For example, in mDNS, if the top-level domain is "local" and search is performed from the host name 17, the domain name included in the URL information 18 may be "local," as described below. Furthermore, the IP address may be automatically assigned by an appropriate Dynamic Host Configuration Protocol (DHCP) server provided in the LAN 4 or a DHCP function provided in the network device 3. The mDNS may be an application such as Bonjour (registered trademark) or Avahi, and the predetermined protocol is not limited to mDNS and may be another protocol such as Link-local Multicast Name Resolution (LLMNR).

[0026] 2B shows an example in which the generated URL information 18 is expressed using elements such as a scheme name (http:) representing the communication protocol, a host name (each of the host names 17 described above), a domain name (local), and a directory and file name (index.html or admin.html). The communication protocol is not limited to HTTP, and HTTPS may also be used. More specifically, the example shows an example in which the user URL information 18a of the first managed device 1A is "http: / / XXX_123.local / index.html" and the management URL information 18b of the first managed device 1A is "http: / / XXX_123.local / admin.html." In addition, an example is shown in which the user URL information 18a of the second managed device 1B is "http: / / XXX_456.local / index.html" and the administration URL information 18b of the second managed device 1B is "http: / / XXX_456.local / admin.html". In addition, an example is shown in which the user URL information 18a of the third managed device 1C is "http: / / XXX_789.local / index.html" and the administration URL information 18b of the third managed device 1C is "http: / / XXX_789.local / admin.html".

[0027] Next, the readable part 19 including the URL information 18 generated as described above is added to the managed device 1 (step S102). The readable part 19 may be a two-dimensional code 19A, as shown in Figures 4(a) and 5(a). With this configuration, the two-dimensional code 19A can be easily read using an app pre-installed on the mobile information terminal 2 or a general-purpose app, eliminating the need for a dedicated reading application or the like.

[0028] Specifically, the two-dimensional code 19A constituting the readable portion 19 may be provided on one side or the like constituting the outer peripheral surface of the housing (casing) of the managed device 1, as shown in FIG. 4( a) and FIG. 5( a) show an example in which the multiple readable portions 19a, 19b are provided with a user two-dimensional code 19Aa including user URL information 18a enabling access to the user web page 8 and a management two-dimensional code 19Ab including management URL information 18b enabling access to the management web page 9. In the illustrated example, the user two-dimensional code 19Aa and the management two-dimensional code 19Ab are provided in relatively close proximity to each other, but they may also be provided in distant locations. For example, the user two-dimensional code 19Aa may be provided in a conspicuous location, and the management two-dimensional code 19Ab may be provided in a less conspicuous location. In this case, the two-dimensional management code 19Ab may be provided at an appropriate location such as inside a maintenance door, instead of at a readable position on the outer periphery of the device 1 to be managed.

[0029] Furthermore, to enable the user two-dimensional code 19Aa and the management two-dimensional code 19Ab to be recognized as being for the user and the management, the words "For User Use" and "For Management Use" are written around each code (on the top in the illustrated example). These characters and the user two-dimensional code 19Aa and the management two-dimensional code 19Ab may be printed directly on the outer surface of the housing of the managed device 1, or may be printed on a sticker (label) or the like attached to the outer surface of the housing of the managed device 1. The user two-dimensional code 19Aa and the management two-dimensional code 19Ab may be in any form as long as the user URL information 18a and the management URL information 18b contained therein can be read by the mobile information terminal 2. In the illustrated example, a QR Code (registered trademark) is used as an example. The user two-dimensional code 19Aa and the management two-dimensional code 19Ab containing the user URL information 18a and the management URL information 18b may be created using an appropriate general-purpose two-dimensional code creation application or the like.

[0030] Instead of the above-described embodiment, the readable portion 19 may be an NFC (Near Field Communication) tag 19B, as shown in FIGS. 4(b) and 5(b). With such a configuration, the NFC tag 19B can be easily read using an NFC tag reader constituting the reading portion 21 pre-installed in the portable information terminal 2, eliminating the need for a dedicated reader. Furthermore, compared to a configuration in which the readable portion 19 is a two-dimensional code 19A, the NFC tag 19B constituting the readable portion 19 is less susceptible to contamination by dust and the like. As described above, the NFC tag 19B constituting the readable portion 19 may be provided on one side constituting the outer circumferential surface of the housing of the managed device 1. 4(b) and 5(b) show an example in which a user NFC tag 19Ba including user URL information 18a and a management NFC tag 19Bb including management URL information 18b are provided as the multiple readable portions 19a, 19b, as in the above. In the examples shown, the user NFC tag 19Ba and the management NFC tag 19Bb are provided in relatively close proximity to each other, as in the above, but they may also be provided in distant positions.

[0031] The illustrated example shows an example in which each of the user NFC tag 19Ba and the management NFC tag 19Bb is provided with a picture (pictogram) as a marker for bringing the mobile information terminal 2 close. Similarly to the above, the words "for user" and "for management" are written around the user NFC tag 19Ba and the management NFC tag 19Bb (on the upper side in the illustrated example) so that it can be recognized that the user NFC tag 19Ba and the management NFC tag 19Bb are for the user and the management, respectively. Similarly to the above, these words and pictures may be printed directly on the outer circumferential surface of the housing of the managed device 1, or may be printed on a sticker (label) or the like attached to the outer circumferential surface of the housing of the managed device 1. The user NFC tag 19Ba and the management NFC tag 19Bb may be embedded in a sticker (label) or the like and attached to the outer circumferential surface or inner circumferential surface of the housing of the managed device 1. The user URL information 18a and the management URL information 18b may be written in the user NFC tag 19Ba and the management NFC tag 19Bb using an appropriate general-purpose NFC tag writing application, etc. The readable part 19 added to the management target device 1 is not limited to the above-mentioned two-dimensional code 19A and NFC tag 19B, and may be any other readable part as long as it is configured to be readable using the reading function of the portable information terminal 2.

[0032] The portable information terminal 2 may be any computer that can be carried by the user, such as a smartphone, tablet terminal, or laptop computer. As shown in FIG. 3 , the portable information terminal 2 is provided with a reading unit 21 capable of reading the readable unit 19 provided in the managed device 1. Such a reading unit 21 may have a reading function appropriate for the readable unit 19. If the readable unit 19 is a two-dimensional code 19A, the reading unit 21 may be a camera or a general-purpose two-dimensional code reader that is standardly installed in the portable information terminal 2. If the readable unit 19 is an NFC tag 19B, the reading unit 21 may be an NFC tag reader that is standardly installed in the portable information terminal 2. The portable information terminal 2 is provided with an operation display unit 22 that displays and operates the web page 7. Such an operation display unit 22 may be a touch panel such as a capacitive type that is integrated with a display, or may be configured such that the operation unit and the display unit are separate devices, and may be composed of, for example, an input device such as a mouse and keyboard and a display.

[0033] The portable information terminal 2 is provided with a communication unit 23 that is wirelessly connected to the LAN 4 via an access point of the network device 3 and has a transmitter and a receiver that enable data transmission and reception between the portable information terminal 2 and the managed device 1. The communication unit 23 is capable of communicating with the managed device 1 using a predetermined protocol that enables searching using the host name 17 described above, and has the function of searching for and communicating with a managed device 1 having a specific host name 17 on the LAN 4. The communication unit 23 may be connected to the network device 3 in accordance with a wireless communication standard such as Wi-Fi. The portable information terminal 2 is provided with a control unit 20 that controls the reading unit 21, operation display unit 22, and communication unit 23 described above. Like the control unit 10 of the managed device 1, the control unit 20 is composed of a control circuit such as a CPU (Central Processing Unit) and a microcomputer (MCU) including various memories such as ROM and RAM, and is connected to each component of the portable information terminal 2 via signal lines, etc.

[0034] In the above-described communication system, when the readable portion 19 provided on the managed device 1 is read using the reading unit 21 of the portable information terminal 2, information including the host name 17 is multicast based on the URL information 18 in accordance with the predetermined protocol described above. The managed device 1 that matches this host name 17 responds with information including its IP address, enabling two-way communication. The web browser 6 is launched on the operation / display unit 22 of the portable information terminal 2, and a web page 7 is displayed based on data such as files transmitted from the server unit 13 of the managed device 1, allowing the user to confirm and operate the confirmation target item 15 and the operation target item 16 of the corresponding managed device 1. For example, as shown in FIGS. 4( a) and 4(b), when the user readable portion 19a (user two-dimensional code 19Aa or user NFC tag 19Ba) is read using the reading unit 21 of the portable information terminal 2, a user web page 8 is displayed on the web browser 6 as shown in FIG. 4(c). Also, for example, as shown in Figures 5(a) and (b), if the management readable portion 19b (the management two-dimensional code 19Ab or the management NFC tag 19Bb) is read using the reading unit 21 of the mobile information terminal 2, the management web page 9 will be displayed on the web browser 6 as shown in Figure 5(c).

[0035] The URL information 18 of the managed device 1 read using the reading unit 21 of the portable information terminal 2 may be stored on the portable information terminal 2 side. With this configuration, it is not necessary to use the reading unit 21 of the portable information terminal 2 to read the readable unit 19 provided on the managed device 1 each time the web page 7 is accessed. In this case, the URL information 18 of the managed device 1 may be registered using a bookmark function or the like of the web browser 6 of the portable information terminal 2. This allows for easy access to the web page 7 of the managed device 1. The web page 7 is not limited to the user web page 8 or management web page 9 described above, and various other web pages 7 may also be used. Furthermore, although the above example shows an example in which both the confirmation target item 15 and the operation target item 16 or the operation target item 16 are displayed on the web page 7, only the confirmation target item 15 may be displayed. Furthermore, in the above example, the managed device 1 is shown to have two readable parts 19a and 19b, but it may also be configured to have three or more readable parts, or to have one readable part.

[0036] Next, modified examples of the managed device will be described with reference to Fig. 6. In the following modified examples, differences from the previously described example will be mainly described, and explanations of similar configurations will be omitted or briefly explained. In addition, in the following modified examples, explanations of the same operational effects as those of the previously described example will be omitted or briefly explained.

[0037] In this modified example, the managed device 1 (1B) constitutes an access point (3A). With this configuration, there is no need to separately install a network device 3 constituting the access point, and a LAN 4A can be constructed using the managed device 1 (1B). As in the example described above, the illustrated example shows an example in which a wireless LAN adapter 3A constituting an access point is provided in one of the multiple managed devices 1, 1, 1 provided in the LAN 4A (in the example, the second managed device 1B). This wireless LAN adapter 3A may have a hub function and an access point function, like the network device 3 described above, and may be configured to be connectable to other networks outside the LAN 4A or the Internet, or may have various other configurations. Furthermore, the illustrated example shows an example in which, of the multiple managed devices 1, 1, 1, the second managed device 1B to which the wireless LAN adapter 3A is connected is connected to the other managed devices 1, 1 via a LAN cable or the like.

[0038] In the above examples, a molding machine or processing machine having a display capable of launching an appropriate web browser may be connected to the network device 3 or the wireless LAN adapter 3A via a LAN cable or the like. In this case, the URL information 18 read using the portable information terminal 2 may be input or transmitted to the molding machine or processing machine, and the web page 7 may be displayed on the display of the molding machine or processing machine. This configuration allows centralized management of the managed device 1 in the molding machine or processing machine. The configuration of the managed device 1 and the components and parts constituting the communication system including the managed device 1 described above is merely an example, and various other modifications are possible.

[0039] REFERENCE SIGNS LIST 1 Managed device 13 Server unit 15 Confirmation target item 16 Operation target item 17 Host name 18 URL information 19 Read target unit 19A Two-dimensional code 19B NFC tag 2 Portable information terminal 3 Network device (access point) 3A Wireless LAN adapter (access point) 4, 4A LAN (local area network) 6 Web browser 7 Web page

Claims

1. A managed device provided within a local area network including an access point accessible by a mobile information terminal, comprising: a server section that runs a web application that uses the web browser of the mobile information terminal to display a web page including at least one of the items to be confirmed and items to be operated of the managed device; and a readable section that includes URL information that enables access to the web page and is generated based on a host name that is fixedly set in the managed device in advance so that communication using a predetermined protocol that can be searched from the host name within the local area network is possible, and that can be read using the reading function of the mobile information terminal.

2. A managed device according to claim 1, which is connected to a network device constituting said access point.

3. A managed device according to claim 1, which constitutes the access point.

4. A managed device according to any one of claims 1 to 3, characterized in that the readable portion is provided so as to be readable on the outer periphery side of the managed device.

5. The managed device according to any one of claims 1 to 4, wherein the readable portion is a two-dimensional code.

6. The managed device according to any one of claims 1 to 4, wherein the readable part is an NFC tag.

7. A managed device according to any one of claims 1 to 6, characterized in that a plurality of said readable parts are provided, each of said readable parts including URL information enabling access to a different Web page.

8. A management device according to any one of claims 1 to 7, characterized in that the management device is a molding-related device installed in association with a molding machine.

Images