DS213 APP 1.28 BUG - channel A to D copying error

RamPhleg

I’ve just got DS213. Hardware version 2.1. Firmware 1.28. I tried to copy channel A to D as written in the documentation. It’s impossible. At first, call SaveWavXXX don’t save TRACKxxx.DAT, it save IMAGExxx.BMP. After that, if you were try to load (LoadWavXXX) then you would get the Error. It’s 100% repeatable bug. This bug isn’t exist in 1.27 version. In addition, if you delete IMAGExxx.BMP then DSO213 is going crazy (zero level start random jumpings, calibration doesn’t helpful), may be, the device loses control and timing is broken. At first, I thought I got a defective product, but restart and long waiting was helped (capacitors discharging?). This is basic function in the documentation, case 4). This bug should be eliminated.

minidso

Thanks for your feedback, we will test it and fix it if it is a bug.

minidso

1. I tried to copy channel A to D as written in the documentation. It’s impossible. At first, call SaveWavXXX don’t save TRACKxxx.DAT, it save IMAGExxx.BMP. After that, if you were try to load (LoadWavXXX) then you would get the Error.

We have reproduced this BUG and it has been fixed now. Please wait for the new firmware to be released.


2. if you delete IMAGExxx.BMP then DSO213 is going crazy (zero level start random jumpings, calibration doesn’t helpful), may be, the device loses control and timing is broken.
3. freeze (hang up) if  you would set 100ns sensitivity. Not only 1.28, any version.

2 and 3 We haven't been able to reproduce this, could you provide further information? Video or pictures, please email me: service@minidso.com

RamPhleg

2. I’m not sure 100% this action sequence. It was two times for me (I'm afraid to break the device). I deleted IMAGExxx.BMP, then I restart the device. After restart, signal is appeared not momentary, but this time the signal didn't appear at all. I recorded the video for seller (https://cloud.mail.ru/home/IMG_0659.mov?weblink=EABb%2FfJ3YsEKS6). It was all evening. I got upset and turned it off. The next day I turned it on and there was no problem. I tried to create a problem again. Somehow it happened. I turned off the device, and I waited one minute (at first time, I was not waiting, and I restarted many times, but problem wasn’t disappeared). After about one minute, I turn on the device, and zero level is ok. It’s capacitors!