JRys

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.

Could you try our example? Open the Generate Values LLB library in \National Instruments\LabVIEW 2022\Examples\ULx\Digital\. The example's front panel has eight buttons, so select the eight lines of FirstPortA.

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]

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

Our Data Acquisition Handbook is a great place to start. https://files.digilent.com/reference/data-acquisition-handbook.pdf

Please review page 18 in the user manual for case dimensions and the attached files for the ACC-205. The ACC-205 kit includes a set of 4-20 x 5/16" screws used to mount the bracket to the existing holes on the bottom of the E-1608 case. ACC_205_DIN_clip_50mm.pdf MCC_ACC-205-assm_50mm-l_din_clip_4-hole_asm.stp

Information about how to repair a USB-TC is not readily available, but I might be able to have them repaired. Please send me a private message with both device serial numbers and your phone/email/shipping address. The repair process takes 4-5 weeks. If it can be repaired, my customer service department will contact you.

You can add (+) another AXI GPIO to your block diagram, similar to how it was done for the button in https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi. Name the (make) external connection pio instead of btn. Constrain the desired IO pins as pio_tri_io[0]...pio_tri_io[7]. Name the block AXI_GPIO_PIO and finish the build by running block automation. Follow the guide to create the HDL header, generate the bit stream, and export the design wrapper. In your SDK app, add the following, like it was done for the buttons and LEDs. #define PIO_ID XPAR_AXI_GPIO_PIO_DEVICE_ID #define PIO_CHANNEL 1 #define PIO_MASK 0b11111111 cfg_ptr = XGpio_LookupConfig(PIO_ID); XGpio_CfgInitialize(&pio_device, cfg_ptr, cfg_ptr->BaseAddress); XGpio_SetDataDirection(&pio_device, PIO_CHANNEL, 0); //output //update the first eight GPIOs. XGpio_DiscreteWrite(&pio_device, PIO_CHANNEL, pio_data);

The USB-1608GX-OEM board was discontinued and is no longer available. The recommended replacement is the USB-1608GX-2AO-OEM.

The BASYS 3 FPGA board has a 100 MHz system clock, so updating the PMOD interface at 25 MHz should be possible.

The USB-231 does not have PWM support, so no. Instead, please consider a USB-1608G or a USB-1808X. These two devices have a timer output that can be used for PWM.

The counter input uses a 50 MHz clock (20nS per tick) and counts repeatedly from the leading edge of your sensor's signal to the next lead edge. At 112,000 RPM (784k Hz), the ideal count is 63.75, 784,000 Hz. However, in the real world, the count may be only 60 or 833,333.3 Hz. There will be more errors in the upper frequencies because the counter input has less time to count. With that said, could you review the attached VI? It will demonstrate a better (more straightforward) way to measure frequency. You can ignore the counter output (TMR0) I used for a test signal. ULx Meas Dig Freq-Buffered-Cont-test.vi

No charge, use the following public activation key: ALYGP-Q889C-TY5X6-MZFWM-75LLG

The PersonalDaq 54, 55, and 56 were discontinued, and no newer version exists. The recommended replacement is the USB-2408-2AO. However, it uses the DAQami software and does not have frequency inputs.

Both LabVIEW and Python are programming environments that can automate a process. If you are unfamiliar with either one, consider the DASYLab BASIC ($1,299.00) software, which has a shorter learning curve.

With seven pulses per sensor revolution, 13,000 pulses per second is approximately 1800 RPM. On the other hand, RPMs up to 112,000 would be 784,000 pulses per second. Could you confirm the sensor's RPM range and the number of pulses per revolution?

If your budget is tight, consider the free Community version of National Instruments LabVIEW. Our LabVIEW support for the Counter Input has a timed mode. It can measure frequency in timed mode by counting pulses over a desired period. For instance, if the period is one second and it determines that 100 pulses have occurred, then the frequency is 100 Hz. Another approach is to create your own Python script to do what you want.

Using 12-volt power, you do not have to do anything with the Scaler resistor. It will override our resistor because it has a much lower value.

Use mcc172_a_in_scan_start first to start the acquisition, then use mcc172_a_in_scan_status to determine the number of samples in the buffer. Study the attached C program. It requests 256 samples and displays the loop execution time, samples read, channel 0, channel 1, and the number of samples left in the buffer after the read. continuous_scan2.c

The USB-2416-4AO counter input has a pull-up resistor, so an external one is unnecessary. Connect the Scaler's +Output to the counter input and the -Output to the ground.

Use the following download for LabVIEW 8.5 support. https://files.digilent.com/archive/MCCDAQ_CD/Archive_6.35/mccdaq.exe

I checked with my manufacturing department about your device. It was discontinued in 2016 and never put into production at Measurement Computing, so I'm sorry to say it is not eligible for repair.

Please review the following forum thread regarding Raspberry PI 5 support.

The PersonalDaq 54, 55, and 56 do not support Windows 10 or 11. However, some of our customers have found ways to make them work. One tip I have found is to ensure the computer's hardware has the latest updates from the manufacturer. This is especially true for new computers, which often ship with outdated firmware. I have also found that some manufacturers do not make drivers available for Windows 10 or 11 that run on older hardware. I have a Dell Precision 5820 desktop with Windows 11 that works with the PersonalDaqs, so it can work.

I apologize for the late response. GND and AGND are connected on the PCB board. However, the AGND path is meant for analog grounds only. Digital grounds tend to have switching noise, and running separate paths reduces overall measurement noise. On the other hand, a ground loop can appear as a noisy signal. If you suspect a ground loop, use a differential connection instead of a single-ended one.