JimR2

Eclypse works well also, thanks again. I also like the separate pulldowns for wavegen and filter channels, those could get quite tall when stacked up!

Attila, I finally got a chance to download and try the above beta version 3.20.27 (2023-08-18), and looks like the crashes are fixed when trying to alter 65536 sample waveforms on my ADP3450. I'll verify on my Eclypse Z7 also, but so far looks good! Thanks. JimR2

Thanks Attila JimR2

Thanks for the detail, I appreciate it. Regards, JimR2

This worked, thanks Attila, I guess the message showing the "buffer size is 65536 samples" despite setting to 32768, is just a warning tht you are not using the entire hardware buffer? I'm really surprised I never saw this before? Has this always been a limitation with Waveforms? Thanks, JimR2

Thanks, will try that tonight. Regards, JimR2

I have an Eclypse with a Zmod config as seen in the pic#1, ZMODA=AWG, and ZMODB = Digitizer What I've found is that when trying to create a custom wavegen waveform, say a 2-tone stimulus by using a sine Func, and then altering it with a 2 cycle sine Func, right after you hit Generate (for 2 cycle sine) and then OK, which should then combine the 2 sine waves, Waveforms crashes. So basically I get to the point shown in Pic#2, and after I hit OK, Waveforms shuts down unexpectedly. After crash, I sometimes have to power off/on the eclypse to get waveforms to connect to it again after a crash. I've done the exact same operation on my adp5250, and it works. I have not confirmed on any other device combination but can try if you need me to (have AD2, AD3 and ADP3450 I can try). I'm still using version 3.10.10 of Waveforms, from the last bug I submitted, please let me know if there is a new download that should fix this, or if you want me to do any other checking. Regards, JimR2

Thanks guys, sorry haven't checked forum in a while. Looks like my defective Eclypse is out for delivery in Washington, will await replacement! Found a Waveforms bug, using the Eclypse this morning, will put in separate thread. Regards, JimR2

I have a fairly new (purchased Feb or March of 2023) Eclypse Board that recently stopped powering up.I have two Eclypse boards and multiple ZMODs, and the board in question always exhibited an odd behavior, but otherwise functioned well. The fan would appear to rty to be starting, but wouldn't start spinning. If I gave it a gentle nudge, it would start. Now it simply won't even light the LED stack when powered up. Is there any diagnostic steps recommended? I plugged my other Eclypse into the same power supply, and it works fine. I also swapped to two Zmods that were in the non-functioning board to the spare, and they seem to also work. Also, jumper configurations are all same, and swapped sim card, and is functional in other board, though thouse shouldn't be keeping the indicator light from coming on. Also couldn't find a warrenty period on these listed anywhere, if you could provide that info, in case I need to return. Thanks, JimR2

There appears to be a bug when using markers in the spectrum analyzer. Attached is a snippet from a 158MHz tone sampled at 1GHz on my ADP5250. It appears the frequency is limited to 100MHz for marking, but the magnitude follows the signal strength, so it appear to be detecting the correct peak tone? Also attached below is the Waveforms version I'm using. Regards, JimR2

Atilla, Thanks for the information. I just downloaded the latest Beta you recommended, and that fixed the ADP3450 Dual DPS3340 issue I was seeing. Thanks! Regards, JimR2

Hi, I recently downloaded a new version of Waveforms (see pic1), and noticed a relatively new feature Select + Dual. A common use case for me is to select my ADP3450 + DPS3340 (see pic2), which has always worked fine before. Now it appears if I try and use the Scope, or scope with DiscoveryPS, I get an error (see pic3) that constantly repeats. Sometime so rapidly, I have to kill the Waveforms task. Also have noticed that when I do this, 8 channels show up on the scope, 4 osc channels, and 4 supply channels. Playing around a little, it appears as if I were to turn on the spectrum analyzer before the scope, this change how the channels appear in the scope, and everything works fine? See pic4, where I have DiscoveryPS, wavegen, spectrum analyzer open (since I ran before opening scope), and eventually scope in upper left corner which behaves as normal. So seems there is a workaround for now, but probably something that should be looked into. I also played around with the select + 2 to combine two identical devices (2 AD2's), very cool feature! Hoping it works with Digital Discovery also, was thinking about buying a 2nd one. Thanks, let me know if you have any questions or things you'd like me to try, Regards, JimR2

So I've repeated my measurements now that I have compression turned off, and am seeing what you see, but in LabView. I think having compression turned on, it was only outputting the state changes, and gave me the impression the clk0 was doing something. I also can configure the trig for dio15, and it behaves accordingly (waits if no trigger present), whereas now when I configure it as mso/clk0, it triggers all the time? Could have sworn I sanity checked that few days ago? Now I'm not so convinced in my finding. Bummer! Jim

Thanks Atilla, So if I understand your post correctly, you've seen no evidence of clk0/1 effective as a trigger in Wafeforms, correct? I'm a little unclear what you mean by "STATE MODE", can you clarify. I've been playing around a little more with LabView, been a few years since I dabbled with this software tool. I'm more of a Matlab guy, but also have become very fond of the scripting ability in your instruments. I've been poking into the Waveforms VI's to overcome limitations in the "RDWF MSO Read.vi". I realized in the sample size seems to be hadcoded to 16384, and Binary to Waveform conversion VI had compression turned on (see snippet), so the data I showed above may not have been ALL the samples that were occuring. It explains some things, but need to repeat with these limitations overcome, as well as trying to output a BCD value to make sure I know what I'm getting is truly due to the clk0 or clk1. Regards, JimR2

Hi Attila, I think I've been able to access the clk0/1 pins of the LA on the ADP5250! I was unable to obtain the VB VI's for the VB8012, so I've been playing with the Digilent provided VI's instead. I noticed when selecting "Description and Tip" on the "Trigger Source" for the "DWF MSO Configure Digital Edge Trigger.vi", that it showed this, With a little playing around, I built a simple LA VI using the Labview Waveforms VI's, and was able to verify that the clk0 on the LA port is accessible this way AND it can provide the behavior similar to the sync mode in Waveforms! To prove this out, I did the following (many pics to follow)...... I setup my ADP3450 to provide a test stimulus of a walking one's pattern (DIO14:0) to the ADP5250, and DIO15 I configured as a clock. See pic below. Then using a simple VI I cobbled together, was able to config the ADP5250, play around with how the VI controls vs what the ADP5250 is actually setting up for some of these (readbacks showed sample rate is always auto adjusted based on data activity, regardless of settings), as well as dump the captured waveform data to a text file viewing. To see if triggering on DIO15 vs clk0 was any different, The stimulus above I made sure the rising edge of the clock was centered in time with the center of the walking ones' bit. Then performed two captures, with the PGen/LA wiring as: trigger PGen DIO15 = LA DIO15 , LA clk0=gnd The captured data below shows a walking one's, but with each being a sequence of 2@ 1's. This appears to be due to the waveform structure or capture itself (maybe you can shed some light here) all events are captured with a time stamp, so the 2@ 1's for each step of the walk is the event when the walking 1 changes to a high state, and the 2nd is when the DIO15 trigger changes to a high state. Thus time stamping at 50us step for a 10KHz walking one, which only changes every 100us. Then I repeated the capture with the only changes being in the VI below for trigger on clk0, and re-wiring PGen/LA as: trigger PGen DIO15 = LA clk0 , LA DIO15=gnd This showed a different behavior as seen in the data below, where now only a single bit is captured for each walking one, coincident with the clk0 rising edge! So this seems to confirm the clk0 isn't really acting as a trigger (maybe my definition is too confining), but more as a what I would call a "sync clock"?? So these results seem very promising for me for use on my ADC test-bench to replicate the Waveforms "sync mode", and plan to experiment some more to better understand the flexibility Labview may give over Waveforms. Wanted to pass along in case this information is also useful for others, since finding documentation on the VB8012 was going nowhere for me. Kind of wish this was specified in the Hardware specs. Kind of glad I missed the mention of the clk0/1 not being supported by Waveforms, may not have purchased the 5250 to begin with? Now I'm hoping to be able to reliably capture higher data-rate up to 32 bits of data!! We'll see..... Regards, JimR2

That was my first instinct, I had followed the instructions on the link you provided with no luck. So far have not been able to get VB installed in the community version of LabView and working, since you can only download the latest version. Was hoping to figure out what it does before shelling out for a license for LabView. I was able to install VB and run outside of LabView, but did not recognize the 5250. On the 5250 webpage it says the VB is "unofficially supported", but so far only can assume I need to own a license of LabView, that will give me the ability to download an older version of LabView when VB was supported, then I can follow the procedure in the post. Have been getting Waveforms VI's up and running, but doubt that will support them. Thanks for replying.

I've recently added a ADP5250 to my equipment list, and am running into a strange inter-operability problem with the Matlab Digilent Toolbox. I've had by bench setup to use multiple running instances of Waveforms doing signal generation, test sequencing and data collection from ADC's on various FPGA platforms. The testing was coordinated from Matlab, which was never an issue before trying to integrate the 5250. It appears that when I do a "daqreset" and a "daqlist" in Matlab, I get the following (see pic1). One of the unknown devices is a Eclypse board with AWG and Digitizer ZMods, configured for Waveforms. The other unknown is the 5250. Pic #2 shows the relevant Matlab code, where I do a "daqreset" and "daqlist", and then extract the deviceID for the DDiscovery and ADP3450 which Matlab will use. The other devices in the list usually will be connected via a Waveforms instance and script running in Waveforms. The problem arises when I try to connect the 5250 to Waveforms. Then the Matlab script goes from working, to the following in Pic #3 error message? Worse, it gets stuck in a loop that you can't cntrl-C out of, and needs to be killed via the Task Manager! None of the other devices cause this interplay when connected to waveforms? Seems the 5250 behaves differently the the other devices (even the Eclypse) when queried by "daqlist" to catastrophic end? Any help understanding and working around this would be greatly appreciated. I had my bench fine tuned, and everything was working very well, but the 5250 seems to not behave and integrate like my other Digilent devices. Thanks, JimR2 Pic1 - DeviceList Pic#2 - Matlab Code Pic3 - Error Message in Matlab when 5250 connected to Wavevforms

Just found this comment in the spec's on the 5250 on the Clk0 and Clk1 lines (see attached pic). I missed that before. Any info or advice on how they could be accessible via Labview, Virtualbench or Programming would be much appreciated. I've looked around for a VB-8012 manual, but so far have turned up nothing but the specs doc. Thanks, JimR2

That is unfortunate, that's been a defining feature of your instruments for me. Is there plans to make them available in the future? What about the "Clk0" and "Clk1" signal on the logic port? Are these accessible somehow? I've installed Labview Community Edition, and have been able to access the 5250 via the Waveform VIs (scope and wavegen), but haven't progressed far enough to play with the logic analyzer. Also, is there an updated method to access the 5250 using the Virtualbench VIs? I have downloaded Virtualbench from NI (2019) but running standalone it doesn't see the 5250, and the procedure you defined in other posts to copy it from older versions of Labview I can't do, since I can't download an older version of Labview with community edition. Don't want to buy a license for Labviwe if that doesn't provide any additonal ability over Waveforms? Thanks, JimR2

Hi, Was going through the different ports of my new ADP5250, and was wondering about differences I've noticed between logic analyzer port use on my ADP3450, AD2 and Eclypse board in Waveforms? One of my favorite use cases is using the logic port to capture ADC data using a synchronization clock input, instead of using a canned sample rate of the device. For this, the "sync" mode has worked very reliably to capture, export and postprocess data in Matlab. I noticed on my new 5250, however, that the "Mode" pulldown in Waveforms is not active, and appears to always be in "Repeated" mode? So is it correct to assume the other modes available on all other Digilent devices (Shift, Screen, Record and Sync) is not available? If so, is there any way to duplicate the logic sample per sync clock edge behavior (perhaps using the trigger which I had yet to explore). Also, I noticed that the 5250 logic port has a "Clk0" and "Clk1" signal, which is absent on all the other devices, but I can find no documentation on how this is used, nor can I find anywhere in the Waveforms logic setup to make use of it??? Very perplexed, so hopefully there is some insight that can be provided? I bought this device specifically for the 1Gs/s logic capture, but if confined to the pull-down selectable sample rates and not allowed a event driven capture, will be disappointed? Thanks, and look forward to any info that can be shared on this topic. Regards, JimR2

Hi Attila, I did the loopback you mention to the ADP5250, actually was the first thing I did. I used three different BNC shielded cables, just to be sure. The signal was noisy in all cases. The AD2 connection also used a BNC cable. I should have mentioned I used the BNC adapter with the AD2, so there was a ground I did not try a scope probe, it was always a BNC cable direct connection. Couple thoughts, 1) I got thinking maybe the AWG output is high impedance, and needs a common mode established by the load? 2) There is a ground terminal on the back of the unit, should I be grounding that to the same ground as the AC supply to avoid ground loops? Didn't seem like this would be necessary for a local loopback check which I did. Thanks for the reply, and look forward to working through this. Hope I'm doing something wrong, seems like a nice unit, although I'm also wondering about the packaging. The unit is not in a ESD bag when it comes in the box, and it has two Styrofoam supports which slip on over each end. I noticed one of the ends completely covers the AWG and Trigger ports comes in direct contact, seems like an ESD vunerability? Regards, Jim Riches

Hi, I just received my ADP5250, and was doing simple initial measurements on all the inputs/outputs, and am seeing significant noise (~500mV) on the AWG output. See below, is a 2V sine from the ADP5250 AWG, measured on a AD2. Regardless of cable or measurement device, the noise is consistent. Also included is the wavegen screen of the ADP5250. Any suggestions? I've got 2 AD2's, and a ADP3450, and have had no issues with the wavegen on those, this seems to maybe be a bad AWG? There's not much on the forum I could find on the 5250, so trying figure out whether I should send this back? Also should add that this noise is seen, even with the AWG not running. In fact, I can turn off the ADP5250 while monitoring with the AD2, then turn back on the ADP5250, and watch the AWG output slowly float from ~0 to 500mV, at which point the noise disappears. Then when I turn on the AWG, the waveform looks reasonable (see third plot) but has a 500mV offset? Then, over time the noise re-appears, and the waveform moves back to that seen in pic#1 Regards, JimR2 4

Thanks Atilla, I will try the newer beta versions soon. Got side tracked installing Vivado and the Digilent board files, and playing with the IP provided for the Eclypse. Went pretty smooth, thanks for your help Out of curiosity, I tried to download and install the WF 3.19.22 beta in a separate location from where I have the latest release, but appears the installer doesn't allow that unless you un-install. I assume this is on purpose Regards, Jim

FYI. The WF3.19.19 Beta, I ran into issues with it all of a sudden, it got com errors with every device. I would try and turn on a scope on my ADP3450, fand run, and it would sit there and do what I call "motorboating". When you hit run on the scope, it would quickly flash up a com error, then you'd hear relays click, and then would repeat the com error, and sit there and oscillate forever (I assume). I've downgraded back to WF3.19.5, and at least I'm able to communicate again? Not sure what set it off? I had connected in the new AD2 I got with my Eclypse Z7 purchase, and had renamed it to a different name, so I could distinguish it (especially in the MATLAB DAQ toolbox). Thought I'd pass that along. I know you said there was newer Beta versions, so will try them later. Regards, Jim

Atilla Good news, I got a new SDHC card, and this one booted fine. I just configure both 1410-105 ZMOD cards, and drove them with my ADP3450 wavegen. Seems to work well! Still curious whether the FPGA fan should be running my default when plugged in, was unclear from one of your earlier posts? Going to dig into my Eclypse Z7 more this weekend, but at least I've seen it function now! Also am curious if I need to be running the WF3.19.19 Beta, or if the latest released download will also work with the Z7? Thanks for your help, Jim