SainSmart USB Eight Channel Relay Board for Automation - 12 V

This will work in linux. I am running MX Linux 23 which uses Debian Bookworm 12 as it's core. First install all your needed packages and dependencies ie sudo apt-get install libftdi1 libftdi-dev libusb-dev.. Google search this and make sure you have all of your needed stuff then search for crelay "This software is intended to run on Linux systems to control USB relay cards from different manufacturers in a unified way." Make sure you get crelay installed. Then using command line is easy as typing crelay -i in your terminal to get the serial. Now issue a command like this (crelay -s AQ03CFDT 1 ON) or (crelay -s AQ03CFDT 1 OFF). Beautiful magic melody to my ears...my sweet little tap dancers....

I purchased this to switch contacts in a data acquisition setup. It works well, all relays function correctly. The 'Relay Manager' program that you can download from the link (and their website) works perfectly.I am having only one issue. I am using LabVIEW to control the board and I cannot get the given (from the download link) library files to open the board. That is, I can run the Open file and get an OK error status in return (it will return various error statuses, depending on the result) but the board will not actually open. I can get the device description, location and handle, but no communication connection. I tried a USB sniffer to check the data going over the port but couldn't seem to find what I was looking for.I contacted the company and was given all the information that I already had. They were very prompt and courteous, but no real help. I never spoke with a programmer, only a secretary or some such.The problem may be with LabVIEW but seems to be some command that I don't know since I can send other commands correctly. I am running Windows 7 and that may be an issue since the library files were written several years ago, although they have stated that they are compatible with this version of Windows and I am not having any other problems.Anyway, my solution (until I can figure out what to do) is to open the board with the 'Relay Manager' and then send commands to the board as I like using my LabVIEW program. I only have to open the board once until I restart my computer and can close the Relay Manager (the initial handshake, whatever it is, remains) and open and close LabVIEW as often as I like with no problems.Now, I had to experiment to find the commands to turn the relays on and off because I could not get their supplied commands to work. I tried and tried and might try some more later but I found what I need through trial and error so it's not an urgent issue right now. As an example, the company said to use FF 01 01 to turn on channel 1. I couldn't get that to work and use 11 instead.So, since the problem seems to be with my programming (although the given D2XX commands don't list anything to cover how to get an initial handshake and I have installed all of the necessary .net files and various drivers) I know that the board works (since their program works well) and I have found the commands to do what I want... I will give it five stars. The board is capable of allowing interface with external switches and will be very useful once I figure out how to get full control over it.edit: For those that are interested, I found the commands for this board (chip). I got a little time and decided to make a program like the one that is provided by the company. I was (once again) trying in vain to get their commands to work and finally just decided to try everything. Well, it turns out that it's pretty simple. After various combinations I found that the on/off state of the switches (relays) are simply represented by binary code from 0 to 255. That is, 00000001 (1 decimal, 01 hex) gives relay #1 on (rest off); 11111111 (255 decimal, FF hex) gives all relays on; 00101101 (45 decimal, 2D hex) gives relays 1, 3, 4, 6 on and the rest off; etc. Also, the communication problem was likewise easily fixed with a little attention to detail.Have fun.

set this up for dof with my virtual pinball table. works easily. if you have issues with it disconnecting check the solenoids you are working.

The USB_Relay program works OK with this board although rather simple. However, serial port apps such as HTerm cannot communicate, nor any home written version. Surprisingly, if you run the original program first then terminate, other programs work. But, the protocol is not like any instruction found. You would expect the code to look like "xFF x04 x01" to turn on relay 4. That does not work. The board uses a bit-bang method. To turn on relays 1, 5, and 8, you would send b10010001 or x91. Either method is fine but the board cannot be initialized by any published method. It appears that the original app does some initializing by direct USB. Until that happens, then board is useless for home brew code.Follow-up, 6-13-23From an electrical and functional point of view, the board is superb. The operational software is the present shortcoming. The board appears as a serial port in the device manager but does not respond to any commands. The board has to be in bit-bang mode to operate. There are several ways of dealing with this issue. First, use the software app from the SS support site. It's a stand-alone copy of the Denkovi app and works fine. Second, use their app to open the board then close the app. This leaves the board in the correct mode while still powered on the USB side. Thereafter, you can use a terminal app like HTerm or your own. Finally, I was able to create a more functional app in Lazarus/Pascal by using direct calls to the FTDI DLL library to put the board into the proper mode. Once it's in a usable mode, it's one of the best.I was in contact with SS tech support on many occasions. They did their best to help but the information is just not available. I gave them suggestions for serial communications that is used on other brand boards. This is a 3-byte set sent in binary. The set is 0xFF 0x0n 0x0s where "FF" awakens the board for possible baud value determination, "n" is the relay number(1-8), and "s" is the status condition(1-on/0=off). This is being considered for a future update. The bit-bang scheme will be left intact for backward compatibility. For all my efforts, SS sent me a free board. I'm now working on the idea of using two boards with multiple instances of my app.73 from KF4JU

I usually prevail over the worst circumstances, tried different USB cables, USB ports, inverting the FF 01 01 various ways, all FF xx 01 combinations.I bought two. they clicked during 'self-test'. good luck. Start with the SKU number underneath. Google it. My SKU was 101-70-116. At the very least, avoid that SKU. Apparently, there are about 300 model numbers- I assume 299 were buggy.

Fast shipping.

Great Board for Pinball Cabinet