Cool! The android UI look so sweet, just think of the quality feeling it would give the nano or quad if the native UI looked like that, it would bring the DSO market to the next generation for sure
This is my first post here. I am eagerly awaiting my quad beta - ETA March.
On the subject of using an external display, I have to say this has some merit. But it’s probably smarter still to walk before running.
What we need is an “Interface Design spec” for two files.
Output file - where parameters which have been sampled go; and
Input file - parameters to control the Quad go.
Initially the files can both be accessed externally using the USB. The external host just needs to be able to access the USB file system, so it could be any garden variety Linux, Mac, or MS based PC. Latter on you could add on bluetooth access to the file system if you want, though this may be a bit more tricky.
both files could be a really simple format CSV, eg:
time, a-value, b-value, c-value, d-value
time-scale, a-scale ,b-scale, c-scale, d-scale, sample-rate, etc
These files are very simple because at least in principle the host is doing all the hard work to display the data, and the quad just needs to write the nearly raw output from the A/Ds. Obviously the file formats will need to be adjusted when doing signal generation.
The output is continually written to by the quad during normal operation and read continually by the host. Input is normally written by the host when the user selects a new scale or whatever. The quad could poll the input file or more efficiently - just read it when the saved date/time changes.
As file accesses is handled on the host by the host OS, the quad application (running on the host) is really just a gui for displaying the data and controlling how it is displayed. Potentially it could be written as a Java application which can run on anything.
The only issue is that this approach has already been done. Just google “digital oscilloscope computer”, but not at a price that competes with the quad. It least if the quad approach is kept open source.
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.
Any news about the development, latest FW etc. ?
A week ago, we had some news on the blog: http://www.seeedstudio.com/blog/2011/03/08/dso-quad-shipping-delay-notification/
But no update till now… and it’s a long time for people waiting.
Back Panel Arrived… Assembly still on going. Sorry for the delay!
Hey, just keep us in the loop, and we will be happy. I also want a good product, so take your time, and get it right
ok ! keep us informed ! how many orders do you have ? is it more that 300 ?
Assembly arrived, test and packing under process!
Super ! How long will it take to start shiping ? 1 week ?
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.
You can track and DL my clent here
as you can see i am planning on at some time using it with 4 inputs and have already coded the waveform viewer and I2C and UART decoders.
All i need now is my Quad to arrive and someone to code up the export
You may want to preview the following video to more quickly use the Quad upon it’s arrival.
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.
After upgrade (SYS1.34 AND APP2.32) I cannot calibrate due to “parameters version error”.
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 am using DS203 and SYS ver 1.51, APP ver 2.52.
Signal 8 MHz:
FRQ: show it as 8 kHz (needed “MHz”)
CIR: 0.0124 us (really 1/8MHz = 0.124 us)
500 kHz showed as 500 Hz (from internal signal generator):
FRQ: show it as 500 Hz (needed “kHz”)
CIR: 2 us (it is correct)
Signals from 0 to 999 Hz it showed correctly, as Hz
Signals from 1 to 999 kHz it showed as Hz
Signals under 1 MHz it showed as kHz
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.
If you have a fix for this, please let me know.