MagChad

Please try this with a 10v sine wave. The rolloff on the channel starts around 5 volts and up.

@DAQman Thank you for the reply. The 12V clamps are a standard protection, so that makes sense. I am disappointed that this effects the other channels, as each channel has its own ADC circuit. Also, there is no indication that my data coming from a NON-OVER-RANGED is corrupt. This data just rolls off and reverses direction, like it is a real signal, instead of clipping to zero or full-scale. I would like to hear what the design engineers have to say about this issue. Thank you.

USB-1604HS-2AO - When channel 3 over ranges, the data from channel 0 is invalid when negative (but OK when positive). Channel 3 is connected to a thermocouple amp that when unplugged, rails 13.1v into channel 3 to detect an open thermocouple. Channel 0 is my primary analog input for our system. When channel 3 is over ranged, channel 0 can only go from -4.5v to +10v. When my test ramps up the signal on channel 0 in the negative direction, the DAQ data is rolling off (attenuating, not just clipping) at around -4.5v. My test keeps ramping the channel 0 input, but the data from the DAQ module channel 0 rolls off and stops. USB DATA IS NOT MATCHING THE INPUT SIGNAL WHEN ANOTHER CHANNEL IS OVER RANGE. Per the documents below, the MAX voltage on the analog inputs is +/-20V. It does not say anything about cross talking or distortion of ranges on all channels when one channel is in over range. I can provide video of this, but it should be straight forward to replicate: put 13v on channel 3 and ramp channel 0 from 0 to -10v. Is there any documentation besides these 2 PDFs that would go into detail on this issue? It stumped me for several days, before I started pulling BNC cables off the module and found what was causing my USB data to NOT MATCH the analog input signal. This could be a serious issue if not detailed in documentation and dealt with in design. Since they are separate circuits, they should not be interfering with each other. (DS-USB-1602_4HS.pdf) & (USB-1604HS-2AO.pdf)

I am having a similar issue with this module. I find that if I leave the USB cable plugged into it, and then power it up, it never wakes up, no blue light. I have to power it up first, then unplug and plug in the USB cable. I am using this in an embedded design. The system power will get turned off when not in use. So now our customers are required to turn the system on, then unplug and replug the USB cable into their computer before launching the software. This does not seem right.

On the USB-1604HS-2AO page, it says there are OEM options available. I am using USB-1604HS-2AO strapped to my circuit board inside a chassis with the BNC connections external. Is there an OEM package of this that omits the case and would let me mount the board directly to my PCB on standoffs? I had did this with the last DAQ (DT9832-04-2- OEM shown below), which is obsolete and forced me to redo my design. Thanks.

Thank you, DAQman. That will work for my purposes. The end connectors are different, but I can deal with that. If the actual STP file becomes available, I would love to be notified. Thank you.

Does anyone have a 3D step or stp file for MCC USB-1604HS-2AO, or one of its options? Thank you.

Hello. I was asked to post this to the forum, since it was too technical for the service team. We have used the DT9832A-04-2-OEM DAQ module in one of our products for many years. This 4 channel DAQ was discontinued a couple years ago, and replaced with it’s 2 channel version, which is not recommended for new designs. We are looking at the USB-1604HS-2AO DAQ to redesign our product around. It has all the features of the original DT9832A-04-2-OEM that has worked very well for us. I wanted to verify one aspect of the USB-1604HS-2AO that the DT9832A-04-2-OEM had. This is critical for our product. I could not find this specifically in the documentation, although it says that both subsystems can use the same pacer clock, but not anything about their startup timing. We require the ADC and the DAC subsystems to simultaneously start, on the same clock pulse. If the USB-1604HS-2AO uses the same “OpenLayers” libraries and it is verified that the simultaneous start works the same as the DT9832A-04-2-OEM, we can move forward with this redesign. A code snippet of ours is below: //Setup simultaneous start list CHECKERROR (olDaGetSSList(&simstartlist)); CHECKERROR (olDaPutDassToSSList(simstartlist, FhAD)); CHECKERROR (olDaPutDassToSSList(simstartlist, FhDA)); //Prestart queue_doneDAC = false; CHECKERROR (olDaSimultaneousPrestart(simstartlist)); //and wait end_time = DT_OVERHEAD + GetTickCount(); while((!queue_doneDAC) && (GetTickCount() < end_time)) { Application->ProcessMessages(); } CheckCallbackMessages(); AddDebugMessage("Playwf Prestart done"); //Start queue_doneADC = false; io_doneDAC = false; CHECKERROR (olDaSimultaneousStart(simstartlist)); · DT9832A-02-2-OEM: Simultaneous USB DAQ Module; 16-bit, 2.0MHz per channel, 2 AI, 32 DIO, 2 C/T, 3 Q/D, No Enclosure. Not recommended for new applications. Please consider the USB-1604HS-2AO instead. Thank you