2-Channel Micro USB Relay Module USB Smart Control Switch USB Intelligent Control Switch (2-Channel Micro USB)
Return this item for free
Free returns are available for the shipping address you chose. You can return the item for any reason in new and unused condition: no shipping charges
Learn more about free returns.- Go to your orders and start the return
- Select the return method
- Ship it!
Return this item for free
Free returns are available for the shipping address you chose. You can return the item for any reason in new and unused condition: no shipping charges
Learn more about free returns.- Go to your orders and start the return
- Select the return method
- Ship it!
Purchase options and add-ons
Connector Type | Micro Usb |
Contact Type | Normally Closed |
Current Rating | 10 Amps |
Brand | NOYITO |
Operation Mode | Automatic |
About this item
- NOYITO 2-Channel Micro USB Relay Module is equipped with a stable USB to serial port chip and a microcontroller. It can use the serial port debugging software to send serial commands on the computer to control the opening and closing of the 2-channel relay.
- Onboard high performance microcontroller chip, CH340 USB control chip.With power LED indicator and relay status LED.On-board 2-channel 5V, 10A/250VAC, 10A/30VDC relay, long relay life, can work 100,000 times continuously.
- Module with overcurrent protection and relay diode freewheel protection.
- NOYITO 8-Channel Micro USB Relay Module ASIN:B09RGTSHHW . NOYITO 4-Channel Micro USB Relay Module ASIN:B09RGVQXXT
- NOYITO 5V 2-Channel Micro USB Relay Module User Manual, Documentation, Schematic https://1drv.ms/u/s!AlzQUCOyZQhKfnmId9Qnm2btrs8?e=38YgQq
Similar items that may ship from close to you
- SainSmart USB 4 Channel Relay Automation (5V)Amazon's Choicein Electromechanical RelaysFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1
- SunFounder Lab 4 Relay Module 5V 4 Channels Relay Module Compatible with Arduino R3 1280 Arm PIC AVR STM32Amazon's Choicein Single Board ComputersFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1
- SainSmart USB Eight Channel Relay Board for Automation - 12 VFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1
- Ewelink WiFi Wireless Smart Relay Module USB DC 5v/12v/24v/48v 2 Channel Switch for Garage Door, Rolling Shutter Door, Electric CurtainFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1Only 20 left in stock - order soon.
- HiLetgo 2pcs 5V One Channel Relay Module Relay Switch with OPTO Isolation High Low Level TriggerFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1
- HiLetgo 2pcs 12V Single Bistable Self-Locking Relay Module Push to Start and StopAmazon's Choicein Electrical RelaysFREE Shipping on orders over $35 shipped by AmazonGet it as soon as Monday, Apr 1
Product details
- Product Dimensions : 1.97 x 1.57 x 0.59 inches; 1.13 ounces
- Date First Available : November 20, 2019
- Manufacturer : NOYITO
- ASIN : B081RM7PMY
- Country of Origin : USA
- Best Sellers Rank: #3,488 in Single Board Computers (Computers & Accessories)
- Customer Reviews:
Product Description
Features:
1. Onboard high-performance microcontrollers chip;
2. Onboard CH340 USB control chip;
3. Onboard power LED and relay status LED;
4. Onboard 2-way 5V, 10A / 250VAC, 10A / 30VDC relays, relay life can be a continuous pull 10 million times;
5. Module with overcurrent protection and relay diode freewheeling protection;
Hardware introduction and description
Board size: 50 x 40mm
Board Interface Description:
COM1: common;
NC1: normally closed;
NO1: normally open.
COM2: common;
NC2: normally closed;
NO2: normally open.
Communication protocol description:
LC USB switch default communication baud rate: 9600BPS
Open the first USB switch: A0 01 01 A2
Turn off the first USB switch: A0 01 00 A1
Open the second USB switch: A0 02 01 A3
Turn off the second USB switch: A0 02 00 A2
USB switch communication protocol
Data (1) --- start flag (default is 0xA0)
Data (2) --- switch address codes (0x01 and 0x02 represent the first and second switches, respectively)
Data (3) --- operating data (0x00 is "off", 0x01 is "on")
Data (4) --- check code
Relay status query command:
Send "FF" as hexadecimal (hex) to query.
For example, if relays 1 and 2 are ON, and relays 3 and 4 are OFF, sending the relay query command "FF"will return:
"CH1:ON \r\nCH2:ON \r\nCH3: OFF\r\nCH4:OFF\r\n"
(Each channel relay is to return 10 byte sequence information)
Usage Description:
1. Connect the USB relay module to the computer and install the CH340 USB to serial chip driver
2. Open the STC-ISP, SSCOM32 such serial debugging software, select the baud rate of 9600, in hexadecimal (hex) form send A0 01 01 A2 and A0 02 01 A3 can be opened the first and second relay ; Send in hexadecimal (hex) A0 01 00 A1 and A0 02 00 A2 can be turned off the first and second relay, respectively.
Package Included:
1pcs NOYITO 5V2-Channel Micro USB Relay Module
Important information
Legal Disclaimer
NOYITO 5V 2-Channel Micro USB Relay Module User Manual, Documentation, Schematic Download Link: https://www.amazon.com/clouddrive/share/IhYb2dP5OuYrDkQgFaowwGynxmnRJYZy867KvhirSsZ
Looking for specific info?
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonCustomers say
Customers like the performance and ease of use of the relay. For example, they mention it works great, is easy to get up and running, and is simple to program. That said, they appreciate the drivers are easily installed and the GUI is available to control output.
AI-generated from the text of customer reviews
Customers are satisfied with the performance of the relay. They mention that it works great, and is easy to use. Some say that it functions perfectly as a serial device under Linux and Mac. However, some customers report that the MODE command works fine but no such port is returned.
"...The results were the same however; MODE command worked fine but "no such port" was returned when I tried sending the hex file to the port...." Read more
"This works exactly as described, and the product description gives you all the information you really need to get going if you know programming...." Read more
"Works just as described. You don't even need to use any special software...." Read more
"...It works great, but I did have to drill down through windows update ->..." Read more
Customers find the relay easy to use, with a simple script it can be up and running in a few minutes. They say it's a true plug and play device with graphical user interface to control output.
"...Drivers are easily installed and there is a GUI available to control output." Read more
"...I'm using Keytext, which is easy to use and can auto-run a program on a schedule...." Read more
"This is very easy to get up and running with a simple script...." Read more
"This device is true plug and play. You plug it in and the system sees a serial port...." Read more
Reviews with images
-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Let me itemize the quirks:
communication to this device requires binary commands that make it difficult to control with a simple terminal program.
The USB chip is not FTDI, it is a Chinese variant that requires their own drivers.
The command set is write only, so there is no status readback command indicating the state of the relay.
Uses a micro USB interface.
The Features:
Uses USB VBUS to power the relays
10A Relays have compliance rating and have routings on PCB to provide HV/HE isolation
Drivers are easily installed and there is a GUI available to control output.
If you're like me (not a programmer) you will likely have some trouble creating a hex file, and I've seen some false info on the web saying how easy it is. Some claim you can create a text file in notepad and just save it as a .hex extension. This does not work; you end up with a "hex" file that has the hex equivalents of ASCII text characters.
I ended up using notepad++ (free) and installing their "hex editor" plug-in (after installing and starting notepad++, look under "Plugins", then "Plugin manager" and select the "hex editor" plugin and click the INSTALL button). You may have to restart notepad++ for the plugin to work.
Next, you will have to create a new file in notepad++, which will open in text editing mode, and then click the "H" icon to switch to hex editing. See photo. In hex mode you just click the empty cell under the "0" and type the characters you want, in this case "a00101a2" for the relay1 on command. Then save the file with an appropriate name and the .hex extension.
Here are the hex commands for each relay:
a0 01 01 a2 - relay 1 on
a0 01 00 a1 - relay 1 off
a0 02 01 a3 - relay 2 on
a0 02 00 a2 - relay 2 off
As others mentioned, I created a batch file (using notepad++) to send the hex file to the com port associated with the device. Simply type this in text editing mode and save this file with an appropriate name and the .bat extension.
mode com3: baud=9600 data=8
copy relay1_on.hex com3:
Make sure your batch and hex files are in a folder that the DOS command has access to. Mine work fine in c:\users\myname folder. You can then run the batch file by double-clicking it or trigger it using another program. I'm using Keytext, which is easy to use and can auto-run a program on a schedule. I'm using it to power up an external hard drive dock to run a backup job at night - I figured why run my external hard drive 24/7 if it only needs to run for an hour a day?
For troubleshooting purposes it may be helpful to add the "pause" command (just put the word "pause" as a third line) in the batch file. This will cause the DOS window to remain open after executing the commands, so you can see if there were any error messages returned by Windows.
=============================
For those interested, here's my ugly story trying to get this device working:
I first tried this device on a USB hub port and it was immediately recognized by Windows10 as a "CH340" (a common usb to serial device) on COM10. I figured I had it made, since it was recognized as an actual com port. Yea! But no, it was not going to be that easy.
While at a DOS prompt Windows happily accepted the MODE command to set the port parameters and responded that the port was configured and enabled. Great. But when I entered the "copy" command to send a .hex file to the port, Windows returned a "no such com port" response. This made no sense to me, so I tried a previously existing com port that had another device on it, and Windows sent the hex file with no problem. That proved to me that my COPY command was working and Windows could find the hex file. Obviously the problem was with the device or com port.
Then I tried using Device Manager to manually configure the device to another unused port, in this case com2. Again, the MODE command worked fine but Windows returned the "no such com port" message when trying to send the hex file. Very frustrating.
So then I moved the device to a USB port directly on the PC, and again it was recognized as CH340 and COM10. The results were the same however; MODE command worked fine but "no such port" was returned when I tried sending the hex file to the port. I spent another hour trying other USB ports on the PC and attempting to change the device to different com ports. Windows would not let me change it to com3 through 9, claiming they were in use, so I tried several supposedly unused ports and always got the same (no such com port) results.
After about 2 hours of plugging and unplugging ad infinitum, I accidentally connected the device to the USB cable from the USB hub - VOILA! Now, for some unknown reason, Windows decided to assign COM3 to the device and from that point forward everything worked perfectly. I can unplug and re-plug the device and it always comes up as COM3 and all of the relay commands work like they should. Beats me, I still have no idea why it refused to work on any of the other USB ports. I would investigate further but it's working now, and I am afraid it will start acting goofy again if I make any changes.
Reviewed in the United States on September 26, 2022
If you're like me (not a programmer) you will likely have some trouble creating a hex file, and I've seen some false info on the web saying how easy it is. Some claim you can create a text file in notepad and just save it as a .hex extension. This does not work; you end up with a "hex" file that has the hex equivalents of ASCII text characters.
I ended up using notepad++ (free) and installing their "hex editor" plug-in (after installing and starting notepad++, look under "Plugins", then "Plugin manager" and select the "hex editor" plugin and click the INSTALL button). You may have to restart notepad++ for the plugin to work.
Next, you will have to create a new file in notepad++, which will open in text editing mode, and then click the "H" icon to switch to hex editing. See photo. In hex mode you just click the empty cell under the "0" and type the characters you want, in this case "a00101a2" for the relay1 on command. Then save the file with an appropriate name and the .hex extension.
Here are the hex commands for each relay:
a0 01 01 a2 - relay 1 on
a0 01 00 a1 - relay 1 off
a0 02 01 a3 - relay 2 on
a0 02 00 a2 - relay 2 off
As others mentioned, I created a batch file (using notepad++) to send the hex file to the com port associated with the device. Simply type this in text editing mode and save this file with an appropriate name and the .bat extension.
mode com3: baud=9600 data=8
copy relay1_on.hex com3:
Make sure your batch and hex files are in a folder that the DOS command has access to. Mine work fine in c:\users\myname folder. You can then run the batch file by double-clicking it or trigger it using another program. I'm using Keytext, which is easy to use and can auto-run a program on a schedule. I'm using it to power up an external hard drive dock to run a backup job at night - I figured why run my external hard drive 24/7 if it only needs to run for an hour a day?
For troubleshooting purposes it may be helpful to add the "pause" command (just put the word "pause" as a third line) in the batch file. This will cause the DOS window to remain open after executing the commands, so you can see if there were any error messages returned by Windows.
=============================
For those interested, here's my ugly story trying to get this device working:
I first tried this device on a USB hub port and it was immediately recognized by Windows10 as a "CH340" (a common usb to serial device) on COM10. I figured I had it made, since it was recognized as an actual com port. Yea! But no, it was not going to be that easy.
While at a DOS prompt Windows happily accepted the MODE command to set the port parameters and responded that the port was configured and enabled. Great. But when I entered the "copy" command to send a .hex file to the port, Windows returned a "no such com port" response. This made no sense to me, so I tried a previously existing com port that had another device on it, and Windows sent the hex file with no problem. That proved to me that my COPY command was working and Windows could find the hex file. Obviously the problem was with the device or com port.
Then I tried using Device Manager to manually configure the device to another unused port, in this case com2. Again, the MODE command worked fine but Windows returned the "no such com port" message when trying to send the hex file. Very frustrating.
So then I moved the device to a USB port directly on the PC, and again it was recognized as CH340 and COM10. The results were the same however; MODE command worked fine but "no such port" was returned when I tried sending the hex file to the port. I spent another hour trying other USB ports on the PC and attempting to change the device to different com ports. Windows would not let me change it to com3 through 9, claiming they were in use, so I tried several supposedly unused ports and always got the same (no such com port) results.
After about 2 hours of plugging and unplugging ad infinitum, I accidentally connected the device to the USB cable from the USB hub - VOILA! Now, for some unknown reason, Windows decided to assign COM3 to the device and from that point forward everything worked perfectly. I can unplug and re-plug the device and it always comes up as COM3 and all of the relay commands work like they should. Beats me, I still have no idea why it refused to work on any of the other USB ports. I would investigate further but it's working now, and I am afraid it will start acting goofy again if I make any changes.
The option of a small case for this, or a link to one, would be nice - the other relay brand I tested came in a case, which makes me feel a lot better about leaving it unattended. The other brand is also much less noisy than this switch.
It does what it says it will do, though; the durability test will only come with time.
Reviewed in the United States on October 31, 2023
The option of a small case for this, or a link to one, would be nice - the other relay brand I tested came in a case, which makes me feel a lot better about leaving it unattended. The other brand is also much less noisy than this switch.
It does what it says it will do, though; the durability test will only come with time.
#PowerShell Script for LCUS-2 USB Relay
#This example "presses" the right pushbutton then the center pushbutton on a Lego Spike Prime Hub
#Assumes wires running from the 1st Channel of the USB relay's Common and N.O. contacts to the Hub's center pushbutton contacts
#Assumes wires running from the 2nd Channel of the USB relay's Common and N.O. contacts to the Hub's right pushbutton contacts
#Set file association of .ps1 PowerShell files to the following so the script can be run...
#C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
#This might not work if the name of this .ps1 file contains spaces
#May need to use the command below in PowerShell (Run as Administrator) one time for this script to work
#set-executionpolicy remotesigned
#Convert the relay's hexidecimal on/off codes to bytes and assign to "hex_on" & "hex_off" variables
[Byte[]] $hex_on = 0xA0,0x01,0x01,0xA2 #Center pushbutton
[Byte[]] $hex_off = 0xA0,0x01,0x00,0xA1 #Center pushbutton
[Byte[]] $hex2_on = 0xA0,0x02,0x01,0xA3 #Right pushbutton
[Byte[]] $hex2_off = 0xA0,0x02,0x00,0xA2 #Right pushbutton
#Assign the "port" variable to the proper COM port for "USB-SERIAL CH340" - Change COM port below if not on COM4!!!!!!!
#Run the following in PowerShell to find the relay's COM port (or check using Device Manager)
#(Get-WmiObject -query "SELECT * FROM Win32_PnPEntity" | Where {$_.Name -Match "COM\d+"}).name
$port = new-Object System.IO.Ports.SerialPort COM4,9600,None,8,one
$port.Open() #Open serial connection
Start-Sleep 1 #Wait to ensure USB relay is ready
#Simulate pressing the Spike Prime Hub right button for 0.3 seconds
$port.Write($hex2_on, 0, 4) #Turn ON USB relay - button-bypass attached to USB relay is activated
Start-Sleep -M 300 #Wait 0.3 seconds (relay remains on, button-bypass still activated)
$port.Write($hex2_off, 0, 4) #Turn OFF USB relay - button-bypass attached to USB relay is deactivated
Start-Sleep 1 #Wait 1 second
#Simulate pressing the Spike Prime Hub center button for 1 second
$port.Write($hex_on, 0, 4) #Turn ON USB relay - button-bypass attached to USB relay is activated
Start-Sleep 1 #Wait 1 second (relay remains on, button-bypass still activated)
$port.Write($hex_off, 0, 4) #Turn OFF USB relay - button-bypass attached to USB relay is deactivated
#Played nicer with AutoHotKey script when adding the delay below (could have been in my head)
Start-Sleep 1 #Wait 1 second
$port.Close() #Close serial connection
Start-Sleep 1 #Wait 1 second
#End of PowerShell Script------------------------------------------------------------------------------------
EDIT:
Having the PowerShell windows popping up while trying to use the laptop for other things at the same time got annoying. Now, I run the PowerShell scripts in the background. To do this, my AutoHotKey script calls a VBScript such as the one below, which calls a PowerShell script such as the one above.
Set objShell = CreateObject("WScript.Shell")
'Replace the filepath and filename of the .ps1 file in the line below with your own
objShell.Run "CMD /C START /B " & objShell.ExpandEnvironmentStrings("%SystemRoot%") & "\System32\WindowsPowerShell\v1.0\powershell.exe -file " & "C:\Users\YourUserName\YourFolder\YourSubFolder\YourPowerShellScript.ps1", 0, False
Set objShell = Nothing
'End of VBScript
#PowerShell Script for LCUS-2 USB Relay
#This example "presses" the right pushbutton then the center pushbutton on a Lego Spike Prime Hub
#Assumes wires running from the 1st Channel of the USB relay's Common and N.O. contacts to the Hub's center pushbutton contacts
#Assumes wires running from the 2nd Channel of the USB relay's Common and N.O. contacts to the Hub's right pushbutton contacts
#Set file association of .ps1 PowerShell files to the following so the script can be run...
#C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
#This might not work if the name of this .ps1 file contains spaces
#May need to use the command below in PowerShell (Run as Administrator) one time for this script to work
#set-executionpolicy remotesigned
#Convert the relay's hexidecimal on/off codes to bytes and assign to "hex_on" & "hex_off" variables
[Byte[]] $hex_on = 0xA0,0x01,0x01,0xA2 #Center pushbutton
[Byte[]] $hex_off = 0xA0,0x01,0x00,0xA1 #Center pushbutton
[Byte[]] $hex2_on = 0xA0,0x02,0x01,0xA3 #Right pushbutton
[Byte[]] $hex2_off = 0xA0,0x02,0x00,0xA2 #Right pushbutton
#Assign the "port" variable to the proper COM port for "USB-SERIAL CH340" - Change COM port below if not on COM4!!!!!!!
#Run the following in PowerShell to find the relay's COM port (or check using Device Manager)
#(Get-WmiObject -query "SELECT * FROM Win32_PnPEntity" | Where {$_.Name -Match "COM\d+"}).name
$port = new-Object System.IO.Ports.SerialPort COM4,9600,None,8,one
$port.Open() #Open serial connection
Start-Sleep 1 #Wait to ensure USB relay is ready
#Simulate pressing the Spike Prime Hub right button for 0.3 seconds
$port.Write($hex2_on, 0, 4) #Turn ON USB relay - button-bypass attached to USB relay is activated
Start-Sleep -M 300 #Wait 0.3 seconds (relay remains on, button-bypass still activated)
$port.Write($hex2_off, 0, 4) #Turn OFF USB relay - button-bypass attached to USB relay is deactivated
Start-Sleep 1 #Wait 1 second
#Simulate pressing the Spike Prime Hub center button for 1 second
$port.Write($hex_on, 0, 4) #Turn ON USB relay - button-bypass attached to USB relay is activated
Start-Sleep 1 #Wait 1 second (relay remains on, button-bypass still activated)
$port.Write($hex_off, 0, 4) #Turn OFF USB relay - button-bypass attached to USB relay is deactivated
#Played nicer with AutoHotKey script when adding the delay below (could have been in my head)
Start-Sleep 1 #Wait 1 second
$port.Close() #Close serial connection
Start-Sleep 1 #Wait 1 second
#End of PowerShell Script------------------------------------------------------------------------------------
EDIT:
Having the PowerShell windows popping up while trying to use the laptop for other things at the same time got annoying. Now, I run the PowerShell scripts in the background. To do this, my AutoHotKey script calls a VBScript such as the one below, which calls a PowerShell script such as the one above.
Set objShell = CreateObject("WScript.Shell")
'Replace the filepath and filename of the .ps1 file in the line below with your own
objShell.Run "CMD /C START /B " & objShell.ExpandEnvironmentStrings("%SystemRoot%") & "\System32\WindowsPowerShell\v1.0\powershell.exe -file " & "C:\Users\YourUserName\YourFolder\YourSubFolder\YourPowerShellScript.ps1", 0, False
Set objShell = Nothing
'End of VBScript