DL/T 645-2007 Meter Access over TCP
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.
Complete ten-DI collection for a 2007-edition meter over TCP, two controlled writes, independent read-back, manual reconnection, and history queries.
Before you start: you have product, device, model, publish, control, and history query permissions; the local application, FMQ, and FMQX Web are available; and you have obtained the official meter number, the DI point table, and controlled authorization.
Access Goal and Connection Direction
Select TCP as the platform transport label and 2007 as the DL/T645 version. The FMQX meter channel actively connects to the FMQ listening address; the meter number and DIs follow the manufacturer's documentation.
Each of the ten DIs maps to an independent property; history is enabled for all of them, and only the first allows controlled writing. After a write, wait for the next normal read, then verify the current value and history.
1. Configure the Product, Device, and Ten-DI Mapping
1. Select the Gateway Device Product Type
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Create the collection meter product for this tutorial, expand Advanced Configuration, and set Product Type to Gateway Device.

Product type in Advanced Configuration is set to Gateway Device.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Product Type | A gateway device carries the meter's TCP gateway session; a direct device is used for devices that do not need gateway binding. Required · Value: Gateway Device |
2. Verify the Basic Product Draft
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Verify the collection meter product and the ten collection fields, then save the draft; the wizard shows JSON/MQTT at this point, and the formal meter protocol is set in the next step.

The basic draft contains 10 collection fields; the formal meter protocol is set in the next step.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Basic Product and Field Count | The wizard creates the collection meter and ten fields; JSON/MQTT at this stage is the basic draft, and the formal protocol must be changed later. Required · Value: collection meter / ten fields / do not add a device yet |
3. Select the 2007 TCP Meter Protocol
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Set the Access Protocol to TCP, set the data format to DL/T645 2007, then save.

Access protocol is TCP and data format is DL/T645 2007.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Access Protocol and Data Format | TCP is the formal network label and DL/T645 2007 is the frame version; the FMQX channel name "TCP transparent gateway" is not the same as the TCP_GATEWAY product label in the other tutorial. Required · Value: TCP / DL/T645 2007 |
| Network Type | The page saved WIFI this time; it describes how the device connects to the network and does not change the TCP listening target. Required · Value: WIFI |
| Enable Device Authorization Code | This tutorial turns this switch off; meter write authorization and access authorization are separate stages. Required · Value: Off |
4. Create the Device and Enter Its Unique Identity
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select this tutorial's collection meter product, enter the meter terminal name and the unique device number; the FMQX gateway connection uses the same number.

Enter the meter terminal name, its product, and the unique device number.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Device Name and Product | The name is used to select the same meter terminal on the binding, running status, and history pages. Required · Value: Meter Terminal / Collection Meter |
| Device Number and Gateway Connection Identity | Use the unique device number; the platform device, the device identifier in the binding, and the FMQX gateway identity must all match. Required · Value: the unique device number of this tutorial's meter terminal |
| Firmware, Positioning, Grouping, Space, and Shadow | Firmware is left unknown in this tutorial, positioning is set to automatic, grouping and space are left blank, and the device shadow is off; none of these is the basis for the native read/write success in this tutorial. Required · Value: Unknown / Automatic positioning / blank / shadow off |
5. Define the Demo Setpoint Property
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Name the first property "demo setpoint", verify it corresponds to the 00010000 data item, and enter DemoSetpoint as the translated name.

The first demo setpoint corresponds to FastBee_di_00010000.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| First Property Name and Identifier | The first property is the demo setpoint, translated as DemoSetpoint, mapped one-to-one to DI00010000; the other nine are named Collection 1 through Collection 9. Required · Value: Demo Setpoint / DemoSetpoint / DI00010000 |
6. Enable History for the First Property and Allow Control
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Enable History Storage for the demo setpoint and clear Read-Only Data; keep the other nine collection properties read-only.

The first property has history storage enabled and read-only data cleared.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| History Storage and Read-Only Data | The first property has history on and read-only off; the other nine have history on and read-only on. Chart display, real-time monitoring, and sharing permission are off for the first property. Required · Value: first property controllable; history on for all |
7. Set the Integer Range and Step
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Set all ten properties to Integer with range 0 to 10000 and step 1; the figure shows the final range of the ninth collection property.

Integer property range is 0 to 10000, step 1, unit left blank.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Data Type, Range, and Step | All ten properties use integer 0 to 10000 with step 1, making the known samples easy to distinguish. Required · Value: Integer / 0–10000 / 1 |
| Unit and Calculation Formula | This tutorial uses dimensionless demo integers, so unit and calculation formula are left blank; for physical meters, fill them in per the manufacturer's dimensions and conversion rules. Required · Value: left blank |
8. Verify the Last Collection Property
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: After saving, check the field row of Collection 9 and verify the data type is Integer with history storage on; check the remaining collection fields the same way.

The identifier of the last item Collection 9 is FastBee_di_00010009, and the data type is Integer.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Collection Field Save Result | The last item Collection 9 corresponds to 00010009; the image shows that row's integer type and history on, but does not mean all ten are shown at once. Required · Value: Collection 9 / 00010009 / Integer / history on |
9. Bind the Platform Device and the Real Gateway
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select this tutorial's meter terminal for both the platform device and the real gateway, enter 123456780807 as the meter number, keep it enabled, and save the draft.

Bind the meter terminal with meter number 123456780807 and protocol DLT645_2007.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Platform Device and Real Gateway | Select this tutorial's gateway device that actually exists for both; the real gateway dropdown comes from the gateway device list, and a self-invented number cannot be typed in. Required · Value: this tutorial's meter terminal |
| Meter Number | A 12-digit number from the meter nameplate or manufacturer documentation; the platform and FMQX must match exactly. Required · Value: 123456780807 |
| Binding Enabled | Once enabled, this meter is included in the publish configuration; the protocol version is determined by the product's 2007 format. Required · Value: Enabled / DLT645_2007 |
10. Create the Ten Polling Items One by One
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Create 00010000 first, then continue up to 00010009; each item has a 60000 ms interval, 3000 ms timeout, and 0 retries; enable and save each.

First item DI00010000: 60000 ms interval, 3000 ms timeout, 0 retries.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Data Identifier DI | The 2007 edition uses 8 hexadecimal digits; the ten items 00010000 through 00010009 each get their own polling item; these are meter data identifiers. Required · Value: 00010000 to 00010009 |
| Polling Interval, Timeout, and Retries | Each item reads every 60000 ms with a 3000 ms timeout and 0 retries; after a write, an independent read may take nearly a minute. Required · Value: 60000 ms / 3000 ms / 0 retries |
| Polling Priority and Enabled | The first item example uses priority 100 and stays enabled; save all ten before mapping. Required · Value: 100 / Enabled |
11. Create the Field Mapping and the First Item's Write Permission
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select the saved formal polling item and the corresponding Thing Model field, set the format to BCD, multiplier 1, offset 0; only the demo setpoint has Allow Write enabled with the specification basis filled in.

DI00010000 mapped to the demo setpoint, with BCD, multiplier 1, offset 0, and write allowed.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Formal Polling Item and Thing Model Field | After saving the polling items, select from the real list; the first item 00010000 corresponds to the demo setpoint, and the remaining DIs correspond to Collection 1 through 9. Required · Value: formal first polling item / demo setpoint |
| Data Format | This tutorial uses BCD, entering the raw BCD value of the decimal digits; choose other formats only when the manufacturer's specification requires them. Required · Value: BCD |
| Value Index, Multiplier, Offset, and Unit | The first item uses value index 0, multiplier 1, offset 0, and a blank unit; keep the input consistent with the read result. Required · Value: 0 / 1 / 0 / unit left blank |
| Allow Write and Specification Basis | Only 00010000 has write enabled, with the basis for this FMQX formal demo scenario filled in; the other nine are off, and read-only energy values are not treated as writable points. Required · Value: only the demo setpoint allows writing |
12. Save the Read Command Policy
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select READ_DATA and 00010000 with risk level LOW; allow manual commands and unified downlink, turn off password reference, and set a 5000 ms timeout with 0 retries.

The read policy is READ_DATA with DI00010000, a 5000 ms timeout, and 0 retries.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Read Operation and Risk Level | Reads use READ_DATA and LOW; writes use WRITE_DATA and HIGH; a low-risk read policy must not be used to pass a write through. Required · Value: READ_DATA / LOW / 00010000 |
| Read Switches | This tutorial allows manual commands and unified downlink, keeps password reference off, and keeps the policy enabled. Required · Value: manual on / unified downlink on / password reference off / enabled |
| Command Timeout and Retries | The command policy uses a 5000 ms timeout and 0 retries; this is a different setting from the 3000 ms polling timeout. Required · Value: 5000 ms / 0 retries |
13. Save the Controlled Write Policy
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select WRITE_DATA and 00010000 with risk level HIGH; turn on Require Password Reference, manual commands, and unified downlink, then save the draft.

The write policy is WRITE_DATA with DI00010000 and requires a password reference.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Write Operation and Risk Level | This tutorial creates a separate WRITE_DATA and HIGH policy for 00010000; once the operation is set to write, the page requires a password reference. Required · Value: WRITE_DATA / HIGH / 00010000 |
| Write Switches | Allow manual commands and unified downlink, turn on Require Password Reference, and enable the policy; authorization for the current device session is still needed. Required · Value: manual on / unified downlink on / password reference on / enabled |
| Command Timeout and Retries | The command policy uses a 5000 ms timeout and 0 retries; this is a different setting from the 3000 ms polling timeout. Required · Value: 5000 ms / 0 retries |
2. Verify the Meter Connection Parameters
14. Select the 2007 Meter and the TCP Channel
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: In the FMQX Web connection wizard, select DL/T645-2007 and verify that the meter simulator connects to FMQ over TCP.

Select DL/T645-2007 in FMQX Web so the meter simulator connects to FMQ over TCP.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| Device Protocol | Used to complete "Select the 2007 Meter and the TCP Channel". Required · Value: DL/T645-2007 |
| Connection Direction | Used to complete "Select the 2007 Meter and the TCP Channel". Required · Value: the device actively connects to FMQ |
15. Verify the Meter Version, TCP Target, and Meter Number
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Open the meter connection configuration and verify the protocol version, the TCP connection target, and the 12-digit meter number.

Connecting to 127.0.0.1:8888, with matching device number and meter address 123456780807.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| Protocol Version | Used to complete "Verify the Meter Version, TCP Target, and Meter Number". Required · Value: 2007 |
| Platform Transport Label | Used to complete "Verify the Meter Version, TCP Target, and Meter Number". Required · Value: TCP |
3. Publish, Connect, and Configure Authorization
16. Publish the Product Configuration
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: After verifying the product, click OK in the publish confirmation box.

After submitting, continue to verify the apply result on the target node.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
17. Confirm the Configuration Has Been Applied
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Open Sync Details, verify the target node shows APPLIED, and only then connect.

The current published configuration has been applied on the target node.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
18. Connect and Send the Default Identity Registration
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: In the original session, run connect and the default identity registration, then wait for normal reads.

The FMQX Web scenario binds the original session and configures the connect step.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
19. Configure Write Authorization for the Current Session
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Enter the controlled authorization per the manufacturer's documentation and save; verify the input fields have been cleared.

Session write authorization is configured, and both password fields are cleared.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
4. Read Ten Different Data Items
Normal polling may record the same DI repeatedly; verify the ten samples by distinct DI.
20. Read the First Data Item
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Select DI00010000, verify the device's actual value, and wait for the normal polling read.

The current value Hex of the first item DI00010000 is 01000000, corresponding to BCD value 1.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| DI / Value | Used to complete "Read the First Data Item". Required · Value: 00010000 / 1 |
21. Complete Reading the Ten Different Data Items
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Verify the remaining nine DIs and normal polling in turn, and finally check DI00010009.

The current value Hex of the last item DI00010009 is 10000000, corresponding to BCD value 10.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| DI Range | Used to complete "Complete Reading the Ten Different Data Items". Required · Value: 00010000 to 00010009 |
5. First Write and Independent Read
22. Submit the First Controlled Write from the Platform
Where: Device Details → Running Status → Meter Write Steps: In the 00010000 control entry, enter the data Hex, the controlled authorization, and the reason, then confirm once.

The target this time is 65, and the data Hex is 65000000.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| DI | Used to complete "Submit the First Controlled Write from the Platform". Required · Value: 00010000 |
| Write Data Hex | Used to complete "Submit the First Controlled Write from the Platform". Required · Value: 65000000 |
23. View the Real Protocol Response
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: View the feedback for this command and verify that a real protocol response was received.

The platform reports that a real protocol response has been received; continue to verify the read-back and the latest report.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
24. Verify the Native Write Response
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: In the FMQX Web communication log, select this write response and verify the time, direction, and complete raw frame.

The device sent a native write-success response with control code 94.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
25. Read the Device's Actual Point Value
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Refresh the device point values and verify the DI and its actual current value.

The current value Hex of the device's first item DI00010000 is 65000000.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
26. Verify the Independent Read Request After the Write
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Wait for the new READ_DATA request after the write executes, and verify the DI and the actual time.

A new independent read request appears after the write executes.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
27. Verify the Independent Read Response
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: View the response to that read request and verify the version, meter number, DI, and value.

The independent read response returns the actual value 65.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
28. Verify the Platform Current Value
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Wait for subsequent reads to update the platform, then read the current value of this DI.

The platform demo setpoint is currently 65.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
6. Manual Recovery After a Normal Disconnect
A normal disconnect and a manual registration reuse the published configuration; submit the new write after connect and registration complete.
29. Disconnect the Original Session Normally
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Click Disconnect and read the status of the same session.

The meter's original session is disconnected; click the connect button to restore it manually.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
30. Connect Manually and Re-register
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Connect the original session and send the default identity registration, reusing the published configuration.

The recovery scenario binds the same session and configures the connect step.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
7. First New Write and Independent Read After Recovery
31. First Controlled Write After Recovery
Where: Device Details → Running Status → Meter Write Steps: In the 00010000 control entry, enter the data Hex, the controlled authorization, and the reason, then confirm once.

The target this time is 66, and the data Hex is 66000000.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
| DI | Used to complete "First Controlled Write After Recovery". Required · Value: 00010000 |
| Write Data Hex | Used to complete "First Controlled Write After Recovery". Required · Value: 66000000 |
32. Verify the Native Write Response
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: In the FMQX Web communication log, select this write response and verify the time, direction, and complete raw frame.

The device sent a native write-success response with control code 94.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
33. Read the Device's Actual Point Value
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Refresh the device point values and verify the DI and its actual current value.

After recovery, the current value Hex of the device's first item DI00010000 is 66000000.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
34. Verify the Independent Read Request After the Write
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Wait for the new READ_DATA request after the write executes, and verify the DI and the actual time.

A new independent read request appears after the write executes.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
35. Verify the Independent Read Response
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: View the response to that read request and verify the version, meter number, DI, and value.

The independent read response returns the actual value 66.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
36. Verify the Platform Current Value
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Wait for subsequent reads to update the platform, then read the current value of this DI.

The platform demo setpoint is currently 66.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
8. Query the Three History Windows Separately
37. Enter the Complete Time Range for the Ten-DI Sample
Where: Data Center → Historical Data Steps: Enter the complete start and end date-times.

Query the corresponding records by complete date-time.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Start Time | Used to complete "Enter the Complete Time Range for the Ten-DI Sample". Required · Value: 2026-10-16 03:40:23 |
| End Time | Used to complete "Enter the Complete Time Range for the Ten-DI Sample". Required · Value: 2026-10-16 03:41:30 |
38. Filter the Ten-DI Sample Fields
Where: Data Center → Historical Data Steps: Select this device and the corresponding DI fields, verify the time, and click Query.

After selecting the meter terminal and its 10 properties, click Query.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Fields | Used to complete "Filter the Ten-DI Sample Fields". Required · Value: 00010000, 00010001, 00010002, 00010003, 00010004, 00010005, 00010006, 00010007, 00010008, 00010009 |
39. Refresh the Ten-DI Sample History
Where: Data Center → Historical Data Steps: Keep the same device, fields, and time, and click the refresh button at the top right of the result area.

After refreshing, the ten properties show 4 records in total.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
40. Verify the Ten-DI Sample Results
Where: Data Center → Historical Data Steps: Read the actual history by time and DI, distinguishing periodic repeated values from different data items.

4 history rows cover the 10 items, with initial values running from 1 to 10.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
41. Enter the Complete Time Range for the First Write Read-Back
Where: Data Center → Historical Data Steps: Enter the complete start and end date-times.

Query the corresponding records by complete date-time.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Start Time | Used to complete "Enter the Complete Time Range for the First Write Read-Back". Required · Value: 2026-10-16 03:41:30 |
| End Time | Used to complete "Enter the Complete Time Range for the First Write Read-Back". Required · Value: 2026-10-16 03:42:23 |
42. Filter the First Write Read-Back Fields
Where: Data Center → Historical Data Steps: Select this device and the corresponding DI fields, verify the time, and click Query.

The first write history filters the demo setpoint, then clicks Query.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Fields | Used to complete "Filter the First Write Read-Back Fields". Required · Value: 00010000 |
43. Refresh the First Write Read-Back History
Where: Data Center → Historical Data Steps: Keep the same device, fields, and time, and click the refresh button at the top right of the result area.

Refreshing the first write history shows 1 record in the result area.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
44. Verify the First Write Read-Back Result
Where: Data Center → Historical Data Steps: Read the actual history by time and DI, distinguishing periodic repeated values from different data items.

2026-10-16 03:42:21, the demo setpoint history is 65.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
45. Enter the Complete Time Range for the Post-Recovery Write Read-Back
Where: Data Center → Historical Data Steps: Enter the complete start and end date-times.

Query the corresponding records by complete date-time.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Start Time | Used to complete "Enter the Complete Time Range for the Post-Recovery Write Read-Back". Required · Value: 2026-10-16 03:42:38 |
| End Time | Used to complete "Enter the Complete Time Range for the Post-Recovery Write Read-Back". Required · Value: 2026-10-16 03:43:23 |
46. Filter the Post-Recovery Write Read-Back Fields
Where: Data Center → Historical Data Steps: Select this device and the corresponding DI fields, verify the time, and click Query.

The post-recovery write history filters the demo setpoint, then clicks Query.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
| Fields | Used to complete "Filter the Post-Recovery Write Read-Back Fields". Required · Value: 00010000 |
47. Refresh the Post-Recovery Write Read-Back History
Where: Data Center → Historical Data Steps: Keep the same device, fields, and time, and click the refresh button at the top right of the result area.

Keep the filter conditions of the post-recovery write and click refresh at the top right of the result area.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
48. Verify the Post-Recovery Write Read-Back Result
Where: Data Center → Historical Data Steps: Read the actual history by time and DI, distinguishing periodic repeated values from different data items.

2026-10-16 03:43:21, the demo setpoint history is 66.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: fill in per the implementation plan · Example: use the actual time window of the corresponding operation |
9. Stop While Keeping Configuration and History
49. Clear the Session Write Authorization
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Clear the current session authorization and verify the authorization shows as not configured.

Write authorization for the current session is not configured, and the password fields are empty.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
50. Stop Sending and Receiving While Keeping the Configuration
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Disconnect the original session and turn off auto-reconnect and any automatic items that actually exist.

The 2007 meter session status is Disconnected.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
51. Unpublish and Confirm the Apply Result
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Unpublish the original product and verify APPLIED in Sync Details.

After unpublishing, the target node result is APPLIED.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
52. View the Retained Writable Point's Current Value After Stopping
**Where:**Product Management, Device Management, or the corresponding operation area in FMQX Web Steps: Read the platform's current value for the first item and check it against the last independent read-back.

After stopping, the demo setpoint still shows the latest read-back value 66.
Screenshot Highlights
| Field / Control | Description |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: fill in per the implementation plan · Example: 00010000 / 65, 66 |
Parameter Sources and Filling Reference
Device Access Wizard
| Field / Control | Filling Notes |
|---|---|
| Product Type | A gateway device carries the meter's TCP gateway session; a direct device is used for devices that do not need gateway binding. Required · Value: Gateway DeviceDirect Device: the device connects directly and does not carry this tutorial's real gateway binding; the device connects directly and does not carry this tutorial's real gateway binding. Gateway Device: selected in this tutorial for the actual TCP gateway identity; selected in this tutorial for the actual TCP gateway identity. |
| Basic Product and Field Count | The wizard creates the collection meter and ten fields; JSON/MQTT at this stage is the basic draft, and the formal protocol must be changed later. Required · Value: collection meter / ten fields / do not add a device yet |
| Device Name and Product | The name is used to select the same meter terminal on the binding, running status, and history pages. Required · Value: Meter Terminal / Collection Meter |
| Device Number and Gateway Connection Identity | Use the unique device number; the platform device, the device identifier in the binding, and the FMQX gateway identity must all match. Required · Value: the unique device number of this tutorial's meter terminal |
| Firmware, Positioning, Grouping, Space, and Shadow | Firmware is left unknown in this tutorial, positioning is set to automatic, grouping and space are left blank, and the device shadow is off; none of these is the basis for the native read/write success in this tutorial. Required · Value: Unknown / Automatic positioning / blank / shadow off |
Protocol and Publish Activation
| Field / Control | Filling Notes |
|---|---|
| Access Protocol and Data Format | TCP is the formal network label and DL/T645 2007 is the frame version; the FMQX channel name "TCP transparent gateway" is not the same as the TCP_GATEWAY product label in the other tutorial. Required · Value: TCP / DL/T645 2007Republish after changes. DL/T645 2007: the meter frame version with 8-digit DIs in this tutorial; the meter frame version with 8-digit DIs in this tutorial. DL/T645 1997: the other frame version, using a separate product and 4-digit DIs; this tutorial's conclusions cannot be reused; the other frame version, using a separate product and 4-digit DIs; this tutorial's conclusions cannot be reused. |
| Network Type | The page saved WIFI this time; it describes how the device connects to the network and does not change the TCP listening target. Required · Value: WIFIRepublish after changes. |
| Enable Device Authorization Code | This tutorial turns this switch off; meter write authorization and access authorization are separate stages. Required · Value: OffRepublish after changes. |
| Platform Device and Real Gateway | Select this tutorial's gateway device that actually exists for both; the real gateway dropdown comes from the gateway device list, and a self-invented number cannot be typed in. Required · Value: this tutorial's meter terminalRepublish after changes. This tutorial's meter terminal: select this tutorial's saved device from the platform's real device and real gateway lists, with both entries corresponding to the same identity; select this tutorial's saved device from the platform's real device and real gateway lists, with both entries corresponding to the same identity. |
| Meter Number | A 12-digit number from the meter nameplate or manufacturer documentation; the platform and FMQX must match exactly. Required · Value: 123456780807Republish after changes. |
| Binding Enabled | Once enabled, this meter is included in the publish configuration; the protocol version is determined by the product's 2007 format. Required · Value: Enabled / DLT645_2007Republish after changes. |
| Data Identifier DI | The 2007 edition uses 8 hexadecimal digits; the ten items 00010000 through 00010009 each get their own polling item; these are meter data identifiers. Required · Value: 00010000 to 00010009Republish after changes. |
| Polling Interval, Timeout, and Retries | Each item reads every 60000 ms with a 3000 ms timeout and 0 retries; after a write, an independent read may take nearly a minute. Required · Value: 60000 ms / 3000 ms / 0 retriesRepublish after changes. |
| Polling Priority and Enabled | The first item example uses priority 100 and stays enabled; save all ten before mapping. Required · Value: 100 / EnabledRepublish after changes. |
| Formal Polling Item and Thing Model Field | After saving the polling items, select from the real list; the first item 00010000 corresponds to the demo setpoint, and the remaining DIs correspond to Collection 1 through 9. Required · Value: formal first polling item / demo setpointRepublish after changes. 00010000 / demo setpoint: for the first item, select 00010000 from the saved polling items and choose the demo setpoint as the model field; for the first item, select 00010000 from the saved polling items and choose the demo setpoint as the model field. |
| Data Format | This tutorial uses BCD, entering the raw BCD value of the decimal digits; choose other formats only when the manufacturer's specification requires them. Required · Value: BCDRepublish after changes. BCD: interprets the value as BCD; selected in this tutorial; interprets the value as BCD; selected in this tutorial. UINT: unsigned integer format; select per the device documentation; unsigned integer format; select per the device documentation. INT: signed integer format; select per the device documentation; signed integer format; select per the device documentation. HEX: raw hexadecimal content; select per the device documentation; raw hexadecimal content; select per the device documentation. ASCII: character content; select per the device documentation; character content; select per the device documentation. |
| Value Index, Multiplier, Offset, and Unit | The first item uses value index 0, multiplier 1, offset 0, and a blank unit; keep the input consistent with the read result. Required · Value: 0 / 1 / 0 / unit left blankRepublish after changes. |
| Allow Write and Specification Basis | Only 00010000 has write enabled, with the basis for this FMQX formal demo scenario filled in; the other nine are off, and read-only energy values are not treated as writable points. Required · Value: only the demo setpoint allows writingRepublish after changes. |
| Read Operation and Risk Level | Reads use READ_DATA and LOW; writes use WRITE_DATA and HIGH; a low-risk read policy must not be used to pass a write through. Required · Value: READ_DATA / LOW / 00010000Republish after changes. READ_DATA / LOW: read policy, used in this step; read policy, used in this step. WRITE_DATA / HIGH: controlled write policy, configured in a separate step; controlled write policy, configured in a separate step. |
| Read Switches | This tutorial allows manual commands and unified downlink, keeps password reference off, and keeps the policy enabled. Required · Value: manual on / unified downlink on / password reference off / enabledRepublish after changes. |
| Command Timeout and Retries | The command policy uses a 5000 ms timeout and 0 retries; this is a different setting from the 3000 ms polling timeout. Required · Value: 5000 ms / 0 retriesRepublish after changes. |
| Write Operation and Risk Level | This tutorial creates a separate WRITE_DATA and HIGH policy for 00010000; once the operation is set to write, the page requires a password reference. Required · Value: WRITE_DATA / HIGH / 00010000Republish after changes. READ_DATA / LOW: for reads only; for reads only. WRITE_DATA / HIGH: this tutorial's controlled write policy; this tutorial's controlled write policy. |
| Write Switches | Allow manual commands and unified downlink, turn on Require Password Reference, and enable the policy; authorization for the current device session is still needed. Required · Value: manual on / unified downlink on / password reference on / enabledRepublish after changes. |
Feature Definition
| Field / Control | Filling Notes |
|---|---|
| First Property Name and Identifier | The first property is the demo setpoint, translated as DemoSetpoint, mapped one-to-one to DI00010000; the other nine are named Collection 1 through Collection 9. Required · Value: Demo Setpoint / DemoSetpoint / DI00010000Republish after changes. |
| History Storage and Read-Only Data | The first property has history on and read-only off; the other nine have history on and read-only on. Chart display, real-time monitoring, and sharing permission are off for the first property. Required · Value: first property controllable; history on for allRepublish after changes. |
| Data Type, Range, and Step | All ten properties use integer 0 to 10000 with step 1, making the known samples easy to distinguish. Required · Value: Integer / 0–10000 / 1Republish after changes. |
| Unit and Calculation Formula | This tutorial uses dimensionless demo integers, so unit and calculation formula are left blank; for physical meters, fill them in per the manufacturer's dimensions and conversion rules. Required · Value: left blankRepublish after changes. |
| Collection Field Save Result | The last item Collection 9 corresponds to 00010009; the image shows that row's integer type and history on, but does not mean all ten are shown at once. Required · Value: Collection 9 / 00010009 / Integer / history onRepublish after changes. |
Current Read/Write and History Operations
| Field / Control | Filling Notes |
|---|---|
| Current DI, Actual Value, and Controlled Write Parameters | Current DI, actual value, and controlled write parameters. Required · Value: 00010000 / 65, 66 |
| This Device, DI Fields, and Complete Date-Time | This device, DI fields, and complete date-time. Required · Value: use the actual time window of the corresponding operation |


