In response to your needs for "three-way power supply automation management", I have compiled a set of solutions for line monitoring and control using Thingboot intelligent hardware.

Considering that you mentioned "slightly colloquial", I did not use the too blunt official document tone, but preferred the actual engineering communication style. I hope it can help you understand more intuitively how to implement it.

1. Why do we need to "plug in" the wings of the Internet of Things to the three-way power supply?

In the operation and maintenance of automated equipment, three power supplies (usually the main power supply, the backup power supply, and the emergency/cold backup power supply) are the lifeblood to ensure uninterrupted production lines.

What are the biggest pain points we have encountered in the past? is "blind". Although the equipment room is equipped with voltmeters and indicator lights, no one knows if the main circuit trips when no one is on site; or it may be that one line of electricity has lost voltage, but the control logic is still switching to that line, causing the machine to shut down.

What we hope to achieve is:Even if I am sleeping at home, I can see the real-time status of the three circuits on my mobile phone; even if I am out of town, I can remotely close/open the circuit breaker, and even let the system automatically "shield" the faulty line.

Thingboot's open interface can solve this problem. The core logic of this solution is simple:Use intelligent hardware to replace human eyes (monitoring voltage) and hands (operating relays), transmit signals to the cloud through the network, and then let your business system make decisions.

2. Hardware selection and integration: How do we connect?

To realize the management of three-way power supply, hardware selection is the first step. Since we want to "integrate", we have to choose the right thing.

For three-way AC 380V or 220V power supply, choose the one within the Thingboot Ecosystem"Smart WiFi Controller (4-way/8-way version)"or"Smart WiFi PDU".

Why choose it?

• Multiplex control: This type of equipment usually supports 4 or 8 relay outputs, which corresponds to the control of your three power supplies (it can even leave one spare to control the cooling fan or alarm light).

• Dry contact/voltage detection: In addition to control, they generally support collecting the voltage status of the line.

• Easy to modify: It is not large in size and can be directly embedded in the existing distribution box and installed on the guide rail.

Physical wiring diagram:

1. Incoming line end: Connect the three power incoming lines (A/B/C) to the "input" detection terminal of the intelligent controller respectively.

2. Outgoing terminal: The "output end" of the controller is connected in series to the contactor coil loop of the line.

   • Simply put: The controller controls the on and off of the corresponding line contactor through the "pull-in" or "off" relay, thereby realizing line switching.

3. Core logic: status feedback and remote control (this is the key)

Now that the hardware is connected, how do you make the system "move" through Thingboot's open interface? There needs to be data flow in two directions:Upward (Feedback)andDownward (Control) .

1. How to "feed back" the line status? (Remote letter)

You want to know whether the three circuits have power now. This is status feedback.

• principle: The intelligent controller will collect the voltage value in the circuit in real time. You can use the interface of Thingboot throughPolling (active query)orAsynchronous message push (passive reception)to get data.

• Floor operation

  • Set up a "data flow" in the Thingboot console.

  • When the voltage is lower than the threshold (such as power failure), the device status change will trigger a message containingdevice_idand currentpower_status(likeline1=0Represents the data of No. 1 power outage).

  • What your business system needs to do: Receive this push, and then update it to the dashboard in your central control room in real time, or push it directly to the WeChat/DingTalk of the operation and maintenance personnel.

2. How to "control" line switching? (remote control)

When you find that the main line is out of power, or you want to remotely switch to the backup line for testing, you need to issue an order.According to Thingboot’s interface specification, issuing instructions is very straightforward:Call HTTP interfaceorPublishing messages via MQTT.

For example, suppose you want to "disconnect power supply No. 1 and close power supply No. 3":You can send an HTTP POST request to Thingboot Cloud with the following structure (simplified version):

After sending successfully, Thingboot Cloud will return to you a{"code":200}, which means that the command has been sent to the device. Within 1 second, the contactor in the distribution box will snap and the line switching is completed..

3. Strategy: Where to place the automation logic?

Since there are three circuits of electricity, switching logic is involved. For example, "If the main road has no power, switch to the backup road after a 2-second delay; if the backup road has no power, switch to the emergency road."

• Plan A (recommended)Cloud-edge collaboration. Write the core "power cut logic" on your business server.

  • process: The server receives the main path "power down" alarm -> determines whether the backup path status is normal -> issues the "switch to backup path" command.

  • advantage: The logic modification is flexible and the switching time or strategy can be adjusted at any time without having to go to the site to change the PLC code.

• Plan BDevice local logic. If the on-site network is unstable, you can use the "linkage rules" function of the smart controller (if available), or use built-in logic to automatically cut off when the network is disconnected.

4. Details and pitfalls in the implementation of the plan

As someone who has done integration, I know that just reading the interface documentation is not enough. Here are some practical experiences for your reference:

1. About the "interlock" mechanismIn three-way power switching,It is strictly prohibited to close both power supplies at the same time(Will short circuit).Although we have written clearly in the software logic "disconnect circuit B before switching circuit A", in order to prevent network delays or program bugs,During physical wiring, hard-wired interlocking (contactor auxiliary contacts in series) serves as the last line of insurance.. Software is responsible for intelligence, and hardware is responsible for life-saving.

2. Asynchronous messages about interfaces (this is important)Thingboot's documentation specifically mentions: Calling the interface returnscode 200only representsThe cloud received the instruction, does not representThe device actually executed successfully(For example, the device may happen to be offline).practice: Don’t just look at the interface return results. You need to listen to the "execution result" callback reported by the device. Only when the device actually pulls the relay on and produces a voltage change, and the device reports the status again, can you determine that "switching was successful" in business terms.

3. Data security and privatizationIf this is the power supply of a military factory or a bank's vault, the data cannot pass through the public network. Thingboot supports privatized deployment. You can set up the MQTT server on your intranet, so that all "closing and opening" commands only run within the LAN, which is fast and safe.

5. Summary

The change this solution brings to you is to make these three power supplies "visible, controllable, and manageable."

• visible: In the past, I had to go to the power distribution room to see the indicator lights, but now the red and green signs are directly displayed on the large screen, which is clear.

• Controllable: In the past, to switch the power supply, you had to run over and turn the switch. Now, engineers click the mouse in the office, or the system sets the switch automatically, which greatly shortens the business interruption time caused by power outages.

• integrated: You don’t have to develop hardware drivers from scratch. Thingboot has encapsulated the complex TCP/IP and MQTT protocols into simpledevice/controlinterface, you only need to focus on implementing the "three-way switching business logic" on your side.

To put it simply, you just need to buy a few relay modules that support remote control, connect the wires, call Thingboot's Yunkouzi to send a few instructions, and it's done.