Speaking of bugs, the programming software is full of them.
First, the manual gives specific directions about what cable should be used for serial communications and how to use a terminal program to send commands. As I mentioned earlier, it also comes with a virtual panel and scripting software to control it via PC. It can execute a script and log the results. What came with it installed without any hassle and at first glance,, appeared to be working correctly with the exception of a screen resolution issue when running on an old XP machine. (the work around for that on my machine is to set the resolution to 800x600, apply, then restore the resolution. That resizes the window properly thereafter)
Well, things sort of work. The pretty graphical interface works, except it does not change the memory storage location on the PSU, it simply lets you have a second set of independent memory buttons, resident in the computer. Voltage changes are truncated at the decimal point. For example, 7.77v sets the PSU to 7.00v. Also, despite the real-time graphs of voltage and current for each channel, it seems to be logging only one of the channels. I suspect #1 but haven't verified that.
So I decided to try the terminal route. I still haven't figured out the serial port connection but either it's dead or maybe requires a null modem cable (manual shows straight pass-through). I did finally successfully communicate through the USB cable to the virtual Serial-USB adapter installed in the PSU itself.
The manual suggests MTTTY is suitable. It is not. Neither is Terminal, Hyperterminal and a host of others that do not send data until "enter" is pushed. The only way I could communicate manually is with RealTerm. Fortunately its open source, available at Source Forge. After selecting the correct port, and opening it, I could send commands via RealTerm's Send tab.
The keyboard locks automagically when the USB cable is connected. The keyboard lock can be overidden manually at the keypad, but not in software that I could see.
Most of the commands will work despite the keyboard lock. Except the memory recall and memory store commands. That explains why the memory buttons are independently duplicated in software.
What is needed here is some decent software to replace the crap that came in the box. The capabilities are there in the machine, but accessing them is not.