Fantastic tool, working to get this as a standard for our college labs instead of LabView with just a tad of bloatware.
The Owon SPM6103 is supported and in the "Owon SPMXXXX.txt" file, so created another metadef for the Owon SPM8205 we acquired since some of our battery packs require >60V for testing with the Owon OEL1515 series of programmable loads.
I created this added definition for the "Owon SPMXXXX.txt" file:
#metadef
#idString OWON,SPM8205,
#name Owon SPM8205
#handle SPM8205
#replaceText MaxVoltageSet 81
#replaceText MaxVoltageLimit 82
#replaceText MaxCurrentSet 20.1
#replaceText MaxCurrentLimit 20.2
but when I connect with TestController, the only response to #VALUES? is the DC voltmeter:
;; Found Owon SPM8205 on USB Serial (COM3) sn: 26170021
*IDN?
;; OWON,SPM8205,26170021,FV:V1.0.0
#VALUES?
;; SPM8205.VoltageDC=0 V
The popup for Setup does allow changing values on the front panel and turning the PS on and off and setting every parameter that I tried correctly.
The DC Multimeter app from Owon also works and track, plot, and save device-under-test voltage, current, and Ah capacity.
What am I missing to get the current, voltage, and Ah information for charting lab tests?
Multiple East Tester ET5410A+ programmable loads work fine in this setup of a charging function with battery discharge testing using TestController. It would be great to get the programmable power supply voltage and current data acquisition accessible from TestController as well.
[Later same day...]

To add to the confusion, the MEAS command does return data, but TC is not seeing it. Any suggestions on where to start with making changes to
"Owon SPMxxxx.txt" markup file? See the attached screenshot.
Thanks, Mark