What would be nice also that you can select a peak in search and highlight it so it shows which one of the markers is this. Maybe that when selected you can send a cursor to that point so you can set them that way.Actually you can do this using the forward & backward search buttons, but only when acquisition is stopped. The highlighted peak is shown by an x-axis cursor. It would be nice if the corresponding marker also changed to the highlight orange colour, instead of remaining white. It would be even nicer if you could touch one of the peak table entries and select it that way as well.
Actually you can do this using the forward & backward search buttons, but only when acquisition is stopped. The highlighted peak is shown by an x-axis cursor.Thanks for that. I tried.
It would be nice if the corresponding marker also changed to the highlight orange colour, instead of remaining white. It would be even nicer if you could touch one of the peak table entries and select it that way as well.
For relative measurements (3rd harmonic distortion as dBc) I used the cursors in tracking mode, instead of peak search. Set X1 to the carrier frequency with the on-screen keypad, set X2 to the 3rd harmonic, and read out the distortion level in dBc from the deltaY. This worked for me since I'm using a known carrier frequency. It is easier than peak search, as when you set a 'reference peak' it doesn't change the amplitude readout to use it as the 0dB level, so you have to subtract the levels manually.
My niggle is over the screen and its lack of visibility when you place it above head height on the bench, in my case it’s on a shelf above a monitor. I have to tilt it down quite a way to make it visible. Thing is, otherwise it’s very usable like this as you can use an under-desk wireless mouse to control it.
The next thing is that the VGA output is letterboxed in in such a way that when displaying it on an external monitor or using a VGA to HDMi adapter, getting it to fill the screen without distorting the image seems impossible: perhaps others have had better luck?
The screen grab posted by @2N3055 shows up another thing I have noticed - when channel 3 is selected, the graticule annotation (X & Y axis scales) are shown in dark blue, and in a lighter weight font that is very hard to read. The other channels & functions aren't too bad but the dark blue is almost illegible. There doesn't seem to be a way of varying the annotation intensity, at least that I could find.I agree. Graticule annotations are not very visible, they are quite dim.
I find it really annoying that the serial number is placed on every screen capture.
Why?
It would be nice to have an option to turn this ON and OFF of have a custom message show instead.
I find it really annoying that the serial number is placed on every screen capture.
Why?
It would be nice to have an option to turn this ON and OFF of have a custom message show instead.
convert scope_0.png -fill white -draw "rectangle 354,12 458,30" output.pngI find it really annoying that the serial number is placed on every screen capture.
Why?
It would be nice to have an option to turn this ON and OFF of have a custom message show instead.
I've used this ImageMagick one-liner in the past, for B&W screen captures which were intended to be printed:Code: [Select]convert scope_0.png -fill white -draw "rectangle 354,12 458,30" output.png
Nice tip, @HighVoltage. I'm also always having to crop off the model/serial things. I've passed this thread along to the scopes planners as well - we love feedback!
I'm starting to believe that the classification of a "bug" is inversely proportional to the $$$ that ones pays for the equipment.
I already posted this in the hacking thread, perhaps it's better here.
Basically, has anyone managed to get the recently released (FW 7.40) USB trigger & decode working in HS on the 3104T?
FS & LS work fine. Possible operator error?
Details here:
https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg3609701/#msg3609701 (https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg3609701/#msg3609701)
We could reproduce the issue and found out that the 4000A x-series scope is working fine, but the 3000T x-series scope, which you use, is not and we also got the red lines. Therefore we logged a defect report to our R&D and they will fix it in the next releases. To set the priority to our R&D correctly, could you please let me know if you have any deadline in your projects that prevents you from doing your work or are you able to work with the TEK scopes while we are fixing the issue?
Thank you very much for bringing this to our attention. We are always looking forward to customers feedback to improve our software and hardware.
You would think that customer that has to use Tek scopes while they fix their bugs would be priority enough, but hey, whatever... :-DD
Thank you for your response.
I’m OK for now thanks, I can get by, but I much prefer using the snappy UI of a Keysight. I was looking forward to ditching the Teks 😉
Many thanks, Howard
In my experience the R&D team is pretty good & quick about getting bugs like this fixed, especially if it already works on the 4000 X-Series (which I believe share a code base). You can always ask for a beta release with the patch, we've been known to do that from time to time (no promises, of course).
In my experience the R&D team is pretty good & quick about getting bugs like this fixed, especially if it already works on the 4000 X-Series (which I believe share a code base). You can always ask for a beta release with the patch, we've been known to do that from time to time (no promises, of course).
@2n3055 I'm honestly not sure. It would have to be a 1-off type thing worked out through your local sales/distributor folks. I know there have been a lot of changes in licensing over the last few years and haven't been connected enough to the details to know how they have decided to handle it. I highly recommend giving the line a call or an email and see what they say for your specific case.
Unfortunately I don't have good news to share.
R&D looked into the issue with the 3000T x-series scope and USB 2.0 HS and found out that 3000T x-series scopes can’t support USB High Speed due to HW limitations. SW support for USB HS was accidentally added in the 7.35 GUI along with the intended and working USB LS and FS support.
In summary, USB LS and FS all work in the following. As far as USB HS…
• The 3000T Series FPGA cannot handle USB HS.
• The 4000X Series has a secondary FPGA that handles USB HS in 1GHz+ models
• The 6000X Series can handle USB HS it in its main FPGA.
R&D is investigating the changes to remove USB HS support from the 3000T Series GUI (targeted for the 7.50 release) while Marketing is reviewing the changes needed to customer facing documents.
My apologies for the mistake which we did in our documentation and software. This will be corrected soon.
Do you also have a 4000X or 6000X series scope from us?
Let me know if I can assist you any further in getting a 4000X or 6000X scope from one of our partners in the UK or with any other question. I hope we didn't loose your trust and you are still interested in ditching the TEKs ;)
@2n3055 I'm honestly not sure. It would have to be a 1-off type thing worked out through your local sales/distributor folks. I know there have been a lot of changes in licensing over the last few years and haven't been connected enough to the details to know how they have decided to handle it. I highly recommend giving the line a call or an email and see what they say for your specific case.
Daniel,
thanks a lot for your answer. As I said, it used to be simple and now is both more versatile and confusing. Soon it will be time to extend my maintenance and I will ask then..
All the best,
Sinisa
@2n3055 I'm honestly not sure. It would have to be a 1-off type thing worked out through your local sales/distributor folks. I know there have been a lot of changes in licensing over the last few years and haven't been connected enough to the details to know how they have decided to handle it. I highly recommend giving the line a call or an email and see what they say for your specific case.
@2n3055 I'm honestly not sure. It would have to be a 1-off type thing worked out through your local sales/distributor folks. I know there have been a lot of changes in licensing over the last few years and haven't been connected enough to the details to know how they have decided to handle it. I highly recommend giving the line a call or an email and see what they say for your specific case.
Daniel,
thanks a lot for your answer. As I said, it used to be simple and now is both more versatile and confusing. Soon it will be time to extend my maintenance and I will ask then..
All the best,
Sinisa@2n3055 I'm honestly not sure. It would have to be a 1-off type thing worked out through your local sales/distributor folks. I know there have been a lot of changes in licensing over the last few years and haven't been connected enough to the details to know how they have decided to handle it. I highly recommend giving the line a call or an email and see what they say for your specific case.
I bumped into a similar situation and reached out to support.
I bought a MSOX3104T from the Keysight EBay store with the full app bundle back in May (2021). They were offering (and still offer) the old, discontinued full app bundle (interesting they can still cut new licenses for it even though it's discontinued). Since that bundle predates the existence of the option, it doesn't have USB decode/trigger included.
I asked Keysight support what the status was of the option (the collaterals about the option on the website are a bit all over the place, some claiming it isn't offered, others that is is offered including HS, yet others that is is offered, but no HS).
They were very responsive (always amazed by Keysight support) and got to the bottom of the issue quickly, but declined to add the USB option to my unit, based on the fact that I got what was advertised (fair), and the fact that the bundle had already been discontinued at the time of purchase didn't really play into it (more debatable).