Help with Mini-Circuits Attenuator RUDAT-6000-30 (USB connection issue) - Page 1
Forum section: electronics / testgear

author: TimYTTT
author_rank: Contributor
timestamp: September 06, 2025, 07:53:50 pm
content: Dear all,I was not able to get my Mini-Circuits attenuator RUDAT-6000-30 working with the official software over a direct USB connection. The device only works when connected via an RS232-to-USB converter cable.I contacted the seller but received no response. I also reached out to Mini-Circuits support, but they informed me that this is an early hardware version that cannot be upgraded with new firmware, so they cannot provide assistance.Has anyone dealt with a similar situation or found a workaround to control such older attenuators via USB, or should I simply continue using the RS232/USB method? Any advice, drivers, or documentation would be greatly appreciated.Best regards, TimYTTT

author: Elio
author_rank: Newbie
timestamp: September 07, 2025, 03:37:02 pm
content: Hi,I have an RCDAT at work, with RJ45 communication and USB required for power supply.I gonna check tomorrow.Simple question, have you checked that usb device is well installed on devices manager?From "GUI Setup Package" (link available on minicircuits Datasheet) the software look compatible from W98, XP until Windows 10. (I checked VISETUP.inf file)

author: TimYTTT
author_rank: Contributor
timestamp: September 08, 2025, 03:47:13 pm
content: Hi Elio and others,Thanks for your help. Yes, I checked the USB settings in Device Manager and did not find anything specific for the RUDAT-6000-30. When I start the Mini-Circuits app, it seems that the connection is functioning — I can click on the "Firmware" button and get a "Firmware Info" pop-up (Model: RUDAT_6000_30, S/N: 11401140007, Firmware: A3_ID30). However, when I try to set the attenuation level, I get the error message: "Error in USB Device, Check Cable." Once I press the "OK" button, the app crashes.I tested this behavior with different USB cables and PCs, but the result is always the same.As I mentioned previously, the attenuator works when I connect it over an RS232/USB converter, using the native USB connector only to supply power to the attenuator.Regards,Tim

author: Elio
author_rank: Newbie
timestamp: September 08, 2025, 07:01:23 pm
content: Hi,So I did a test on my RCDAT-6000-30 (quite similar to your but with RJ45 instead of RS-232) and I tried to use only USB and it works fine.I tested it on Windows 10 LTSC, using GUI Setup Package (https://www.minicircuits.com/softwaredownload/patt.html) I installed the software RUDAT_Setup.And it works fine setting and reading attenuation values using only USB.I guess both version RUDAT and RCDAT share the same microcontroller but I didn't checked the firmware though.You can check on device manager there is a "Mini-Circuits" device that should appear. (I'm not sure but I had to sort differently on "View" options)Here is a screenshot on device manager, you can see two sub-devices "USB Input Device" and "HID .. device" inside Mini-Circuits device. Make sure both are available and well installed.Can you also check on register if your device is available :HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBAnd find device Vendor ID of Minicircuits which is 0x20CE, meaning the device should starts with "VID_20CE" and Product ID mine is PID_0023.

author: TimYTTT
author_rank: Contributor
timestamp: September 10, 2025, 02:12:55 pm
content: Hi Elio,Thank you for the update and the detailed feedback. I de-installed RUDAT-6000-30 GUI, downloaded new one from the link you provided to me, but no change.In Device Manager there is no USB entry for Mini-Circuits as shown in your document (pls. see attachment to this email). I was also not able to identify the Mini-Circuits registry entry as you suggested.Since my RUDAT-6000-30 is not showing up under USB devices in Device Manager, it seems the driver is not loading correctly or the hardware is not being detected over USB. Given the age of my unit (S/N: 11401140007, Firmware: A3_ID30), it is possible that the firmware or hardware USB interface has developed an issue. I do not understand what changed and why the product is behieving like this. Anyhow, I can use RS232 connection as the backup.Kind regards, Tim

author: Elio
author_rank: Newbie
timestamp: September 10, 2025, 04:25:59 pm
content: Hi Tim,Well, even if the device is not recognized it should at least appears and be logged in registry.I see many cases that should explain why it is not communicate.- Did you test without any connection cable on RS-232, I'm not sure but micro-controller may detect that Sub-DB9 cable is connected and so try to only communicate on RS-232.- You can also check that your device is at least detected from USB Hub. All devices even a simple one that only use power supply from USB should be logged and indicate how much it draws current. Go to USB-Controller and then select "Generic USB-Hub" and then check into "Power" tab. (see attachment showing my mouse is drawing (or negotiate on max current I guess) 100 mA and many others devices on the same USB Hub)- If your device is not shown maybe it's simply because your USB communication pins doesn't works, are damaged/rusted pins (pin 2 & 3) maybe?. This can happens after many uses and disconnections if you can check with a binocular and if you notice rust/stain on pins maybe you can try to clean it with alcohol medical or isopropyl, maybe try with another mini-USB cable?- There are a lot a tools to check if your device interact with your system, like "Process Monitor" from Sysinternals tools suite (free specialized tools available on Microsoft site but a bit complicated to handle) or tools from NirSoft like USBDeview, USBLogView that should help you to know if your device communicate or not.As you said good think RS-232 is still working, and it's not system dependent contrary to USB.