Skip to content

DL/T 645-1997 Meter TCP Gateway Access and Controlled Write ​

This page is an online operation reference compiled from an existing operation manual. Operations marked as expected or not executed in the source material must still be verified against the actual environment.

Starting from copying a product, complete ten-point collection, controlled writes, independent read-back, history queries, and a safe stop for one FMQX demo meter.

Before you start: you already have a copyable 1997-edition TCP gateway product; this tutorial reuses its model and verifies each item; you have obtained access to the current platform, the FMQ gateway, and FMQX Web, plus the materials for this independent device; you hold product, device, model, protocol draft, publish, history query, and demo write permissions; writes target only the writable first point of the FMQX demo; a real device requires separate explicit manufacturer specifications and on-site authorization.

Understand This Access Flow Before You Start ​

This tutorial completes 1997-edition TCP gateway access with one FMQX demo meter: copy the product, verify the model, add the device, configure the protocol, publish, register, collect, write under control, query history, and stop safely.

Prepare a reusable product with the same protocol, the manufacturer's point table, and the connection address provided by the current environment first. The names and parameters in the screenshots are the actual values of this demonstration; fill in the device number, addresses, grouping, and authorization fields according to your own on-site materials.

This tutorial shows the actual journey of a local single node with the FMQX demo meter; it has not yet undergone a real novice read-through or version-specific acceptance.

Relationship Between Configuration, Collection, and Writing

This is a functional relationship diagram for understanding the responsibilities of each component, not a screenshot of the running platform.

Replace These Parameters Before Copying the Templates ​

This tutorial's code uses generic template names; the screenshots keep the actual historical resources. Complete the following checks before saving as a UTF-8 file or sending frames.

  • In the YAML, device is the session alias of this flow; demo-session-id must be replaced with the real ID of this tutorial's target session via session binding, while the session of the action nodes stays device.
  • Paste the full definition first, validate it, and save the version; saving only proves the configuration was saved — verify the run and device results separately per the steps.
  • demo-device is the device number template. Replace the device number in clientId, the device number in every publish/subscribe topic, and the clientId of TCP reports together with the platform device number for this device; the product ID and tenant ID in the MQTT identity must also be replaced with the current device connection parameters.
  • 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; enter passwords only securely on the connection page.
  • The group, session, and subscription ids are internal references of the import file; if you rename them, groupId must match the corresponding group id. Verify before importing, and do not create a duplicate connection 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 been proven to import successfully. Historical screenshots, send times, and business pass scope still follow the records in each step; do not treat template names as the actual resource names in the old evidence.

Copy the Product and Prepare an Independent Draft ​

This tutorial starts by copying a retained product. Preview the existing protocol and feature definition first, then save the independent product; this tutorial is not written as a field-by-field creation from scratch.

1. Select Copy Product ​

Where: Device Management → Device Access Steps: On the Device Access page, select Copy Product.

Select Copy Product

The Copy Product card is selected.

2. Specify the Source Product and the New Name ​

Where: Device Management → Device Access Steps: Select the source product and enter the new product name for this round.

Specify the source product and the new name

Both the source product and the new name are filled in.

3. Verify the Source Product ​

Where: Device Management → Device Access Steps: Open Preview Product and verify the product name.

Verify the source product

The preview shows the source product selected this time.

4. Verify the Source Product Protocol ​

Where: Device Management → Device Access Steps: Check the source product's protocol and device type.

Verify the source product protocol

It is the 1997 edition, TCP gateway, and gateway device.

5. View the Existing Collection Properties ​

Where: Device Management → Device Access Steps: In the upper half of the feature definition, verify the existing properties.

View the existing collection properties

The energy properties this tutorial needs to reuse are visible.

6. Verify the Remaining Collection Properties ​

Where: Device Management → Device Access Steps: Scroll the preview and verify Energy 4 through 10.

Verify the remaining collection properties

All ten collection properties can be found.

7. Confirm the 1997 Edition and TCP Gateway ​

Where: Device Management → Device Access Steps: Return to the wizard and verify the protocol and transport mode.

Confirm the 1997 edition and TCP gateway

The protocol is the 1997 edition and the transport mode is TCP gateway.

8. Prepare the Product First ​

Where: Device Management → Device Access Steps: Select Prepare product only, do not create a device yet.

Prepare the product first

This round only prepares the product draft.

9. Verify the Optional Product Information ​

Where: Device Management → Device Access Steps: Expand Advanced Configuration and verify the category and device type against the figure.

Verify the optional product information

This tutorial uses a gateway device; firmware is not filled in.

10. Verify the Wizard Summary ​

Where: Device Management → Device Access Steps: Go to the confirmation page and review Configuration Pre-check.

Verify the wizard summary

The configuration pre-check passed; no device is added yet.

11. Save the Product Draft ​

Where: Device Management → Device Access Steps: Click Save Product Draft.

Save the product draft

Submit this tutorial's independent product draft.

12. Confirm the Product Has Been Saved ​

Where: Device Management → Device Access Steps: Review the preparation result after saving.

Confirm the product has been saved

The page shows the product draft has been saved.

13. Open the New Product ​

Where: Device Management → Device Access Steps: Open the newly saved product and verify its name.

Open the new product

The new product is unpublished, and its access configuration is pending activation.

Device Management → Device Access ​

Field / ControlFilling Notes
Access SourceDetermines the starting point of this access.
Optional · Value: Copy ProductCopy Product: determines the starting point of this access; this tutorial copies the retained old-meter product.
Copy ProductSelects the source product that provides the feature definition.
Required · Value: fill in per your environment
Select an existing product with the same protocol from Product Management. Current batch resource: selects the source product that provides the feature definition; preview the protocol, gateway type, and ten collection properties first.
Product NameNames the independent product copied this time.
Required · Value: fill in per your environment
Named by the person performing this access, according to its purpose.
Preview ProductViews the source product's identity and feature definition.
ProtocolDefines the meter frame format and data identifier length.
Required · Value: DLT645_1997
From the meter nameplate and manufacturer protocol documentation. DLT645_1997: defines the meter frame format and data identifier length; the 1997 edition is used consistently throughout and must not be mixed with the 2007 edition.
Transport ModeAccesses the meter over a connection actively established by the gateway.
Required · Value: TCP_GATEWAY
From the actual gateway access method. TCP_GATEWAY: accesses the meter over a connection actively established by the gateway; this tutorial selects TCP gateway, and the gateway device type must match.
Prepare product only, do not create a device yetSave the product draft first and add the device separately later.
Optional · Value: SelectedOn: enables this option; save the product draft first and add the device separately later. Off: disables this option; the behavior is not enabled.
NextEnters the next stage and verifies the summary.
PreviousReturns to the previous step to fix unsubmitted configuration.
Configuration Pre-checkShows whether the product draft meets the submission conditions.
Save Product DraftCreates this tutorial's independent product draft.
Product Draft SavedShows the product preparation result.

Advanced parameters (4 items)

Field / ControlFilling Notes
Advanced ConfigurationExpands the product category, type, firmware, and other information.
Product CategoryClassifies the product for business purposes.
Required · Value: Uncategorized
From the current platform's category dictionary. Uncategorized: classifies the product for business purposes; this tutorial keeps it uncategorized, and other projects choose per their management practice.
Device TypeDetermines the role of devices under the product.
Required · Value: Gateway Device
From the actual gateway role. Gateway Device: determines the role of devices under the product; this tutorial uses the same device to represent the transparent gateway.
Firmware VersionRecords the device firmware information.
Required · Value: left blank
From the manufacturer's firmware documentation.

Verify the Ten Collection Properties ​

The model identifier is the fixed key for the later point mapping. The first point is used for the FMQX demo write; clearing read-only also turns off the chart and real-time monitoring; all ten fields keep history storage.

14. Verify the First Point's Name and Identifier ​

Where: Product Details → Feature Definition Steps: In Feature Definition, open Energy 1 and verify the name, translation, and model identifier.

Verify the first point's name and identifier

The first point corresponds to this tutorial's demo point table.

15. Prepare the Writable Demo First Point ​

Where: Product Details → Feature Definition Steps: Clear read-only on the first point, verify that the chart and Real-Time Monitoring are turned off together, and keep History Storage.

Prepare the writable demo first point

The first point can enter controlled writing and still keeps history.

16. Verify the First Point's Numeric Range ​

Where: Product Details → Feature Definition Steps: Verify the Decimal type, range, step, and unit.

Verify the first point's numeric range

Decimal, range 0 to 99999999, step 1, unit empty.

17. Save the First Point's Property ​

Where: Product Details → Feature Definition Steps: Click Modify.

Save the first point's property

Submit the current modification of the first point's property.

18. Return to the First Point's Property List ​

Where: Product Details → Feature Definition Steps: View the Energy 1 property row returned after saving.

Return to the first point's property list

It is still Energy 1 in this tutorial's product.

19. Verify the Second Point's Property ​

Where: Product Details → Feature Definition Steps: Open Energy 2 and verify the name, translation, and identifier.

Verify the second point's property

Energy 2 corresponds to the second data identifier.

20. Keep the Remaining Points Read-Only ​

Where: Product Details → Feature Definition Steps: Verify the second point keeps read-only, chart, Real-Time Monitoring, and History Storage.

Keep the remaining points read-only

This point is used in read-only collection mode.

21. Verify the Energy 3 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 3 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 3 property

Energy 3 corresponds to data identifier 9012.

22. Verify the Energy 4 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 4 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 4 property

Energy 4 corresponds to data identifier 9013.

23. Verify the Energy 5 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 5 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 5 property

Energy 5 corresponds to data identifier 9014.

24. Verify the Energy 6 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 6 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 6 property

Energy 6 corresponds to data identifier 9015.

25. Verify the Energy 7 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 7 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 7 property

Energy 7 corresponds to data identifier 9016.

26. Verify the Energy 8 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 8 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 8 property

Energy 8 corresponds to data identifier 9017.

27. Verify the Energy 9 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 9 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 9 property

Energy 9 corresponds to data identifier 9018.

28. Verify the Energy 10 Property ​

Where: Product Details → Feature Definition Steps: Open Energy 10 and verify this tutorial's name, translation, and model identifier.

Verify the Energy 10 property

Energy 10 corresponds to data identifier 9019.

Product Details → Feature Definition ​

Field / ControlFilling Notes
Feature DefinitionViews and adjusts the copied model.
Model NameProvides a readable name for each collected value.
Required · Value: fill in per your environment
From the manufacturer's point table and this demonstration's naming.
Republish after changes.
Model IdentifierThe fixed key for point mapping and data display.
Required · Value: fill in per your environment
From the current product's feature definition.
Republish after changes.
Model CategoryDistinguishes properties, functions, and events.
Optional · Value: Property
Republish after changes. Property: distinguishes properties, functions, and events; all ten points in this tutorial are properties.
Chart DisplayControls chart display; enabling it requires read-only.
Optional · Value: off for the first point, on for the other nine
Republish after changes. On: enables this option; controls chart display; enabling it requires read-only. Off: disables this option; the behavior is not enabled.
Real-Time MonitoringControls read-only monitoring display, linked with read-only.
Optional · Value: off for the first point, on for the other nine
Republish after changes. On: enables this option; controls read-only monitoring display, linked with read-only. Off: disables this option; the behavior is not enabled.
Read-Only DataRestricts whether the property can be written from the device control entry.
Optional · Value: off for the first point, on for the other nine
From the range of operations the real device allows.
Republish after changes. On: enables this option; restricts whether the property can be written from the device control entry. Off: disables this option; the behavior is not enabled.
History StorageAllows the property to keep historical records.
Optional · Value: On
Republish after changes. On: enables this option; allows the property to keep historical records. Off: disables this option; the behavior is not enabled.
Data TypeDetermines which numeric type the model uses to receive data.
Required · Value: Decimal
From the manufacturer's point table and the decoding result.
Republish after changes. Decimal: determines which numeric type the model uses to receive data; this tutorial uses Decimal, which must be compatible with the mapping format.
MinimumConstrains the lower bound of usable values for the model.
Required · Value: 0
From the manufacturer's field range.
Republish after changes.
MaximumConstrains the upper bound of usable values for the model.
Required · Value: 99999999
From the manufacturer's field width and range.
Republish after changes.
StepDefines the increment per adjustment of the control.
Required · Value: 1
Republish after changes.
UnitAdds a dimension to the property.
Required · Value: left blank
From the manufacturer's point table.
Republish after changes.
ModifySaves the current property modification.
Republish after changes.
CancelDiscards the current unsubmitted modification.
Property ListShows the models currently saved in the product.
From the current product query result.

Advanced parameters (3 items)

Field / ControlFilling Notes
Model TranslationSaves the translation configuration of the current model.
Required · Value: meter_9010 to meter_9019
Follows the actual configuration of the model copied in this tutorial.
Republish after changes.
Sharing PermissionControls sharing-related flags and does not determine the collection chain.
Optional · Value: was selected in the form
From the platform's sharing permission requirements.
Republish after changes. On: enables this option; controls sharing-related flags and does not determine the collection chain. Off: disables this option; the behavior is not enabled.
Calculation FormulaUsed for calculation conversion at the model layer.
Required · Value: the screenshot only shows the label
From business calculation needs and the current model configuration.
Republish after changes.

Add This Tutorial's Gateway Device ​

The device number is used for connection registration, and the meter number identifies the meter in the connection. After selecting the product, re-verify the device number, then save the device.

29. Manually Add This Tutorial's Device ​

Where: Device Management → Access Device → Add Manually Steps: In the Access Device menu, click Add Manually.

Manually add this tutorial's device

The new device form opens.

30. Select This Tutorial's New Product ​

Where: Device Management → Access Device → Add Manually Steps: On the Product Select page, select the newly saved product.

Select this tutorial's new product

This tutorial's new product is selected.

31. Confirm the Product ​

Where: Device Management → Access Device → Add Manually Steps: Click Confirm Selected Product.

Confirm the product

Return to the device form with this tutorial's product carried over.

32. Complete the Device Name and Number ​

Where: Device Management → Access Device → Add Manually Steps: Enter this tutorial's device name and device number, and verify the product.

Complete the device name and number

Name, product, and number are all complete.

33. Save the New Device ​

Where: Device Management → Access Device → Add Manually Steps: Click OK.

Save the new device

Submit this tutorial's new device.

34. Confirm the Device Has Been Created ​

Where: Device Management → Access Device → Add Manually Steps: View the device card and verify the name, protocol, and product.

Confirm the device has been created

This tutorial's device exists but is not yet activated.

Device Management → Access Device → Add Manually ​

Field / ControlFilling Notes
Add ManuallyOpens the new device form.
Device NameDistinguishes this device with a short name.
Required · Value: fill in per your environment
Named by the person performing the access, according to its purpose.
ProductAssociates the device with this tutorial's new product.
Required · Value: fill in per your environment
From the platform product list. Current batch resource: associates the device with this tutorial's new product; select the newly copied product, then re-verify the device number.
SelectOpens the product selection page.
Confirm Selected ProductBrings the selected product back to the device form.
Device NumberThe platform uses this number to identify the gateway connection.
Required · Value: copy from this tutorial's device materials
From the device number in the platform device details.
OKSaves this tutorial's new device.
CloseExits the unsubmitted device form.
Device StatusShows the current device registration and connection status.
From the device query result.

Advanced parameters (6 items)

Field / ControlFilling Notes
GenerateGenerates a new device number.
Generated by the platform.
Firmware VersionRecords the device firmware version.
Required · Value: the actual value was not fully verified; fill in per the current device materials
From the manufacturer's device materials.
Positioning MethodControls the source of the device location.
Required · Value: the actual value was not fully verified; fill in per the current device materials
From the device installation method. Actual options pending verification: this selection control is visible in the source code, but the actual options were not fully observed; choose per the current tenant and device materials; this tutorial does not provide an environment value to copy.
Device OrganizationDetermines the business ownership of the device.
Required · Value: the actual value was not fully verified; fill in per the current device materials
From this tenant's organization configuration. Actual options pending verification: this selection control is visible in the source code, but the actual options were not fully observed; choose per the current tenant and device materials; this tutorial does not provide an environment value to copy.
Device SpaceAssociates the space the device belongs to.
Required · Value: the actual value was not fully verified; fill in per the current device materials
From this tenant's space configuration. Actual options pending verification: this selection control is visible in the source code, but the actual options were not fully observed; choose per the current tenant and device materials; this tutorial does not provide an environment value to copy.
Device ShadowControls shadow behavior while offline.
Optional · Value: the actual value was not fully verified; fill in per the current device materialsOn: enables this option; controls shadow behavior while offline. Off: disables this option; the behavior is not enabled.

Bind the Device, Gateway, and Meter Number ​

This tutorial carries this demo meter on the same platform gateway device. In a real project, select the gateway according to the actual topology, and do not treat the meter address as the device number.

35. Enter the Meter Protocol Configuration ​

Where: Product Details → Protocol Configuration → Device Binding Steps: Open Protocol Configuration in this tutorial's product.

Enter the meter protocol configuration

The device binding, polling, mapping, and policy entries are visible.

36. Fill In the Gateway and Meter Number Binding ​

Where: Product Details → Protocol Configuration → Device Binding Steps: Select this tutorial's device and real gateway, enter the meter number, verify the protocol, and enable it.

Fill in the gateway and meter number binding

The device, gateway, and meter number match this tutorial's meter.

37. Save the Binding Draft ​

Where: Product Details → Protocol Configuration → Device Binding Steps: Click Save Draft.

Save the binding draft

Submit the current binding.

38. Verify the Binding List ​

Where: Product Details → Protocol Configuration → Device Binding Steps: Verify the saved device, gateway, meter number, and enabled status.

Verify the binding list

The list shows the correct binding for this tutorial's device.

Product Details → Protocol Configuration → Device Binding ​

Field / ControlFilling Notes
Device BindingSelects the device binding list.
Add ConfigurationOpens the binding draft form.
Republish after changes.
Platform DeviceDetermines the platform device that owns the data.
Required · Value: fill in per your environment
Select from the current product's device list.
Republish after changes. Current batch resource: determines the platform device that owns the data; select this tutorial's newly created device.
Device IdentifierAutomatically carried over from the selected device.
Auto-filled from the platform device record.
Real GatewaySpecifies the gateway that carries this meter's connection.
Required · Value: fill in per your environment
From the platform gateway device list.
Republish after changes. Current batch resource: specifies the gateway that carries this meter's connection; this tutorial uses the same gateway device and does not select other test connections.
Meter Number (12 digits)Determines the meter to access in the gateway connection.
Required · Value: 123456780998
From the meter address setting or manufacturer documentation.
Republish after changes.
Protocol VersionInherits the current product's meter protocol.
From the current product protocol.
EnableAllows this binding to be included when publishing.
Optional · Value: On
Republish after changes. On: enables this option; allows this binding to be included when publishing. Off: disables this option; the behavior is not enabled.
Save DraftSaves the current binding; not yet published.
Republish after changes.
Binding ListShows the binding save result.
From the current product binding query.

Configure the Ten Polling Items ​

Each data identifier gets its own polling item. This tutorial explicitly sets a 10-second interval, 3-second timeout, and zero retries; the defaults of the platform's new-item form are different.

39. Fill In the First Point's Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: Add a polling item and fill in the first point's parameters as shown.

Fill in the first point's polling

The first point reads every 10 seconds, with a 3-second timeout and 0 retries.

40. Save the First Point's Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: Click Save Draft.

Save the first point's polling

The first point's polling is written to the current product.

41. Verify the First Point's Polling Record ​

Where: Product Details → Protocol Configuration → Polling Items Steps: In the list, verify the first point's data identifier and collection parameters.

Verify the first point's polling record

The list shows this tutorial's actual polling record.

42. Save the Energy 2 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 2 polling

Energy 2 corresponds to 9011; the other collection parameters match the first point.

43. Save the Energy 3 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 3 polling

Energy 3 corresponds to 9012; the other collection parameters match the first point.

44. Save the Energy 4 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 4 polling

Energy 4 corresponds to 9013; the other collection parameters match the first point.

45. Save the Energy 5 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 5 polling

Energy 5 corresponds to 9014; the other collection parameters match the first point.

46. Save the Energy 6 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 6 polling

Energy 6 corresponds to 9015; the other collection parameters match the first point.

47. Save the Energy 7 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 7 polling

Energy 7 corresponds to 9016; the other collection parameters match the first point.

48. Save the Energy 8 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 8 polling

Energy 8 corresponds to 9017; the other collection parameters match the first point.

49. Save the Energy 9 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 9 polling

Energy 9 corresponds to 9018; the other collection parameters match the first point.

50. Save the Energy 10 Polling ​

Where: Product Details → Protocol Configuration → Polling Items Steps: After verifying the current field parameters in the figure, click Save Draft.

Save the Energy 10 polling

Energy 10 corresponds to 9019; the other collection parameters match the first point.

Product Details → Protocol Configuration → Polling Items ​

Field / ControlFilling Notes
Polling ItemsViews this product's read schedule.
Add ConfigurationOpens a new polling draft.
Republish after changes.
Polling NameMakes it easier to select the formal polling item later in the mapping.
Required · Value: fill in per your environment
Named by the person performing the access, after the collection point.
Republish after changes.
Data Identifier DI (hexadecimal)Selects the data to read inside the meter.
Required · Value: 9010 to 9019
From the manufacturer's point table for this model; this tutorial uses the demo point table.
Republish after changes.
Protocol VersionInherits the current product protocol.
Carried over automatically from the product configuration.
Polling Interval (ms)Determines the period for repeated reads of the same field.
Required · Value: 10000
Republish after changes.
Timeout (ms)Limits how long one read waits for a response.
Required · Value: 3000
Republish after changes.
RetriesDetermines how many times a read is retried after a timeout.
Required · Value: 0
Republish after changes.
EnableAllows this polling item to be included when publishing.
Optional · Value: On
Republish after changes. On: enables this option; allows this polling item to be included when publishing. Off: disables this option; the behavior is not enabled.
Save DraftSaves the polling item and returns the formal record.
Republish after changes.
Polling ListShows the saved polling items and their actual primary keys.
From the product polling query.

Advanced parameters (1 item)

Field / ControlFilling Notes
PrioritySaves the scheduling priority of the polling task.
Required · Value: 100
Republish after changes.

Map Formal Polling Items to Properties ​

The mapping must select the corresponding polling item and model from the platform's formal candidates. The multiplier, offset, unit, and encoding should come from the same manufacturer point table; this tutorial uses the demo point table.

51. Map Energy 1 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 1

Energy 1 corresponds to 9010; only this demo first point allows writing.

52. Map Energy 2 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 2

Energy 2 corresponds to 9011; this point stays read-only.

53. Map Energy 3 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 3

Energy 3 corresponds to 9012; this point stays read-only.

54. Map Energy 4 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 4

Energy 4 corresponds to 9013; this point stays read-only.

55. Map Energy 5 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 5

Energy 5 corresponds to 9014; this point stays read-only.

56. Map Energy 6 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 6

Energy 6 corresponds to 9015; this point stays read-only.

57. Map Energy 7 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 7

Energy 7 corresponds to 9016; this point stays read-only.

58. Map Energy 8 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 8

Energy 8 corresponds to 9017; this point stays read-only.

59. Map Energy 9 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 9

Energy 9 corresponds to 9018; this point stays read-only.

60. Map Energy 10 ​

Where: Product Details → Protocol Configuration → Point Mapping Steps: From the candidates, select the corresponding formal polling item and the energy property with the same sequence number; verify the parameters in the figure and click Save Draft.

Map Energy 10

Energy 10 corresponds to 9019; this point stays read-only.

Product Details → Protocol Configuration → Point Mapping ​

Field / ControlFilling Notes
Point MappingAssociates formal polling results with model properties.
Add ConfigurationOpens a mapping draft.
Republish after changes.
Formal Polling ItemSpecifies a saved polling record.
Required · Value: fill in per your environment
Select from the polling candidates returned by the platform query.
Republish after changes. Select the current batch resource corresponding to this field: specifies a saved polling record; verify the name and data identifier, and do not type or guess a primary key.
Thing Model FieldDetermines which property the parsed value is saved to.
Required · Value: fill in per your environment
From the current product's feature definition.
Republish after changes. Select the current batch resource with the same sequence number: determines which property the parsed value is saved to; Energy 1 corresponds to the first point, and the other nine correspond one by one.
Data Identifier DI (hexadecimal)Matches the data identifier of the selected formal polling item.
Required · Value: 9010 to 9019
Carried over from the formal polling selection and verified.
Republish after changes.
Protocol VersionInherits the product protocol version.
From the product configuration.
Data FormatDefines how the raw value is decoded.
Required · Value: BCD
From the manufacturer's point table and data encoding documentation.
Republish after changes. BCD: defines how the raw value is decoded; this tutorial selects BCD, and other encodings must not be interpreted directly as BCD.
MultiplierMultiplies the decoded result by a factor.
Required · Value: 1
From the manufacturer's decimal places and dimension documentation.
Republish after changes.
OffsetAdds an offset to the result after the multiplier is applied.
Required · Value: 0
From the manufacturer or business calculation documentation.
Republish after changes.
UnitStays consistent with the unit of the model property.
Required · Value: left blank
From the same model property and manufacturer documentation.
Republish after changes.
Allow WriteAllows this mapping to accept controlled writes.
Optional · Value: on for the first point only
From the write range explicitly allowed by the manufacturer.
Republish after changes. On: enables this option; allows this mapping to accept controlled writes. Off: disables this option; the behavior is not enabled.
EnableAllows this mapping to be published.
Optional · Value: On
Republish after changes. On: enables this option; allows this mapping to be published. Off: disables this option; the behavior is not enabled.
Save DraftSaves and validates the current mapping.
Republish after changes.

Advanced parameters (2 items)

Field / ControlFilling Notes
Value IndexSpecifies the value position in the response data.
Required · Value: 0
From the manufacturer's response data structure.
Republish after changes.
Write Device Specification or Official Scenario BasisRecords the specific basis that allows writing.
Required · Value: FMQX demo first point allows BCD writes
For a real device this comes from the manufacturer's formal documentation; in this tutorial it comes from the FMQX demo capability.
Republish after changes.

Set the Read and Demo Write Policies ​

Read and write policies are saved separately. 9010 is the FMQX demo writable field; it does not mean a real metering meter allows modifying its energy values; a real device must have an explicit manufacturer basis and on-site authorization.

61. Save the First Point's Read Policy ​

Where: Product Details → Protocol Configuration → Command Policy Steps: Verify the first point's read policy against the figure and click Save Draft.

Save the first point's read policy

Read, low risk, 3-second timeout, 0 retries, password requirement off.

62. Save the First Point's Write Policy ​

Where: Product Details → Protocol Configuration → Command Policy Steps: Verify the first point's write policy against the figure and click Save Draft.

Save the first point's write policy

Write, high risk, password required, 3-second timeout, and 0 retries.

Product Details → Protocol Configuration → Command Policy ​

Field / ControlFilling Notes
Command PolicySets the allowed reads and controlled writes.
Operation TypeDefines read and write policies separately.
Required · Value: READ_DATA,WRITE_DATA
From the operations the current device allows.
Republish after changes. READ_DATA: defines read and write policies separately; select READ_DATA for reads and WRITE_DATA for writes. WRITE_DATA: defines read and write policies separately; select READ_DATA for reads and WRITE_DATA for writes.
Data Identifier DI (hexadecimal)Restricts the policy to the demo first point.
Required · Value: 9010
From the enabled point mapping.
Republish after changes.
Protocol VersionInherits the product's meter protocol.
From the current product.
Risk LevelMarks the operation risk of the policy.
Required · Value: LOW,HIGH
Republish after changes. LOW: marks the operation risk of the policy; reads are LOW and writes are HIGH. HIGH: marks the operation risk of the policy; reads are LOW and writes are HIGH.
Allow Manual CommandsAllows this policy to be initiated from the manual operation entry.
Optional · Value: On
Republish after changes. On: enables this option; allows this policy to be initiated from the manual operation entry. Off: disables this option; the behavior is not enabled.
Allow Unified DownlinkAllows the platform's unified downlink entry to use this policy.
Optional · Value: On
Republish after changes. On: enables this option; allows the platform's unified downlink entry to use this policy. Off: disables this option; the behavior is not enabled.
Require Password ReferenceRequires the necessary authorization fields when writing.
Optional · Value: fill in per your environment
From the manufacturer's write specification and this authorization.
Republish after changes. On: enables this option; requires the necessary authorization fields when writing. Off: disables this option; the behavior is not enabled.
Timeout (ms)Limits the waiting time of a single policy invocation.
Required · Value: 3000
Republish after changes.
RetriesControls repeated attempts after a policy timeout.
Required · Value: 0
Republish after changes.
EnableAllows this policy to be published.
Optional · Value: On
Republish after changes. On: enables this option; allows this policy to be published. Off: disables this option; the behavior is not enabled.
Save DraftSaves the policy draft, waiting for the unified publish.
Republish after changes.

Prepare the FMQX Meter Connection ​

Import this tutorial's complete point table and edit the connection in FMQX Web. The gateway address is provided by this environment, and the client number is copied from the platform device number. The temporary password is not saved in the connection configuration.

**Complete connection and point JSON template (no password)**json

text
{

  "schemaVersion": 3,

  "groups": [

    {

      "id": "DLT97_TCPGW_Tutorial_02_group",

      "name": "旧表接入"

    }

  ],

  "sessions": [

    {

      "id": "DLT97_TCPGW_Tutorial_02_session",

      "groupId": "DLT97_TCPGW_Tutorial_02_group",

      "name": "接入旧表",

      "protocol": "DLT645_1997",

      "transport": "TCP",

      "host": "127.0.0.1",

      "port": 8888,

      "clientId": "demo-device",

      "autoReconnect": false,

      "dlt645MeterAddress": "123456780998",

      "dlt645IncludePreamble": false,

      "dlt645MaxFrameBytes": 1024,

      "dlt645Points": [

        {

          "dataIdentifier": "9010",

          "valueHex": "21000000",

          "writable": true

        },

        {

          "dataIdentifier": "9011",

          "valueHex": "22000000",

          "writable": false

        },

        {

          "dataIdentifier": "9012",

          "valueHex": "23000000",

          "writable": false

        },

        {

          "dataIdentifier": "9013",

          "valueHex": "24000000",

          "writable": false

        },

        {

          "dataIdentifier": "9014",

          "valueHex": "25000000",

          "writable": false

        },

        {

          "dataIdentifier": "9015",

          "valueHex": "26000000",

          "writable": false

        },

        {

          "dataIdentifier": "9016",

          "valueHex": "27000000",

          "writable": false

        },

        {

          "dataIdentifier": "9017",

          "valueHex": "28000000",

          "writable": false

        },

        {

          "dataIdentifier": "9018",

          "valueHex": "29000000",

          "writable": false

        },

        {

          "dataIdentifier": "9019",

          "valueHex": "30000000",

          "writable": false

        }

      ]

    }

  ]

}

After verifying against the replacement checklist, save it as a UTF-8 file named 连接配置.json (connection configuration) and choose Import Configuration in FMQX Web; this rewrite of the body 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.

63. Import This Tutorial's Meter Configuration ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: After verifying this section's complete JSON against the replacement checklist, save it as a UTF-8 file named 连接配置.json (connection configuration), then in FMQX Web choose Import Configuration under More Actions. The original step's screenshot keeps the original batch operation.

Import this tutorial's meter configuration

This tutorial's single meter and complete point table are imported.

64. Select the Imported Meter ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Click this tutorial's meter card and verify the name and the 1997-edition mark.

Select the imported meter

The current one is this tutorial's disconnected meter session.

65. Verify the Meter Protocol ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Open this tutorial's connection editor and verify the 1997-edition protocol card.

Verify the meter protocol

DL/T 645-1997 is selected.

66. Verify the Connection Name and Group ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Verify this tutorial's connection name, group, and Save to Local.

Verify the connection name and group

The connection is saved in this tutorial's group.

67. Fill In the Gateway Address and Client Number ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Enter this round's FMQ gateway address and port, and copy the device number from the platform as the client number.

Fill in the gateway address and client number

The address is reachable, and the client number matches the platform device number.

68. Save the First Point's Initial Value Once ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Verify the meter address and the first point, temporarily enter the encoding of 20, then Save Changes.

Save the first point's initial value once

The first point uses the initial encoding of 20, and the full ten points are kept.

69. Reopen to Verify the Saved Value ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Reopen this tutorial's connection editor and view the first point's initial value.

Reopen to verify the saved value

The initial value is still the encoding of 20 just saved.

70. Restore the Formal Sampling Starting Point ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Change the first point's initial value back to the encoding of 21.

Restore the formal sampling starting point

The first point's initial value is 21000000.

71. Save the Connection Preparation Result ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Click Save Changes.

Save the connection preparation result

This tutorial's connection definition is saved and waits for registration after publishing.

FMQX Web → This Tutorial's Meter → Edit Connection ​

Field / ControlFilling Notes
Import ConfigurationImports this tutorial's single-meter connection and complete point table.
From this tutorial's accompanying connection configuration.
This Tutorial's Meter SessionSelects the current meter connection.
From the connection just imported.
Select ProtocolDetermines the protocol version of the FMQX demo meter.
Required · Value: DL/T 645-1997
From the platform product and manufacturer documentation.
Reconnect after changes. DL/T 645-1997: determines the protocol version of the FMQX demo meter; this tutorial edits the imported 1997 meter and does not use the cancelled new-connection preview.
Connection NameDistinguishes connections in FMQX.
Required · Value: fill in per your environment
Named by the person performing this access, according to its purpose.
GroupPlaces the connection into this tutorial's group.
Required · Value: fill in per your environment
From the current FMQX groups. Current batch resource: places the connection into this tutorial's group; only operate this one meter in this tutorial's group.
Save MethodDetermines how the connection configuration is retained.
Optional · Value: Save to LocalSave to Local: determines how the connection configuration is retained; this tutorial saves locally, and the password is still kept only in the current session memory.
FMQ Gateway HostSpecifies the FMQ gateway address FMQX connects to.
Required · Value: 127.0.0.1
Provided by the current test environment or the operations staff.
Reconnect after changes.
FMQ Gateway PortSpecifies the corresponding gateway listening port.
Required · Value: 8888
From the current FMQ gateway configuration.
Reconnect after changes.
TCP Gateway Client NumberLets the platform identify the current gateway device at registration.
Required · Value: copied from the platform device number
From the device number of this tutorial's platform device.
Reconnect after changes.
Meter AddressDetermines the meter simulated by FMQX.
Required · Value: 123456780998
From the meter address bound in this tutorial's platform.
Reconnect after changes.
Data IdentifierEdits the first point in the complete point table.
Required · Value: 9010
From this tutorial's demo point table.
Initial Value HexSets the raw BCD data of the first point in the connection definition.
Required · Value: 21000000
From this tutorial's encoding of the demo value 21.
Write PermissionAllows the first point to accept platform writes after temporary authorization.
Required · Value: allow platform writes (this round's authorization still required)
From the demo meter capability and the current authorization. Allow platform writes (this round's authorization still required): allows the first point to accept platform writes after temporary authorization; enabled only for the FMQX first point, the other nine points are read-only.
Save ChangesSaves the connection definition and keeps the complete point table.
Save and ConnectAttempts to connect immediately after saving.
CancelDiscards the unsubmitted connection edits.
Meter Data PointViews the specified point in the current complete point table.
Required · Value: 9010 to 9019
From the imported ten-point configuration. 9010 to 9019: views the specified point in the current complete point table; the first point is writable and the other nine are read-only.
Current Value HexShows the raw value currently inside the device.
From the current FMQX demo meter state.
Refresh Real Point TableRe-reads the device's current point table state.

Advanced parameters (1 item)

Field / ControlFilling Notes
Maximum Frame LengthLimits the length of frames that can be processed.
Required · Value: 1024

Validate, Publish, and Verify Runtime Adoption ​

Draft validation, the platform accepting the publish, and the runtime node adopting it are three different results. Finally, verify that the current node's receipt is APPLIED with no failure reason.

72. Validate This Tutorial's Protocol Draft ​

Where: Product Details → Publish and Sync Details Steps: Click Validate Publish Configuration.

Validate this tutorial's protocol draft

The draft validation passed, with a prompt to publish from the top of the product.

73. Verify the Sampling Starting Point ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: In Meter Data Point, view the first point's initial value and current value.

Verify the sampling starting point

Both are the encoding of 21; writing still requires this round's authorization.

74. Publish This Tutorial's Product ​

Where: Product Details → Publish and Sync Details Steps: Click Publish Product at the top of this tutorial's product.

Publish this tutorial's product

The product publish confirmation box opens.

75. Confirm the Product Publish ​

Where: Product Details → Publish and Sync Details Steps: After verifying the current publish target, click OK.

Confirm the product publish

This product publish is submitted.

76. View the Publish Feedback ​

Where: Product Details → Publish and Sync Details Steps: View and close the Operation Succeeded prompt.

View the publish feedback

The platform has accepted this publish action.

77. Verify the Product Has Taken Effect ​

Where: Product Details → Publish and Sync Details Steps: View the publish and Access Configuration status at the top of this tutorial's product.

Verify the product has taken effect

The product is published, and the access configuration has taken effect.

78. Verify the Runtime Node Receipt ​

Where: Product Details → Publish and Sync Details Steps: Open Sync Details and view the node result and failure reason.

Verify the runtime node receipt

This node's result is APPLIED, and the failure reason is empty.

Product Details → Publish and Sync Details ​

Field / ControlFilling Notes
Validate Publish ConfigurationChecks whether the current protocol draft can be published.
Draft Validation PassedIndicates this tutorial's draft passes the publish validation.
Publish ProductPublishes the current product configuration to the runtime plane.
OKConfirms the current publish action.
Operation SucceededIndicates the platform has accepted the publish action.
Access ConfigurationShows the product's latest runtime sync status.
Sync DetailsViews the runtime node's feedback on this publish.
Runtime Node ResultIndicates the runtime node has adopted this configuration.
From the node receipt of this publish.

Connect and Register This Meter ​

Verify the connect, default registration, and wait nodes first, then run the access registration flow. After successful registration, wait for the platform's normal polling.

Prepare this tutorial's registration flow: open "Automation Testing" → "YAML" in the FMQX top bar, paste the definition below in full, click "Validate" and then "Save Version". Then, in session binding, point device to this tutorial's newly imported and verified session; after verifying the run nodes and current status, click Run per the following steps. Do not use the import flow file button here.

Complete YAML template for 1997 meter access registrationyaml

text
schemaVersion: 2

id: DLT97GW_Tutorial_Registration_02

name: 接入注册

description: 仅连接本篇旧版电表TCP网关,先发送平台默认身份注册包,再等待真实轮询。保留会话供手动读写。

tags: []

variables: {}

requiredEnvironment: []

sessions:

  device:

    sessionId: demo-session-id

    isolation: existing

steps:

- id: connect

  kind: action

  enabled: true

  action: session.connect

  session: device

  timeoutMs: 10000

  retries: 0

  continueOnFailure: false

  repeat: 1

  format: Text

  qos: 0

  retain: false

  durationMs: 0

  maxConcurrency: 1

  parameters: {}

  assertions: []

  steps: []

  else: []

  parallel: []

- id: registration

  kind: action

  enabled: true

  action: registration.default.send

  session: device

  timeoutMs: 10000

  retries: 0

  continueOnFailure: false

  repeat: 1

  format: Text

  qos: 0

  retain: false

  durationMs: 0

  maxConcurrency: 1

  parameters: {}

  assertions: []

  steps: []

  else: []

  parallel: []

- id: wait_poll

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 3000

  retries: 0

  continueOnFailure: false

  repeat: 1

  format: Text

  qos: 0

  retain: false

  durationMs: 1500

  maxConcurrency: 1

  parameters: {}

  assertions: []

  steps: []

  else: []

  parallel: []

finally: []

Use the YAML page to paste, validate, and save the version; bind device to this tutorial's meter. Replaceable customer template names are used here; verify against this section's replacement checklist before importing or sending.

79. Verify the Access Registration Flow ​

Where: FMQX Web → Testing → Access Registration Flow Steps: In Automation Testing → YAML, paste the access registration definition above in full, validate it, and save the version; on the Flow page, verify the connect, default registration, and wait nodes, plus the device session binding.

Verify the access registration flow

The three nodes are in the correct order.

80. Verify the Registration Node ​

Where: FMQX Web → Testing → Access Registration Flow Steps: Select the registration node and verify the action, session alias, and timeout.

Verify the registration node

The default registration action is bound to this tutorial's device session.

81. Run the Access Registration ​

Where: FMQX Web → Testing → Access Registration Flow Steps: Click Run.

Run the access registration

This tutorial's connect, registration, and wait process begins.

82. Confirm the Access Flow Passed ​

Where: FMQX Web → Testing → Access Registration Flow Steps: View the three nodes in the Run Console.

Confirm the access flow passed

Connect, registration, and wait all passed.

FMQX Web → Testing → Access Registration Flow ​

Field / ControlFilling Notes
FlowViews the visualized nodes of the access registration.
Node PropertiesShows the configuration of the currently selected flow node.
From this tutorial's registration flow.
ActionSends the default registration identity frame.
Required · Value: Common / Send FMQ default registration bytes
From this tutorial's protocol test action. Common / Send FMQ default registration bytes: sends the default registration identity frame; use the default registration action to avoid writing the registration identity incorrectly.
Session AliasBinds the flow action to this tutorial's meter session.
Required · Value: device
From the session settings of this tutorial's test flow.
Timeout (ms)Limits the waiting time of the registration flow action.
Required · Value: 10000
RunExecutes this tutorial's registration flow.
Run ConsoleShows the connect, registration, and wait results separately.
From this actual run.

Observe Continuous Ten-Point Collection ​

The first point changes step by step from 21 to 30, while the other nine stay at 22 through 30. When polls are staggered, the history table places different fields on different time rows; the number of merged time rows does not equal the number of field records.

83. View the Platform's First Point 21 ​

Where: FMQX Web → Testing and Connection Status Steps: Return to this tutorial's device details and view Energy 1.

View the platform's first point 21

The platform's current value is 21.

Prepare this tutorial's continuous sampling flow: open "Automation Testing" → "YAML" in the FMQX top bar, paste the definition below in full, click "Validate" and then "Save Version". Then, in session binding, point device to this tutorial's newly imported and verified session; after verifying the run nodes and current status, click Run per the following steps. Do not use the import flow file button here.

Complete YAML template for continuous sampling of the 1997 meteryaml

text
schemaVersion: 2

id: DLT97GW_ContinuousSamples_v1_02

name: 连续旧表采集

description: 本篇1997演示电表按已发布10秒轮询周期采集首点21至30,保留其余九点及写权限。

tags: []

variables: {}

requiredEnvironment: []

sessions:

  device:

    sessionId: demo-session-id

    isolation: existing

steps:

- id: set_22

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 22 00 00 00

  assertions: []

- id: await_poll_22

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_23

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 23 00 00 00

  assertions: []

- id: await_poll_23

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_24

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 24 00 00 00

  assertions: []

- id: await_poll_24

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_25

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 25 00 00 00

  assertions: []

- id: await_poll_25

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_26

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 26 00 00 00

  assertions: []

- id: await_poll_26

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_27

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 27 00 00 00

  assertions: []

- id: await_poll_27

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_28

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 28 00 00 00

  assertions: []

- id: await_poll_28

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_29

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 29 00 00 00

  assertions: []

- id: await_poll_29

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

- id: set_30

  kind: action

  enabled: true

  action: dlt645.data.set

  session: device

  timeoutMs: 12000

  retries: 0

  repeat: 1

  continueOnFailure: false

  parameters:

    dataIdentifier: 90 10

    valueHex: 30 00 00 00

  assertions: []

- id: await_poll_30

  kind: action

  enabled: true

  action: delay

  session: device

  timeoutMs: 15000

  retries: 0

  repeat: 1

  continueOnFailure: false

  durationMs: 11000

  parameters: {}

  assertions: []

finally: []

Use the YAML page to paste, validate, and save the version; bind device to this tutorial's meter. This flow runs from 22 to 30; first confirm that the first point 21 was collected in the previous section — the ten samples consist of 21 plus the nine subsequent values from this flow. Replaceable customer template names are used here; verify against this section's replacement checklist before importing or sending.

84. Run Continuous Sampling ​

Where: FMQX Web → Testing and Connection Status Steps: In Automation Testing → YAML, paste the continuous sampling definition above in full, validate it, and save the version, with device bound to this tutorial's meter; after confirming the first point 21 has been collected, click Run to continue producing 22 through 30.

Run continuous sampling

The first point starts changing step by step according to the flow.

85. Observe Sampling in Progress ​

Where: FMQX Web → Testing and Connection Status Steps: View the current flow's run progress.

Observe sampling in progress

The set-value and wait nodes continue executing.

86. Verify Continuous Sampling Completed ​

Where: FMQX Web → Testing and Connection Status Steps: View the console after the flow completes.

Verify continuous sampling completed

The complete run record shows this tutorial's flow has finished.

87. Verify the Platform Has Reached 30 ​

Where: FMQX Web → Testing and Connection Status Steps: View the current value of Energy 1 for this tutorial's device.

Verify the platform has reached 30

The first point's current value is 30.

FMQX Web → Testing and Connection Status ​

Field / ControlFilling Notes
RunExecutes this tutorial's continuous collection flow.
Run ConsoleShows the real flow progress.
From this run's result.
StopStops the currently running flow.
Platform Current ValueShows the value obtained by subsequent normal polling.
From the platform's current value for this device.
DisconnectStops this tutorial's meter connection.
Connection StatusShows the current session's connection status.
From comparing the current page with the actual session state.
Access Registration FlowRestores registration and polling after reconnecting.

Controlled Write, Disconnect Recovery, and Independent Read-Back ​

Configure the temporary authorization for the current session first, then demonstrate 61, the post-recovery 62, and 63 in turn. Submit only once each time, and verify the device's actual execution, the platform's real response, and the new normal read result separately. The platform's response prompt itself cannot replace proof of device execution.

88. Open the Demo First Point Write ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: On this tutorial's Energy 1 control card, open Meter Write.

Open the demo first point write

The write box shows this tutorial's target device and the required fields.

89. Configure Authorization for This Session ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: In this tutorial's FMQX session, enter the password and operator code through the authorization channel, then click Configure This Authorization.

Configure authorization for this session

It shows as configured, and the submitted inputs are cleared.

90. Confirm the Demo Write 61 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: Enter the native encoding of 61, the current authorization fields, and the reason, then Confirm Write once.

Confirm the demo write 61

Wait for this round's real protocol response; do not click repeatedly.

91. Verify the Device Actually Wrote 61 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: In FMQX, view this write's execution record.

Verify the device actually wrote 61

The actual execution count is 1, and the post-write value is 61.

92. Verify the Platform Response and the 61 Read-Back ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: View the platform's real protocol response prompt and the subsequent current value.

Verify the platform response and the 61 read-back

The platform received the response, and a new normal read shows 61.

93. Disconnect This Tutorial's Meter ​

Where: FMQX Web → Testing and Connection Status Steps: In this tutorial's FMQX session, click Disconnect.

Disconnect this tutorial's meter

The actual session is disconnected.

94. Verify the Disconnected Status After Refresh ​

Where: FMQX Web → Testing and Connection Status Steps: Refresh the same Chrome page and view this tutorial's session again.

Verify the disconnected status after refresh

Both the page and the real session show disconnected.

95. Run the Access Registration Again ​

Where: FMQX Web → Testing and Connection Status Steps: Run this tutorial's verified Access Registration Flow.

Run the access registration again

Connect, registration, and wait all passed.

96. Verify the Device Retains 61 ​

Where: FMQX Web → This Tutorial's Meter → Edit Connection Steps: Refresh the real point table and verify the first point's current value.

Verify the device retains 61

The connection initial value is still 21, and the current device value is 61.

97. Confirm the Demo Write 62 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: Enter the native encoding of 62, the current authorization fields, and the reason, then Confirm Write once.

Confirm the demo write 62

Wait for this round's real protocol response; do not click repeatedly.

98. Verify the Device Actually Wrote 62 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: In FMQX, view this write's execution record.

Verify the device actually wrote 62

The actual execution count is 2, and the post-write value is 62.

99. Verify the Platform Response and the 62 Read-Back ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: View the platform's real protocol response prompt and the subsequent current value.

Verify the platform response and the 62 read-back

The platform received the response, and a new normal read shows 62.

100. Confirm the Demo Write 63 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: Enter the native encoding of 63, the current authorization fields, and the reason, then Confirm Write once.

Confirm the demo write 63

Wait for this round's real protocol response; do not click repeatedly.

101. Verify the Device Actually Wrote 63 ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: In FMQX, view this write's execution record.

Verify the device actually wrote 63

The actual execution count is 3, and the post-write value is 63.

102. Verify the Platform Response and the 63 Read-Back ​

Where: Device Details → Device Control; FMQX Web → Current Session Write Authorization Steps: View the platform's real protocol response prompt and the subsequent current value.

Verify the platform response and the 63 read-back

The platform received the response, and a new normal read shows 63.

Device Details → Device Control; FMQX Web → Current Session Write Authorization ​

Field / ControlFilling Notes
Meter WriteOpens the controlled write box for the current writable first point.
Device Serial NumberConfirms the target device of this write.
From the current platform device details.
Write Data (hexadecimal)Provides the write content in the BCD encoding the demo meter allows.
Required · Value: 61000000, 62000000, 63000000
From this tutorial's demo field encoding specification.
Meter Password (8 hexadecimal digits)Provides the meter password for this write.
Required · Value: fill in per your environment
Provided by the device owner through a controlled channel.
Operator Code (8 hexadecimal digits)Provides the operator identity code for this write.
Required · Value: obtain through the authorization channel; not recorded in the document
Provided by the device owner through a controlled channel.
Write ReasonRecords the purpose of this write.
Required · Value: FMQX demo meter controlled write and independent read-back
Filled in by the current operator according to the actual purpose.
Confirm WriteSubmits one controlled write.
Configure This AuthorizationConfigures the temporary write authorization only within the current FMQX session.
From the authorization obtained for this round.
Current Session Write AuthorizationShows the authorization configuration status of the current session.
From the FMQX masked status.
Current Session Write Execution RecordShows the device execution count and the pre/post-write values.
From the FMQX device-side actual execution record.
Real Protocol ResponseIndicates the device protocol response has been processed by the platform.
From this command's reply.
Current ValueShows the current value brought by the subsequent normal read.
From this device's new read data.

Query the Sampling and Write History ​

Query after selecting this tutorial's device, variables, and the exact time window. The first point's 12 real samples include repeated 22 and 30; this is the actual collection result. The whole batch of ten points has 123 field records, merged by time into 67 rows on the page.

103. Enter Historical Data ​

Where: Data Center → Historical Data → Device Steps: Open Historical Data in Data Center and select the Device tab.

Enter Historical Data

The device history filter entry is visible.

104. Search for This Tutorial's Device ​

Where: Data Center → Historical Data → Device Steps: In the device dropdown, type this tutorial's device name.

Search for this tutorial's device

This tutorial's device candidate appears.

105. Select the Device and Expand the Filter ​

Where: Data Center → Historical Data → Device Steps: Select this tutorial's device and expand Advanced Filter.

Select the device and expand the filter

The current query target is this tutorial's device.

106. Open the Variable List ​

Where: Data Center → Historical Data → Device Steps: Expand the Variable Name candidates.

Open the variable list

This tutorial's energy properties can be selected.

107. Select the Ten Collection Fields ​

Where: Data Center → Historical Data → Device Steps: Select this tutorial's Energy 1 through 10.

Select the ten collection fields

The ten collection fields are selected.

108. Set the Sampling Time Window ​

Where: Data Center → Historical Data → Device Steps: Select the start and end time of this tutorial's sampling and confirm.

Set the sampling time window

The query window is 2026-10-15 10:44:25 to 10:46:30.

109. View the Ten-Point Collection Details ​

Where: Data Center → Historical Data → Device Steps: Click Query and verify the ten fields and their corresponding times.

View the ten-point collection details

All ten points have data, with different polling moments distributed across different time rows.

110. Verify the Query Range and Row Count ​

Where: Data Center → Historical Data → Device Steps: View the device, variables, and count in the history trend title.

Verify the query range and row count

This tutorial's device, the ten variables, and the 67 merged time rows are visible.

111. View the Ten-Point Trend ​

Where: Data Center → Historical Data → Device Steps: View the time trend of the ten fields.

View the ten-point trend

The first point goes from 21 up to 30 step by step, and the other nine keep their demo values.

112. Query Only the First Point ​

Where: Data Center → Historical Data → Device Steps: Change the variable selection to Energy 1 only, then Query.

Query only the first point

The history shows only this tutorial's first point.

113. Expand the Complete First Point Records ​

Where: Data Center → Historical Data → Device Steps: In Page Size, select 20 per page.

Expand the complete first point records

One page is enough to view this tutorial's 12 first-point records.

114. Verify the Complete First Point Changes ​

Where: Data Center → Historical Data → Device Steps: View all current history rows of the first point.

Verify the complete first point changes

The first point's 21 through 30 are fully visible, with 22 and 30 each appearing twice.

115. Set the First Write Window ​

Where: Data Center → Historical Data → Device Steps: Select the times before and after the first write and confirm.

Set the first write window

The range covers 30 before the write and 61 after it.

116. Verify 30 Changed to 61 ​

Where: Data Center → Historical Data → Device Steps: Query the first point's history in the first write window.

Verify 30 changed to 61

30 before the write, and the subsequent normal collection is 61.

117. Set the Post-Recovery Write Window ​

Where: Data Center → Historical Data → Device Steps: Select the times before and after the second post-recovery write and confirm.

Set the post-recovery write window

The range covers 61 to 62.

118. Verify 61 Changed to 62 ​

Where: Data Center → Historical Data → Device Steps: Query the first point's history for the second post-recovery write.

Verify 61 changed to 62

61 before the write, and the subsequent normal collection is 62.

119. Set the Third Write Window ​

Where: Data Center → Historical Data → Device Steps: Select the times before and after the third write and confirm.

Set the third write window

The range covers 62 to 63.

120. Verify 62 Changed to 63 ​

Where: Data Center → Historical Data → Device Steps: Query the first point's history for the third write.

Verify 62 changed to 63

62 before the write, and the subsequent normal collection is 63.

121. Refresh the History Page ​

Where: Data Center → Historical Data → Device Steps: Refresh the current Chrome page.

Refresh the history page

The history page reloads, and the device and variable filters are reset.

122. Query Again After Refresh ​

Where: Data Center → Historical Data → Device Steps: Re-select this tutorial's device and Energy 1, set 11:08:20 to 11:09:00, then Query.

Query again after refresh

After refreshing, the original history from 62 to 63 can still be queried.

Data Center → Historical Data → Device ​

Field / ControlFilling Notes
DeviceEnters the device history query.
Device NameRestricts the device to query.
Required · Value: fill in per your environment
Select from the current tenant's device list. Current batch resource: restricts the device to query; search for and select this tutorial's device — do not just type the name into the search box.
Advanced FilterExpands the variable selection conditions.
Variable NameRestricts which stored properties are queried.
Optional · Value: fill in per your environment
From the models of the selected device that have history storage enabled. Current batch resource: restricts which stored properties are queried; select all ten for the ten-point overview, and Energy 1 alone for the first-point changes.
Start and End TimeRestricts the historical data range.
Required · Value: use the actual time windows of this tutorial's sampling and writes
From the times of the actual sampling and write records.
QueryRe-queries using the current device, variables, and time.
ResetClears the current filter conditions.
RefreshRe-reads the history under the current conditions.
History TrendShows how the selected fields change over time.
From the history query result.
History DetailsShows the historical values and their update times.
From the history query result.
Page SizeDetermines how many history details one page shows.
Required · Value: 20 per page10 per page: at most 10 details per page; only changes pagination display, not the historical data. 20 per page: at most 20 details per page; only changes pagination display, not the historical data. 30 per page: at most 30 details per page; only changes pagination display, not the historical data. 50 per page: at most 50 details per page; only changes pagination display, not the historical data.

Advanced parameters (1 item)

Field / ControlFilling Notes
ExportExports the current query result.

Stop This Tutorial's Traffic While Keeping History ​

Clear this tutorial's session authorization, disconnect, and verify the automatic entries are off; then unpublish this tutorial's product. Refresh Sync Details to verify the runtime withdrawal receipt; finally, re-query the original history and keep the product and device for later review.

123. Open the Clear Session Authorization Entry ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Enter the write authorization area of this tutorial's meter and click Clear Authorization.

Open the clear session authorization entry

Only this tutorial's session's temporary authorization is cleared.

124. Confirm the Temporary Authorization Has Been Cleared ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Verify the current session write authorization and the two sensitive inputs.

Confirm the temporary authorization has been cleared

It shows as not configured, and both the password and operator code inputs are empty.

125. Disconnect This Tutorial's Meter Connection ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: After verifying the current session name, click Disconnect.

Disconnect this tutorial's meter connection

This tutorial's connection stops.

126. Verify the Session Is Indeed Disconnected ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: View this tutorial's session title and connection operation.

Verify the session is indeed disconnected

This tutorial's session shows as disconnected, and a connect button appears.

127. Verify Scheduled Sending Is Off ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Switch to the Scheduled Sending tab and verify the switch and status.

Verify scheduled sending is off

Scheduled sending is not enabled, and both the next send and last execution are empty.

128. Verify Auto Reply Is Off ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Switch to the Auto Reply tab and verify the master switch and rules.

Verify auto reply is off

The master switch is off, and there are currently no auto-reply rules.

129. Verify Auto Reconnect Is Off ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: In the current session's connection configuration, view Auto Reconnect.

Verify auto reconnect is off

Auto reconnect is off.

130. Unpublish This Tutorial's Product ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Return to this tutorial's product details and click Unpublish.

Unpublish this tutorial's product

The unpublish confirmation box for this tutorial's product opens.

131. Verify the Withdrawal Scope and Confirm ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Read the current confirmation box prompt, confirm that only this tutorial's demo product is withdrawn, then click OK.

Verify the withdrawal scope and confirm

This unpublish is submitted.

132. View the Withdrawal Feedback ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: View and close the Operation Succeeded prompt.

View the withdrawal feedback

The platform has accepted this unpublish.

133. Refresh and Verify the Runtime Withdrawal Receipt ​

Where: FMQX Web → This Tutorial's Session; Product Details → Unpublish Steps: Refresh the same product page, then open Sync Details.

Refresh and verify the runtime withdrawal receipt

The product is unpublished, and the runtime node returned APPLIED for this withdrawal.

134. Verify History Retention Again After Stopping ​

Where: Data Center → Historical Data → Device Steps: After refreshing the history page, re-select this tutorial's device, Energy 1, and the original write window, then click Query.

Verify history retention again after stopping

The original four history records from 62 to 63 can still be queried, with pagination and record count visible.

FMQX Web → This Tutorial's Session; Product Details → Unpublish ​

Field / ControlFilling Notes
Scheduled SendingStops this tutorial's scheduled traffic at the end.
Optional · Value: OffOn: enables this option; stops this tutorial's scheduled traffic at the end. Off: disables this option; the behavior is not enabled.
Auto ReconnectDoes not automatically restore this tutorial's connection at the end.
Optional · Value: OffOn: enables this option; does not automatically restore this tutorial's connection at the end. Off: disables this option; the behavior is not enabled.
Auto ReplyStops this tutorial's custom reply tasks at the end.
Optional · Value: OffOn: enables this option; stops this tutorial's custom reply tasks at the end. Off: disables this option; the behavior is not enabled.
Clear AuthorizationRemoves the current session's temporary write authorization.
DisconnectStops this tutorial's meter connection.
UnpublishWithdraws this tutorial's product runtime configuration.
OKConfirms the current unpublish action.
Operation SucceededIndicates the platform has accepted this unpublish.
Product and Connection StatusShows the product publish and current session status.
From the actual page after stopping.
Runtime Withdrawal ReceiptIndicates the target runtime node adopted this withdrawal configuration.
From the current product's Sync Details.
History RetentionThe original window can still be used to query history after stopping.
From the actual query after stopping.

Item-by-Item Checks When Results Disagree ​

SymptomPossible CauseCheck FirstHow to Recover
The number is empty when creating the device.Switching the product may clear the previously entered number.Return to the final device form and verify the name, product, and device number.Complete this tutorial's number and save again, and also verify the FMQX client number.
The mapping cannot find a polling item or reports inconsistency.The formal polling item has not been saved yet, or the polling item and model of another point were selected.Verify the polling list first, then select the record with the same data identifier from the real candidates.Fix the mapping, then save, validate, and republish.
It still shows pending activation after publish or unpublish.The page feedback and the runtime node adoption happen at different points in time.Refresh the current product page and view the node result and failure reason in Sync Details.Fix according to the actual failure reason, and continue only after receiving APPLIED for the current operation.
The meter is actually disconnected, but the page still shows connected.A page display lag was observed this time.Refresh the same Chrome page and compare with this tutorial's real session status.In this tutorial they matched after refresh; the source-code fix is unverified, so re-verify the connection identity before continuing.
The platform shows a response received, but the post-write value cannot be confirmed.A protocol response does not equal proof of device execution and independent read-back.Verify the device execution count, the pre/post-write values, and the new normal READ separately.Wait for the subsequent normal read and history; do not click write repeatedly.
Blank cells in the ten-point history or fewer rows than collection rounds.Different polling moments are merged for display by time; the counting criteria differ.Verify the device, the ten variables, and the sampling window, then select only the first point to view the full 12 records.Verify against each field's time and value; do not treat merged time rows as message counts.
The history conditions or results disappeared after refresh.A browser refresh may reset the device, variable, or time conditions.Re-select the same device, Energy 1, and the original write window, then click Query.Confirm the original history is still there after stopping; stopping in this tutorial does not delete the product, device, or history.