A multi-functional, fully protected armored serial cable
By using a through-type protective shielding structure of stainless steel braided armor layer and metal shielding shell in the industrial serial communication conversion cable, the problem of unstable data transmission in the prior art is solved, and mechanical tolerance and signal anti-interference capability in harsh environments are achieved, ensuring the stability and isolation security of data transmission.
Patent Information
- Application Number
- CN202611275227.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-21
- Publication Date
- 2026-11-17
AI Technical Summary
Existing industrial serial communication conversion cables are easily damaged in harsh environments, resulting in unstable data transmission and failing to simultaneously meet the requirements of mechanical durability, signal interference resistance, and isolation safety.
A through-type protective shielding structure is formed by a stainless steel braided armor layer and a metal shielding shell, combined with an isolated serial port conversion circuit to achieve mechanical protection, electromagnetic shielding and multi-standard serial port communication.
It improves the resistance of USB connectors, cables, and circuit board housings to biting, crushing, and bending, reduces interference from external high-frequency electromagnetic fields on signals, and ensures the stability and isolation security of data transmission.
Smart Images

Figure CN123121198A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of industrial serial communication conversion equipment technology, and more specifically, to a multifunctional, fully protected armored serial cable. Background Technology
[0002] In the field of industrial serial communication conversion hardware, USB to serial converter cables are mainly used to establish data channels between the USB interface of computers, industrial gateways or edge computing nodes and PLCs, data acquisition instruments, access controllers, embedded sensors and other field devices. Existing products typically have a USB to TTL main control circuit, an electrical isolation circuit, a level conversion circuit between TTL and RS232 / RS485, and a voltage stabilization circuit on the conversion circuit board. The TTL, RS232, and RS485 signals and power supply voltage are then centrally led out through a DB9 connector to meet the needs of edge computing nodes for unified access and local data acquisition of field devices with different communication standards. In industrial workshops, underground low-voltage wells, outdoor equipment boxes, and power data acquisition sites, edge computing nodes typically need to continuously receive status data uploaded by field devices for extended periods and perform filtering, summarization, or control command issuance locally. Therefore, their serial port conversion cables must maintain the original electrical isolation between the USB side and the industrial communication side, maintain stable transmission in environments near motors, frequency converters, high-power switching equipment, and long-distance communication cables, and withstand being stepped on by people, squeezed by equipment, bitten by rodents and insects, repeatedly bent, and pulled by connectors. Existing conversion cables mostly use ordinary plastic sheaths, partial braided mesh, or only metal shells at the connectors. When the cables are subjected to external forces, the sheaths are prone to tearing, local flattening, and bending fatigue. The external force is further transmitted to the internal core wires and the connector welding positions, manifesting as core wire breakage, intermittent contact, and intermittent communication. At the same time, there are often connection interruptions, insufficient overlap areas, or local exposed areas between the cable shielding layer and the USB connector shell, circuit board shell, and DB9 connector shell. After the external high-frequency electromagnetic field couples to the USB differential line and serial port signal line through the shielding interruption, it will cause garbled received data, frame verification failure, repeated transmission, communication interruption, or USB device re-enumeration, resulting in missing or disordered field data obtained by the edge computing node, or control commands not being delivered in a timely manner. Even if the conversion circuit has been equipped with digital isolation, surge clamping and electrostatic protection, the external mechanical structure and shielding connection of the cable will still become weak points in the long-term operation of the edge computing link, making it difficult to simultaneously meet the requirements of mechanical tolerance, signal anti-interference and isolation safety in harsh environments. The technical problem this application aims to solve is: how to form an overall protective structure for the USB connector, cable, circuit board shell, and DB9 connector that combines bite resistance, compression resistance, stepping resistance, bending resistance, and electromagnetic shielding capabilities without destroying the electrical isolation between the USB side and the industrial communication side, so as to maintain the stability of data transmission between edge computing nodes and field serial port devices. Summary of the Invention
[0003] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a multifunctional, fully protected armored serial cable. This cable forms a through-type protective shielding structure through a stainless steel braided armor layer and a metal shielding shell, and combines this with an isolated serial port conversion circuit to achieve mechanical protection, electromagnetic shielding, and multi-standard serial communication coordination, thereby solving the problems mentioned in the background art.
[0004] To achieve the above objectives, the present invention provides the following technical solution: a multi-functional, fully protected armored serial cable, comprising: USB signal input circuit J1, USB to TTL output circuit U5, TTL signal isolation output circuit U2, TTL RXD signal distribution output circuit U3, TTL signal to RS485 circuit U1, TTL signal to RS232 circuit U4, 5V to 3.3V output circuit U7, DB9 output connector J2, and armored physical protection components. The TXD signal of U5 is transmitted through U2 to form TTL-TXD, and the TX_EN signal of U5 is transmitted through U2 to form RE / DE. TTL-TXD is connected to pin 4 of J2, pin 4 of U1, and pin 11 of U4 respectively. RE / DE is connected to pin 2 and pin 3 of U1. Pin 1 of U1 forms TTL_RXD1, which is transmitted through U2 to form RXD1. Pin 12 of U4, pin 1 of J2, and pin 11 of U2 are connected through the TTL_RXD2 network. TTL_RXD2 is transmitted through U2 to form RXD2. U3 performs a bitwise AND operation on RXD1 and RXD2 and sends the generated RXD to pin 5 of U5. Pin 16 of U2 forms ISO_5V. U7 converts ISO_5V to ISO_3.3V. The circuit containing U5 uses GND, while the circuits containing U1, U4, and U7 use Ground. GND and Ground are not directly connected on the circuit board. The armor-type physical protection component includes a USB metal shell, a stainless steel braided armor layer, a metal shielding shell covering the circuit board, and a DB9 metal shell. The two ends of the stainless steel braided armor layer are electrically connected to the USB metal shell and the DB9 metal shell, respectively, and the metal shielding shell is electrically connected to the DB9 metal shell.
[0005] In a preferred embodiment, pin 1 of J1 is connected to VCC_5V, pin 2 is connected to pin 16 of U5 via the DM- network, pin 3 is connected to pin 15 of U5 via the DP+ network, and pins 4 and 5 are connected to GND. U5 uses FT232RL. Pins 4 and 20 of U5 are connected to VCC_5V, pins 7, 18, 21, 25 and 26 are connected to GND, pin 17 forms VCC_3V3, pin 1 forms TXD, pin 5 receives RXD, pin 13 forms TX_EN, pins 3 and 11 are connected, pins 2 and 9 are connected, and pins 6, 8, 10, 12, 14, 24, 27 and 28 remain unconnected. R6 has a resistance of 4.7KΩ and is connected between VCC_5V and pin 19 of U5. R7 has a resistance of 10KΩ and is connected between pin 19 of U5 and GND. C9 and C10 each have a capacitance of 0.1μF and are connected between VCC_5V and GND. C16 has a capacitance of 0.1μF and is connected between VCC_3V3 and GND. Pins 23, D1, R4, and VCC_3V3 of U5 are connected in sequence. Pins 22, D2, R5, and VCC_3V3 of U5 are connected in sequence. The resistance of R4 and R5 is 499Ω.
[0006] In a preferred embodiment, U2 uses an NSIP8941. Pin 1 of U2 is connected to VCC_5V, pins 2 and 8 are connected to GND, pin 3 is connected to TXD, pin 4 is connected to TX_EN, pin 5 is connected to RXD1, pin 6 is connected to RXD2, pin 7 is left unconnected, pins 9, 10 and 15 are connected to Ground, pin 11 is connected to TTL_RXD2, pin 12 is connected to TTL_RXD1, pin 13 is connected to RE / DE, pin 14 is connected to TTL-TXD, and pin 16 is connected to ISO_5V. C3 has a capacitance of 10μF, C5 has a capacitance of 0.1μF, and C3 and C5 are connected between VCC_5V and GND respectively; C2 has a capacitance of 10μF, C4 has a capacitance of 0.1μF, and C2 and C4 are connected between ISO_5V and Ground respectively; R9 and R10 both have a resistance of 4.7KΩ, R9 is connected between TTL_RXD1 and ISO_5V, and R10 is connected between TTL_RXD2 and ISO_5V.
[0007] In a preferred embodiment, U1 uses SP485EN. Pin 1 of U1 is connected to TTL_RXD1, pins 2 and 3 are connected to RE / DE, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, and pin 8 is connected to ISO_5V. The resistance values of R1, R2, and R3 are all 4.7KΩ. R1 is connected between TTL_RXD1 and ISO_5V, R2 is connected between RS485-B and ISO_5V, and R3 is connected between RS485-A and Ground. C1 has a capacitance of 0.1μF and is connected between ISO_5V and Ground. D6 is connected between RS485-B and Ground, and D7 is connected between RS485-A and Ground. RS485-A is connected to pin 6 of J2, and RS485-B is connected to pin 7 of J2.
[0008] In a preferred embodiment, U4 uses an STI3232. Pin 11 of U4 is connected to TTL-TXD, pin 14 to RS232-TXD, pin 13 to RS232-RXD, pin 12 to TTL_RXD2, pin 15 to Ground, pin 16 to ISO_5V, and pins 7, 8, 9, and 10 remain unconnected. C11 has a capacitance of 0.1μF and is connected between pins 1 and 3 of U4, and C12 has a capacitance of 0.1μF and is connected between pins 4 and 5. Between pins 5, C7 has a capacitance of 0.1μF and is connected between pin 6 of U4 and Ground; C8 has a capacitance of 0.1μF and is connected between pin 2 of U4 and ISO_5V; C15 has a capacitance of 0.1μF and is connected between ISO_5V and Ground; pin 1 of D4 is connected to RS232-TXD, pin 2 is connected to TTL-TXD, and pin 3 is connected to Ground; pin 1 of D5 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, and pin 3 is connected to Ground.
[0009] In a preferred embodiment, U3 uses a 74AHC1G08. Pin 1 of U3 is connected to RXD2, pin 2 is connected to RXD1, pin 3 is connected to GND, pin 4 forms RXD, pin 5 is connected to VCC_5V, and C14 has a capacitance of 0.1μF and is connected between VCC_5V and GND. U3 outputs a high level when both RXD1 and RXD2 are high, and outputs a low level when either RXD1 or RXD2 is low. The RXD output of U3 is connected to pin 5 of U5.
[0010] In a preferred embodiment, pin 1 of U7 is connected to ISO_5V, pin 2 is connected to Ground, pin 3 is connected to ISO_5V via R8, pin 4 is connected to Ground via C17, pin 5 forms ISO_3.3V, the resistance of R8 is 10KΩ, the capacitance of C17 is 0.01μF, the capacitance of EC1 and EC2 is 10μF, EC1 is connected between ISO_5V and Ground, and EC2 is connected between ISO_3.3V and Ground; J2 is a 9-pin male connector. Pin 1 of J2 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, pin 3 is connected to RS232-TXD, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, pin 8 is connected to ISO_3.3V, and pin 9 is connected to ISO_5V.
[0011] In a preferred embodiment, the armor-type physical protection component further includes a core wire harness and an insulating sheath covering the core wire harness. A stainless steel braided armor layer covers the insulating sheath circumferentially. The stainless steel braided armor layer is cross-woven from a first metal wire bundle arranged in a first helical direction and a second metal wire bundle arranged in a second helical direction, with the first helical direction being opposite to the second helical direction. A USB metal shell is welded to the USB end of the stainless steel braided armor layer, and a DB9 metal shell is welded to the DB9 end of the stainless steel braided armor layer. A metal shielding shell covers the circuit board and makes conductive contact with the DB9 metal shell. The insulating sheath separates the core wire harness from the stainless steel braided armor layer.
[0012] In a preferred embodiment, the edge computing node connected to the USB signal input circuit J1 establishes a serial port configuration table. Each row of the serial port configuration table records the baud rate b, data bits d, stop bits s, and parity bit type p in sequence. The baud rate b can be 300bps, 600bps, 1200bps, 2400bps, 4800bps, 9600bps, 19200bps, 38400bps, 57600bps, 115200bps, 230400bps, 460800bps, 921600bps, 1500000bps, 2000000bps and 3000000bps respectively; the number of data bits d can be 7 or 8; the number of stop bits s can be 1 or 2; and the parity bit type p can be Even, None, Odd, Mark or Space. When the device under test is connected to RS232-TXD and RS232-RXD, the edge computing node deletes rows with baud rates b higher than 115200bps; the edge computing node writes each row of the serial port configuration table into U5 in sequence, and controls the transmission interval of the test frame according to the character period τ. The character period τ is calculated according to τ = (1 + d + h + s) / b. When the parity bit type p is None, h is 0, and when the parity bit type p is Even, Odd, Mark or Space, h is 1. The edge computing node continuously sends three test frames with identical byte content for each row in the serial port configuration table. After each test frame is sent, it stops sending other data and records the sequence of returned bytes received by the U5, the number of returned bytes, the arrival time of the first returned byte, the number of frame errors, the number of parity errors, the number of receive overflows, and the number of Break states. The test frame includes a device address field, a function field, a data field, and a check field. If the device address field in the returned byte sequence is the same as the device address field in the test frame, the function field is the same as the function field in the test frame, and the check field operation passes, the return is recorded as a valid return. The edge computing node records the number of invalid returns in the three tests as C, and adds the number of frame errors, parity errors, receive overflows, and break states to form the number of line errors E. The edge computing node sorts the number of bytes of the three valid returns in ascending order, takes the number of bytes in the second position L2, and calculates the sum of the absolute values of the differences between the three byte numbers and L2 to form the length discrete value L. The edge computing node sorts the time length between the completion time of the three test frames and the arrival time of the first returned byte in ascending order, takes the second position time length T2, and calculates the sum of the absolute values of the differences between the three time lengths and T2 to form the time discrete value T. The edge computing node first sorts the serial port configuration table in ascending order of C. If C is the same, it sorts in ascending order of E. If C and E are the same, it sorts in ascending order of L. If C, E, and L are the same, it sorts in ascending order of T. If C, E, L, and T are the same, it sorts in descending order of baud rate b. The edge computing node takes the first row of the sort and re-executes the test three times. If the first row of the sort has the same b, d, s, and p for two consecutive rounds, and C and E are both 0 for two consecutive rounds, and the difference between the third and first positions of the sort in the arrival time of the first returned byte in each round does not exceed the character period τ, the edge computing node stops the serial port configuration filtering and writes the first row of the sort to U5. If no valid return is obtained for any row in the serial port configuration table, the edge computing node outputs a serial port configuration unrecognized record, which includes the device address and C, E, L, and T of each row.
[0013] In a preferred embodiment, the edge computing node configures U5 based on the output baud rate b, data bits d, stop bits s, and parity type p, and establishes a device timing table. Each row of the device timing table sequentially records the device address, receive tributary identifier, request byte sequence, request completion time, arrival time of the first returned byte, and arrival time of the last returned byte. For devices connected to RS485-A and RS485-B, the receive tributary identifier is recorded as RXD1; for devices connected to RS232-RXD or TTL_RXD2, the receive tributary identifier is recorded as RXD2. The edge computing node continuously sends three request byte sequences for each device address, and does not send request byte sequences to other device addresses before the three requests and returns for one device address are completed. For each device address, the edge computing node records the completion times of three request transmissions as a1, a2, and a3, the arrival times of the first byte of the three returned requests as c1, c2, and c3, and the arrival times of the last byte of the three returned requests as e1, e2, and e3. It also calculates the delays of the first byte (c1-a1, c2-a2, c3-a3) and the delays of the last byte (e1-a1, e2-a2, e3-a3). The edge computing node arranges the three first byte delays in ascending order, using the first byte as the left end of the device response interval, and arranges the three last byte delays in ascending order, using the sum of the third byte delay and the character period τ as the right end of the device response interval. The device response interval, along with the device address and the receiving branch identifier, is written into the device timing table as input for the request timing arrangement. The edge computing nodes first arrange the device timing table in ascending order of device address, and then determine the sending time of each request byte sequence starting from the first row of the table. The sending time of the request in the first row of the table is recorded as 0, and the sending time of the request in the next row is equal to the sum of the sending time of the request in the previous row and the right end of the device response interval in the previous row. For two adjacent rows i and j in the table, the edge computing nodes calculate the first set of results according to the current order, and then swap the positions of the two rows to calculate the second set of results. Each set of results includes the number of overlapping response intervals K, the idle time of the response interval H, and the total time to complete all requests P. When the end time of the response interval of row i is higher than the start time of the response interval of row j, the difference between the two is recorded as an overlap time and K is incremented by 1. When the end time of the response interval of row i is not higher than the start time of the response interval of row j, the absolute value of the difference between the two is accumulated to H, and P is the end time of the response interval of the last row of the table. When the value of K in the second set of results is lower than the value of K in the first set of results, the edge computing node retains the order after the swap; when K is the same in both sets of results, and the value of H in the second set of results is lower than the value of H in the first set of results, the edge computing node retains the order after the swap; when both K and H are the same in both sets of results, and the value of P in the second set of results is lower than the value of P in the first set of results, the edge computing node retains the order after the swap; in other cases, the order before the swap is restored; the edge computing node completes the comparison of adjacent rows from the first row to the last row of the device timing table in sequence, and starts from the first row again after completing one round of comparison; when one round of comparison is completed continuously and no position swap occurs, the edge computing node stops requesting timing arrangement and drives U5 to send the request byte sequence according to the order in the device timing table and the request sending time; After each round of request execution, the edge computing node converts the arrival time of the actual first byte and the arrival time of the actual last byte into a delay relative to the request completion time. If the actual first byte delay is earlier than the left end of the device response interval, the left end of the device response interval is replaced with the actual first byte delay. If the actual last byte delay is later than the right end of the device response interval, the right end of the device response interval is replaced with the sum of the actual last byte delay and the character period τ. The edge computing node re-executes the comparison of adjacent rows using the updated device response interval. If no overlap occurs between any two device response intervals in two consecutive rounds, the check field operation of all returned byte sequences passes, and the number of frame errors, parity errors, receive overflows, and Break states recorded in U5 are all 0, the edge computing node outputs the request timing table. If the number of execution rounds reaches twice the number of rows in the device timing table and there is still an overlap of response intervals, the edge computing node outputs the overlapping device record, which includes the addresses of the two overlapping devices, the receive branch identifier, and the overlap time. The edge computing node is a computer, industrial gateway, or embedded host that connects to J1 via a USB interface and runs serial port parameter filtering and polling timing calculation programs on-site to configure U5 and process its data transmission and reception.
[0014] The technical effects and advantages of this invention are as follows: 1. The stainless steel braided armor layer covers the core wire harness and forms a continuous shielded connection with the USB metal shell, metal shielding shell and DB9 metal shell. This allows the armor layer to bear the external squeezing, stepping and bending forces, reducing the direct mechanical impact on the core wire and the joint welding position. At the same time, the metal shielding path reduces the coupling of external high-frequency electromagnetic fields to the USB differential line and serial port signal line through the cable gap, mitigating the problems of data garbled characters, frame errors and communication interruptions in industrial fields. 2. The U2 digital isolation circuit separates the USB side GND from the isolation side Ground, and supplies ISO_5V to the RS485 and RS232 conversion circuits through VISO output, reducing the direct electrical connection between the USB side and the industrial communication side, and reducing the impact of field potential fluctuations on the computing node side circuit. 3. The TXD and TX_EN signals output by U5 are isolated by U2 to form TTL-TXD and RE / DE. TTL-TXD is connected to TTL, RS232 and RS485 transmission paths at the same time, realizing the output of data from a single USB interface to devices with multiple serial port standards. 4. TTL_RXD1 output from U1 and TTL_RXD2 output from U4 are input to U3 after being reverse isolated by U2. U3 performs logical operations on RXD1 and RXD2 to form the RXD return signal, reducing the number of serial port receiving lines. 5. The edge computing node tests the baud rate, data bits, stop bits, and parity method according to the serial port configuration table, and filters communication parameters based on the changes in the amount of returned data, error status, and response time, making the serial port parameter configuration process when field devices are connected more standardized. Attached Figure Description
[0015] Figure 1 This is the circuit schematic diagram of the present invention. Detailed Implementation
[0016] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0017] Refer to the instruction manual appendix Figure 1 This embodiment provides a multi-functional, fully protected armored serial cable for connecting the USB interface of an edge computing node to field devices using TTL, RS232, or RS485 communication standards. The multi-functional, fully protected armored serial cable includes a USB signal input circuit J1, a USB-to-TTL output circuit U5, a TTL signal isolation output circuit U2, a TTL RXD signal distribution output circuit U3, a TTL signal-to-RS485 circuit U1, a TTL signal-to-RS232 circuit U4, a 5V-to-3.3V output circuit U7, a DB9 output connector J2, and armored physical protection components. The component numbers, pin numbers, network names, and connection paths in the circuit are as per the attached instruction manual. Figure 1 set up; The edge computing node is a computer, industrial gateway, or embedded host that sets up a processor, memory, USB host controller, and serial port driver; the USB host controller is connected to the USB signal input circuit J1 through the USB interface; the processor executes the serial port parameter filtering program and the request timing calculation program in the memory; the serial port driver writes the baud rate, data bits, stop bits, and parity bit type to U5, and reads the received byte sequence, received byte count, and line status word uploaded by U5; I. Relationship between power supply area and signal transmission The circuit board includes a USB-side circuit area using VCC_5V, VCC_3V3, and GND, and an isolation-side circuit area using ISO_5V, ISO_3.3V, and Ground. The USB signal input circuit J1, USB-to-TTL output circuit U5, and TTL RXD signal distribution output circuit U3 are located in the USB-side circuit area. The TTL signal to RS485 circuit U1, TTL signal to RS232 circuit U4, and 5V to 3.3V output circuit U7 are located in the isolation-side circuit area. The TTL signal isolation output circuit U2 spans between the two circuit areas. No direct conductive paths are established between GND and Ground on the circuit board's copper foil, pads, vias, and device pins. When transmitting data, U5 outputs TXD from pin 1 and TX_EN from pin 13; TXD enters from pin 3 of U2 and forms TTL-TXD from pin 14 of U2, and TX_EN enters from pin 4 of U2 and forms RE / DE from pin 13 of U2; TTL-TXD enters from pin 4 of J2, pin 4 of U1, and pin 11 of U4 respectively, so that the same serial port byte sequence forms TTL transmit signal, RS485 differential transmit signal, and RS232 transmit signal respectively; RE / DE enters from pins 2 and 3 of U1 at the same time to switch the receive and transmit states of U1. When receiving data, U1 outputs TTL_RXD1 from pin 1. TTL_RXD1 enters from pin 12 of U2 and forms RXD1 from pin 5 of U2. Pin 12 of U4, pin 1 of J2, and pin 11 of U2 are connected through the TTL_RXD2 network. TTL_RXD2 enters from pin 11 of U2 and forms RXD2 from pin 6 of U2. U3 performs an AND operation on RXD1 and RXD2, forming RXD from pin 4 of U3. RXD enters from pin 5 of U5 and is then converted by U5 into USB data reception. II. USB signal input circuit J1 The USB signal input circuit J1 has five pins; pin 1 of J1 is connected to VCC_5V, pin 2 forms a DM- network, pin 3 forms a DP+ network, and pins 4 and 5 are connected to GND; the 5V power supply wire in the USB cable is soldered to pin 1 of J1, the negative differential data wire is soldered to pin 2 of J1, the positive differential data wire is soldered to pin 3 of J1, and the ground wire is soldered to pins 4 and 5 of J1 respectively. After the USB interface of the edge computing node is plugged into the USB metal casing, the edge computing node is powered by VCC_5V through pin 1 of J1, and exchanges USB differential data with U5 through the DM- network and DP+ network; pins 4 and 5 of J1 are only connected to GND on the circuit board, and pins 4 and 5 of J1 are not used as connection terminals of the metal braided armor layer. III. USB to TTL output circuit U5 The USB to TTL output circuit U5 uses FT232RL; pin 16 of U5 is connected to pin 2 of J1 via the DM- network, and pin 15 of U5 is connected to pin 3 of J1 via the DP+ network; pins 4 and 20 of U5 are connected to VCC_5V; pins 7, 18, 21, 25, and 26 of U5 are connected to GND; pin 17 of U5 forms VCC_3V3; pin 1 of U5 forms TXD; pin 5 of U5 receives RXD; pin 13 of U5 forms TX_EN; Pins 3 and 11 of U5 are directly connected to form a loop between RTS and CTS; pins 2 and 9 of U5 are directly connected to form a loop between DTR and DSR; pins 6, 8, 10, 12, 14, 24, 27 and 28 of U5 are not connected to other devices or networks. R6 has a resistance of 4.7KΩ and is connected between VCC_5V and pin 19 of U5; R7 has a resistance of 10KΩ and is connected between pin 19 of U5 and GND; C9 and C10 each have a capacitance of 0.1μF and are connected between VCC_5V and GND respectively; C16 has a capacitance of 0.1μF and is connected between VCC_3V3 and GND. Pins 23, D1, R4, and VCC_3V3 of U5 are connected in sequence, with D1 being a yellow LED; pins 22, D2, R5, and VCC_3V3 of U5 are connected in sequence, with D2 being a green LED; the resistance values of R4 and R5 are both 499Ω; the display status of D1 and D2 is determined by the internal function settings of pins 23 and 22 of U5. The internal non-volatile configuration area of U5 sets the CBUS2 function of pin 13 to transmit enable output; when U5 starts transmitting a serial frame, pin 13 of U5 outputs the TX_EN level that puts U1 into the transmit state; after the last stop bit of the serial frame is transmitted, pin 13 of U5 returns to the TX_EN level that puts U1 into the receive state; TX_EN is not generated by U3, RTS or CTS. IV. TTL Signal Isolation Output Circuit U2 The TTL signal isolation output circuit U2 uses NSIP8941; pin 1 of U2 is connected to VCC_5V, pins 2 and 8 are connected to GND, pin 3 is connected to TXD, pin 4 is connected to TX_EN, pin 5 is connected to RXD1, pin 6 is connected to RXD2, and pin 7 is not connected to any other network; pins 9, 10, and 15 of U2 are connected to Ground, pin 11 is connected to TTL_RXD2, pin 12 is connected to TTL_RXD1, pin 13 is connected to RE / DE, pin 14 is connected to TTL-TXD, and pin 16 is connected to ISO_5V; TXD enters from pin 3 of U2, and forms TTL-TXD from pin 14 through the positive signal channel of U2; TX_EN enters from pin 4 of U2, and forms RE / DE from pin 13 through the positive signal channel of U2; TTL_RXD1 enters from pin 12 of U2, and forms RXD1 from pin 5 through the inverted signal channel of U2; TTL_RXD2 enters from pin 11 of U2, and forms RXD2 from pin 6 through the inverted signal channel of U2. C3 has a capacitance of 10μF, C5 has a capacitance of 0.1μF, and C3 and C5 are connected between VCC_5V and GND respectively; C2 has a capacitance of 10μF, C4 has a capacitance of 0.1μF, and C2 and C4 are connected between ISO_5V and Ground respectively; R9 and R10 both have a resistance of 4.7KΩ, R9 is connected between TTL_RXD1 and ISO_5V, and R10 is connected between TTL_RXD2 and ISO_5V; R9 and R10 keep TTL_RXD1 and TTL_RXD2 at a high level when no serial port data is being received; Pin 16 of U2 forms ISO_5V to the isolation side; ISO_5V supplies power to pin 9 of U1, U4, U7, and J2; the current carried by pin 16 of U2 satisfies: In the formula, This is the operating current of U1. This is the operating current of U4. This is the operating current of U7. This is the 5V current output from pin 9 of J2 to external devices. This refers to the current consumed by the 3.3V output from pin J2 on the input side of U7. For the conversion efficiency of U7, This is the allowable output current for pin 16 of U2; the power supply current for external devices is determined based on the datasheets for U2 and U7, and the operating currents of U1 and U4. V. TTL signal to RS485 conversion circuit U1 The TTL signal to RS485 converter U1 uses SP485EN; pin 1 of U1 is connected to TTL_RXD1, pins 2 and 3 are connected to RE / DE, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, and pin 8 is connected to ISO_5V. When RE / DE is in transmit state, U1 reads TTL-TXD from pin 4 and forms an RS485 differential voltage between pins 6 and 7; when RE / DE is in receive state, U1 reads the RS485 differential voltage from pins 6 and 7 and outputs TTL_RXD1 from pin 1; pins 2 and 3 of U1 use the same RE / DE network, allowing receive enable and transmit enable to switch according to the TX_EN state. The resistance values of R1, R2, and R3 are all 4.7KΩ; R1 is connected between TTL_RXD1 and ISO_5V; R2 is connected between RS485-B and ISO_5V; R3 is connected between RS485-A and Ground; the capacitance of C1 is 0.1μF, and C1 is connected between ISO_5V and Ground. D6 is connected between RS485-B and Ground, and D7 is connected between RS485-A and Ground. When a transient voltage relative to Ground appears on RS485-B, D6 forms a clamping path; when a transient voltage relative to Ground appears on RS485-A, D7 forms a clamping path; RS485-A is connected to pin 6 of J2, and RS485-B is connected to pin 7 of J2. When multiple field devices are connected to the RS485 bus, each RS485 device has a different device address; a request frame contains only one target device address, and RS485 devices with the same target device address return an acknowledgment frame, while the other RS485 devices remain in the receiving state; when termination matching is required, the termination resistor is connected to the two physical ends of the RS485 bus, and J2 does not internally set a fixed termination resistor between RS485-A and RS485-B; VI. TTL signal to RS232 converter circuit U4 The TTL signal to RS232 converter U4 uses an STI3232; pin 11 of U4 is connected to TTL-TXD, pin 14 to RS232-TXD, pin 13 to RS232-RXD, pin 12 to TTL_RXD2, pin 15 to Ground, and pin 16 to ISO_5V; pins 7, 8, 9, and 10 of U4 are not connected to other devices or networks. C11 has a capacitance of 0.1μF and is connected between pins 1 and 3 of U4; C12 has a capacitance of 0.1μF and is connected between pins 4 and 5 of U4; C7 has a capacitance of 0.1μF and is connected between pin 6 of U4 and Ground; C8 has a capacitance of 0.1μF and is connected between pin 2 of U4 and ISO_5V; C15 has a capacitance of 0.1μF and is connected between ISO_5V and Ground; U4 is configured according to... Figure 1 The pin numbers and capacitor connections in the assembly do not change the connection of C8 between pin 2 of U4 and ISO_5V. TTL-TXD enters pin 11 of U4, and after being converted by U4, it forms RS232-TXD from pin 14; RS232-RXD enters pin 13 of U4, and after being converted by U4, it forms TTL_RXD2 from pin 12. Pin 1 of D4 is connected to RS232-TXD, pin 2 is connected to TTL-TXD, and pin 3 is connected to Ground; pin 1 of D5 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, and pin 3 is connected to Ground; D4 forms a clamping path to Ground for RS232-TXD and TTL-TXD, and D5 forms a clamping path to Ground for TTL_RXD2 and RS232-RXD. Pin 1 of J2 and pin 12 of U4 share the TTL_RXD2 network. When using RS232 reception, the external RS232 device is connected to pins 2 and 3 of J2, and pin 1 of J2 remains open. When using TTL reception, the external TTL device is connected to pins 1 and 4 of J2, and pin 2 of J2 remains open. The RS232 receiving device and the TTL receiving device are not connected simultaneously in the same working cycle to prevent the external TTL output and pin 12 of U4 from driving TTL_RXD2 simultaneously. VII. TTL RXD Signal Distribution Output Circuit U3 The TTL RXD signal distribution output circuit U3 uses a 74AHC1G08; pin 1 of U3 is connected to RXD2, pin 2 is connected to RXD1, pin 3 is connected to GND, pin 4 forms RXD, and pin 5 is connected to VCC_5V; the capacitance of C14 is 0.1μF, and C14 is connected between VCC_5V and GND; RXD is connected to pin 5 of U5; U3 performs the following level operation: RXD = RXD1 ∧ RXD2; When both RXD1 and RXD2 are high, RXD outputs a high level; when RXD1 is low and RXD2 is high, RXD outputs a low level; when RXD1 is high and RXD2 is low, RXD outputs a low level; when both RXD1 and RXD2 are low, RXD outputs a low level. When no data is being transmitted via the serial port, RXD1 and RXD2 remain at a high level. RXD1 carries the return data from the RS485 device, and RXD2 carries the return data from the RS232 or TTL device. When both RXD1 and RXD2 carry return frames simultaneously, RXD forms the result of the AND operation of the two bit sequences, and RXD no longer represents any return frame. Therefore, the edge computing node arranges the request transmission order according to the device response interval to prevent return frames from different devices from overlapping in time. 8. 5V to 3.3V output circuit U7 The 5V to 3.3V output circuit U7 uses... Figure 1 The RS3236_3.3 is labeled as follows: Pin 1 of U7 is connected to ISO_5V, pin 2 is connected to Ground, pin 3 is connected to ISO_5V via R8, pin 4 is connected to Ground via C17, and pin 5 forms ISO_3.3V. The resistance of R8 is 10KΩ, and the capacitance of C17 is 0.01μF. The capacitances of EC1 and EC2 are both 10μF. EC1 is connected between ISO_5V and Ground, and EC2 is connected between ISO_3.3V and Ground. Figure 1 There is a solid wire electrical connection between pin 4 of U7 and C17. During assembly, the solid wire connection shall be followed. Figure 1 The NC next to pin 4 is a device symbol display text and is not treated as pin 4 being disconnected. ISO_5V enters pin 1 of U7, and U7 outputs ISO_3.3V from pin 5; ISO_3.3V is used to power pin 8 of J2; ISO_3.3V provides 3.3V power to external devices without changing the level domain of the signal network where TTL-TXD and TTL_RXD2 are located. 9. DB9 Output Connector J2 J2 is a 9-pin male connector; pin 1 of J2 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, pin 3 is connected to RS232-TXD, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, pin 8 is connected to ISO_3.3V, and pin 9 is connected to ISO_5V. J2 is a composite signal connector and does not follow the pin definitions of a standard RS232 nine-pin connector. External TTL devices use pins 1, 4, and 5; external RS232 devices use pins 2, 3, and 5; and external RS485 devices use pins 6, 7, and 5. Pins 8 and 5 are used when a 3.3V power supply is required, and pins 9 and 5 are used when a 5V power supply is required. Unused signal and power supply pins should be kept disconnected. Pin 5 of J2 belongs to the isolation side Ground; the metal casing of DB9 is an armor-type physical protection component and does not use pin 5 of J2 as a conductive connection terminal. 10. Armor-type physical protection components The armor-type physical protection assembly includes a core wire harness, an insulating sheath, a stainless steel braided armor layer, a USB metal shell, a metal shielding shell covering the circuit board, and a DB9 metal shell; the core wire harness includes a VCC_5V wire connected to pin 1 of J1, a DM- wire connected to pin 2 of J1, a DP+ wire connected to pin 3 of J1, and a GND wire connected to pins 4 and 5 of J1. The insulating sheath covers the core wire bundle along its length and is located between the core wire bundle and the stainless steel braided armor layer. When the core wire insulation layer is partially compressed, the insulating sheath prevents the stainless steel wire from contacting the core wire conductor. The stainless steel braided armor layer is woven by a first metal wire bundle and a second metal wire bundle; the first metal wire bundle is arranged around the insulating sheath along a first spiral direction, and the second metal wire bundle is arranged around the insulating sheath along a second spiral direction opposite to the first spiral direction; the first metal wire bundle and the second metal wire bundle are alternately located in the outer and inner layers at adjacent intersection positions, so that the braided structure forms a cylindrical cover around the insulating sheath. When the stainless steel braided armor layer is subjected to radial compression, the first and second metal wire bundles support each other at the intersection, and the radial load is distributed along the circumference and axial direction of the cable; when the cable is bent, the metal wire bundles in the two helical directions slip and change angle respectively, and the bending load is not concentrated on a single core wire; when the cable is subjected to axial tension, the helical metal wire bundles tighten along the axial direction and transmit the tension to the metal shells at both ends. The USB end of the stainless steel braided armor layer is unfolded circumferentially and welded to the USB metal shell; the DB9 end of the stainless steel braided armor layer is unfolded circumferentially and welded to the DB9 metal shell; the metal shielding shell covers the circuit board and makes conductive contact with the DB9 metal shell; the USB metal shell, the stainless steel braided armor layer, the DB9 metal shell and the metal shielding shell form a metal shielding path. The circuit board is fixed inside the metal shielding shell by insulating pillars; an insulating sleeve is set between the USB metal shell and the GND pad of J1; an insulating seat is set between the DB9 metal shell and pin 5 of J2; an insulating distance is set between the metal shielding shell and GND, Ground and each signal network; thus, the metal shielding path is not directly connected to GND or Ground, and GND and Ground do not form a bypass through the armored physical protection components. After assembly, shielded path continuity test and isolation path test are performed respectively; during shielded path continuity test, a detection current is applied between the USB metal casing and the DB9 metal casing. Measure voltage The shielding path resistance is calculated using the following formula: When the testing equipment obtains a finite resistance value, a conductive path is formed between the USB metal shell, the stainless steel braided armor layer, the DB9 metal shell, and the metal shielding shell; when the isolation path is tested, the DC continuity between the metal shielding path and GND, the metal shielding path and Ground, and GND and Ground are measured respectively, and no DC continuity is formed at any of the three test positions. XI. Serial Port Data Transmission and Return Path After the edge computing node writes the request byte sequence to U5, U5 converts the request byte sequence into TXD; TXD is then converted into TTL-TXD by U2, and TTL-TXD is simultaneously sent to the TTL output branch, RS485 output branch, and RS232 output branch; when using the address request response protocol, the device address in the request frame determines the device that returns the request frame, and other devices do not send data after receiving request frames with different addresses; When an RS485 device returns data, RS485-A and RS485-B enter U1. U1 outputs TTL_RXD1 from pin 1, and TTL_RXD1 is converted into RXD1 via U2. When an RS232 device returns data, RS232-RXD enters U4. U4 outputs TTL_RXD2 from pin 12, and TTL_RXD2 is converted into RXD2 via U2. When a TTL device returns data, the TTL receive signal enters TTL_RXD2 from pin 1 of J2, and TTL_RXD2 is converted into RXD2 via U2. U3 performs a bitwise AND operation on RXD1 and RXD2 to form RXD. U5 converts RXD into USB receive data and transmits it to the edge computing node. 12. Equipment Access Record The edge computing node establishes a device access record for each field device; the device access record includes at least the device address, interface type, J2 pin used, receive tributary identifier, request byte sequence, expected number of returned bytes, response start time limit, and verification field operation rules. When the interface type is RS485, the receiving tributary identifier is recorded as RXD1; when the interface type is RS232 or TTL, the receiving tributary identifier is recorded as RXD2; the edge computing node reads the interface type from the device access record and does not infer the interface type based on the received data; the RS232 device and the TTL device are selected to connect within one execution cycle; The expected number of bytes to be returned in the device access record is determined by the requested function field and the device communication protocol; fixed-length return frames directly record the number of bytes; variable-length return frames first read the length field, and then determine the position of the last byte of the return frame based on the length field; the response start time limit is determined by the time from the completion of the request reception to the sending of the first byte of the return, as recorded by the device communication protocol. 13. Serial Port Configuration Table and Character Cycle The edge computing node establishes a serial port configuration table; each row of the serial port configuration table records the baud rate b, data bits d, stop bits s, and parity bit type p in sequence. The baud rate b is set to 300bps, 600bps, 1200bps, 2400bps, 4800bps, 9600bps, 19200bps, 38400bps, 57600bps, 115200bps, 230400bps, 460800bps, 921600bps, 1500000bps, 2000000bps, and 3000000bps, respectively; the data bits d is 7 or 8; the stop bits s is 1 or 2; and the parity bit type p is Even, None, Odd, Mark, or Space. When the device under test uses RS232-TXD and RS232-RXD, the edge computing node deletes rows with a baud rate higher than 115200bps. A serial port character consists of a start bit, d data bits, h parity bits, and s stop bits; when the parity bit type is None, h is 0; when the parity bit type is Even, Odd, Mark, or Space, h is 1; the character period τ is calculated according to the following formula: The character period τ is in seconds; the edge computing node writes each row of the serial port configuration table into U5 sequentially; XIV. Test Frames and Verification Fields The test frame includes, in sequence, a device address field, a function field, a data field, and a check field; the device address field is used to specify the device under test; the function field is used to specify the read, query, or status return action; the data field is used to store the register address, the number of reads, or the test data; and the check field is used to determine whether a bit error occurred during the transmission of the returned byte sequence. When using CRC16 checksum, the edge computing node uses 0xFFFF as the initial CRC value. It performs an XOR operation on a byte to be checked with the lower eight bits of the CRC in byte order. After each XOR operation, it performs eight right shifts. When the least significant bit before the right shift is 1, it performs an XOR operation on the right shift result with 0xA001. When the least significant bit before the right shift is 0, it retains the right shift result. After all bytes to be checked have been processed, the checksum field is first written to the lower byte of the CRC, and then to the higher byte of the CRC. If the device address field in the returned byte sequence is the same as the device address field in the test frame, the function field is the same as the function field in the test frame, and the verification field operation passes, the return is recorded as a valid return; if no bytes are received, the return address is different, the returned function field is different, the number of returned bytes is insufficient, or the verification field operation fails, the return is recorded as an invalid return. 15. Definitions of transmission completion time and reception time When an edge computing node submits a test frame to the serial port driver, the serial port driver writes all bytes of the test frame into the U5 transmission buffer. The moment when the serial port driver confirms that all test bytes have been written into the U5 transmission buffer is recorded as the test frame transmission completion time. The test frame transmission completion time does not refer to the moment when the last stop bit leaves the TTL-TXD. All subsequent delay calculations are based on the moment when the serial port driver confirms that the writing is complete. When the serial port driver detects that the number of bytes in the U5 receive buffer changes from 0 to non-zero, it reads the same monotonically increasing timer and records the timing value. The recorded timing value is subtracted from the time when the test frame is sent to form the arrival time of the first byte. The arrival time of the first byte in this article refers to the time length from the end of the test frame being written into the U5 send buffer to the first return byte entering the U5 receive buffer, and does not represent the absolute time of the computer system. When the number of received bytes reaches the expected number of returned bytes in the device access record, or when the last byte of the verification field is read based on the returned frame length field, the arrival time of the last returned byte is recorded; the arrival time of the last returned byte also represents the time length relative to the time when the test frame was sent. XVI. Serial Port Configuration Test Record The edge computing node continuously sends three test frames with identical byte content to each row of the serial port configuration table; after each test frame is sent, the edge computing node does not send data to other devices, and determines the reception deadline W according to the response start time limit and expected number of returned bytes in the device access record. In the formula, The response start time limit in the device access record is m, the expected number of bytes to be returned is mτ, the return frame transmission time is 3.5τ, and the frame interval after the return frame ends. Each test generates a test record; the test record includes the returned byte sequence, the actual number of returned bytes, the arrival time of the first byte, the valid return identifier, the number of frame errors, the number of parity errors, the number of receive overflows, and the number of Break states; If no bytes are received within the receiving deadline W, the actual number of bytes returned is recorded as 0, the arrival time of the first byte is recorded as W, and the valid return identifier is recorded as invalid. When some bytes are received, the actual number of bytes returned is recorded according to the number of bytes in the receiving buffer, the arrival time of the first byte is recorded according to the timer difference, and a valid return identifier is generated based on the device address field, function field, expected number of bytes returned, and check field. Before each test, the edge computing node clears the U5 receive buffer and resets the frame error count, parity error count, receive overflow count, and Break state count to zero. The serial port driver reads the frame error bit, parity error bit, receive overflow bit, and Break state bit from the line status word returned by U5. When a status bit changes from an unoccupied state to an present state, the corresponding count is incremented by 1. The count is not incremented again during the duration of the Break state. 17. Calculation of C, E, L, and T The number of invalid returns in the three tests is denoted as C; the number of frame errors, parity errors, receive overflows, and break states in the three tests are added together to form the number of line errors, E. The actual number of bytes returned in the three tests are denoted as follows: , and When all three tests return valid results, , and This refers to the number of bytes returned in three valid responses. When invalid responses exist, they are still used in the length discrete value calculation based on the actual number of bytes received. If no bytes are received, the value is 0. The edge computing node will... , and Sort in ascending order, and the second position is denoted as Length discrete value Calculate according to the following formula: The arrival times of the first byte in the three tests are denoted as follows: , and Edge computing nodes will , and Sort in ascending order, and the second position is denoted as Discrete time values Calculate according to the following formula: Invalid return quantity Prior to and The serial port configuration with invalid returns will not be ranked before the serial port configuration with three valid returns due to its lower length discrete value or time discrete value. 18. Serial Port Configuration Sorting and Stopping Process The edge computing nodes first arrange the serial port configuration table in ascending order of C; if C is the same, arrange it in ascending order of E; if C and E are the same, arrange it in ascending order of L; if C, E, and L are the same, arrange it in ascending order of T; if C, E, L, and T are the same, arrange it in descending order of baud rate b. The first row is arranged to form a candidate configuration; the edge computing node writes the candidate configuration into U5, sends three test frames in succession, recalculates the C, E, L and T of the candidate configuration, and writes the calculation results back to the serial port configuration table and re-sorts them. This process is recorded as one round of verification. After two consecutive rounds of verification, if the first row of the two sorting has the same b, d, s, and p, and C and E in both rounds are 0, and the difference between the third and first byte after the arrival time of the three first bytes in each round is no more than the character period τ, the edge computing node stops the serial port configuration filtering and writes the first row of the sorting to U5. When the first row of the sorting changes after verification, the edge computing node performs the next round of verification on the new first row of the sorting; when no valid return is obtained for any row in the serial port configuration table, the edge computing node outputs a serial port configuration unrecognized record; the serial port configuration unrecognized record includes the device address, interface type, and b, d, s, p, C, E, L, and T of each row; 19. Equipment timing table and three-stage response acquisition The edge computing node uses serial port configuration to filter the b, d, s, and p configurations of U5 and establishes a device timing table. Each row of the device timing table records the device address, receive branch identifier, request byte sequence, request completion time, arrival time of the first returned byte, arrival time of the last returned byte, left end of the device response interval, and right end of the device response interval. For devices connected to RS485-A and RS485-B, the receiving tributary identifier is RXD1; for devices connected to RS232-RXD or TTL_RXD2, the receiving tributary identifier is RXD2. An edge computing node sends three consecutive request byte sequences to a device address. Before the three requests and responses are completed, it does not send request byte sequences to other device addresses. The completion times of the three requests are recorded as a1, a2, and a3, respectively. The timing values for the first byte of the three responses entering the U5 receive buffer are recorded as c1, c2, and c3, respectively. The timing values for the last byte of the three responses entering the U5 receive buffer are recorded as e1, e2, and e3, respectively. The delay of the first byte is calculated according to c1-a1, c2-a2, and c3-a3 respectively; the delay of the last byte is calculated according to e1-a1, e2-a2, and e3-a3 respectively; the first byte after the three first byte delays are arranged in ascending order is taken as the left end of the device response interval; the sum of the third byte after the three last byte delays are arranged in ascending order and the character period τ is taken as the right end of the device response interval. If an invalid response is returned in three requests for a device address, the device address will not be included in the request sequence arrangement, and no record will be established for the device response interval output by the edge computing node. The unestablished record for the device response interval includes the device address, the receiving tributary identifier, the number of invalid responses, and the number of line errors. 20. Time base for requesting transmission The request sending time in the device timing table refers to the moment when the entire serial port driver confirmation request byte sequence is written into the U5 transmit buffer, not the moment when the last stop bit of the request frame leaves the TTL-TXD; the left and right ends of the device response interval both take the request sending time as the zero point, so the device response interval already includes the time taken for the request byte sequence to be sent by U5, for the field device to receive the request, for the field device to form an acknowledgment, and for the return byte to enter the U5 receive buffer; With this time base, the request sending time of the subsequent device is set after the right end of the device response interval of the preceding device. The last byte returned by the preceding device has already entered the U5 receive buffer, and the request byte sequence of the subsequent device is written into the U5 send buffer, thereby avoiding the overlap between the request sending process and the return process of the preceding device. 21. Request Initial Sequence Arrangement The edge computing nodes first arrange the device timing table in ascending order of device address. The request sending time of the first row is recorded as 0. The request sending time of each subsequent row is equal to the sum of the request sending time of the previous row and the right end of the device response interval of the previous row. The time when the request was sent is recorded as The left end of the device response interval is denoted as The right end of the device response interval is denoted as ,equipment The start time of the absolute response interval and termination time Calculate according to the following formulas respectively: The first row of the arrangement satisfies Equipment in arrangement Located in the equipment Afterwards, the following conditions are met: The calculated times are all relative to the start time of a round of requests. Before the edge computing node starts actually sending, the current monotonically increasing timer reading is recorded as the reference time, and the request sending times in the device timing table are added to the reference time to form the execution time of each request. 22. Number of overlapping response intervals, K Edge computing nodes calculate the overlap time of response intervals for any two rows i and j in the device timing table, starting from... and The earlier value is selected as the candidate termination time for overlap, and then from... and The later value in the middle is taken as the start time of the overlapping candidate. When the end time of the overlapping candidate is later than the start time of the overlapping candidate, the response intervals of device i and device j overlap. The overlap time is calculated according to the following formula: When the termination time of overlapping candidates is not later than the start time of overlapping candidates. Recorded as 0; the number of overlapping response intervals is calculated by traversing all device pairs in the device timing table of the edge computing node. Calculate according to the following formula: In the formula, This represents the number of rows in the device timing table. exist Take 1 at time, in When the time interval is 0; the initial arrangement is based on the right end of the device response interval when the request is requested. Typically, the value is 0. However, in actual operation, when the response time of the field equipment exceeds the equipment response interval formed by three samplings, the updated equipment response intervals will overlap. Used to record the number of overlapping device pairs; 23. Response interval idle time H and request completion time P Edge computing nodes check adjacent response intervals according to the device timing table row order; when the start time of the next response interval is later than the end time of the previous response interval, the difference between the two is recorded as the idle time; when the start time of the next response interval is not later than the end time of the previous response interval, the idle time is recorded as 0; the idle times of all adjacent response intervals are added together to form H; The end time of the response interval in the last row of the device timing table is denoted as P; P represents the time elapsed from the base time of a round of requests to the end of the last device's response. 24. Interchange of adjacent rows and stopping sorting The edge computing node selects two adjacent rows i and j starting from the first row of the device timing table; while maintaining the current row order, it recalculates the request sending time, response interval start time, and response interval end time of all rows, and calculates the first set of K, H, and P; after swapping the positions of the two rows, it recalculates the request sending time, response interval start time, and response interval end time of all rows again, and calculates the second set of K, H, and P. When the second group K is lower than the first group K, the edge computing nodes retain the order after the swap; when both groups K are the same, and the second group H is lower than the first group H, the edge computing nodes retain the order after the swap; when both groups K and H are the same, and the second group P is lower than the first group P, the edge computing nodes retain the order after the swap; in other cases, the order before the swap is restored. Edge computing nodes compare adjacent rows sequentially from the first row to the last row of the device timing table to form one round of sorting; after one round of sorting is completed, they start again from the first row; when one round of sorting is completed and no row position swap occurs, the edge computing node stops requesting timing arrangement; 25. Request Execution and Device Response Interval Update The edge computing node writes the request byte sequence to U5 according to the order in the device timing table and the request sending time; before each round of request execution, the edge computing node clears the line error count; after each request is sent, the edge computing node records the actual arrival time of the first returned byte and the actual arrival time of the last returned byte, and performs operations on the return frame address field, function field and check field; equipment The actual first byte delay is denoted as The actual last byte delay is denoted as If the actual first byte delay is earlier than the left end of the device response interval, the left end of the device response interval is replaced by the actual first byte delay; if the actual last byte delay is later than the right end of the device response interval, the actual last byte delay is multiplied by the character period. The sum replaces the right end of the device response range, and the update rule is expressed as follows: in Indicates the first The left-hand time of the updated response interval of each device is used to record the time boundary when the first byte of the device returns. This represents the leftmost time of the response interval that was saved before the i-th device was updated; This means selecting the earlier time value from two time values, causing the left end of the response interval to expand in the earlier direction; This represents the right-hand end of the response interval after the i-th device updates, used to record the end position of the device's return. This represents the rightmost time of the response interval that was saved before the i-th device was updated; This means selecting the later time value from two time values, causing the right end of the response interval to expand in the delayed direction; The device response interval only expands to the left of the earlier time or the right of the later time, and the already recorded response delay range is not deleted due to a short response; the edge computing node uses the updated device response interval to re-execute adjacent row swapping and request timing reordering; 26. Request timing output and overlay device record In two consecutive rounds of request execution, if the response intervals of any two devices do not overlap, the verification field operation of all returned byte sequences passes, and the number of frame errors, parity errors, receive overflows, and Break states recorded by U5 are all 0, the edge computing node outputs the request timing table. The request timing table includes the device address, receive tributary identifier, request byte sequence, request sending time, device response interval start time, device response interval end time, response interval overlap number K, response interval idle time H, and request completion time P; When the device timing table has N rows, the number of execution rounds increases by 1 after each completion of all device requests, device response interval updates, and adjacent row sorting. If there are still overlapping response intervals after the number of execution rounds reaches 2N, the edge computing node stops requesting timing updates and outputs the overlapping device records. The overlapping device record includes the addresses of the two overlapping devices, the identifiers of the two receiving branches, the start time of the response intervals of the two devices, the end time of the response intervals of the two devices, and the overlapping time. The overlapping device record is used to determine the combination of devices that return simultaneously. During field operation, the overlapping devices are assigned to different request batches, or the request sending time of one of the devices is delayed, so that RXD1 and RXD2 do not carry different return frames in the same time period.
[0018] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.
Claims
1. A multi-functional full-protection armored serial cable, characterized by, include: USB signal input circuit J1, USB to TTL output circuit U5, TTL signal isolation output circuit U2, TTL RXD signal distribution output circuit U3, TTL signal to RS485 circuit U1, TTL signal to RS232 circuit U4, 5V to 3.3V output circuit U7, DB9 output connector J2, and armored physical protection components. The TXD signal of U5 is transmitted through U2 to form TTL-TXD, and the TX_EN signal of U5 is transmitted through U2 to form RE / DE. TTL-TXD is connected to pin 4 of J2, pin 4 of U1, and pin 11 of U4 respectively. RE / DE is connected to pin 2 and pin 3 of U1. Pin 1 of U1 forms TTL_RXD1, which is transmitted through U2 to form RXD1. Pin 12 of U4, pin 1 of J2, and pin 11 of U2 are connected through the TTL_RXD2 network. TTL_RXD2 is transmitted through U2 to form RXD2. U3 performs a bitwise AND operation on RXD1 and RXD2 and sends the generated RXD to pin 5 of U5. Pin 16 of U2 forms ISO_5V. U7 converts ISO_5V to ISO_3.3V. The circuit containing U5 uses GND, while the circuits containing U1, U4, and U7 use Ground. GND and Ground are not directly connected on the circuit board. The armor-type physical protection component includes a USB metal shell, a stainless steel braided armor layer, a metal shielding shell covering the circuit board, and a DB9 metal shell. The two ends of the stainless steel braided armor layer are electrically connected to the USB metal shell and the DB9 metal shell, respectively, and the metal shielding shell is electrically connected to the DB9 metal shell.
2. The multifunctional fully protected armored serial cable according to claim 1, characterized in that: Pin 1 of J1 is connected to VCC_5V, pin 2 is connected to pin 16 of U5 through the DM- network, pin 3 is connected to pin 15 of U5 through the DP+ network, and pins 4 and 5 are connected to GND. U5 uses FT232RL. Pins 4 and 20 of U5 are connected to VCC_5V, pins 7, 18, 21, 25 and 26 are connected to GND, pin 17 forms VCC_3V3, pin 1 forms TXD, pin 5 receives RXD, pin 13 forms TX_EN, pins 3 and 11 are connected, pins 2 and 9 are connected, and pins 6, 8, 10, 12, 14, 24, 27 and 28 remain unconnected. R6 has a resistance of 4.7KΩ and is connected between VCC_5V and pin 19 of U5. R7 has a resistance of 10KΩ and is connected between pin 19 of U5 and GND. C9 and C10 each have a capacitance of 0.1μF and are connected between VCC_5V and GND. C16 has a capacitance of 0.1μF and is connected between VCC_3V3 and GND. Pins 23, D1, R4, and VCC_3V3 of U5 are connected in sequence. Pins 22, D2, R5, and VCC_3V3 of U5 are connected in sequence. The resistance of R4 and R5 is 499Ω.
3. The multifunctional fully protected armored serial cable according to claim 2, characterized in that: U2 uses NSIP8941. Pin 1 of U2 is connected to VCC_5V, pins 2 and 8 are connected to GND, pin 3 is connected to TXD, pin 4 is connected to TX_EN, pin 5 is connected to RXD1, pin 6 is connected to RXD2, pin 7 is left unconnected, pins 9, 10 and 15 are connected to Ground, pin 11 is connected to TTL_RXD2, pin 12 is connected to TTL_RXD1, pin 13 is connected to RE / DE, pin 14 is connected to TTL-TXD, and pin 16 is connected to ISO_5V. C3 has a capacitance of 10μF, C5 has a capacitance of 0.1μF, and C3 and C5 are connected between VCC_5V and GND respectively; C2 has a capacitance of 10μF, C4 has a capacitance of 0.1μF, and C2 and C4 are connected between ISO_5V and Ground respectively; R9 and R10 both have a resistance of 4.7KΩ, R9 is connected between TTL_RXD1 and ISO_5V, and R10 is connected between TTL_RXD2 and ISO_5V.
4. The multifunctional fully protected armored serial cable according to claim 3, characterized in that: U1 uses SP485EN. Pin 1 of U1 is connected to TTL_RXD1, pins 2 and 3 are connected to RE / DE, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, and pin 8 is connected to ISO_5V. The resistance values of R1, R2, and R3 are all 4.7KΩ. R1 is connected between TTL_RXD1 and ISO_5V, R2 is connected between RS485-B and ISO_5V, and R3 is connected between RS485-A and Ground. C1 has a capacitance of 0.1μF and is connected between ISO_5V and Ground. D6 is connected between RS485-B and Ground, and D7 is connected between RS485-A and Ground. RS485-A is connected to pin 6 of J2, and RS485-B is connected to pin 7 of J2.
5. A multifunctional, fully protected armored serial cable according to claim 4, characterized in that: U4 uses an STI3232. Pin 11 of U4 is connected to TTL-TXD, pin 14 to RS232-TXD, pin 13 to RS232-RXD, pin 12 to TTL_RXD2, pin 15 to Ground, and pin 16 to ISO_5V. Pins 7, 8, 9, and 10 remain unconnected. C11 has a capacitance of 0.1μF and is connected between pins 1 and 3 of U4. C12 has a capacitance of 0.1μF and is connected between pins 4 and 5 of U4. C7 has a capacitance of 0.1μF and is connected between pin 6 of U4 and Ground; C8 has a capacitance of 0.1μF and is connected between pin 2 of U4 and ISO_5V; C15 has a capacitance of 0.1μF and is connected between ISO_5V and Ground; pin 1 of D4 is connected to RS232-TXD, pin 2 is connected to TTL-TXD, and pin 3 is connected to Ground; pin 1 of D5 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, and pin 3 is connected to Ground.
6. A multi-functional, fully protected armored serial cable according to claim 5, characterized in that: U3 uses 74AHC1G08. Pin 1 of U3 is connected to RXD2, pin 2 is connected to RXD1, pin 3 is connected to GND, pin 4 forms RXD, pin 5 is connected to VCC_5V, and C14 has a capacitance of 0.1μF and is connected between VCC_5V and GND. U3 outputs a high level when both RXD1 and RXD2 are high, and outputs a low level when either RXD1 or RXD2 is low. The RXD output of U3 is connected to pin 5 of U5.
7. A multifunctional, fully protected armored serial cable according to claim 6, characterized in that: Pin 1 of U7 is connected to ISO_5V, pin 2 is connected to Ground, pin 3 is connected to ISO_5V via R8, pin 4 is connected to Ground via C17, and pin 5 forms ISO_3.3V. The resistance of R8 is 10KΩ, the capacitance of C17 is 0.01μF, and the capacitances of EC1 and EC2 are both 10μF. EC1 is connected between ISO_5V and Ground, and EC2 is connected between ISO_3.3V and Ground. J2 is a 9-pin male connector. Pin 1 of J2 is connected to TTL_RXD2, pin 2 is connected to RS232-RXD, pin 3 is connected to RS232-TXD, pin 4 is connected to TTL-TXD, pin 5 is connected to Ground, pin 6 is connected to RS485-A, pin 7 is connected to RS485-B, pin 8 is connected to ISO_3.3V, and pin 9 is connected to ISO_5V.
8. A multi-functional, fully protected armored serial cable according to claim 7, characterized in that: The armor-type physical protection component also includes a core wire harness and an insulating sheath covering the core wire harness. A stainless steel braided armor layer covers the insulating sheath circumferentially. The stainless steel braided armor layer is cross-woven from a first metal wire bundle arranged in a first helical direction and a second metal wire bundle arranged in a second helical direction, with the first helical direction being opposite to the second helical direction. The USB end of the stainless steel braided armor layer is welded to a USB metal shell, and the DB9 end of the stainless steel braided armor layer is welded to a DB9 metal shell. The metal shielding shell covers the circuit board and makes conductive contact with the DB9 metal shell. The insulating sheath separates the core wire harness from the stainless steel braided armor layer.
9. A multifunctional, fully protected armored serial cable according to claim 8, characterized in that: The edge computing node connected to the USB signal input circuit J1 establishes a serial port configuration table. Each row of the serial port configuration table records the baud rate b, data bits d, stop bits s, and parity bit type p in sequence. The baud rate b can be 300bps, 600bps, 1200bps, 2400bps, 4800bps, 9600bps, 19200bps, 38400bps, 57600bps, 115200bps, 230400bps, 460800bps, 921600bps, 1500000bps, 2000000bps and 3000000bps respectively; the number of data bits d can be 7 or 8; the number of stop bits s can be 1 or 2; and the parity bit type p can be Even, None, Odd, Mark or Space. When the device under test is connected to RS232-TXD and RS232-RXD, the edge computing node deletes rows with baud rates b higher than 115200bps; the edge computing node writes each row of the serial port configuration table into U5 in sequence, and controls the transmission interval of the test frame according to the character period τ. The character period τ is calculated according to τ = (1 + d + h + s) / b. When the parity bit type p is None, h is 0, and when the parity bit type p is Even, Odd, Mark or Space, h is 1. For each row in the serial port configuration table, three consecutive test frames with the same byte content are sent. After each test frame is sent, other data is stopped, and the sequence of returned bytes received by U5, the number of returned bytes, the arrival time of the first returned byte, the number of frame errors, the number of parity errors, the number of receive overflows, and the number of Break states are recorded. The test frame includes a device address field, a function field, a data field, and a check field. When the device address field in the returned byte sequence is the same as the device address field in the test frame, the function field is the same as the function field in the test frame, and the check field operation passes, the return is recorded as a valid return. The number of invalid returns in the three tests is denoted as C. The number of frame errors, parity errors, receive overflows, and break states are added together to form the number of line errors, E. The edge computing node sorts the number of bytes of the three valid returns in ascending order, takes the number of bytes in the second position L2, and calculates the sum of the absolute values of the differences between the three byte numbers and L2 to form the length discrete value L. The time length between the completion time of the three test frames and the arrival time of the first returned byte is sorted in ascending order, takes the second position time length T2, and calculates the sum of the absolute values of the differences between the three time lengths and T2 to form the time discrete value T. First, sort the serial port configuration table in ascending order of C. If C is the same, sort in ascending order of E. If C and E are the same, sort in ascending order of L. If C, E, and L are the same, sort in ascending order of T. If C, E, L, and T are the same, sort in descending order of baud rate b. Take the first row of the sort and re-execute the test three times. If the first row of the sort has the same b, d, s, and p for two consecutive rounds, and C and E are both 0 for two consecutive rounds, and the difference between the third and first positions of the sort in the arrival time of the first returned byte in each round does not exceed the character period τ, stop the serial port configuration filtering and write the first row of the sort to U5. If no valid return is obtained for any row in the serial port configuration table, the edge computing node outputs a serial port configuration unrecognized record, which includes the device address and C, E, L, and T of each row.
10. A multifunctional, fully protected armored serial cable according to claim 9, characterized in that: The edge computing node configures U5 based on the output baud rate b, data bits d, stop bits s, and parity type p, and establishes a device timing table. Each row of the device timing table records the device address, receive tributary identifier, request byte sequence, request completion time, arrival time of the first returned byte, and arrival time of the last returned byte in sequence. For devices connected to RS485-A and RS485-B, the receive tributary identifier is recorded as RXD1; for devices connected to RS232-RXD or TTL_RXD2, the receive tributary identifier is recorded as RXD2. Three consecutive request byte sequences are sent for each device address. Request byte sequences are not sent to other device addresses until the three requests and returns for one device address are completed. For each device address, the completion times of the three request transmissions are denoted as a1, a2, and a3, the arrival times of the first byte of the three returned requests are denoted as c1, c2, and c3, and the arrival times of the last byte of the three returned requests are denoted as e1, e2, and e3. The delays of the first byte (c1-a1, c2-a2, c3-a3) and the delays of the last byte (e1-a1, e2-a2, e3-a3) are calculated. The three delays of the first byte are arranged in ascending order, with the first position as the left end of the device response interval. The three delays of the last byte are arranged in ascending order, with the sum of the third position and the character period τ as the right end of the device response interval. The device response interval, along with the device address and the receiver branch identifier, is written into the device timing table as input for the request timing arrangement. The edge computing nodes first arrange the device timing table in ascending order of device address, and then determine the sending time of each request byte sequence starting from the first row of the table. The sending time of the request in the first row of the table is recorded as 0, and the sending time of the request in the next row is equal to the sum of the sending time of the request in the previous row and the right end of the device response interval in the previous row. For two adjacent rows i and j in the table, the edge computing nodes calculate the first set of results according to the current order, and then swap the positions of the two rows to calculate the second set of results. Each set of results includes the number of overlapping response intervals K, the idle time of the response interval H, and the total time to complete all requests P. When the end time of the response interval of row i is higher than the start time of the response interval of row j, the difference between the two is recorded as an overlap time and K is incremented by 1. When the end time of the response interval of row i is not higher than the start time of the response interval of row j, the absolute value of the difference between the two is accumulated to H, and P is the end time of the response interval of the last row of the table. When the value of K in the second set of results is lower than the value of K in the first set of results, the edge computing node retains the order after the swap; when K is the same in both sets of results, and the value of H in the second set of results is lower than the value of H in the first set of results, the edge computing node retains the order after the swap; when both K and H are the same in both sets of results, and the value of P in the second set of results is lower than the value of P in the first set of results, the edge computing node retains the order after the swap; in other cases, the order before the swap is restored; the edge computing node completes the comparison of adjacent rows from the first row to the last row of the device timing table in sequence, and starts from the first row again after completing one round of comparison; when one round of comparison is completed continuously and no position swap occurs, the edge computing node stops requesting timing arrangement and drives U5 to send the request byte sequence according to the order in the device timing table and the request sending time; After each round of request execution, the edge computing node converts the arrival time of the actual first byte and the arrival time of the actual last byte into a delay relative to the request completion time. If the actual first byte delay is earlier than the left end of the device response interval, the left end of the device response interval is replaced with the actual first byte delay. If the actual last byte delay is later than the right end of the device response interval, the right end of the device response interval is replaced with the sum of the actual last byte delay and the character period τ. The updated device response interval is used to re-execute the comparison of adjacent rows. If no overlap occurs between any two device response intervals in two consecutive rounds, the check field operation of all returned byte sequences passes, and the number of frame errors, parity errors, receive overflows, and Break states recorded in U5 are all 0, the edge computing node outputs the request timing table. If the number of execution rounds reaches twice the number of rows in the device timing table and there is still an overlap of response intervals, the overlapping device record is output. The overlapping device record includes the addresses of the two overlapping devices, the receiver branch identifier, and the overlap time.
