attila

Technical Forum Moderator
  • Content Count

    1913
  • Joined

  • Last visited

  • Days Won

    115

Everything posted by attila

  1. Hi @Nithin Yes. See the AnalogIO_DigitalDiscovery.py how to adjust the IO voltage, enable VIO output, set pull-up/downs, slew rate, drives The DigitalIO functions can be used the same way controlling DIO[24:31] The DigitalOut functions are the same but you have 32k custom bit/line for DIO[24:31] The DigitalIn by default samples DIN[0:23]&DIO[24:31]. To sample DIO lines first DIO[24:39]&DIN[0:15] set FDwfDigitalInInputOrderSet(hdwf, true). This way if you sample 16 bits you will get DIO[24:39]. The base frequency is 800MHz (FDwfDigitalInInternalClockInfo), like use FDwfDigitalInDividerSet(hdwf, 8 ) for 100MHz
  2. Hi @Rick314 I see now what causes the confusion... The reference is only valid when it is enabled, when dB is selected, and it is irrelevant for the other units. For the next release I have modified it to give valid reference values even when it is disabled: Thank you for the observation.
  3. Hi @omur // start capture and wait to be finished Logic1.single() Logic1.wait() // on AD by default the Logic Analyzer and Wavegen have the same 4064 buffer var datam = Logic1.Channels.Bus.data var data_norm = [] datam.forEach(function(v){data_norm.push(v/4095)}) plot1.Y1.data = data_norm Wavegen1.Channel1.Mode.text = "Custom" Wavegen1.Custom.set("mycustom", data_norm) Wavegen1.Channel1.Custom.Type.text = "mycustom" Wavegen1.run()
  4. Hi @Rick314 The dBV "standard" is relative to 1Vrms, 1.41Vpeak, 2.83Vpk2pk. The dB is expressed in the application relative to Vpeak to be in accordance with Wavegen (peak) amplitude adjustment.
  5. Hi @tauquir_iqbal Such measurements are on the edge or above of the device capabilities. We are trying to compare 10 Ohms with mOhms, the AWG current is on the limits, voltage drop is close to scope resolution... The contact resistance can also ruin the measurements... it would need special clips mentioned by @fonak Here I tried to compare various setups, but after short compensation the results are pretty close to each other, given the conditions... Traces: - IA: using IA adapter - IAComp: compensated - Kelvin: the following single ended setup, with twisted (1+/- 2+/- W1/GND) wires hooked to a breadboard, trying to do 4 terminal sensing - KComp: same with compensation - Diff: differential measurement on breadboard, 4 terminal - DiffComp: same with compensation
  6. Hi @joe3 The AD2 has no power led. The green led lights up, blinks after software connection. To see if the device is ok, try using a Windows or Linux machine. Please see the following post, try running the digi_enum.py
  7. Hi @Satz Sorry but I can't say anything for sure. - It could be problem with the USB socket, GND/VCC is fine, but there is slight chance data lines to be damaged - The USB controller might be damaged, but I don't remember any similar problem with the EExplorer board - The firmware could be partially erased and the USB controller stops working You can try to cut the trace between JP1200 and see if any device is detected. At the moment I don't have any better option.
  8. Hi @alexw Here you can find WF v3.10.6: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
  9. Hi @tauquir_iqbal Perform short compensation before the measurements and enable it. This will eliminate/reduce the wiring, AD2 scope contacts, IA adapter relay, socket... resistance. The open compensation is useful for low capacitance measurements, to eliminate the wiring capacitance. Such measurements are very sensitive, it would ideally require kelvin connection... Electrical contacts can have several mOhms resistance which is comparable or even higher than the inductor resistance and can ruin the measurement. Here I tried to measure a low ESR 1uH coil. The Short trance is the short compensation, NoComp is the inductor measurement without compensation and Comp the short compensated measurement.
  10. Hi @alexw You are right, the digital channels are not accessible from scope math. It will be supported in the next software release. Thank you for your feedback. Such user requests improve the application. Let us know if you have any other observation.
  11. Hi @Satz The USB controller of the board is powered from the 12V supply. Make sure this is supplied, the red led should be lit. The yellow led should light up to indicates the USB GND/5V. Please inspect the USB socket on the board if the soldering is in place and the internal contact plate is not broken. On the EExplorer revF and earlier the USB EEPROM could get erased by 12V supply spikes. In this case the device is normally detected as USB VID_04B4&PID_8613 (see in Windows Device Manager) and can be reprogrammed. It might also get erased in a way that it fails to boot and the system should report after about a minute unrecognized device. To solve this, power up having the EEPROM disconnected: 1. cut the trace between JP1200 pads, located on the bottom close to the USB plug 2. solder a jumper, verify with a DMM there is no continuity on these pads/pins 3. power up the board with 12V supply and connect it to the PC, now it should be detected as unknown device VID_04B4&PID_8613 4. short the jumper with a header, this will attach the EEPROM 5. use the reprogramming application to rewrite the firmware
  12. Hi @tauquir_iqbal Could you post some screenshots with your measurement results? A window can be dragged from the tab bar (A) or the entire group of tabbed windows can be dragged from title bar (B), and dropped to other place. Make sure to have suffice space in the parent window to be able to perform such operation.
  13. Hi @Satz I don't think the software update is guilty, since the USB device detection is done by the operating system, so the device should be detected regardless of the installed software. Try restarting the computer, disconnect the 12V supply from the board and reconnect after a few seconds to reset it properly, try reconnecting or changing the USB cable, use another socket or hub... Let us know if it is working or if you need further assistance.
  14. Hi @tauquir_iqbal The component characteristics depend on current and voltage, or the measurement is inaccurate. This is what i see with an 1uH: Notice the warnings: at low frequency, the DUT voltage is low, and around 1MHz the reference resistor voltage/current (C2 in time view) is very low. In these cases the measurement might be inaccurate.
  15. Hi @kojak WF beta v3.10.5 adds Measurements for Logic Analyzer. Next version will add possibility to open such digital measurements from Scope interface too. https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
  16. Hi @Rick314 The precision of AM/FM sine signal index is corrected for EExplorer in WF beta v3.10.5: https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
  17. Hi @Jaye It refers to "Microsoft Visual C++ Redistributable Package", required to run applications built with Microsoft Visual Studio. The installer of this is included in the WaveForms setup package.
  18. Hi @vwegert The requirements highly depend on the data processing you want to perform. You can test the application in demo mode: https://reference.digilentinc.com/waveforms3 For simple tasks a 10 year old PC or single board computer is fine but if you want to work with millions of samples it might require several GBs of RAM. You have many instruments, view, options in the applications...
  19. Hi @Jaye Windows XP or newer versions are supported. Windows 2000 is not supported. I have removed you previous duplicate post.
  20. Hi @venkatap Here the AnalogIn_Sample2.py writes the record.csv
  21. Hi @sib Here you have a new wrapper based on the latest beta WF SDK: dwf.vb https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ I added this time some string wrapping functions.
  22. Hi @sib Here you have VB wrapp er, converted from the old C# wrapper: dwf.vb I have not tested all the functions only the following: Imports System.Text Module Module1 Sub Main() Dim hdwf As Integer dwf.FDwfDeviceOpen(-1, hdwf) Console.WriteLine(CStr(hdwf)) Dim str As StringBuilder = New StringBuilder(512) dwf.FDwfGetLastErrorMsg(str) Console.WriteLine(str.ToString()) dwf.FDwfAnalogInConfigure(hdwf, 1, 1) Dim sts As Byte dwf.FDwfAnalogInStatus(hdwf, 1, sts) Console.WriteLine(CStr(sts)) Dim rg(8192) As Double dwf.FDwfAnalogInStatusData(hdwf, 0, rg, 8192) Console.WriteLine(CStr(rg(0))) Console.WriteLine(CStr(rg(1))) Console.WriteLine(CStr(rg(8191))) End Sub End Module
  23. Hi @Rick314 Thank you for your rigorous approach. That helped us to finally find the problem: The "Sine" Modulator signal is obtained in the FPGA with a Cordic algorithm. There is a scaling error which reduces the modulator amplitude to 95% of the desired value. This affects the Modulation Index. We will fix the error in the next WafeForms release. Until then, here is the workaround we suggest: build the modulator as a "Custom" signal: - click the gear next to the FM signal type, then "New" - In the WaveGen – Custom window, select “Sine”, then click “Generate”, and “OK”. Select the desired modulation parameters and Run the AWG. Please see the attached workspace, for the EE board. FMIssueEE.dwf3work This issue is only present with the Electronics Explorer board. If you use an Analog Discovery or Analog Discovery 2, you do not face the issue, so you do not need the workaround.