The firmware is so buggy on these Keysight scopes that I avoid them for any troubleshooting work.Sexy LCD and fast CPU but I had to laugh when I kept getting a blank trace and putting a Tektronix to the same probe point gave me a trace, just as I expected.I especially love setting it to AC coupled and turning the trigger level negative -0.2V really makes sense

What scope are you using? Overall I'd expect that it's more of a use-model thing than a buggy firmware thing...

Is it not possible for an AC signal to drop below zero volts? You should be able to set the trigger at any level in the AC wave form - positive or negative - no? That seems to be how my scope works.

Yes, just need to bear in mind that the level would be relative to the avarage level of the signal, not absolute voltage to ground

Dave - I think you are wrong when you say the 1000X does not have an MSO capability - it is an MSO, with just one digital input. This input seems to be able to do everything a digital input can do on the 2,3,4,6-X series MSO's (provided that is supported by the installed decode options), it's just it's shared with the external trigger function.

Dave - I think you are wrong when you say the 1000X does not have an MSO capability - it is an MSO, with just one digital input. This input seems to be able to do everything a digital input can do on the 2,3,4,6-X series MSO's (provided that is supported by the installed decode options), it's just it's shared with the external trigger function.

It isn't really shared with the ext trig function - it is an independent digital input, just like an MSO. You can trigger on any source and still display, decode or measure the digital input

Dave - I think you are wrong when you say the 1000X does not have an MSO capability - it is an MSO, with just one digital input. This input seems to be able to do everything a digital input can do on the 2,3,4,6-X series MSO's (provided that is supported by the installed decode options), it's just it's shared with the external trigger function.

It isn't really shared with the ext trig function - it is an independent digital input, just like an MSO. You can trigger on any source and still display, decode or measure the digital input

An external trigger is more than just a digital MSO input. Usually the external trigger is sampled at a rate much lower than the digitizer rate so the trigger to sample time has to be interpolated to prevent jitter in the waveform display.

I searched through the available DSOX1000 documentation and did not find any specifications for when the external trigger input is used as a 1-bit digital input. Maybe they sample it at the vertical sample rate so no interpolation is required? Can it even be used outside of protocol decoding?

I was watching Dave's latest video, are these the configuration resistors:[picture of processor card]They look suspicious. May be try continuity to the ADC inputs on the SPEAR chip?

As mike said previously the separate PCB for the processor and ASICs is likely tested independently of the scope (configured to limit signals to 200MHz) and then once its put into the scope assumes its full identity. I'd be looking to the main board for resistor straps or flash memory to identify what its plugged into, unless someone wants to get their hands on the lower end models to compare against.

YES, for the umpteenth time. You can display it, trigger on it, measure from it and decode from it, in any permutation. You can set the threshold over 2 ranges +/-1.6v and +/-8V, and apply probe scaling factors. It works JUST LIKE AN MSO INPUT.The only limitation I've noticed is when you are displaying it, you can't select some acquisition modes like avaraging.

YES, for the umpteenth time. You can display it, trigger on it, measure from it and decode from it, in any permutation. You can set the threshold over 2 ranges +/-1.6v and +/-8V, and apply probe scaling factors. It works JUST LIKE AN MSO INPUT.The only limitation I've noticed is when you are displaying it, you can't select some acquisition modes like avaraging.

You sure cannot tell from the documentation which also leaves out a whole bunch of other questions I had.

YES, for the umpteenth time. You can display it, trigger on it, measure from it and decode from it, in any permutation. You can set the threshold over 2 ranges +/-1.6v and +/-8V, and apply probe scaling factors. It works JUST LIKE AN MSO INPUT.The only limitation I've noticed is when you are displaying it, you can't select some acquisition modes like avaraging.

You sure cannot tell from the documentation which also leaves out a whole bunch of other questions I had.

The documentation that also uses the word "cheap" to describe the product. I had a laugh at that, not exactly how you want to describe a product from a marketing perspective. It could use a revision to say the least.

YES, for the umpteenth time. You can display it, trigger on it, measure from it and decode from it, in any permutation. You can set the threshold over 2 ranges +/-1.6v and +/-8V, and apply probe scaling factors. It works JUST LIKE AN MSO INPUT.The only limitation I've noticed is when you are displaying it, you can't select some acquisition modes like avaraging.

You sure cannot tell from the documentation which also leaves out a whole bunch of other questions I had.

YES, for the umpteenth time. You can display it, trigger on it, measure from it and decode from it, in any permutation. You can set the threshold over 2 ranges +/-1.6v and +/-8V, and apply probe scaling factors. It works JUST LIKE AN MSO INPUT.The only limitation I've noticed is when you are displaying it, you can't select some acquisition modes like avaraging.

You sure cannot tell from the documentation which also leaves out a whole bunch of other questions I had.

Yep. This is one of the 'scopes biggest features IMHO but Keysight doesn't think it's important.

Considering the separate processor board:Maybe it has to do with layer count? e.g. they need 4 or 6 layers to route the zillion BGA pins, while the rest is pretty simple and only needs 2. I haven't noticed any layer markings in the video though.

Sorry if this was already mentioned, but I don't have the time right now to check the previous 6 pages.

Considering the separate processor board:Maybe it has to do with layer count? e.g. they need 4 or 6 layers to route the zillion BGA pins, while the rest is pretty simple and only needs 2. I haven't noticed any layer markings in the video though.

Sorry if this was already mentioned, but I don't have the time right now to check the previous 6 pages.

mike, there is an unpopulated QFP + others components near the area where a lan connector would be (according to the mechanical assembly)what could it be?could it be perhaps of an ethernet phy? even though there is no jack footprint on the board...

mike, there is an unpopulated QFP + others components near the area where a lan connector would be (according to the mechanical assembly)what could it be?could it be perhaps of an ethernet phy? even though there is no jack footprint on the board...

It is in line with the USB device port,and bypassed with 0R resistors on the underside. I think it may have been something like a hub as a workaround for silicon errata on the SPEAR - the boot text references a USB PHY workaround. It is definitely not an ethernet PHY. I haven't checked but I'd be surprised if the unpopulated connector on the sub-board didn't have all the PHY signals. The SPEAR needs an external PHY, so it's not just a case of lashing on a magjack. And it probably isn't supported by the software anyway.

I replaced the fan on my 1000X with a Noctua fan too a few weeks ago, the stock one was incredibly loud and annoying. A lot better now, I'm not sure yet if I should silence it further with one of the included low-noise adapters. It's mostly airflow noise now. The heatsinks on the board are getting quite hot, I might have to make some measurements.

Then I got a second 1000X yesterday. To my surprise, it is way quieter than the first one when I turned it on. No need to replace the fan. Now I get why people are saying the scope is silent enough, but it's odd there is such a difference between them. I don't have anything to measure the noise level, but I'd guess it's half as loud and an order of magnitude less annoying.

Maybe there is a quality problem with the fan? The second scope's serial number is lower than the first one, so I guess it's a bit older.