{"id":3218,"date":"2026-11-17T18:38:34","date_gmt":"2026-11-17T10:38:34","guid":{"rendered":"https:\/\/resource.fatek.com\/index.php\/2026\/11\/17\/mplc-m03-en-11\/"},"modified":"2026-11-17T18:38:34","modified_gmt":"2026-11-17T10:38:34","slug":"mplc-m03-en-11","status":"publish","type":"post","link":"https:\/\/resource.fatek.com\/index.php\/2026\/11\/17\/mplc-m03-en-11\/","title":{"rendered":"Chapter 11 Ethernet Function and Ethernet Communication"},"content":{"rendered":"<h3>11-1  Setting the Network Interface<\/h3>\n<p><strong>Default parameter of network interface<\/strong><\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Address<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Content<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>IP Address<\/p>\n<\/td>\n<td>\n<p>192.168.2.4<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>Sub-net Mask<\/p>\n<\/td>\n<td>\n<p>255.255.255.0<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>Gateway Preset<\/p>\n<\/td>\n<td>\n<p>192.168.2.1<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>DNS Primary Address<\/p>\n<\/td>\n<td>\n<p>1.1.1.1<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>DNSS Secondary Address<\/p>\n<\/td>\n<td>\n<p>8.8.8.8<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p><strong>Setting network interface through software: <\/strong><\/p>\n<ol>\n<li>Open UperLogic software and then set up the connection between PC and PLC. Click \u201cConnection Parameter\u201d in PLC tag.<\/li>\n<li><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\63.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-001.png\" \/><\/li>\n<\/ol>\n<p>Figure 63 \u201cConnection Parameter\u201d under PLC tag<\/p>\n<ol>\n<li>Select the USB type that will be connected.<\/li>\n<li>Connection test: Check if the connection is normal while displaying the required information such as the connected model and firmware version, etc.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\64.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-002.png\" \/><\/p>\n<p>Figure 64 Connection Parameter<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\65.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-003.png\" \/><\/p>\n<p>Figure 65 Connection Test<\/p>\n<ol>\n<li>Click \u201cEthernet Configuration\u201d and the Ethernet setup window will appear. At this time, you may start setting the PLC IP address, sub-net mask, gateway preset and DNS service as well as selecting the need of using the DHCP function. You also can set up the primary and secondary ports of FATEK and Modbus TCP communication protocols.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\67.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-004.png\" \/><\/p>\n<p>Figure 66 Setting of Ethernet<\/p>\n<p>6.  Click \u201cOK\u201d and then the system will start writing in the PLC.<\/p>\n<p>The network interface setting through the registers:<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Special Register No.<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35382<\/p>\n<\/td>\n<td>\n<p>CPU Unit IP address OCT1 (Leading)<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35383<\/p>\n<\/td>\n<td>\n<p>CPU Unit IP address OCT2<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35384<\/p>\n<\/td>\n<td>\n<p>CPU Unit IP address OCT3<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35385<\/p>\n<\/td>\n<td>\n<p>CPU Unit IP address OCT4<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35386<\/p>\n<\/td>\n<td>\n<p>CPU Unit Sub-net Mask OCT1 (Leading)<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35387<\/p>\n<\/td>\n<td>\n<p>CPU Unit Sub-net Mask OCT2<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35388<\/p>\n<\/td>\n<td>\n<p>CPU Unit Sub-net Mask OCT3<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35389<\/p>\n<\/td>\n<td>\n<p>CPU Unit Sub-net Mask OCT4<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35390<\/p>\n<\/td>\n<td>\n<p>CPU Unit Gateway OCT1 (Leading)<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35391<\/p>\n<\/td>\n<td>\n<p>CPU Unit Gateway OCT2<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35392<\/p>\n<\/td>\n<td>\n<p>CPU Unit Gateway OCT3<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35393<\/p>\n<\/td>\n<td>\n<p>CPU Unit Gateway OCT4<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35394<\/p>\n<\/td>\n<td>\n<p>CPU Unit Primary DNS Server OCT1 (Leading)<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35395<\/p>\n<\/td>\n<td>\n<p>CPU Unit Primary DNS Server OCT2<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35396<\/p>\n<\/td>\n<td>\n<p>CPU Unit Primary DNS Server OCT3<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35397<\/p>\n<\/td>\n<td>\n<p>CPU Unit Primary DNS Server OCT4<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35398<\/p>\n<\/td>\n<td>\n<p>CPU Unit Secondary DNS Server OCT1 (Leading)<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35399<\/p>\n<\/td>\n<td>\n<p>CPU Unit Secondary DNS Server OCT2<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35400<\/p>\n<\/td>\n<td>\n<p>CPU Unit Secondary DNS Server OCT3<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35401<\/p>\n<\/td>\n<td>\n<p>CPU Unit Secondary DNS Server OCT4<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Special Contact No.<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>M9164<\/p>\n<\/td>\n<td>\n<p>Network interface restarting<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>M9165<\/p>\n<\/td>\n<td>\n<p>DHCP enable<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Special Register No.<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35481<\/p>\n<\/td>\n<td>\n<p>FATEK M1 Communication Protocols Port<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>R35482<\/p>\n<\/td>\n<td>\n<p>Modbus TCP Communication Protocols Port<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>When using the register to set up the Ethernet IP address, please execute the following procedure:<\/p>\n<p>To set the IP address of the PLC as \u201c192.168.0.152\u201d:<\/p>\n<ol>\n<li>If the IP address of the original Ethernet of the CPU Unit is \u201c192.168.0.150\u201d, check the value of special registers R35382\u2013R35385 on the monitoring page, i.e., R35382=192, R35383=168, R35384=0 and R35385=150, as per below.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\70.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-005.png\" \/><\/p>\n<p>Figure 70 Values of R25382~R35383 special registers on status page<\/p>\n<ol>\n<li>Change the values of R35382\u2013R35385 special registers as follows: <\/li>\n<\/ol>\n<p>R35382=192, R35383=18, R35384=0 and R35385=152, as per the figure below.<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\71.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-006.png\" \/><\/p>\n<p>Figure 71 Modifying values of R25382~R35383 special registers<\/p>\n<ol>\n<li>Run M9164 for one pulse and then write the value of special register on Ethernet in the PLC in order to establish the changed IP address. At this time, you have completed the setting of Ethernet IP address for M-PLC with the register.<\/li>\n<li>Note: M9164 is designed in resetting type. After being set as \u201cON\u201d, it will be restored automatically.<\/li>\n<\/ol>\n<h3>11-2  FATEK Searching Protocols<\/h3>\n<p>When there is more than one CPU Unit in the same network domain, users need a method to make it easier to maintain on CPU Units with different purposes. This is the purpose of the FATEK Searching Protocols. You can use the software to search for CPU Units in the current domain, obtain the main information of each CPU Unit, and directly connect to the target CPU Unit. <\/p>\n<p><strong>Execute the function of searching on network through software:<\/strong><\/p>\n<ol>\n<li>Open UperLogic and then click \u201cConnection Parameter\u201d in PLC tag.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\72.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-007.png\" \/><\/p>\n<p>Figure 72 \u201cConnection Parameter\u201d in PLC tag<\/p>\n<ol>\n<li>Click \u201cEthernet\u201d in \u201cConnection Parameter\u201d.<\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-008.png\" \/><\/p>\n<p>Figure 73 Click \u201cEthernet\u201d<\/p>\n<ol>\n<li>Click \u201cSearch\u201d.<\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-009.png\" \/><\/p>\n<p>Figure 74 Network searching<\/p>\n<ol>\n<li>Click \u201cScan\u201d, and the CPU Units in the same domain that support the FATEK searching protocol will appear, and their IP (name), MAC address, and mode information will be displayed.<\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-010.png\" \/><\/p>\n<p>Figure 75 Click \u201cScan\u201d<\/p>\n<ol>\n<li>To connect with the PLC of other unit, click the PLC of that unit and then press \u201cOK\u201d and the connection parameter will be set as the IP address of the respective PLC automatically.<\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-011.png\" \/><\/p>\n<p>Figure 77 CPU Unit connection<\/p>\n<h3>11-3  NTP Time Synchronization<\/h3>\n<p>The purpose of NTP time synchronization function is to avoid the trouble of manual time calibration regularly for the PLC to execute the time synchronization through the network and the appointed server in order to achieve more efficient time calibration and synchronization for the equipment.<\/p>\n<p><strong>Setting and description of NTP time synchronization function:<\/strong><\/p>\n<ol>\n<li>Open UperLogic and click the \u201cServer Configuration\u201d in \u201cProject\u201d tag or click \u201cServer Configuration\u201d in \u201cProject management\u201d.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\78.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-012.png\" \/><\/p>\n<p>Figure 78 Click \u201cServer Configuration\u201d in \u201cProject\u201d.<\/p>\n<ol>\n<li>After that, the system will show the \u201cServer Configuration\u201d dialogue window as per below:<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\79.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-013.png\" \/><\/p>\n<p>Figure 79 Server setting<\/p>\n<ol>\n<li>Click the left-side \u201cNTP\u201d function option and the right-side is the function setting.<\/li>\n<li>Select the \u201cNTP Enabled\u201d option as \u201cEnable\u201d and then set \u201cSync Interval\u201d, \u201cTimezone\u201d and \u201cNTP URL\u201d. Finally, download the project to PLC to complete the setting process.<\/li>\n<li>If the PLC network maintains normal communication after downloading the project to PLC, the system will execute the first round of time synchronization and then follow the programmed synchronization interval. If the PLC network is operating unstably from the very beginning, then it will execute the synchronization during the next round of synchronization interval.<\/li>\n<\/ol>\n<div class=\"fatek-tw\">\n<table>\n<thead>\n<tr>\n<th>\n<p>Option<\/p>\n<\/th>\n<th>\n<p>Description<\/p>\n<\/th>\n<\/tr>\n<tr>\n<th>\n<p>NTP Enabled<\/p>\n<\/th>\n<th>\n<p>Click the NTP time synchronization function to see if it is enabled. <\/p>\n<\/th>\n<\/tr>\n<tr>\n<th>\n<p>Sync Interval<\/p>\n<\/th>\n<th>\n<p>To set the synchronous time; the unit will be expressed in minutes.<\/p>\n<\/th>\n<\/tr>\n<tr>\n<th>\n<p>Timezone<\/p>\n<\/th>\n<th>\n<p>Set according to the time zone where the application is located. The example shown is Taipei GMT+08:00 and it means that the time zone in Taipei will be GMT+8 hours.<\/p>\n<\/th>\n<\/tr>\n<tr>\n<th>\n<p>NTP URL<\/p>\n<\/th>\n<th>\n<p>The website where the network time-setting server (NTP server) is installed.<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n<\/table>\n<\/div>\n<p>Table 22 Description table of NTP setting options<\/p>\n<h3>11-4  Publishing\/ Subscribing MQTT<\/h3>\n<p>The MQTT serves a kind of communication protocol designed for the IoT. Being simple and compact, it is suitable for applying in an environment where the hardware resources and the network bandwidth are restricted in order to satisfy the remote monitoring and data swapping demands.<\/p>\n<p>The message transmission mechanism is designed in publishing\/subscribing mode. Each individual message should be assigned with a subject name for easier identification such as temperature. The Client end is acting the publisher and subscriber role in which, the Publisher is liable for publishing the subject-affixed message and the Subscriber is playing the role of subscribing the subject. The server end serves as a Broker to receive the message from the Publisher and then transfer to the Subscriber asking for the subject.<\/p>\n<p>The MQTT function triggered by the M-Series CPU Units can play the aforesaid 3 roles concurrently, i.e., Publisher, Subscriber and Broker. Through MQTT function, M-Series CPU Units will be allowed to publish the register address of the device (HMI, PLC) to the Broker on the network; in the meantime, it also connects the subject data to be subscribed by the Broker and then read and write such data in the register address. Further, the M SERIES PLC can also use the built-in Broker directly without the need of searching for another Broker tool. <\/p>\n<p>This chapter will describe the MQTT related pages and setting method.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-014.jpg\" \/><\/p>\n<p>Figure 80 Schematic diagram of MQTT application<\/p>\n<h5><strong>11-4-1 Server configuration                                                         <\/strong><\/h5>\n<p>To use the MQTT function, click \u201cMQTT\u201d from the \u201cServer Configuration\u201d window in the left-side \u201cProject\u201d and you will be allowed to access the setup page. The \u201cServer\u201d page can be used to set the MQTT Server (Broker), as per the figure below:<\/p>\n<p> <img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\81.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-015.png\" \/><\/p>\n<p>Figure 81 Setting window of MQTT Server<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Column<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010Set MQTT server\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Enable\/ Disable\u3011<\/p>\n<p>For selecting to see if to enable \u201cMQTT\u201d and it is serving as the main switch of the \u201cMQTT\u201d function. After being enabled, you will be allowed to set the detail column and use the desired \u201cSubject publishing\u201d and \u201cSubject subscribing\u201d pages.<\/p>\n<p>\u3010Host (IP or domain name)\u3011<\/p>\n<p>To set the Broker host address, you may log in the IP or domain name and then it will be preset as \u201c127.0.01\u201d.<\/p>\n<p>\u3010Port No.\u3011<\/p>\n<p>To set the Broker connection port. Preset as \u201c1883\u201d.<\/p>\n<p>\u3010Client ID\u3011<\/p>\n<p>The ID specially owned by the Client. It can be set privately and you may use special code bearing \u201c%\u201d prefix to combine them into unique ID:<\/p>\n<p>%1: HMI name<\/p>\n<p>%2: Random code<\/p>\n<p>\uff05\uff05: Bit %<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010ID verify\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Enable\/Disable\u3011<\/p>\n<p>For selecting to see if MOTT Broker ID should be used.<\/p>\n<p>The Broker to be connected has been set with an ID. You may input the following items here:<\/p>\n<p>\u3010User name\u3011<\/p>\n<p>Input the username appointed by the Broker.<\/p>\n<p>\u3010Password\u3011<\/p>\n<p>Input the password appointed by the Broker. After that, it will be protected with the encryption code.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010TLS\/SSL\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Enable\/Disable\u3011<\/p>\n<p>For selecting to see if the TLS\/SSL function of MQTT should be used<\/p>\n<p>\u3010Certification Mode\u3011<\/p>\n<p>For selecting to see if it belongs to one-way verification or two-way verification function.<\/p>\n<p>The Broker to be connected has been set with TLS\/SSL encrypted message transmission function. You may import the certification file here.<\/p>\n<p>\u3010Select server certificate\u3011<\/p>\n<p>When using server certification method, \u201cimport\u201d the required certificate.<\/p>\n<p>\u3010Select Client certificate\u3011<\/p>\n<p>Use the Client certification method in order to \u201cimport\u201d the required certificate.<\/p>\n<p>\u3010Select private key\u3011<\/p>\n<p>For selecting the private key to be used.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Table 23: Properties for setting MQTT Server page<\/p>\n<h4>11-4-2 Topic Publish                                                          <\/h4>\n<p>To use the MQTT function, click \u201cMQTT\u201d from the \u201cServer Configuration\u201d window in the left-side \u201cProject\u201d and then select \u201cEnable\u201d to show the \u201cTopic Publish\u201d. Next, click the upper-left \u201cAdd\u201d button to add a new subject. By clicking \u201cDelete\u201d button, you may delete the selected subject. By clicking \u201cEdit\u201d or double clicking the item in the Topic List, you may edit the selected topic. If the Topic List contains the existing items, you may click \u201cExport\u201d and all of the topic data will be exported for creating the specific-format CSC file. By clicking the \u201cImport\u201d button, you may import the specific-format CSC file for updating the topic table. In Topic List, the left-side of each topic is provided an exclusive ID and it will be used as the topic ID.<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\82.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-016.png\" \/><\/p>\n<p>Figure 82 Topic setting of publishing MQTT topics<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\83.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-017.png\" \/><\/p>\n<p>Figure 83 Topic publish of MQTT<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Column<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010Basic\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Name\u3011<\/p>\n<p>For setting the topic name and it can be used to describe the name.<\/p>\n<p>\u3010Topic\u3011<\/p>\n<p>The topic when MQTT is transmitting the message.<\/p>\n<p> (Notice: \u201c#\u201d and \u201c+\u201d are wildcard characters and they should not be used). <\/p>\n<p>\u3010Transmission Mode\u3011<\/p>\n<p>a. \u3010Cyclic\u3011<\/p>\n<p>Transmitting the message periodically and it can be used to set the interval second duration.<\/p>\n<p>b. \u3010Value change trigger\u3011<\/p>\n<p>The system will transmit the message when the value of the figure data item has changed.<\/p>\n<p>\u3010Retain message\u3011<\/p>\n<p>For determining if the MQTT message should be retained in the server. If selecting this item, the server will preserve such subject message. If a new subscriber is required or when the interrupted subscriber should be reconnected, then they will receive the latest message being retained.<\/p>\n<p>\u3010QoS\u3011<\/p>\n<p>For setting the Quality of Service of MQTT, and it comprises the following 3 classes:<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Class<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>0<\/p>\n<\/td>\n<td>\n<p>Message transmitted once only. Message serving not guaranteed. Message will not be repeated.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Message will be served at least once. Message serving guaranteed. Message may be repeated.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\uff12<\/p>\n<\/td>\n<td>\n<p>Message will be served just once. Message serving guaranteed. Message will not be repeated.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>\u3010Data format\u3011<\/p>\n<p>The message content of each individual subject is composed of the address values of the figure data item, as per below:<\/p>\n<p>\u3010Raw Data\u3011<\/p>\n<p>01 2a 03 b8 1e e5 3f 6c 6f 76 65<\/p>\n<p>Note: <\/p>\n<p>\u3010JSON\u3011<\/p>\n<p>{ <\/p>\n<p>     &quot;d&quot;: {<\/p>\n<p>     &quot;DataItem0&quot;: [true, true],<\/p>\n<p>     &quot;DataItem1&quot;: [810, 793, 688],<\/p>\n<p>     &quot;DataItem2&quot;: [1.789, 3.51],<\/p>\n<p>     &quot;DataItem3&quot;: [&quot;love&quot;]<\/p>\n<p>   },<\/p>\n<p>   &quot;error&quot;: [],<\/p>\n<p>   &quot;ts&quot;: &quot;2019-06-18T10:55:41.491&quot;<\/p>\n<p> }<\/p>\n<p>\u3010Custom\u3011<\/p>\n<p>User-defined Text using %1, %2, \u2026 variables to incorporate register or relays.<\/p>\n<p>Note:<\/p>\n<ol>\n<li>The data format and the figure data item to be published and subscribed must be the same in order that the data will be swapped successfully.<\/li>\n<li>When it is in JSON mode, the data format will be JSON ARRAY.<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010Set figure data item\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Number of figure data item\u3011<\/p>\n<p>Set the number of figure data item required for such topic.<\/p>\n<p>Described below is the detailed setting of figure data item.<\/p>\n<p>\u3010Name\u3011<\/p>\n<p>The name of figure data item cannot be left blank and the name of each item must be unique and exclusive. The user shall be allowed to input the item name directly. <\/p>\n<p>\u3010Type of figure data\u3011<\/p>\n<p>It comes with \u3010bit\u3011, \u301016-bit BCD number\u3011, \u301016-bit positive integer\u3011, \u301032-bit BCD number\u3011, \u301032-bit integer\u3011, \u301032-bit positive integer\u3011, \u301032-bit floating point number\u3011 and \u3010Ascii (U.S.)\u3011 for option. <\/p>\n<p>\u3010Address\u3011<\/p>\n<p>Based on the type of figure data, the user will be allowed to set the address for each individual figure data item.<\/p>\n<p>\u3010Length\u3011<\/p>\n<p>If the type of figure data is configured in 16-bit, it will occupy one byte and 32-bit will occupy two bytes. In case of Ascii-String, it allows the user to determine the number of bytes that will be occupied by the figure data item. Each individual byte can accommodate 2 bits.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h4>11-4-3 Topic Subscribe                                                        <\/h4>\n<p>To use the MQTT function, click \u201cMQTT\u201d from the \u201cServer Configuration\u201d window in the left-side \u201cProject\u201d and then select \u201cEnable\u201d to show the \u201cTopic Subscribe\u201d. Next, click the upper-left \u201cAdd\u201d button to add a new topic. By clicking the \u201cDelete\u201d button, you may delete the selected topic. By clicking \u201cEdit\u201d or double clicking the item in the Topic List, you may edit the selected topic. If the Topic List contains the existed items, you may click \u201cExport\u201d and all of the topic data will be exported for creating the specific-format CSC file. By clicking the \u201cImport\u201d button, you may import the specific-format CSC file for updating the topic table. In Topic List, the left-side of each topic is provided with an exclusive ID and it will be used as the topic ID.<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\84.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-018.png\" \/><\/p>\n<p>Figure 84 Topic setting of MQTT topic subscribe<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\85.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-019.png\" \/><\/p>\n<p>Figure 85 Topic Subscribe<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Column<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010Basic\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Name\u3011<\/p>\n<p>Setting the topic name for making detailed description. <\/p>\n<p>\u3010Topic\u3011<\/p>\n<p>The topic used when MQTT is transmitting the message.<\/p>\n<p>(Notice: \u201c#\u201d and \u201c+\u201d are wildcard characters and they should not be used).                                                                       <\/p>\n<p>\u3010QoS\u3011<\/p>\n<p>For setting the QoS (Quality of Service) for MQTT, and it comprises the following 3 classes:<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Class<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>0<\/p>\n<\/td>\n<td>\n<p>Message transmitted once only. Message serving not guaranteed. Message will not be repeated.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Message will be served at least once. Message serving guaranteed. Message may be repeated.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\uff12<\/p>\n<\/td>\n<td>\n<p>Message will be served just once. Message serving guaranteed. Message will not be repeated.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>\u3010Data Format\u3011<\/p>\n<p>The message content of each individual subject is composed of the address values of the data item, as per the format below:<\/p>\n<p>\u3010Raw Data\u3011<\/p>\n<p>01 2a 03 b8 1e e5 3f 6c 6f 76 65<\/p>\n<p>\u3010JSON\u3011<\/p>\n<p>{ <\/p>\n<p>     &quot;d&quot;: {<\/p>\n<p>     &quot;DataItem0&quot;: [true, true],<\/p>\n<p>     &quot;DataItem1&quot;: [810, 793, 688],<\/p>\n<p>     &quot;DataItem2&quot;: [1.789, 3.51],<\/p>\n<p>     &quot;DataItem3&quot;: [&quot;love&quot;]<\/p>\n<p>   },<\/p>\n<p>   &quot;error&quot;: [],<\/p>\n<p>   &quot;ts&quot;: &quot;2019-06-18T10:55:41.491&quot;<\/p>\n<p> }<\/p>\n<p>\u3010Custom\u3011<\/p>\n<p>User-defined Text using %1, %2, \u2026 variables to incorporate register or relays.<\/p>\n<p>Note:<\/p>\n<ol>\n<li>The data format and the figure data item to be published and subscribed must be the same in order that the data will be swapped successfully.<\/li>\n<li>When it is in JSON mode, the data format will be JSON ARRAY.<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u3010Set figure data item\u3011<\/p>\n<\/td>\n<td>\n<p>\u3010Number of figure data item\u3011<\/p>\n<p>Set the number of figure data item required for such subject.<\/p>\n<p>Described below is the detailed setting of figure data item.<\/p>\n<p>\u3010Name\u3011<\/p>\n<p>The name of figure data item cannot be left as blank and the name of each item must be unique and exclusive. The user shall be allowed to input the item name directly.<\/p>\n<p>\u3010Type of figure data\u3011<\/p>\n<p>It comes with \u3010bit\u3011, \u301016-bit BCD number\u3011, \u301016-bit positive integer\u3011, \u301032-bit BCD number\u3011, \u301032-bit integer\u3011, \u301032-bit positive integer\u3011, \u301032-bit floating point number\u3011 and \u3010Ascii (U.S.)\u3011 for option.<\/p>\n<p>\u3010Address\u3011<\/p>\n<p>Based on the type of figure data, the user will be allowed to set the address for each individual figure data item.<\/p>\n<p>\u3010Length\u3011<\/p>\n<p>If the type of figure data is configured in 16-bit, it will occupy one byte and 32-bit will occupy two bytes. In case of Ascii-String, it allows the user to determine the number of bytes that will be occupied by the figure data item. Each individual byte can accommodate 2 bits.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Table 25 Setting Properties of Topic Subscription Edit Window<\/p>\n<h4>11-4Status Register                                                 <\/h4>\n<p>The system provides the MQTT status register R35679 for users to check the MQTT connection status.<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>R35679 Status Code<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>0<\/p>\n<\/td>\n<td>\n<p>Connected<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Version not support<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>2<\/p>\n<\/td>\n<td>\n<p>Descriptor Mismatch<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>3<\/p>\n<\/td>\n<td>\n<p>Access Denied<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>4<\/p>\n<\/td>\n<td>\n<p>Wrong account &amp; password<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>5<\/p>\n<\/td>\n<td>\n<p>Authentication failed<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>256<\/p>\n<\/td>\n<td>\n<p>Connection Closed<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>257<\/p>\n<\/td>\n<td>\n<p>Connection Timeout<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>258<\/p>\n<\/td>\n<td>\n<p>Memory Allocation Failed<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>259<\/p>\n<\/td>\n<td>\n<p>Incompatible Custom Format<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h4>11-4-5 Used Tools                                                            <\/h4>\n<p>This chapter describes the MQTT related tools:<\/p>\n<p>Using external Broker<\/p>\n<p>In \u3010Host (IP or domain name)\u3011 of \u3010Server\u3011 setup page, input the IP address or the domain name of the external Broker. <\/p>\n<p>Example: Using the publicly tested Broker on Mosquitto (<a href=\"https:\/\/test.mosquitto.org\/\">https:\/\/test.mosquitto.org\/<\/a>)<\/p>\n<ul>\n<li>Host: test.mosquitto.org<\/li>\n<li>Port: 1883<\/li>\n<\/ul>\n<p>Install the Broker<\/p>\n<p>It allows the user to install the Broker. <\/p>\n<p>Example: Using Mosquitto (<a href=\"http:\/\/mosquitto.org\/download\/\">http:\/\/mosquitto.org\/download\/<\/a>), and it is a public and free resource. For detailed installation and using method, please visit its website.<\/p>\n<h4>11-4-6 Client application                                                      <\/h4>\n<p>To monitor the data transmitted by MQTT, it will be required to use the MQTT client program provided by the third party for connecting to the selected Broker and then you may subscribe the topic published by HMI in order to receive the updated data. Currently, a lot of free MQTT client programs are available on the network for download. <\/p>\n<p>Example: MQTT.fx (<a href=\"https:\/\/mqttfx.jensd.de\/index.php\/download\">https:\/\/mqttfx.jensd.de\/index.php\/download<\/a>)<\/p>\n<h3>11-5  Modbus TCP Communication Protocols<\/h3>\n<p>Modbus TCP Slave Station<\/p>\n<p>The scope of Modbus slave station address conversion can be planned by the designer in &quot;Modbus<\/p>\n<p>Address Allocation&quot; through software, please refer to Section 10-4-2.<\/p>\n<p>Modbus TCP Master Station<\/p>\n<p>Use the Modbus network communication connection command to communicate, please refer to<\/p>\n<p>Section 11-5-1.<\/p>\n<h4>11-5-1 Convenient command for Modbus network communication connection    <\/h4>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td colspan=\"3\">\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>Symbol<\/p>\n<\/td>\n<td colspan=\"4\"><\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\">\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\FUN152.png\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-020.png\" \/><\/p>\n<\/td>\n<td colspan=\"2\">\n<p>SR: Starting register address in the table<\/p>\n<p>MD: <br \/>Modbus TCP proactive communication (=1)<br \/>Modbus TCP proactive communication( specified station number)(=2)<\/p>\n<p>WR: Working Register<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"5\">\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td rowspan=\"2\">\n<p>Range<\/p>\n<p>           Operand<\/p>\n<p>                        \u904b\u7b97\u5143<\/p>\n<\/td>\n<td>\n<p>WY<\/p>\n<\/td>\n<td>\n<p>WM<\/p>\n<\/td>\n<td>\n<p>WS<\/p>\n<\/td>\n<td>\n<p>TMR<\/p>\n<\/td>\n<td>\n<p>CTR<\/p>\n<\/td>\n<td>\n<p>HR<\/p>\n<\/td>\n<td>\n<p>OR<\/p>\n<\/td>\n<td>\n<p>SR<\/p>\n<\/td>\n<td>\n<p>ROR<\/p>\n<\/td>\n<td>\n<p>DR<\/p>\n<\/td>\n<td>\n<p>K<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WY0<\/p>\n<p>\u2223<\/p>\n<p>WY1008<\/p>\n<\/td>\n<td>\n<p>WM0<\/p>\n<p>\u2223<\/p>\n<p>WM29584<\/p>\n<\/td>\n<td>\n<p>WS0<\/p>\n<p>\u2223<\/p>\n<p>WS3088<\/p>\n<\/td>\n<td>\n<p>T0<\/p>\n<p>\u2223<\/p>\n<p>T1024<\/p>\n<\/td>\n<td>\n<p>C0<\/p>\n<p>\u2223<\/p>\n<p>C1280<\/p>\n<\/td>\n<td>\n<p>R0<\/p>\n<p>\u2223<\/p>\n<p>R34767<\/p>\n<\/td>\n<td>\n<p>R35024<\/p>\n<p>\u2223<\/p>\n<p>R35151<\/p>\n<\/td>\n<td>\n<p>R35280<\/p>\n<p>\u2223<\/p>\n<p>R40279<\/p>\n<\/td>\n<td>\n<p>R40280<\/p>\n<p>\u2223<\/p>\n<p>R48471<\/p>\n<\/td>\n<td>\n<p>D0<\/p>\n<p>\u2223<\/p>\n<p>D7999<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR<\/p>\n<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb*<\/p>\n<\/td>\n<td>\n<p>\u25cb*<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>MD<\/p>\n<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR<\/p>\n<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td>\n<p>\u25cb*<\/p>\n<\/td>\n<td>\n<p>\u25cb*<\/p>\n<\/td>\n<td>\n<p>\u25cb<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\">\n<p>Description<\/p>\n<\/td>\n<td colspan=\"3\"><\/td>\n<\/tr>\n<tr>\n<td colspan=\"5\">\n<ol>\n<li>The FUN152 (NCR) command is connected to the smart peripheral (slave station) with the Modbus communication protocol through the Ethernet port.<\/li>\n<li>This command is mainly based on the specified form, such as using the Modbus Master TCP form, read or write according to the form specified, and actively carry out network communication. The communication form must be set before use; only six registers are required for definition. Every 6 registers define a transfer transaction.<\/li>\n<li>When EN is ON for this command, the communication will continue.<\/li>\n<li>When the data transaction is being transmitted, the output indication &quot;ACT&quot; is ON.<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td>\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\">\n<p>Description of FUN152 command operand SR<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>SR<\/p>\n<\/td>\n<td>\n<p>Word Size<\/p>\n<\/td>\n<td>\n<p>Purpose<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 0<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>ID letter: 0x544D<\/p>\n<\/td>\n<td>\n<p>For identifying effect table: \u201cM\u201d, \u201cT\u201d.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 1<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>ID letter: 0x544D<\/p>\n<\/td>\n<td>\n<p>Each lot of communication will be expressed by 6 registers.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 2<\/p>\n<\/td>\n<td>\n<p>2<\/p>\n<\/td>\n<td>\n<p>Remote IP<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 4<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Remote port<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 5<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>TCP online active<\/p>\n<\/td>\n<td>\n<p>=0: One round of online created for each individual communication.<\/p>\n<p>=1: One round of TCP online maintained in the table.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 6<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Overtime setting<\/p>\n<\/td>\n<td>\n<p>Unit: 10ms<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 7<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Retest number<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 8<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Enable done signal<\/p>\n<\/td>\n<td>\n<p>=0, Disabled<\/p>\n<p>=1, Enabled<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 9<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Communication table done signal<\/p>\n<\/td>\n<td>\n<p>M XXXXX<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 10<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Order Code (1<sup>st<\/sup> lot)<\/p>\n<\/td>\n<td>\n<p>=1, Read<\/p>\n<p>=2, Write<\/p>\n<p>=3, Write once<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 11<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Data Length<\/p>\n<\/td>\n<td>\n<p>Register: Reading length is 125 and writing length is 123.<\/p>\n<p>Contacts: 1\u2013255<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 12<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Type of Master PLC data<\/p>\n<\/td>\n<td>\n<p>Please see the data type, code and initial number of FATEK master station.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td>\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\">\n<p>Description of FUN152 command operand SR<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>SR<\/p>\n<\/td>\n<td>\n<p>Word Size<\/p>\n<\/td>\n<td>\n<p>Purpose<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 13<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Master PLC data starting number<\/p>\n<\/td>\n<td>\n<p>Please see the data type, code and initial number of FATEK master station.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 14<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Slave PLC data type<\/p>\n<\/td>\n<td>\n<p>Please refer to Modbus Data Type Table.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 15<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Slave PLC data starting number<\/p>\n<\/td>\n<td>\n<p>Please refer to Modbus Data Type Table.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 16<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Command code (second lot)<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>When it is Modbus TCP active communication (specified station number), it must be adjusted as follows:<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>SR<\/p>\n<\/td>\n<td>\n<p>Word Size<\/p>\n<\/td>\n<td>\n<p>Purpose<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 16<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Slave PLC data starting number<\/p>\n<\/td>\n<td>\n<p>Please refer to Modbus Data Type Table.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 17<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>System reserved<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>SR + 18<\/p>\n<\/td>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Command code (second lot)<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td>\n<p>\u2026<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td>\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\">\n<p>The data type, code and initial number of FATEK master station.<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Data Code<\/p>\n<\/td>\n<td>\n<p>Data Type<\/p>\n<\/td>\n<td>\n<p>Scope<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Y (Output Relay)<\/p>\n<\/td>\n<td>\n<p>0~1023<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>2<\/p>\n<\/td>\n<td>\n<p>M (Internal Relay)<\/p>\n<\/td>\n<td>\n<p>0~29599<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>3<\/p>\n<\/td>\n<td>\n<p>S (Stepping Relay)<\/p>\n<\/td>\n<td>\n<p>0~3103<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>12<\/p>\n<\/td>\n<td>\n<p>R (Data Register)<\/p>\n<\/td>\n<td>\n<p>0~34767<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>13<\/p>\n<\/td>\n<td>\n<p>D (Data Register)<\/p>\n<\/td>\n<td>\n<p>0~7999<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<ul>\n<li>Slave Station (Modbus) data type, code and starting number<\/li>\n<\/ul>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>Data Code<\/p>\n<\/td>\n<td>\n<p>Data Type<\/p>\n<\/td>\n<td>\n<p>Scope<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>0<\/p>\n<\/td>\n<td>\n<p>Output or internal relay<\/p>\n<\/td>\n<td>\n<p>1~65535<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>4<\/p>\n<\/td>\n<td>\n<p>Data Register <\/p>\n<\/td>\n<td>\n<p>1~65535<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Contact input<\/p>\n<\/td>\n<td>\n<p>1~65535<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>3<\/p>\n<\/td>\n<td>\n<p>Input Register<\/p>\n<\/td>\n<td>\n<p>1~65535<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Note: The data type of Master and Slave must be the same. In other words, if Master Station is Y\/M\/S, then the Slave Station must be coded as\u201d0\/1\u201d. <\/p>\n<p>If the Master Station is R\/D, then the Slave Station must be coded as \u201c3\/4\u201d; and vice versa.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td>\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\">\n<p>Description of FUN152 command operand WR<\/p>\n<p>High Byte\t Low Byte<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>WR+0<\/p>\n<\/td>\n<td>\n<p>Current communication index<\/p>\n<\/td>\n<td>\n<p>\u2022  Current communication index: The system is executing No. xx transaction (starting from 0).<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR+1<\/p>\n<\/td>\n<td>\n<p>Result Code<\/p>\n<\/td>\n<td>\n<p>\u2022  Result Code saving operation result: 0=Normal; other value = Abnormal <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR+2<\/p>\n<\/td>\n<td>\n<p>Function Code<\/p>\n<\/td>\n<td>\n<p>\u2022  Function Code: Please refer to the description provided below.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR+3<\/p>\n<\/td>\n<td>\n<p>Internal TCP online index<\/p>\n<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR+4<\/p>\n<\/td>\n<td>\n<p>Connection status<\/p>\n<\/td>\n<td rowspan=\"2\">\n<p>\u2022  Connection status: WR+4=0, communication success<\/p>\n<p>=2, waiting for reply<\/p>\n<p>=3, communication out of time<\/p>\n<p>=4, try to communication<\/p>\n<p>=5, communication error<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>WR+5<\/p>\n<\/td>\n<td>\n<p>Retest number<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Function Code:  Low Byte valid;<\/p>\n<p>                        =0, read slave PLC system status<\/p>\n<p>                        =1, read slave PLC data<\/p>\n<p>                        =2, write data to slave PLC<\/p>\n<p>Result code: 0, communication success.<\/p>\n<p>2, data length error (=0 or out of upper limit.)<\/p>\n<p>3, command code error (=0, or &lt;3)<\/p>\n<p>4, data type error (refer data types code)<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"4\">\n<p>5: Data number is incorrect (see data starting number).<\/p>\n<p>6: Master and slave data type are not the same.<\/p>\n<p>(e.g., Master Station is Y\/M\/S and Slave Station is coded as \u201c4\u201d).<\/p>\n<p>8: Illegal communication table is used.<\/p>\n<p>A: Slave Station remains inactive (Time-out error)<\/p>\n<p>B: Communication is abnormal.<\/p>\n<p>  (Receiving incorrect data or incorrect message is replied by Slave Station).<\/p>\n<p>C: Connect error<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\">\n<p>Example<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Slave Station 400101\u2013 400105 (IP: 192.168.0.151) to Master Station R100\u2013R104 addresses (IP: 192.168.0.150).<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"4\">\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\fun152_3.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-021.png\" \/><\/p>\n<p>Description of program example<\/p>\n<p>When the input control &quot;EN&quot; changes from 0 to 1, based on the settings in the Modbus TCP table, the remote IP Slave Station reads the register data and stores it in the PLC Master Station, and continuously completes the data transaction.<\/p>\n<p>For detailed setting steps, please see the description provided below<\/p>\n<p>1. First, add the \u201cModbus Master\u201d table in the original data list.<\/p>\n<p>2. In Modbus Master table, define remote IP and Port as well as the address that will be read and written, including the Master Station and Slave Station data.<\/p>\n<p>3. Edit Fun152 NCR command in Master Station Ladder.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\">\n<p>Example<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"4\">\n<p>Edit communication table with UperLogic <\/p>\n<p> In Project window, click followings:<br \/> Communication order table<strong>: <\/strong>Project name<\/p>\n<p>                             Data List<\/p>\n<p>Modbus Master Table <\/p>\n<p>Press right key and then click \u201cNew Modbus Table\u201d. The table type will be \u201cMaster TCP table\u201d. You may also click \u201cTable Edit\u201d in \u201cProject\u201d tag, roll down for selecting \u201cModbus Master table\u201d and then select \u201cNew Modbus Table\u201d. The table can also be configured as \u201cModbus TCP table\u201d type.\u3002<\/p>\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\modbustable.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-022.png\" \/><\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\">\n<p>Example<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"4\">\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-023.png\" \/><\/p>\n<p>Figure 87 Editing Modbus Master Table<\/p>\n<ul>\n<li>Table type: Select as \u201cModbus TCP Table\u201d.<\/li>\n<li>Table name: It can be configured in the online table type for inputting an identifiable name for the convenience of modifying or debugging later on.<\/li>\n<li>Table starting position: The starting position of the Start Register (SR) required for the communication program (data transmission table) used by the input communication command (FUN152).<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<td colspan=\"2\">\n<p>Convenient command for Modbus network (Master station) communication connection<\/p>\n<\/td>\n<td>\n<p>FUN152<\/p>\n<p>NCR<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"2\">\n<p>Example<\/p>\n<\/td>\n<td colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<td colspan=\"4\">\n<p><img decoding=\"async\" alt=\"D:\\patrick\\\u8aaa\u660e\u66f8\u7ffb\u8b6f_\u529f\u80fd\u7bc7\\\u5716\\88.PNG\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-024.png\" \/><\/p>\n<p>Figure 88 Modbus Master Table<\/p>\n<ul>\n<li>Remote IP: The IP address of remote device.<\/li>\n<li>Remote port number: The port number of remote device.<\/li>\n<li>Order: The order used by the Master Station to read data from Modbus Slave Station or to write the data to Modbus Slave Station.<\/li>\n<li>Master Station data: For reading, it serves as the position for saving the data being read from Slave Station. As for writing, it is the position in Master Station that will be used to write the data to Slave Station.<\/li>\n<li>Slave Station Data: For reading, it serves as the position for transmitting the data to the Master Station. As for writing, it is the position for Master Station to write the data to Slave Station.<\/li>\n<li>Length: The length of data to be transmitted. The reading length is coded as \u201c125\u201d and the writing length is coded as \u201c123\u201d.<\/li>\n<li>Connection maintenance: When starting, it will only initiate a TCP connection establishment request for the remote IP, and subsequent communications will exchange data on this connection; otherwise, it will re-establish a TCP connection for each communication<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h3>11-6  iMonitor Remote Monitoring<\/h3>\n<p>FATEK IoT provides a new iMonitor remote monitoring HMI and PLC solution, as long as the device can be connected to the Internet, users can easily obtain the data on the device, and can monitor and access multiple device systems at the same time, and receive the system alarm information and data collection function in a real time for remote debugging and troubleshooting. In terms of communication security, there is also a professional security encryption mechanism to help customers check, so as to effectively protect the operation and access equipment data, and avoid the use of malicious people. Above, users do not need to make any network settings.<\/p>\n<p>For detailed usage, please refer to the FATEK IoT cloud service user manual linked below:<\/p>\n<p><a href=\"https:\/\/www.fatek.com\/zh-tw\/download.php?act=list&amp;cid=16\">https:\/\/www.fatek.com\/zh-tw\/download.php?act=list&amp;cid=16<\/a><\/p>\n<h4>11-6-1 HWID                                                                   <\/h4>\n<p>Every FATEK product that supports iMonitor has a unique device code called HWID. You can view \u3010PLC Status\u3011 in the project, as shown in the figure below, and you can also view the current iMonitor connection status in this window. The same information can also be obtained in server-related settings. In order to facilitate the user to register the device correctly in the cloud background, click the function icon behind the HWID to quickly copy the HWID text content. <\/p>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-025.png\" \/><\/p>\n<p>Figure 81 Status of PLC<\/p>\n<h4>11-6-2 Server Setting                                                         <\/h4>\n<p>For the iMonitor function, click \u3010IoT\u3011 in the \u3010Server Configuration\u3011 window in the \u3010Project\u3011 on the left to enter its setting page. The \u3010Server\u3011 tab can be used to view and configure iMonitor, as shown in the figure below:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/resource.fatek.com\/wp-content\/uploads\/fatek\/mplc-m03-en-11\/mplc-m03-en-11-026.png\" \/><\/p>\n<p>Figure 81 iMonitor setting window<\/p>\n<h4>11-6-3 Status Register                                                        <\/h4>\n<p>In addition to knowing the iMonitor connection information through the software interface, the relevant detailed information can also be obtained in the status register R35483.<\/p>\n<div class=\"fatek-tw\">\n<table>\n<tr>\n<td>\n<p>R35483 Status Code<\/p>\n<\/td>\n<td>\n<p>Description<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>0<\/p>\n<\/td>\n<td>\n<p>Offline<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>1<\/p>\n<\/td>\n<td>\n<p>Online<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>2<\/p>\n<\/td>\n<td>\n<p>In connection<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>Other<\/p>\n<\/td>\n<td>\n<p>Error code<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h3>11-7 Fatek Binary&#8217;s open protocol explains the communication protocol<\/h3>\n<p>Please reference <a href=\"https:\/\/file.fatek.com\/en\/PLC\/MPLC\/Document\/Manual\/08_M_PLC_Binary_Communication_Protocol_User_Manual.pdf\">Fatek Binary communication user manual<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>11-1 Setting the Network Interface Default parameter of [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[47],"tags":[],"class_list":["post-3218","post","type-post","status-publish","format-standard","hentry","category-en-mplc-m03"],"_links":{"self":[{"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/posts\/3218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/comments?post=3218"}],"version-history":[{"count":0,"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/posts\/3218\/revisions"}],"wp:attachment":[{"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/media?parent=3218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/categories?post=3218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/resource.fatek.com\/index.php\/wp-json\/wp\/v2\/tags?post=3218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}