Part Number: PGA309
I have a DAQ board connected to a multi-cal master board with PGA0309 boards on the interface board.All cables seem correctI have them set for 4 wire voltage mode, and I select the 4 wire voltage mode model in the software.my supplies are on, the +9V to the DC jack, the USB is plugged in, the15/-15V and 5V that supplies the DUT the corresponding LED's light up,I set up 4 temperature points. After scanning, the LED corresponding to Vdut is always bright, and it can complete the calibration of the initial temperature. However, after a certain temperature calibration, all calibration paths (8 ways) fail. At this time, the Vdut corresponding LED will go out. I measured the voltage between Vdut and GND and found that it was already no longer in 5V and turned into a 0V. By looking at USB DAQ Platform USER 'S Guide, I know that Vdut has been disconnected. This happens so often that the calibration of the sensor can not be completed. However, as long as I shorten the time between the temperature points, the frequency of this situation can decrease. By looking at USB DAQ Platform USER 'S Guide, I know that the software setting disconnects the Vdut. I want to know why Vdut is interrupted in the calibration process so that it can't be calibrated. I would like to know how to avoid Vdut being disconnected from the calibration process.
Precision Amplifier Applications - TI Tucson
In reply to Alexander Davis:
The version I'm using now is V2.3i, and the previous version is V1.6b. These two versions all have this problem. This situation appears at second, third, fourth temperature points and has nothing to do with the temperature point. I think this is likely to be the case with too long calibration time, usually from fourth to fifth hours. When a failure occurs, Dut Power and Vdut dischange (TP29) will become high levels, and Pull up (TP25) and Disconnect one (Tp27) will become low levels. Before starting calibration today, I force Dut Power and Vdut dischange (TP29) onto GND, and Pull up (TP25) and Disconnect one (TP27) are forced to VCC. Two calibration cycles have been completed today, and there is no mistake for the time being.I think it's a problem with the software. 1. would you please help to confirm that my practice is feasible? 2. can you help to provide code or update software? 3. can you help to provide the specification of the V2.3i version, and about the TEST/DEbug and other functions of the software，I do not yet know how to use them. The attached map is the software interface after the error. Thanks very much
In reply to user4164924:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.