I have the original LCD scope and have ordered the Quad beta.
Given the fantastic new speed of both the ADC and the CPU, it seems realistic to think about a spectrum analyzer as well as a scope. Codespace might require that only one or the other be loaded, but this could easily give you a 36 MHz spectrum analyzer using direct sampling and no other hardware.
I have been workin on a PC clent to work woth the Quad, but as Benf pointed out it is not going to be easy to squeeze all that information into the paultry 2 meg of disk space the quad has. I was thinking about perhaps a binary file. Not so easy on the eye but more compact.
Today I appear to have broken my Quad (engineering version HW v2.2) while installing the newer firmware. I think that the FPGA update got me because that update reports completed now that the Quad never completes boot-up (had to video the start-up screen and then frame step the video to find that very quick flash message “FPGA Update Successful”). With the previous versions you could always hold the right arrow key and power up to USB drive only, to revert back to previous software. After this problem, that USB drive only feature no longer works. So now that I am unable to access the USB drive, I am also unable to restore back to the previous version because I can’t change the files on the USB drive.
you means you can not access to the USB disk only feature after updated the FPGA ? would you pls sent me a email to descrip the detail with some pictures ? thanks …
Yeah I got mine finally it is working and looks like a great start. The usb disk for updating is a lose for me because it does not work with Linux or Mac os which are all I have easy to use. From what I can see it should not be hard to fix it, but this needs to be fixed. Is there an open source source pool for building this with gcc available? Two days of using this with the current UI and I am getting ready to change some things. There is much that needs to be done.
We too have a lot of trouble updating the F/W.
When we tried to copy the file, 1 by 1, to the USB disk, it sometimes would not reset. We had to delete that erroneous file and recopying it multiple time.
I recognized that the scaling of the between 1V and 0.5V resolution is somehow strange. See the pictures attached. The square wave was generated using the internal function generator. I have the latest firmware uploaded.
I don’t know if the error mentionned by Sergey82K has been fixed, but i have the same error on my DSO203. The frequency seems to be measured correctly but the measure (Hz or KHz or MHz) is not displayed correctly.
Hardware ver 2.60
Serial no 223D70DA
SYS ver 1.51
APP ver 2.52
Here are some screenshots :
10Hz -> 10.03Hz -> It seems to be correct.
100Hz -> 100.4Hz -> It seems to be correct.
1000Hz -> 1.007KC -> If KC means KHz, It seems to be correct.
10000Hz -> 10.03Hz -> It is wrong, it should be 10.03Khz or maybe 10.03KC.
100000Hz -> 104.7Hz -> It is wrong, it should be 104.7Khz or maybe 104.7KC.
500000Hz -> 546.7Hz -> It is wrong, it should be 546.7Khz or maybe 546.7KC.
1000000Hz -> 1.169KC -> It is wrong, it should be 1.169Mhz or maybe 1.169MC.