Skip to content

IEC104 and TCP Remote Signalling Station Access ​

This article reorganizes an existing operation manual into an online operation reference. Operations marked as expected or not executed in the original must still be verified against the actual environment.

Complete IEC104 ten-address remote signalling, two native single commands, independent states and history queries, plus a normal stop and republish recovery.

Before you begin: You have product, device, model, publish, control, and history permissions; the local application, single-node FMQ, and FMQX Web are available, and this device's connection parameters have been obtained

Learn This First ​

This article uses FMQX Web as the IEC104 controlled station, listening on TCP 15040; FMQ connects as the master station, and the platform manages products, devices, point tables, publish, and history.

Common address 1 identifies the controlled station; information object addresses 1001 to 1010 identify the ten remote signalling points respectively. true displays as Closed and false as Open.

This round's ten samples are one per address, odd true and even false; both single-point controls target 1001 — first false, then true after recovery.

Replace These Parameters Before Copying Templates ​

The code in this article uses generic template names; the screenshots retain actual historical resources. Complete the following checks before saving as a UTF-8 file or sending messages.

  • The host, port, and listening direction in the connection file must be changed to the actual addresses of the current environment; 127.0.0.1 means the local machine running FMQX. When MQTT is involved, also verify the product ID, username, subscription topics, and responseRoute; passwords are only entered securely on the connection page.
  • Group, session, and subscription ids are internal references of the import file; if renaming is needed, the groupId must match the corresponding group id. Verify before importing, and do not repeatedly create connections with the same name on a retained session.
  • The code blocks are customer templates rewritten from existing password-free assets or original code; this version of the template has not yet been proven to import successfully. Historical screenshots, send times, and business pass scope are still subject to the records of each step; do not treat template names as the actual resource names in the old evidence.

1. Creating the Product and Configuring the Protocol ​

This article reuses the first modeling, binding, mapping, and FMQX import records from 2026-10-13; this round reuses product 887, device 1244, and the existing session, without recreating, saving the model, or importing again.

The odd-false, even-true values in the first JSON screenshot were only used for modeling; this round's actual samples start from the later reporting section.

1. Creating Ten Boolean Properties from a Sample ​

Location: Device Access Wizard → JSON Sample Steps: Enter the ten remote signalling field sample and click Parse Preview; this step is only for modeling.

First configuration record: creating ten boolean properties from a sample

Use ten boolean fields to build the thing model; the sample is only used to identify fields and types — actual remote signalling is reported over IEC104.

Screenshot Highlights ​

Field / ControlDescription
First Modeling SampleThe historical JSON generates ten boolean models; the sample is odd false and even true and is not used as this round's report values.
Required · Fill in: Odd fields false; even fields true

2. Verifying the Fields and Boolean Type ​

Location: Device Access Wizard → Collection Point Table Steps: Verify the identifiers and boolean type of the ten fields, corresponding in address order.

First configuration record: verifying the fields and boolean type

Verify the ten fields and their boolean type item by item, building the mapping in the address order of the formal point table.

Screenshot Highlights ​

Field / ControlDescription
First Modeling SampleThe historical JSON generates ten boolean models; the sample is odd false and even true and is not used as this round's report values.
Required · Fill in: Fill according to the implementation plan · Example: Ten boolean fields
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010; control 1001
Remote Signalling TypeSingle-point remote signalling maps to BOOLEAN; true is Closed, false is Open.
Required · Fill in: Fill according to the implementation plan · Example: M_SP_NA_1 / BOOLEAN
Modeling SampleJSON is only used to generate the ten boolean models; the final selection is native IEC104.
Required · Fill in: 10 boolean fields
Information Object Address (ioa)The independent address of each remote signalling point in the point table; it is not the common address.
Required · Fill in: 1001–1010
Remote Signalling Type (asduType)This article uses single-point remote signalling, with values true/false.
Required · Fill in: M_SP_NA_1 / BOOLEAN

3. Filling in This Article's Device Identity ​

Location: Device Access Wizard → Device Information Steps: Fill in the independent device number and name for later binding.

First configuration record: filling in this article's device identity

Fill in a unique device number and name for this device.

Screenshot Highlights ​

Field / ControlDescription
Device IdentityThe independent device number stays identical to the platform-bound clientId.
Required · Fill in: This article's controlled station

4. Switching to the Final Native Protocol ​

Location: Product Details → Basic Information Steps: Select TCP and IEC 60870-5-104, then save the changes.

First configuration record: switching to the final native protocol

Select TCP as the access channel and IEC 60870-5-104 as the data format.

Screenshot Highlights ​

Field / ControlDescription
Access Protocol and Data FormatFMQ connects to the controlled station as the master station, using native IEC104.
Required · Fill in: TCP / IEC 60870-5-104

5. Enabling History and Allowing Remote Signalling 1 Control ​

Location: Product → Function Definition → Modify Thing Model Steps: Turn off read-only data for Remote Signalling 1 and enable history storage; keep the other nine items read-only with history enabled.

First configuration record: enabling history and allowing Remote Signalling 1 control

Enable history storage; Remote Signalling 1 allows control, and the other nine items remain read-only.

Screenshot Highlights ​

Field / ControlDescription
Property Permission and HistoryAll ten items have history enabled; 1001 allows control, and the other nine items are read-only.
Required · Fill in: Fill according to the implementation plan · Example: Ten boolean properties; 1001 writable
Property Permission and HistoryRemote Signalling 1 allows control; the rest are read-only, and all ten items have history storage enabled.
Required · Fill in: Boolean; 1001 writable; history on

6. Binding the Device and the Controlled Station Address ​

Location: Product → Device Protocol Configuration → Device Binding Steps: Select this device, fill in the clientId, common address, IP, and port, enable, and save the draft.

First configuration record: binding the device and the controlled station address

Fill in the actual controlled station's IP, port, and common address; FMQ actively establishes the connection as the master station.

Screenshot Highlights ​

Field / ControlDescription
Device BindingdeviceId 1244, clientId is this device's number; enable the binding.
Required · Fill in: This device / common address 1
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: Fill according to the implementation plan · Example: 1
Controlled Station IPThe platform binding fills in the controlled station's reachable listening IP; the local demo uses the loopback address.
Required · Fill in: 127.0.0.1
Controlled Station PortThe platform binding stays consistent with the imported controlled station's listening port.
Required · Fill in: 15040
Common Address (commonAddress)The station address provided by the formal point table; binding, remote signalling, general interrogation, and remote control must all be consistent.
Required · Fill in: 1

7. Saving the Address and Remote Signalling Mapping ​

Location: Device Protocol Configuration → Point Mapping Steps: Configure 1001 to 1010 according to the point table, single-point remote signalling and BOOLEAN, scale 1, offset 0; only 1001 is writable.

First configuration record: saving the address and remote signalling mapping

The ten remote signalling addresses are 1001 to 1010, corresponding to thing model fields item by item.

Screenshot Highlights ​

Field / ControlDescription
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010; control 1001
Remote Signalling TypeSingle-point remote signalling maps to BOOLEAN; true is Closed, false is Open.
Required · Fill in: Fill according to the implementation plan · Example: M_SP_NA_1 / BOOLEAN
Scale and OffsetThe boolean demo keeps scale 1 and offset 0, with the unit left blank.
Required · Fill in: 1 / 0; unit left blank
Property Permission and HistoryAll ten items have history enabled; 1001 allows control, and the other nine items are read-only.
Required · Fill in: Fill according to the implementation plan · Example: Ten boolean properties; 1001 writable
Information Object Address (ioa)The independent address of each remote signalling point in the point table; it is not the common address.
Required · Fill in: 1001–1010
Remote Signalling Type (asduType)This article uses single-point remote signalling, with values true/false.
Required · Fill in: M_SP_NA_1 / BOOLEAN
Property Permission and HistoryRemote Signalling 1 allows control; the rest are read-only, and all ten items have history storage enabled.
Required · Fill in: Boolean; 1001 writable; history on

8. Setting the Normal General Interrogation Cycle ​

Location: Device Protocol Configuration → Collection Group Steps: Fill in common address 1, enable general interrogation, set the interval to 60000 milliseconds, and enable.

First configuration record: setting the normal general interrogation cycle

Configure periodic general interrogation; 60000 milliseconds means requesting the current point values once per minute.

Screenshot Highlights ​

Field / ControlDescription
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: Fill according to the implementation plan · Example: 1
Historical Collection Group ConfigurationThe first configuration enabled general interrogation with a 60000-millisecond interval; this only describes the saved items and is not proof of a successful manual general interrogation in this round.
Required · Fill in: Fill according to the implementation plan · Example: interrogationEnabled on; 60000 milliseconds
Common Address (commonAddress)The station address provided by the formal point table; binding, remote signalling, general interrogation, and remote control must all be consistent.
Required · Fill in: 1
General Interrogation GroupEnables general interrogation, normally asking for the whole-station state every 60 seconds.
Required · Fill in: interrogationEnabled on; 60000 ms

9. Configuring the Single-Point Remote Control Template ​

Location: Device Protocol Configuration → Command Templates Steps: Common address 1, IOA 1001, type C_SC_NA_1, mapped to Remote Signalling 1; turn off select-before-execute and save the draft.

First configuration record: configuring the single-point remote control template

Single remote control uses common address 1 and information object address 1001, consistent with the writable property Remote Signalling 1.

Screenshot Highlights ​

Field / ControlDescription
Single-Point Remote Control TemplateCommon address 1, information object address 1001, select-before-execute off, using direct execution.
Required · Fill in: Fill according to the implementation plan · Example: C_SC_NA_1; selectBeforeExecute off
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010; control 1001
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: Fill according to the implementation plan · Example: 1
Remote Control TemplateAddress 1001 maps to Remote Signalling 1, using single-command direct execution.
Required · Fill in: C_SC_NA_1; selectBeforeExecute off
Information Object Address (ioa)The independent address of this article's writable Remote Signalling 1.
Required · Fill in: 1001
Common Address (commonAddress)The station address provided by the formal point table; binding, remote signalling, general interrogation, and remote control must all be consistent.
Required · Fill in: 1

**Complete connection and point JSON template (password-free)**json

text
{

  "schemaVersion": 3,

  "groups": [

    {

      "id": "tutorial_IEC104_01",

      "name": "Remote Signalling Tutorial",

      "sortOrder": 80,

      "isSystem": false

    }

  ],

  "sessions": [

    {

      "id": "import_IEC104_01",

      "name": "Controlled Station",

      "groupId": "tutorial_IEC104_01",

      "protocol": "IEC104",

      "transport": "TCP",

      "host": "127.0.0.1",

      "port": 15040,

      "autoReconnect": false,

      "iec104CommonAddress": 1,

      "iec104Points": [

        {

          "informationObjectAddress": 1001,

          "type": "M_SP_NA_1",

          "value": false,

          "writable": true

        },

        {

          "informationObjectAddress": 1002,

          "type": "M_SP_NA_1",

          "value": true,

          "writable": false

        },

        {

          "informationObjectAddress": 1003,

          "type": "M_SP_NA_1",

          "value": false,

          "writable": false

        },

        {

          "informationObjectAddress": 1004,

          "type": "M_SP_NA_1",

          "value": true,

          "writable": false

        },

        {

          "informationObjectAddress": 1005,

          "type": "M_SP_NA_1",

          "value": false,

          "writable": false

        },

        {

          "informationObjectAddress": 1006,

          "type": "M_SP_NA_1",

          "value": true,

          "writable": false

        },

        {

          "informationObjectAddress": 1007,

          "type": "M_SP_NA_1",

          "value": false,

          "writable": false

        },

        {

          "informationObjectAddress": 1008,

          "type": "M_SP_NA_1",

          "value": true,

          "writable": false

        },

        {

          "informationObjectAddress": 1009,

          "type": "M_SP_NA_1",

          "value": false,

          "writable": false

        },

        {

          "informationObjectAddress": 1010,

          "type": "M_SP_NA_1",

          "value": true,

          "writable": false

        }

      ]

    }

  ]

}

After verifying against the replacement checklist, save it as 连接配置.json and select Import Configuration in FMQX Web; this rewritten text does not mean the template has actually been imported. Replaceable customer template names are used here; verify against this section's replacement checklist before importing or sending.

10. Importing the FMQX Controlled Station Configuration ​

Location: FMQX Web → Configuration File Steps: After verifying this section's complete JSON against the replacement checklist, save it as the UTF-8 file 连接配置.json, then select Import Configuration under More Actions in FMQX Web. The original step screenshot retains the original batch operation.

First configuration record: importing the FMQX controlled station configuration

Import the demo controlled station configuration and point table in FMQX Web.

Screenshot Highlights ​

Field / ControlDescription
Import ConfigurationImports the controlled station's IP, port, common address, and ten-point table from a configuration file.
Required · Fill in: 连接配置.json

Historical Optional Configuration: Station-Wide General Interrogation Whitelist ​

The historical general interrogation whitelist configuration is kept to explain address 0. This round did not re-save or execute a manual general interrogation, and the old general interrogation operation, history, or success conclusions are not carried over.

11. Historical Optional Configuration: Adding a Station-Wide General Interrogation Whitelist ​

Location: IEC104 Workbench → Command Whitelist → Add Steps: Configure the general interrogation whitelist: common address 1, information object address 0, C_IC_NA_1, associated with Remote Signalling 1; turn off select-before-execute and enable. This article's downlink demo uses single remote control.

First configuration record: adding a station-wide general interrogation whitelist

The general interrogation template uses common address 1, information object address 0, and C_IC_NA_1; this article's control demo uses the single remote control template.

Screenshot Highlights ​

Field / ControlDescription
Historical Optional Station-Wide General InterrogationOnly the first whitelist configuration is kept for reference; this round did not re-save or execute a manual general interrogation.
Required · Fill in: Common address 1; address 0; C_IC_NA_1

2. Verifying Names, Publishing, and Confirming the Connection ​

The connection editor only provides the name, group, and save method. The native listening parameters come from the imported configuration; verify them together with the platform binding and the current connection summary.

12. Read-Only Verification of the Connection Name and Group ​

Location: FMQX Web → This Article's Session → Connection Parameters Steps: Verify the connection name, owning group, and save method, then cancel editing.

Read-only verification of the connection name and group

This window is for the name, group, and save method; the controlled station address and point table come from the imported configuration.

Screenshot Highlights ​

Field / ControlDescription
Connection NameUsed to complete "Read-Only Verification of the Connection Name and Group".
Required · Fill in: FastBee_受控站
Owning GroupUsed to complete "Read-Only Verification of the Connection Name and Group".
Required · Fill in: FastBee_遥信教程

13. Publishing This Article's Product Configuration ​

Location: Product Details → Basic Information Steps: First start this article's controlled station listener, then verify this article's product and click OK in the publish confirmation box.

Publishing this article's product configuration

FMQ actively connects to 127.0.0.1:15040 as the master station; after publishing, continue to check node application and STARTDT.

Screenshot Highlights ​

Field / ControlDescription
Controlled Station IPThe platform binding fills in the controlled station's reachable listening IP; the local demo uses the loopback address.
Required · Fill in: Fill according to the implementation plan · Example: 127.0.0.1
Controlled Station PortThe platform binding stays consistent with the imported controlled station's listening port.
Required · Fill in: Fill according to the implementation plan · Example: 15040
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: Fill according to the implementation plan · Example: 1

14. Confirming the Runtime Configuration Has Been Applied ​

Location: Product Details → Sync Details Steps: Open the sync details and verify the target node's APPLIED status and effective time.

Confirming the runtime configuration has been applied

Verify the target node shows APPLIED, then check the controlled station connection and actual send/receive.

15. Confirming the Controlled Station Is Connected and STARTDT Is Complete ​

Location: FMQX Web → Connection Configuration Steps: Verify the role, station address, listening endpoint, point count, and connection status.

Confirming the controlled station is connected and STARTDT is complete

Controlled station Server, common address 1, ten points, 127.0.0.1:15040; connected / STARTDT confirmed, 1 active connection.

Screenshot Highlights ​

Field / ControlDescription
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: Fill according to the implementation plan · Example: 1
Controlled Station IPThe platform binding fills in the controlled station's reachable listening IP; the local demo uses the loopback address.
Required · Fill in: Fill according to the implementation plan · Example: 127.0.0.1
Controlled Station PortThe platform binding stays consistent with the imported controlled station's listening port.
Required · Fill in: Fill according to the implementation plan · Example: 15040

3. Reporting Ten Different Addresses in Turn ​

16. Saving and Reporting the First Remote Signalling Point ​

Location: FMQX Web → Communication → Remote Signalling Point Steps: Set address 1001 to true, save the point, then click Send Telemetry once.

Saving and reporting the first remote signalling point

The first sample is 1001=true; saving the demo point value and sending telemetry are done separately.

Screenshot Highlights ​

Field / ControlDescription
Set Demo Point ValuesSave each of the ten-sample addresses once: odd true, even false; the recovery 1002=true and the second baseline 1001=false are saved separately by the operator.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010 once each
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: 1001
Remote Signalling TypeSingle-point remote signalling maps to BOOLEAN; true is Closed, false is Open.
Required · Fill in: Fill according to the implementation plan · Example: M_SP_NA_1 / BOOLEAN
Boolean ValueUsed to complete "Saving and Reporting the First Remote Signalling Point".
Required · Fill in: true / Closed

17. Verifying the First Independent Remote Signalling Raw Frame ​

Location: FMQX Web → Communication Records Steps: Open the 02:05:18.803 send record and verify the raw frame and address.

Verifying the first independent remote signalling raw frame

type1 is single-point remote signalling, cause3 is spontaneous reporting; common address 1, 1001=true, consistent with the first sample.

18. Reporting Ten Different Remote Signalling Points in Address Order ​

Location: FMQX Web → Communication → Remote Signalling Point Steps: After completing the save, send, and native-frame verification for address 1001 in the previous two steps, continue saving and sending once for each of 1002 to 1010; odd true, even false, waiting for the platform to update each time.

Reporting ten different remote signalling points in address order

The ten samples correspond to ten different addresses; the tenth address is 1010=false. Wait for the platform to update before operating the next point each time.

Screenshot Highlights ​

Field / ControlDescription
Set Demo Point ValuesSave each of the ten-sample addresses once: odd true, even false; the recovery 1002=true and the second baseline 1001=false are saved separately by the operator.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010 once each
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010; control 1001
Ten AddressesUsed to complete "Reporting Ten Different Remote Signalling Points in Address Order".
Required · Fill in: 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010
This Round's ValuesUsed to complete "Reporting Ten Different Remote Signalling Points in Address Order".
Required · Fill in: true, false, true, false, true, false, true, false, true, false

4. First Platform Remote Control and Independent State ​

The activation request, activation confirmation, and activation termination correspond to cause6, 7, and 10 respectively; after termination, only select the address and send telemetry — avoid manually saving the value and overwriting the control result.

19. Changing Remote Signalling 1 to Open from the Platform ​

Location: Device Details → Running Status → Remote Signalling 1 Steps: Verify the current state is Closed, control Remote Signalling 1 to false, send once, then check on the device side.

Changing Remote Signalling 1 to Open from the platform

This image shows true before writing; this target false and the execution result are proven by the subsequent independent native records.

Screenshot Highlights ​

Field / ControlDescription
First Remote Signalling 1 ControlThis round controls from true to false; the screenshot shows true before writing.
Required · Fill in: Fill according to the implementation plan · Example: 1001: Closed → Open
Control AddressUsed to complete "Changing Remote Signalling 1 to Open from the Platform".
Required · Fill in: 1001
Target ValueUsed to complete "Changing Remote Signalling 1 to Open from the Platform".
Required · Fill in: false / Open

20. Confirming the First Remote Control Request Was Received ​

Location: FMQX Web → Communication Records Steps: View the 02:05:42.740 received frame.

Confirming the first remote control request was received

Received a C_SC_NA_1 single command, cause6 is the activation request, common address 1, 1001=false.

21. Confirming the First Remote Control Was Accepted ​

Location: FMQX Web → Communication Records Steps: View the subsequent 02:05:42.741 sent frame.

Confirming the first remote control was accepted

The same single command returns cause7 activation confirmation, 1001=false; continue verifying the termination confirmation.

22. Confirming the Native End of the First Remote Control ​

Location: FMQX Web → Communication Records Steps: View the 02:05:42.742 sent frame.

Confirming the native end of the first remote control

The device sends the activation termination confirmation, Remote Signalling 1=false; continue verifying the actual state with an independent spontaneous report.

23. Independently Reporting the State After the First Control Without Saving the Point Value ​

Location: FMQX Web → Remote Signalling Point and Communication Records Steps: Only select address 1001 and send telemetry, keeping the point value unsaved, then verify the new 02:05:44.938 sent frame.

Independently reporting the state after the first control without saving the point value

The independent type1/cause3 report is 1001=false and is associated with actual history; this report did not manually save the point value.

5. Republish Recovery After a Normal Stop ​

This round recovers in the order of normal stop, unpublish, starting the controlled station, and republishing, without injecting network failures. The recovery 1002=true is a new demo value set by the operator.

24. Normally Stopping the Controlled Station Connection ​

Location: FMQX Web → This Article's Session Steps: After completing the first control, disconnect normally and verify the left side shows Disconnected.

Normally stopping the controlled station connection

The controlled station has stopped listening, and the connection status shows Disconnected.

25. Unpublishing to Pause This Article's Collection ​

Location: Product Details → Unpublish Steps: Read the notice that republishing may reset device data, then click OK.

Unpublishing to pause this article's collection

Pause this article's runtime configuration, keeping the product, device, thing model, session, and the history already formed.

26. Confirming the Paused Configuration Has Been Applied ​

Location: Product Details → Sync Details Steps: Verify the unpublished state and the node application result.

Confirming the paused configuration has been applied

Verify the unpublish has been applied. To recover, start the controlled station first, then republish the product.

27. Republishing After Starting the Controlled Station ​

Location: FMQX Web → This Article's Session; Product Details → Publish Steps: First start the same controlled station listener, then republish the original product and wait for application; verify the left side shows Connected.

Republishing after starting the controlled station

The controlled station is started, the republish has been applied, and the connection is restored; continue sending new remote signalling for verification.

28. Setting and Reporting a New Point Value After Recovery ​

Location: FMQX Web → Remote Signalling Point and Communication Records Steps: Save 1002 as true, then send, and verify the 02:06:01.571 independent remote signalling frame.

Setting and reporting a new point value after recovery

After recovery, report 1002=true and check that the platform receives the new point value.

Screenshot Highlights ​

Field / ControlDescription
Set Demo Point ValuesSave each of the ten-sample addresses once: odd true, even false; the recovery 1002=true and the second baseline 1001=false are saved separately by the operator.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010 once each
Recovery ReportUsed to complete "Setting and Reporting a New Point Value After Recovery".
Required · Fill in: 1002=true

6. Executing a New Opposite-Direction Control After Recovery ​

1001=false is the second pre-write baseline set and sent by the operator; afterwards, the platform controls true, followed by an independent report without saving the point value — verify them separately.

29. Setting the Baseline, Then Changing Remote Signalling 1 to Closed from the Platform ​

Location: FMQX Web → Remote Signalling Point; Device Details → Running Status Steps: First save 1001 as false and send it at 02:06:03.060 as the manual baseline; verify the platform shows Open, then control it to true from the platform.

Setting the baseline, then changing Remote Signalling 1 to Closed from the platform

This image shows false before the second write; the manual baseline and the remote control execution are verified separately, and the subsequent new native records prove the target true.

Screenshot Highlights ​

Field / ControlDescription
Set Demo Point ValuesSave each of the ten-sample addresses once: odd true, even false; the recovery 1002=true and the second baseline 1001=false are saved separately by the operator.
Required · Fill in: Fill according to the implementation plan · Example: 1001–1010 once each
New Control After RecoveryThe operator first saves and sends the 1001=false baseline, then the platform controls true.
Required · Fill in: Fill according to the implementation plan · Example: 1001: Open → Closed
Manual Recovery BaselineUsed to complete "Setting the Baseline, Then Changing Remote Signalling 1 to Closed from the Platform".
Required · Fill in: 1001=false
Second Platform TargetUsed to complete "Setting the Baseline, Then Changing Remote Signalling 1 to Closed from the Platform".
Required · Fill in: 1001=true

30. Confirming the New Remote Control Was Received After Recovery ​

Location: FMQX Web → Communication Records Steps: View the newly received frame at 02:06:08.622.

Confirming the new remote control was received after recovery

Received a new C_SC_NA_1/cause6, common address 1, 1001=true; distinguish it from the first false command.

31. Confirming the Second Remote Control Was Accepted ​

Location: FMQX Web → Communication Records Steps: View the newly sent activation confirmation at 02:06:08.623.

Confirming the second remote control was accepted

Returns C_SC_NA_1/cause7, 1001=true.

32. Confirming the Native End of the Second Remote Control ​

Location: FMQX Web → Communication Records Steps: View the activation termination frame at the same moment right after.

Confirming the native end of the second remote control

The device sends the activation termination confirmation, Remote Signalling 1=true; continue verifying the independent spontaneous report.

33. Independently Reporting the State After the Second Control Without Saving the Point Value ​

Location: FMQX Web → Remote Signalling Point and Communication Records Steps: Only select address 1001 and send telemetry without saving the point value, then verify the new 02:06:10.945 sent frame.

Independently reporting the state after the second control without saving the point value

The independent type1/cause3 report is 1001=true and forms actual history; the earlier manual false baseline cannot replace this proof.

7. Stopping Operation and Verifying the Retained State ​

The complete ten-point image was captured after the final stop and only illustrates the retained current values; it cannot replace the ten-sample baseline or the manual general interrogation proof.

34. Ending Send/Receive and Preserving the Session ​

Location: FMQX Web → This Article's Session Steps: Disconnect normally, and stop scheduled sending and auto reply.

Ending send/receive and preserving the session

Stop the controlled station listener and turn off auto sending, keeping the session and the point table.

35. Final Unpublish and Confirmation of Application ​

Location: Product Details → Unpublish and Sync Details Steps: Finally unpublish this article via the confirmation entry above, wait for node application, then verify the sync details.

Final unpublish and confirmation of application

The unpublish has been applied; the product, device, thing model, session, and history records are preserved.

36. Verifying the Ten-Point Current Values Retained After Stopping ​

Location: Device Details → Running Status → Real-time Metrics Steps: After stopping send/receive, read the ten remote signalling current values item by item.

Verifying the ten-point current values retained after stopping

All ten points are fully visible: 1001 and 1002 Closed; 1003, 1005, 1007, 1009 Closed, and 1004, 1006, 1008, 1010 Open. This image is the retained state after the end.

8. Filtering, Refreshing, and Verifying History Record by Record ​

The ten-sample query selects the ten remote signalling points, and each table row has a value only in the column of that record's address. The second window selects Remote Signalling 1, and the six records include two controls, two independent reports, one recovery publish state, and one manual baseline.

37. Filling in the Complete Time Range for the Ten Independent Remote Signalling Samples ​

Location: Data Center → Historical Data Steps: Fill in this query's complete start and end date-times.

Filling in the complete time range for the ten independent remote signalling samples

Fill in the complete start and end dates and times, covering the ten reports.

Screenshot Highlights ​

Field / ControlDescription
Start TimeUsed to complete "Filling in the Complete Time Range for the Ten Independent Remote Signalling Samples".
Required · Fill in: 2026-10-16 02:05:17
End TimeUsed to complete "Filling in the Complete Time Range for the Ten Independent Remote Signalling Samples".
Required · Fill in: 2026-10-16 02:05:31

38. Filtering This Article's Device and the Ten Remote Signalling Points ​

Location: Data Center → Historical Data Steps: Select this controlled station and Remote Signalling 1 to 10, verify the time conditions, then click Query.

Filtering this article's device and the ten remote signalling points

The device, fields, and previous complete time range stay consistent.

Screenshot Highlights ​

Field / ControlDescription
FieldsUsed to complete "Filtering This Article's Device and the Ten Remote Signalling Points".
Required · Fill in: Remote Signalling 1–10

39. Refreshing the Ten Independent Remote Signalling Sample History ​

Location: Data Center → Historical Data Steps: Keep the same device, fields, and time conditions, and click the refresh button at the top right of the result area.

Refreshing the ten independent remote signalling sample history

After refresh, there are 10 time records in total, each corresponding to one address.

40. Verifying the Ten Independent Remote Signalling Sample History Record by Record ​

Location: Data Center → Historical Data → Query Results Steps: Verify 1001 to 1010 row by row, by time and field; each row has a value only for that record's address, and the other fields are blank.

Verifying the ten independent remote signalling sample history record by record

02:05:18, 21, 22, 23, 24, 25, 26, 27, 28, 29 correspond to 1001 to 1010 in order, odd true and even false; blank means the record does not have that field, not false.

41. Filling in the Complete Time Range for the Remote Signalling 1 Control and Recovery ​

Location: Data Center → Historical Data Steps: Fill in this query's complete start and end date-times.

Filling in the complete time range for the Remote Signalling 1 control and recovery

Fill in the complete time range covering the two controls, the recovery, and the independent reports.

Screenshot Highlights ​

Field / ControlDescription
Start TimeUsed to complete "Filling in the Complete Time Range for the Remote Signalling 1 Control and Recovery".
Required · Fill in: 2026-10-16 02:05:41
End TimeUsed to complete "Filling in the Complete Time Range for the Remote Signalling 1 Control and Recovery".
Required · Fill in: 2026-10-16 02:06:13

42. Filtering This Article's Device and Remote Signalling 1 ​

Location: Data Center → Historical Data Steps: Select this controlled station and Remote Signalling 1, verify the time conditions, then click Query.

Filtering this article's device and Remote Signalling 1

The device, fields, and previous complete time range stay consistent.

Screenshot Highlights ​

Field / ControlDescription
FieldsUsed to complete "Filtering This Article's Device and Remote Signalling 1".
Required · Fill in: Remote Signalling 1

43. Refreshing the Remote Signalling 1 Control and Recovery History ​

Location: Data Center → Historical Data Steps: Keep the same device, fields, and time conditions, and click the refresh button at the top right of the result area.

Refreshing the Remote Signalling 1 control and recovery history

After refresh, there are 6 Remote Signalling 1 time records in total.

44. Verifying the Remote Signalling 1 Control and Recovery History Record by Record ​

Location: Data Center → Historical Data → Query Results Steps: Verify row by row the two controls, the post-control independent reports, the recovery publish state, and the manual baseline.

Verifying the Remote Signalling 1 control and recovery history record by record

02:05:42=false (first control state); 02:05:44=false (independent report); 02:05:58=false (recovery publish state); 02:06:03=false (manual baseline); 02:06:08=true (second control state); 02:06:10=true (independent report).

Where Parameters Come From and How to Fill Them ​

First Device Access Configuration ​

Field / ControlHow to Fill
First Modeling SampleThe historical JSON generates ten boolean models; the sample is odd false and even true and is not used as this round's report values.
Required · Fill in: Ten boolean fields
Device IdentityThe independent device number stays identical to the platform-bound clientId.
Required · Fill in: FastBee_IEC104_Tutorial_01

Platform Protocol Configuration and Publish ​

Field / ControlHow to Fill
Access Protocol and Data FormatFMQ connects to the controlled station as the master station, using native IEC104.
Required · Fill in: TCP / IEC 60870-5-104
Publish after changes.TCP / IEC 60870-5-104: Native IEC104 connects to the controlled station over TCP; use this article's native station address and point table.
Controlled Station IPThe platform binding fills in the controlled station's reachable listening IP; the local demo uses the loopback address.
Required · Fill in: 127.0.0.1
Publish after changes.
Controlled Station PortThe platform binding stays consistent with the imported controlled station's listening port.
Required · Fill in: 15040
Publish after changes.
Common AddressIdentifies the station; keep the platform binding and native messages consistent.
Required · Fill in: 1
Publish after changes.
Device BindingdeviceId 1244, clientId is this device's number; enable the binding.
Required · Fill in: 1244 / FastBee_IEC104_Tutorial_01
Publish after changes.
Information Object AddressTen independent remote signalling addresses; 1001 is this article's writable point.
Required · Fill in: 1001–1010; control 1001
Publish after changes.
Remote Signalling TypeSingle-point remote signalling maps to BOOLEAN; true is Closed, false is Open.
Required · Fill in: M_SP_NA_1 / BOOLEAN
Publish after changes.
Scale and OffsetThe boolean demo keeps scale 1 and offset 0, with the unit left blank.
Required · Fill in: 1 / 0
Publish after changes.
Historical Collection Group ConfigurationThe first configuration enabled general interrogation with a 60000-millisecond interval; this only describes the saved items and is not proof of a successful manual general interrogation in this round.
Required · Fill in: interrogationEnabled on; 60000 milliseconds
Publish after changes.
Single-Point Remote Control TemplateCommon address 1, information object address 1001, select-before-execute off, using direct execution.
Required · Fill in: C_SC_NA_1; selectBeforeExecute off
Publish after changes.
Publish and ApplicationStart the controlled station listener first, then publish and wait for the node to reach APPLIED.

First Thing Model Configuration ​

Field / ControlHow to Fill
Property Permission and HistoryAll ten items have history enabled; 1001 allows control, and the other nine items are read-only.
Required · Fill in: Ten boolean properties; 1001 writable
Publish after changes.

Historical Optional General Interrogation Configuration ​

Field / ControlHow to Fill
Historical Optional Station-Wide General InterrogationOnly the first whitelist configuration is kept for reference; this round did not re-save or execute a manual general interrogation.
Required · Fill in: Common address 1; address 0; C_IC_NA_1
Publish after changes.

FMQX Web Controlled Station ​

Field / ControlHow to Fill
First Imported ConfigurationThe IP, port, common address, and ten-point table are provided by the imported file; this round did not re-import.
Connection NameThe connection name visible in the current editor; read-only verification in this round.
Owning GroupThe group visible in the current editor; read-only verification in this round.
Save MethodThe current editor shows saving to this machine or for this use only; editing was cancelled in this round.
Start the Controlled StationAs a Server, listen on 15040 first, then the FMQ master station connects.
Reconnect after changes.
Connection and STARTDTVerify the role, station address, ten points, and 1 active connection.

Device Remote Signalling and Raw Frames ​

Field / ControlHow to Fill
Set Demo Point ValuesSave each of the ten-sample addresses once: odd true, even false; the recovery 1002=true and the second baseline 1001=false are saved separately by the operator.
Required · Fill in: 1001–1010 once each
Send TelemetrySend after saving the demo point value; wait for the platform to update before switching to the next address.
Raw FrameVerify by time the direction, type, cause code, station address, point address, and the complete HEX.

Platform Control and Feedback ​

Field / ControlHow to Fill
Platform Retained Current ValuesThe closing complete ten-point image was captured after the final stop; 1001 and 1002 are both Closed, and 1003 to 1010 remain odd Closed and even Open.
First Remote Signalling 1 ControlThis round controls from true to false; the screenshot shows true before writing.
Required · Fill in: 1001: Closed → Open断开: The first target false; sends the address 1001 single command.合上: This round's first pre-write value; verify the actual target with the native frames.
Native Remote Control Feedbackcause6 activation request, cause7 activation confirmation, cause10 activation termination; an independent remote signalling report follows.

Stop and Recovery ​

Field / ControlHow to Fill
Normal Stop and Explicit RecoveryUnpublish after a normal disconnect; to recover, start the controlled station first, then explicitly republish.
Reconnect after changes.
New Control After RecoveryThe operator first saves and sends the 1001=false baseline, then the platform controls true.
Required · Fill in: 1001: Open → Closed断开: The pre-write baseline set by the operator; must be described separately from the later remote control.合上: The second platform target; sends a new native single command.
Independent Report After ControlOnly select address 1001 and send telemetry without saving the point value; false the first time, true the second time.
End and PreserveFinally stop the controlled station and unpublish, keeping the product, device, model, session, and the queried history.
Reconnect after changes.

This Round's Historical Data ​

Field / ControlHow to Fill
History FilteringSelect this controlled station and Remote Signalling 1 to 10 for the ten samples; select only Remote Signalling 1 for the control-recovery window.
Complete Time RangeTen samples 02:05:17 to 02:05:31; control and recovery 02:05:41 to 02:06:13, all on 2026-10-16.
Record-by-Record History ValuesFor the ten samples, read the column corresponding to each row's address; the six Remote Signalling 1 rows are distinguished by source and are not called six controls.
Refresh ResultsKeep the device, fields, and complete time conditions, and click the refresh button at the top right of the result area.

Where to Check First When Problems Occur ​

SymptomPossible CauseWhere to Check FirstHow to Recover
Controlled station not connectedThe listener is not started, the endpoint does not match, or the current configuration is not appliedFirst verify this article's listening port 15040, then check the publish APPLIED status and STARTDTStart the original controlled station, explicitly republish, and wait for application before sending.
Remote signalling values or history do not correspondThe station address, point address, mapping, or time window is inconsistentVerify common address 1, 1001 to 1010, the boolean values, and this round's timesAfter fixing, send only one new point and verify the corresponding field.
The platform has control records but the result is unconfirmedThe native end and the independent state have not been verified yetAssociate cause6/7/10 with the subsequent independent type1/cause3Wait for the current command to end, only select the address and send telemetry, and do not manually save the point value.
The other history table columns are emptyThat report only contains one addressRead the value in the column of that record's addressContinue checking the independent rows for the other addresses.