nanderson

The driver version reported by Device Manager for the AD3 is 2.12.36.4, and the properties of ftd2xx.dll match the screenshot you sent, save for the last modified date being in august 2021. I did notice that the ValueCAN dongle opens a COM port when it's plugged in (I noticed while ensuring that the AD3 wasn't opening a COM port, which it isn't). I've attempted to uninstall the driver but only succeeded in getting Windows confused about it to the point where I had to reinstall Waveforms to fix it. I copied the .dll around like you said and it seems to be working as of the time of writing this, I'm going to try to avoid using the ValueCAN at the same time as the AD3 for now to avoid breaking it, but I'll reply here if it does break again.

I installed the FDTI driver from the setup exe file, no luck either. I'm also not able to connect to the AD3 even after a full reboot today after it first crashed out this morning. The device works with no issues on other computers. When I hit the "Find devices" button in the Waveforms device fix menu with the AD3 plugged in, Waveforms crashes.

I tried powering the AD3 with the external supply input, no dice. I'm running directly from my laptop, which has never given me problems before. I also tried a different cable. It looks like the needing to wiggle the connector was just an issue with the USB-C cable that came with it, other cables are working fine. I'm able to connect to the AD3 after a full shutdown+reboot (usually) and there seems to be some order of operations I can use to launch it with the ValueCAN successfully, but I haven't nailed down exactly what that is. I've attached a screenshot of the exact error I get when I plug in the ValueCAN with Waveforms running: The "Device communication failed" error is somewhat common for me when plugging in other devices, but usually it reconnects fine. The "JTAG init failed" seems to be what's killing it, if I try to reconnect to the AD3 manually in Waveforms that's the error I keep getting. To clarify, I can get that error to pop up when Waveforms drops the AD3, if I restart Waveforms it simply doesn't connect and gives me no errors. Would you agree with that assessment given the above?

I'm on Waveforms v30.20.20 and am having trouble getting my AD3 to connect to Waveforms. It appears as "Digilent Analog Discovery 3" under USB controllers in Device Manager, but Waveforms isn't detecting a device. If I go through the "My device is not listed" tool, Waveforms crashes when I hit the Find Devices button. I'm working with other USB controlled sensors (specifically a ValueCAN 3 dongle) that have made Waveforms spit an error when I connect them, but didn't get one immediately before Waveforms stopped wanting to connect. I've also noticed that I need to slightly angle the USB-C cable down towards the bottom of the device when plugging it in or else the green LED doesn't light and the device doesn't connect at all, if that's relevant. Currently the LED is lighting and windows is recognizing it, however.

Thank you for that! I also have noticed that setting certain values of AM period produces discontinuities in the carrier waveform. For example, at 10khz sine carrier, nearly any period with more than 1 decimal place of precision produces a discontinuity at the start of the period, but that same period value may not produce a discontinuity at other carrier frequencies.

Oop yeah, didn't know that was the requirement for triggering on periods, that's working fine still. I'm still unable to get the wavegen AM to behave like I expect, though. With offset at -100% I expect to see the waveform fully flipped for half the period, but instead I see that behavior with offset around -6, and anywhere past -10 or so I get no AM at all. I have workspace files saved from previous versions of the software that had configuration like the 2nd image but output like the 1st.

Actually, it looks like something is very messed up with the Offset option. Setting it around 6% gives me a result close to what I would expect at 100%. The preview in the Wavegen tool is very different than the feedback in the Scope tool. Feeding the wavegen output back to the scope confirms that the feedback in the Scope tool is accurate. I also seem to remember that the Wavegen trigger source would trigger on modulation periods, not just edge events. Could we get that back as an option? It was very useful.

I was on v3.18.1 previously but updated to 3.20.1 when I got an AD3. Previously, I could set AM settings to 100% Amplitude/index and 100% offset to get a sinusoid to invert fully over the AM period, but now when Amplitude is 100% setting any significant offset makes the waveform freeze for part of the AM period, and when offset is +-100% there is no AM at all. In addition, when the two channels are set to synchronized, the "Wavegen C1/C2" trigger option in the scope doesn't trigger.

Replacing the chip was definitely easier said than done, but it seems to be working again. Thanks for the help, and props for having the device be user serviceable!

Then I have no idea what could have caused the damage. The only other thing of note that was going on when the damage occurred was Waveforms freaking out when I tried hooking up a Digital Discovery at the same time as the AD2. Since it looks like I'm out of luck for warranty service, do you offer any repair service? I could replace the IC on my own, but would rather not for what's supposed to be a measurement device I trust to have been calibrated by someone with proper equipment.

Could a static shock have done it? The scope was hooked up to something that was only generating at max 5v output, but I may have accidentally shocked it while standing out of my chair. I'd hope that there would be some sort of protection against that, but that's the only thing I can think of having caused it.

Hi all, At some point yesterday, I believe while attempting to get a DD working at the same time as an AD2, my AD2 started seeing a ~25.7v offset on channel 1, with the leads completely floating or even shorted together. I tried re-running calibration but wasn't getting good results. Is there anything that can be done about this, or do I need to reach out to digilent?