that is strange , i have tested it before i sent it to you . and , i have told by the designer the Quad do not have the set of 1X or 10X. it recongnize the probe as 1X only .
maybe you need check your peobe again, ensure it is 1X.
Thanks, I just wanted to make sure that there is no probe setting such as in the Nano. Just do the math in your head for 10x probes, OK, but …
There is an obvious mistake in your probe calibration (probe compensation) procedures because you ignore C1A and C2A for 1x probe compensation, yet those caps are always in the circuit and need to be considered. This is especially true if the Quad does not know when a 10x probe is attached. This needs to be sorted out and the probe compensation procedures revised accordingly.
As I said, I used a direct BNC cable, no probe involved. I also tested the MCX to BNC adapter and found zero ohms on the center conductor, so no attenuation there.
I suspect that the calibration is way off because on another scale the display is 1/3rd the input signal.
Apparently you did not test for amplitude on the two scales that I am using, 50mv/Div and 0.5v/Div.
I will calibrate these input ranges and then repeat the tests.
ok, i suggest you upgrage the app,sys and FPGA firmware first and then go on your testing . thanks for your testing reports and i will put your finding to the designer to seek improving the system.
i am now repeat your testing,especilly your finding on applitude error . with app 2.35 sys 1.34 and fpga 2.5
i tested all the V/div of the Quad in my hand, and found it is ok. have you done the channelA and B calibration before your testing?
No, as I said previously, I was first trying out of the box testing with no changes as a base-line. I will calibrate the scales and then repeat the tests before changing software, and then repeating the tests again with the latest software.
I ordered up MCX to BNC adapters (Not from Seeed, got fed up with waiting for them to come up with the goods) with a 90 deg plug and it won’t push far enough into the quad to make contact
… Ho hum another design flaw with this product to add to the bugs and suggestions list. I also bought some Garmin extension cables with … you guessed it 90 deg plugs on them … they don’t push far enough into the unit either. So aside from wasting my money on a useless lump of plastic with a pretty screen on it I also now have a box full of cables that don’t fit it anyway
… Am I beginning to sound a little annoyed … that could be because I am. We have a considerable number of talented people in these forums demonstrating faults and more importantly how to rectify them but SILENCE as to how they propose to implement these findings from Seeed.
We also seem to have an ever growing list of bugs and suggestions … To the best of my knowledge this is nothing more than that, a list, and is serving , if anything, to put potential new clients off and to further add to the frustration of the existing customers watching a list that is growing and never seemingly being addressed.
Ohh and i am also getting fed up with waiting for my digital probes.
Cheers Pete.
Thanks, Pete. I contacted the eBay seller and got this reply,
very sorry about this, as a responsible seller, we will give you refund now
- just_for_survive
AND they actually refunded my money! I ordered Seeed’s adapter today and in just a few short WEEKS for shipping I’ll be able to let you know if it works.
SEEED! - WHERE ARE OUR DIGITAL PROBES???
Hey Seeed,
Loving my quad. It does just what I expected it to.
Just thought I’d say thank you.
- tgo
the digital probes are ready , have you ordered with you coupon?
Yes, I ordered my probes. For people that don’t have the time to trole every topic and happen to be looking at this one, don’t forget to change the quantity to two (2) probes, as that is what the coupon covers. The link for the probes as:
Mine too , now this IS a company that takes thier customers seriously and listens to what they are saying.
Not at the time the original post was made 
I understand your need to do damage limitation but honestly do you think that making a few cents worth of probes available is actually going to be enough to quell the torrent of disquiet that the quad it currently suffering.
It also helps to get your time lines correct when trying to make good.
Still waiting to see that ever growing list of suggestions and bugs start to shrink, excepting the availability of the probes.
Cheers Pete.
I am very satisfied with Seeed’s products and customer support. I understand the current QUAD is a BETA version and I knew that all along so I took the risk of buying. I have faith that Seeed and their partners are working to fix the problems. All it requires is a little patience from our side.
On a side note, the post office lost a package in December and Seeed replaced the entire order.
Well in that case I am not surprised you are “very satisfied” 
Hi,
I upgrade from FPGA ?, sys 1.33, app 2.32 toward fpga2.5, sys1.41, app2.43.
All is in the title : the setting are not saved so each time you restart the DS203 you have to reconfigure everything.
PS: I do not know how the setting are saved but with the old system i have already saved some settings. I do not know, if the upgrade delete old setting or try to import it. Nevertheless old or new setting are not saved.
Regards
Elmout
Hi,
After dowgrade to sys 1.37/app2.35, calibrate it and use it all afternoon compared with a true scope at $20000.
-
An autoscale will be welcome : actually when there is an overrange it display either something false like a line at the botton of the screen or nothing at all (mode : normal). At least a message should say over/under-range and when not in trig mode an autorange mode should be added: when the adc reach its high/low limits it switch to upper or lower range.
-
When you are in normal mode and change a setting such as time scale and let the cursor on time scale, it trig and store sample but at the last scale.
Regards
I find the button interface to be random and impossible to navigate. Buttons function differently depending on what is currently selected. Can I suggest a better way?
Buttons:
Left button push, left button left/right
Right button push, right button left/right
Screen
Organize into 5 main groups, each with a set of subgroups, each subgroup has a set of values of which only one can be selected. The *channel means that there is one such item per channel.
Channels (*channel)
—Coupling (none, AC, DC, GND)
—Voltage (50mV …)
—Position (scrolls up and down)
Timebase
—screen timebase
—acquire timebase (if implemented)
Trigger (*channel)
—Type
—Edge
—Threshold
Markers
—V1 (scroll)
—V2 (scroll)
—Delta V (*channel)
—T1 (scroll)
—T2 (scroll)
—Delta T (*channel)
Functions
—too long to list but things like Vpp, VDC, Vbat, and output waveform. Some are *channel some are singletons
The map right button push to cycle through the 5 main categories, right button left/right to select a sub category, left button push to cycle through channels for *channel sensitive fields, and left button left/right to cycle/scroll through values. One can also remember the current subgroup for each group so that scrolling would start from that subgroup.
The display of the fields can stay how it is now, but if the screen is reorganized a bit to correspond with the groupings that would be better (like putting delta V and delta T at the bottom near the markers’ icons).
I would like to modify this myself, but I’m afraid to brick my scope. Also I don’t have the tools and don’t want to pay for them.
I like the idea of improving the interface and would be open to testing this idea; however, having used the Quad in the field for actual troubleshooting, and, found the menuing combersom to use, I think the easiest fix would be to add more than one setup save. If I could have, maybe, a half dozen presets I would only be one or two clicks from exactly what I need, if that, for most of my applications.
I agree with that. Perhaps they could save to the virtual SD card multiple setups like BenF has done with the DSO Nano.
I thought app v2.45(b) was supposed to fix the problem with saving the scope configuration. I see no difference except it’s now displaying “reload parameter OK”, and still the saved configuration was not restored.