I've had the same issue with Win10, but sometimes the unit will just stop working between tests. Not often but enough so you really remember it. Unplugging the USB is a PITA in my case as I have to go around the basement to reach the rear of the bench to do it. Everything is in a rack. I think it is a windows problem because cycling the power on the RTX doesn't solve it. I am running v1.19 and have been since it came out. Same issues.
Powering down the RTX won't shut down the USB interface and the XMOS since it gets power from the host. My guess is that the XMOS sends something when powered off that tells the PC that its disconnected however it never does the initial handshake when powered back up because the USB VBUSS never went away. You could make a USB cable where VBUSS comes from the RTX. It may provide VBUSS internally as well so simply cutting the Vbuss wire would fix the problem. Looking at the enumerated devices on the PC when its "locked up" under devices may give some clues.
Windows 10 has had some recent updates to USB drivers that also indirectly impact UAC2 driver. I noticed these when the Windows UAC2 started behaving differently to the async feedback coming from my USBI2S board. The worrying thing is that Microsoft UAC2 experts were apparently not even aware of these updates and their impact to UAC2.
Can you share what changed specifically? Thanks a lot.
I wonder if MS actually has any UAC2 experts, since their UAC2 driver was developed by Thesycon https://docs.microsoft.com/en-us/wi...udio/usb-2-0-audio-drivers#driver-development .
I don't know what exactly was the update to the USB drivers but after that UAC2 responded to async feedback more aggressively which caused buffer over/underruns on my board as I was using quite small buffers. Slight change to the feedback scheme and increase to buffer sizes mitigated the issue. Update involved several usbxxxx.sys files in \windows\system32\drivers but usbaudio2 drivers were not updated. My hunch is that the UAC2 driver uses some lower level USB functionality for e.g. async feedback handling as that is not only for UAC2.
IIUC the Windows UAC2 driver was developed by Thesycon but is now maintained by Microsoft. But as said Microsoft's UAC2 experts were not even aware that there had been updates to USB.
IIUC the Windows UAC2 driver was developed by Thesycon but is now maintained by Microsoft. But as said Microsoft's UAC2 experts were not even aware that there had been updates to USB.
Last edited:
Op amps have current limiting and the signal levels are not that high considering power. You will get distortion long before damage. So it comes down to the load impedance that is reflected into the generator really.
Most amplifiers have a gain between 29 to 35 dB. It might be just as easy to use a consumer amplifier for this job. I do have +10 and +20 dB RF amplifier modules (connectorized) for RF work.
Most amplifiers have a gain between 29 to 35 dB. It might be just as easy to use a consumer amplifier for this job. I do have +10 and +20 dB RF amplifier modules (connectorized) for RF work.
I don't think you will damage the RTX6001, but you won't achieve your goal either. The two channels are connected, and share a common ground, so you would basically just short the two outputs with opposite phase. Since the output impedance of he two outputs are equal, it would be like shorting the connection point to ground.
The single ended output impedance is 50 ohm by the way. Balanced output impedance is 100 ohm.