DAQman

Use  pulse_out_start and pulse_out_stop. There's an example called pulse_out.py in the Console examples.

 

The Universal Library is incompatible with the dot net core, so you are relegated to using dot net framework 4x for the time being.
 

You can use two DT9834 and synchronize them using the external D/A clock input, which could be driven by a counter channel's output. I believe you would need to change out the timing vi for a DtOLTimingSetOutput.vi because it provides the external clock option. 

You are going to be successful if you know what your sensors output. The USB231 measures voltage. Your sensors may output voltage or current. You mentioned at the beginning that you have a distance sensor that outputs 4-20 milliamps (mA). Because we measure voltage, not current, we use a resistor to convert the current to a voltage. Many customers use a 250 ohm resistor because that results in a voltage between 1 & 5 volts. The USB-231 must be in differential mode to measure the voltage drop across the resistor.
Your sensor measures 0 - 200mm; at 200mm, the measurement is 5 volts (20mA * 250). At zero distance, the measurement is 1 volt. The scale factor is 200 / (5 - 1) or 25. The offset is 0 = 1 * (200 / (5-1)) + b, where b is the offset. Rearrange the equation, and you get b  = -25. So the scale equation to get distance is f(x) = 25x - 25, where x is the measured voltage.
Here's a quick read on 4-20mA sensors https://digilent.com/reference/daq-and-datalogging/documents/current-sensors

It is up to you to modify the program to convert the voltage readings to something more meaningful, like temperature or distance. For example, a sensor rated at 100 with a 4-20mA (1 to 5 volt) output can be scaled by multiplying the voltage by 25 and subtracting 25, assuming you're using a 250 ohm shunt resistor.
 

Here's a slightly better version of the DtInitDACBuffers vi. It has an input for number of channels and number of samples.
DtInitDACBuffersNChan.vi

I made a custom CSV file containing four waveforms - sine, triangle, sawtooth, and square. The waveform amplitudes are less than +/- 10 volts.  Attached is a new version of DtInitDACBuffers modified to work with four channels. Could you run the attached example with my csv file and verify that you see the correct waveform on every channel? 
 
 
CSV_DAC_DT9834_LabVIEW.zip

I think it should work. What does the data look like in a Waveform Chart, and what is the Analog Output update frequency? Is the NumQueued Out terminal on the Write VI indicating the data is buffered? 
You could run the DtAoutWaveform.vi or the DtAinAoutContinuous.vi example as a test.
 

Please attach your program and data file. 

The USB-2408-2AO can indeed output 150mA on one pin but not simultaneously on two or more. The maximum rating for the whole port is 150mA. Please look at the specifications in the rear of the user manual. 
The digital output configuration is an open collector and acts like a switch. It cannot source or drive an external relay. An easy test is to connect a digital output to a digital input set to pull up.  Turning on the output acts like a short circuit and current flows from +5v through the 28k pull-up resistor to the ground. The result is the input reads a low condition. If you switch it to pull down, the other end of the 28k resistor is ground. Turning on the output acts like a short between two grounds and the input returns zero. 
Assuming you have a 12-volt relay, tie one end of its coil to a +12 power supply and the other to the digital output. Connect the 12-volt return to DGND.  When the digital output is turned on, the open collector transistor conducts, and current flows from +12 to ground, and the relay is activated.  Ensure that +12 volts divided by coil resistance divided by the number of relays will not exceed 150mA.
 
 

NC terminals should not be connected to the ground or anything else. NC terminals are reserved for future expansion and can be connected to the circuitry on some devices. Your device may differ from this, but we don't want customers using NC terminals as a rule. 

Yes, send them to me via message. Also include your name, email, phone, and shipping address.
Thanks

I'm sorry to hear you're having trouble, and it sounds like you've covered all the bases. I was going to recommend running sudo daqhats_read_eeproms, but you've done that. Under the Accessories, you should have a utility called MCC DAQ HAT Manager. Address zero is the default, so see if you can open the board with it.  I can replace it if it's less than a year old, but I'll need its serial number or a sales order number.

The USB-1608G inputs are high impedance and are designed to be connected to low-impedance signal sources. When the inputs are left floating or open, they can charge to any value, which is normal. To an analog input, nothing connected appears as a very high-impedance signal. If you're creating a LabVIEW app that may sometimes use a different number of channels, reading a floating input hurts nothing. If you know the channel will not be used, don't use or display its data.
 

Most of the Data Translation products have designated EOL. However, we do plan to continue to sell the DT9816-S. Otherwise, consider using a USB-1608G series device. 
If you need a DT321 replacement, I believe you can still get one. Reach out to sales@digilent.com.

The USB-1208FS-Plus digital IO is limited to about 100 Hz in LabVIEW because the output is a polled operation. It cannot use the internal clock to make it run faster.
The sync output (pin 19) is active when an analog input is scanned. It outputs the same rate frequency with a fixed  +5 volt 10uS wide pulse.

Hello @liamsul
The default input mode is differential. The 10 volt range has a resolution of 305uV per A/D count, and a 60mV would consist of about 197 counts, so you should have gotten something close to 60mV. The measurement would consist of 1967 counts when using the 1 volt range and that would produce a measurement that is closer to 60mV. If your reading is nowhere near 60mV, then check out page 11 in the user manual. It discusses what to do if your signal is isolated,for instance, battery powered.

To understand the other two wires, you must realize a four-wire measurement. Excitation current runs through the Excitation wires and will drop voltage if the cables are long. The other two wires (Sense wires) carry no current and measure the voltage at the sensor. So a four-wire measurement can accurately measure the voltage of the device when long cables are used. The USB-2404-UI cannot accommodate long wire runs. So, you can either leave them unconnected or shove them into the same terminals as the excitation wires. 
As for scaling to engineering units, you're on the right path. However, I prefer to use the Enter 2 points because it's easier. X1=0.000, X2=0.0019994, Y1=0, Y2=500000, and DASYLab will figure it out.

Review the following guide: https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi
When you get to the microprocessor section, choose MicroBlaze and boards with DDR

The USB-2404-UI returns millivolts per volt of excitation power - mV/V sensitivity. It uses the excitation power as a reference to the A/D. If the excitation power fluctuates, it will not change the accuracy of the measurement. Some devices use a fixed excitation power and return millivolts. If the excitation power fluctuates, the accuracy will suffer. So what they do is use another pair of wires as feedback to regulate the power. Long story short, when loaded to 500kg, your load cell should return 0.002 volts. You should have received a calibration sheet with the load cell with the calibrated sensitivity rating. For instance, instead of the nominal 2mV/V, is may be 2.1mV/V at 500kg. Make sense?  

Hello,
Most load cells, as well as strain gauges, output a small signal. For example, a 1000lbs load cell with a sensitivity of 2mV/V will output only 20mV at full load. The USB-231 has a fixed +/-10 volt range, and although it's a 16-bit device, it will struggle with mV measurements. The HX711 will not work because it uses a two-wire interface (Clock and Data) for communication. It would be best to have a signal conditioner with analog output, like the 8B38 from www.dataforth.com https://www.dataforth.com/8b38. It translates the mV signal to 0 -5 or +/- 5 volts which the USB-231 can read.
Best regards,
John

Set the bottom board to address zero (no jumper). Set the top board to address 1 (jumper on A0). Run sudo daqhats_read_eeproms, then test each board using the DAQ HAT Manager on the Accessories menu. If you add a third board at address 2, you must rerun sudo daqhats_read_eeproms.
Best regards,
John

Hello,
Use the Mathematics->Scaling module after the DT9837 input module. Use linear scaling as the type of module. On the setup page, use the default linear function. Leave b=0 and set a=1 / sensitivity. For example, if you have a 100 mV/g sensor, a=10. For units, type 'g' in the unit drop box. It's only a text label, so you could have bananas as the units if you wanted.
Best regards,
John

Hello,
The MCC 128 does not have per-channel input mode configurations. You either use all differential or all single-ended inputs. The same is true when setting the voltage range. The range setting applies to all the channels. 
Best regards,
John

Hello,
The USB-1208FS-Plus does not have PWM support.
The call-back event notifications are for the analog input and output. There's nothing for the digital IO. For more information about the event notifications, see the UL Help file. Specifically, search on USB-1208FS-Plus to get to your device page. https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm
Best regards,
John