Jump to content

JRys

MCC Staff
  • Posts

    1,452
  • Joined

  • Last visited

Posts posted by JRys

  1. If you are programming in Python, the function is c_in_scan, and one of the terms is scan rate. Let's say you program it to read a totalizing (counting) counter input with a 1000 hz square wave as the input signal. If the scan rate is set to 100, the data returned will be 10, 20, 30, 40, etc. 

    If, instead, you were to use a polling function like c_in_32 and call this function within a loop, then you might get values like 9, 21, 30, 99, 41, etc. because the loop timing is not precise. 

  2. You can use the following installation program and install InstaCal version 6.74. 

    https://files.digilent.com/downloads/InstaCal/icalsetup.exe

    Next, enable .Net framework version 3.5, as shown below. After doing this, run the DASYLab Configurator utility, and in Packages->Data Acquisition, enable the Measurement Computing driver. Note that the Measurement Computing driver installer will look for a folder named ...\DASYLab\. Press the Change button and change the path to ..\DASYLab 2022.1_en\. If all goes well, DASYLab will be ready to use a measurement computing device.

     

    image.png

  3. The 96 MHz clock drives the FPGA and is only remotely related to the sample rate. When you request a sample rate, a sub-clock is used to achieve the rate. If you were to request a sample rate of 100, the FPGA still runs at 96 Mhz, but data is recorded 100 times a second. When using the Totalize mode (counting), the count increases on each edge of the applied signal, whether you read it or not. Clear on Read does just that; after each read, the register is reset to the minimum value, typically zero. 

     

  4. The DBK604 and DBK605 are connector panels for the DBK60 box, which can hold up to three DBK cards. Open the box to view the cards and their jumper addresses. The box with thermocouple connectors most likely has three DBK82. The other box could have any number of cards, so you need to look for their identities besides the address jumper.  Some boards have jumpers and switches to set the address, so you will need the user manuals. The best way to find the user manual is with a Google search or browse https://files.digilent.com/#manuals/

     

     

  5. The PMD-1208LS is not a NI-DAQ device. To use it with LabVIEW, install ULx for NI LabVIEW and use our VI's for control. Once installed, look for our VI pallet on User Libraries. LabVIEW 2024 support is not yet available. Before starting, review the help document that is accessible via LabVIEW's Help menu item.  The examples are installed in ..\National Instruments\LabVIEW 2023\Examples\ULx\. I suggest starting with the example ULx Cont Acq&Chart Samples-SW Timed, which is in Measure Slow Varying Signal.llb in ..\ULx\Analog In\.

  6. We are aware of no reported problems regarding Visual Studio 2017. There's likely a programming mistake; for example, there is no test to determine if TestBoard is valid, and the error status needs to be checked when executing the AIn function call. I am attaching a USB-201 test program that returns data from the first four channels for display. 

     

    Program.cs

  7. If possible, could you plug it into another computer and make sure the power switch is set to 'on.' If nothing lights up, then the board is probably broken. It's hard to say what happened; it could be that a static shock took it out or that it simply failed. In this case, you can use the forum's private message and send me the serial number, purchase information such as an invoice or order number, and your shipping address. 

  8. I suspect you forgot to constrain the pins used by the PmodAD1_01.  Go to Sources, select Constraints, and add a constraints file. Open the file and copy the constraints below. Please pay close attention to the ja_pin#_io numbers, as they are not in order. 

    ## Pmod Header JA
    set_property -dict { PACKAGE_PIN Y18   IOSTANDARD LVCMOS33 } [get_ports { ja_pin1_io }]; #IO_L17P_T2_34 Sch=ja_p[1]
    set_property -dict { PACKAGE_PIN Y19   IOSTANDARD LVCMOS33 } [get_ports { ja_pin2_io }]; #IO_L17N_T2_34 Sch=ja_n[1]
    set_property -dict { PACKAGE_PIN Y16   IOSTANDARD LVCMOS33 } [get_ports { ja_pin3_io }]; #IO_L7P_T1_34 Sch=ja_p[2]
    set_property -dict { PACKAGE_PIN Y17   IOSTANDARD LVCMOS33 } [get_ports { ja_pin4_io }]; #IO_L7N_T1_34 Sch=ja_n[2]
    set_property -dict { PACKAGE_PIN U18   IOSTANDARD LVCMOS33 } [get_ports { ja_pin7_io }]; #IO_L12P_T1_MRCC_34 Sch=ja_p[3]
    set_property -dict { PACKAGE_PIN U19   IOSTANDARD LVCMOS33 } [get_ports { ja_pin8_io }]; #IO_L12N_T1_MRCC_34 Sch=ja_n[3]
    set_property -dict { PACKAGE_PIN W18   IOSTANDARD LVCMOS33 } [get_ports { ja_pin9_io }]; #IO_L22P_T3_34 Sch=ja_p[4]
    set_property -dict { PACKAGE_PIN W19   IOSTANDARD LVCMOS33 } [get_ports { ja_pin10_io }]; #IO_L22N_T3_34 Sch=ja_n[4]

  9. I have a Rev D Arty Z7. After reading your post, I walked through the Zynq Server guide using Vivado 2023.1 and did not experience the same trouble. Older Arty Z7 boards use an older Rev Realtek PHY chip and should work as is with Vivado, whereas new boards require a patch to the LWIP Library. To patch your system, use the attached file and overwrite: C:\Xilinx\Vitis\2023.1\data\embeddedsw\ThirdParty\sw_services\lwip213_v1_0\src\contrib\ports\xilinx\netif\xemacpsif_physpeed.c, assuming you have 2023.1. 

    Could you walk through the Zynq Server guide using one of your new boards to see if you can get the echo server working with the update to the LWIP Library? 

    xemacpsif_physpeed.c

×
×
  • Create New...