They could have a lower input capacitance, but this could not explain the huge difference. Even the Keysight probe with only 11pF input capacitance and assuming the PP215 actually had 20pF (which I really doubt, 16pF is much more likely) could not turn 22ns into 10ns.Little side note:
PP215 10:1 input capacitance is listed on the probe brochure and in Siglent websites as 13 or 14 pF......not 16pF
Well, then that's Siglent's fault.
But you are right: The little card that comes in the probe bag lists the input capacitance as 14pF
Believe the LCR meter used to measure what the probes actually are.
We need remember these probes are supplied by a third party and Siglent staff have made error when copying specs onto their webpage. The card in the probe pouch should always be the final and absolute reference in all cases as it comes from the probe manufacturer. I highly value the card and have them for any and all new probes I have ever bought !
QuoteBut you are right: The little card that comes in the probe bag lists the input capacitance as 14pFI've got some for PP215 that list it as 13 pF, who to believe ?
Believe the LCR meter used to measure what the probes actually are.At what frequency ?
Pp215 probe card received today?
Input capacitance 1x85pf-120pf / 10x 18.5pf-22.5 ?
It’s what my card tells me?
Pp215 probe card received today?
Input capacitance 1x85pf-120pf / 10x 18.5pf-22.5 ?
It’s what my card tells me?
That would be the specification for PP510 - according to the Probe Datasheet V1.5, which in turn doesn't always comply with the probe cards.
Because otherwise we have 1k source resistance for the rising edge. You could easily prove that by looking at the falling edge – if this is much faster, than it is actually an open drain output.
The card is for a pp215, and came with the sds1202x-e , today, that is what’s printed on the card for my pp215?
Performa01 & tautech I don't know what kind of PP215 you have/use but this is what comes with 1204X-E:
Performa01 & tautech I don't know what kind of PP215 you have/use but this is what comes with 1204X-E:
Interesting assumption but the screenshots I attached for every probe clearly show that rise and fall times are the same.
See attachments for the PP215 (sorry for the poor image quality).
I guess we can only wait and see what tautech finds out. Maybe Siglent could test a sample of their currently shipped PP215 probes and verify their performance.
Is it missing row 11 as well on picture #2?
I would like to report on the recently found problems/bugs:
2) I also noticed that sometimes the last saved screenshot is not saved on the USB drive. it might be a result of some caching and I am not sure how to handle properly safe removal of USB drive since looks like 1204X-E does not provide any options for that.
3) And finally: looks like Siglent does not provide a way to inspect data payload longer than 0x15 bytes. The max number of bytes displayed in the single row of the table is 0x10 and there is no horizontal scrolling. The max number of decoded bytes shown at the bottom of the screen about ox16 without a possibility to properly scroll it. Before someone suggests to use horizontal position/scale knob he has to try it first since it does not work. That, seemingly minor thing, upsets me the most since it might be a design flaw and therefore cannot be easily fixed without major changes.
I would appreciate if one of Siglent distributors reported these bugs to Siglent.
Nice demo tautech, thanks.
Are visual differences between each curve possible in color too, or in trace light intensity only?
Curious how much more cable mess are added to desktop measurement procedure by deciding
to external (USB connected) SAG1021 instead to build in one?
Personally prefer build-in one or standalone AWG. One more reason to invest in SDG1062X (or SDG1032X) before SAG1021.
Hi,
I've updated my SDS1104X-E with the new firmware but now I notice something strange on channel 4.
I can't see any signal with 50V/div, 5V/div, 1V/div, 200 mv/div (probe set to x10, with x1 the values are 5V, 500mV, 100mV, 20mV). To be more precise I can see the signal only for an instant after changing the V/div scale and then it disappears.
I never noticed this with the previous fimware so I think that is a firmware problem.
can someone check this? or can I try something to figure out what is going on?
Thanks
I found a bug related to displaying long IC2 decoded packets, I am running the latest X.20 firmware.
Look at the first column in the table, we cannot see the row 9:
.............
Now that the factory is back at work after Chinese new year hols and after checking they were aware of issues with v7.6.1.20, they've replied that they're trying to get a replacement firmware version out this later week.