New firmware for Keysight 3000T and 4000 series scopes - version 7.11

[TheSteve]

Edit - version 7.11 has now replaced version 7.10

Download here:

http://www.keysight.com/main/software.jspx?ckey=2573488&lc=eng&cc=CA&nid=-11143.0.00&id=2573488

Release notes:

http://www.keysight.com/main/redirector.jspx?action=ref&nid=-11143.0.00&lc=eng&cc=CA&ckey=2573486&cname=EDITORIAL&nfr=-11143.0.00


It looks like the new firmware Daniel from Keysight mentioned during scopemonth has been released for the 3000T and 4000 series scopes.

The firmware version has changed from 4.08 to 7.10 (quite the odd change).

New features added:

–Added Frequency Response Analyzer option (DSOXT3FRA).
–Added Manchester/NRZ serial decode option (DSOXT3NRZ).


Enhancements:

–The measurement system has been updated to provide more flexibility to support new measurements with more complex configurations.  Some installed measurements will not be recallable if the setup (.scp) file was created with firmware prior to version 7.10.
–Users can now pick specific edges to be used by the Delay measurement. 
–Bartlett is now supported as an FFT window choice. 
–The UART serial decode now supports baud rates to 12Mbits/s. 
–DVM and training signals are now standard features.
–Added random trigger holdoff feature. 
–Added support to the NFC option for NFC-F reverse polarity triggering.
–Added Channel Power, Occupied Bandwidth, Adjacent Power Ratio, and Total Harmonic Distortion measurements

Bug Fixes:

–Fixed an issue where in certain circumstances the Serial Lister would not properly display some UART data.
–Fixed an issue where in certain circumstances the Peak-Peak measurement was incorrect. 

[Keysight DanielBogdanoff]

Download link:

3000T:
http://www.keysight.com/main/software.jspx?ckey=2573488

4000X:
(It's the same firmware) It's NOT the same firmware, make sure you use the right version for your scope.
http://www.keysight.com/main/software.jspx?cc=US&lc=eng&ckey=2287602

[Dubbie]

Nice!

Thanks for posting this.
[edit]
Ooh! I have to say I LOVE the new axis labels. Much faster than counting graticle lines.
Thanks R&S!.... I mean Keysight....

[TheSteve]

I'm not a fan of the safety warning when enabling 50 ohm input.

Daniel - Do you guys have plans to add further options that aren't included in the app bundle?

I doubt I will need NFC triggering or CXPI triggering/decode but it makes the app bundle feel a little less complete now. With so much competition in the scope market at the moment I am surprised they weren't included in the bundle(yes I have the app bundle for my 3024T).

[Keysight DanielBogdanoff]

N
[edit]
Ooh! I have to say I LOVE the new axis labels. Much faster than counting graticle lines.
Thanks R&S!.... I mean Keysight....

I know! I've been asking R&D to put this in for a long, long time. Also, ouch .

Daniel - Do you guys have plans to add further options that aren't included in the app bundle?

My understanding is that app bundles purchased from now on will include these, but prior ones will not. It's generally due to the architecture of how we enable options, and the thought (for better or more likely worse) is that people who bought the bundle previously didn't need or want that and bought it anyways, so they probably won't have a need for it.

[TheSteve]

Ouch, that actually makes it hurt a little more. Punished for being an "early adopter".

[gslick]

N
[edit]
Ooh! I have to say I LOVE the new axis labels. Much faster than counting graticle lines.
Thanks R&S!.... I mean Keysight....

I know! I've been asking R&D to put this in for a long, long time. Also, ouch .

Is this another feature that will only be present on the 3000T going forward and most likely won't make its way back to a 3000A firmware update in the future?

[Keysight DanielBogdanoff]

Ouch, that actually makes it hurt a little more. Punished for being an "early adopter".

If it becomes an issue for you, let me know via PM.

[ralphrmartin]

Daniel - Do you guys have plans to add further options that aren't included in the app bundle?

My understanding is that app bundles purchased from now on will include these, but prior ones will not. It's generally due to the architecture of how we enable options, and the thought (for better or more likely worse) is that people who bought the bundle previously didn't need or want that and bought it anyways, so they probably won't have a need for it.

That seems pretty unfortunate. Is there any way you could reconsider this? Some of those extra options would be pretty handy, and would certainly be a good goodwill gesture to those who already have got the App Bundle. The individual options are *very* expensive.
 

[Keysight DanielBogdanoff]

Daniel - Do you guys have plans to add further options that aren't included in the app bundle?

My understanding is that app bundles purchased from now on will include these, but prior ones will not. It's generally due to the architecture of how we enable options, and the thought (for better or more likely worse) is that people who bought the bundle previously didn't need or want that and bought it anyways, so they probably won't have a need for it.

That seems pretty unfortunate. Is there any way you could reconsider this? Some of those extra options would be pretty handy, and would certainly be a good goodwill gesture to those who already have got the App Bundle. The individual options are *very* expensive.
 

This decision is unfortunately out of my hands at this point. If you're looking for the FRA option and have an application bundle, you get all that functionality as part of the power supply testing option. So, getting the FRA doesn't actually gain you anything. If I recall correctly, there's actually a gain margin & phase margin measurement in the power app that isn't included in the FRA option.

[ralphrmartin]

If you're looking for the FRA option and have an application bundle, you get all that functionality as part of the power supply testing option. So, getting the FRA doesn't actually gain you anything. If I recall correctly, there's actually a gain margin & phase margin measurement in the power app that isn't included in the FRA option.

Ah, OK, but then it seems odd to sell two options, one of which is a subset of the other, rather than them being complementary functionality That means that if you buy the FRA option first, then later buy the power option for its extra functionality, you are paying for some things twice,,,

Anyway, thanks for the clarification..

[ralphrmartin]

That's a huge jump in version number. Daniel, any comments on what that's all about?

[TheSteve]

I'm going to guess that the jump from 4.08 to 7.10 is really x.08 to x.10 - and the jump from 4 to 7 is probably just a series reset to avoid confusion between various other oscilloscope firmware versions.

I suspect when more people find out that new purchasers of the app bundle get apps that existing customers don't they will be "displeased" with Keysight.

[kaz911]

I'll chime in as a disgruntled App bundle buyer and owner ! Not nice !

and apart from that how are people going to be able to differentiate later on if they want to sell the scope. "It includes the App Bundle" - "Ahh ok- but from which date?" 

If you buy the bundle - it should either stay the same bundle (product) or everybody's bundle should be updated. I could really do with the Manchester decode option. I would even pay a fee for updating my bundle but not full SRP of an option.

Anyway - seems like Keysight's license business managers are coughing up licensing hairballs all over the place just like in BenchVue.  

[raupi]

Hi,

anyone noticed problems using a mouse with the new firmware (Keysight 3000T)? I'm using a Logitech M185 wireless mouse and every time I switch the scope on now I have to remove and reinsert the USB receiver dongle to force the mouse pointer to appear on the screen. This wasn't necessary in previous firmwares 

Thanks.

[Keysight DanielBogdanoff]

I've corrected my post above, the 3000T and 4000X use different firmware, they aren't identical. So make sure you use the right version for your scope (don't switch 3k firmware with 4k firmware).

[raupi]

Thanks @Keysight_DanielBogdanoff, but I've used the correct version for 3000T models (even did a reflash today, just to make sure). I did a "Clear NVRAM" and "Reset to Factory Defaults" as well but that doesn't help either. I will try to borrow a different brand mouse to check if it's just an incompatibility with this specific Logitech mouse model.

[Keysight DanielBogdanoff]

@raupi, I'll take a look at it, too. Let me know what you find!

[blacksheeplogic]

My understanding is that app bundles purchased from now on will include these, but prior ones will not. It's generally due to the architecture of how we enable options, and the thought (for better or more likely worse) is that people who bought the bundle previously didn't need or want that and bought it anyways, so they probably won't have a need for it.

I would be interested in any clarification on this point. My scope that arrive last week was shipped with 7.10 with Factory installed application bundle. While FRA is included, CXPI, Manchester, and NRZ are not licensed.

I guess, as other have said those with the app bundle and missing the licenses should have a better upgrade path than full SRP.

Also if these options are now being given with the app bundle as of release 7.10, since the scope shipped with 7.10 & the app bundle I would have expected the licenses delivered would be the same as if I installed the license post delivery.

[smithnerd]

I'm seeing a mouse issue with my 4000X too. The mouse is working (e.g. wheel up/down changes waveform intensity), it's just the mouse pointer that's missing on boot, until I hotplug the dongle - rather a nuisance.

I have a Logitech M-RAA93.

Edit: happens with every mouse I've tried. I hooked it up to a USB KVM switch as a workaround.

[Keysight DanielBogdanoff]

The mouse issue is a verified bug in 7.10 firmware. There will be a new firmware version posted to k.com tomorrow or the next day - I'll follow up here with a link once it's live.

[electr_peter]

Checked with X3000T 7.10 with cheap wireless mouse/keyboard. Mouse works, but pointer is not shown on the screen. Reconnecting USB dongle bring back muse pointer.
Looking forward for SW update.

[Keysight DanielBogdanoff]

New firmware is up! It's still labeled 7.10 but it has a new date code, in case of any confusion.

3000T:
http://www.keysight.com/main/software.jspx?ckey=2573488

4000X:
http://www.keysight.com/main/software.jspx?cc=US&lc=eng&ckey=2287602

Also, Johnnie did a nice little write up about some of the new stuff in 7.10, including User-definable Manchester/NRZ Trigger & Decode
https://community.keysight.com/community/keysight-blogs/oscilloscopes/blog/2017/05/03/new-infiniivision-firmware-release-version-710

[Amazing]

The new features look really good, particularly the RF measurements on the FFT.  I'm looking forward to trying them out.

I have to say though, that as a recent purchaser of an MSOX3104T and app bundle, that I'm a little annoyed that the new options aren't included.  I thought after spending that much that I'd be getting all of the software updates.

Regarding the Manchester decoding, do you (Daniel) know if it will decode SMPTE timecode?  SMPTE TC is bi-phase mark. Would I be able to trigger on particular frame?

That would be very useful for checking that the timing of the equipment that I develop that follows timecode.

Thanks.

[mikeselectricstuff]

Bug report/misfeature - the horizontal scale annotations disappear when bus decoding is on. As the bus decode always sits at the bottom of thescreen, maybe move the scale to the top?
Also they are too dim, especially when blue or pink.

[mikeselectricstuff]

Another bug - the horizontal scale offset is incorrect  when you set the time reference to left or right.

[TheSteve]

Mike - you can try the newer version of 7.10 - maybe the second bug was fixed.

[nfmax]

Will there ever be an FRA option available for the 2000X series? All the other MZ4 InfiniVison series have one now!

[mikeselectricstuff]

Just updated to 7.10.2017042905 ( was 7.10.20171130), no difference

[electr_peter]

Another bug - the horizontal scale offset is incorrect  when you set the time reference to left or right.

I can confirm this issue, I have noticed it as well after FW update.

[mikeselectricstuff]

The custom splashscreen function seems to no longer work - attempting to load a 800x480 image (MSOX3104T) , it displays about the top 384 lines of the image, immediately, vertically stretched and says "do not know how to load the selected file".
The display is then garbled - with parts of the image overlaying where the traces should be

Wondering if maybe it's looking for a different resolution?
Have tried PNG and BMP

[electr_peter]

The custom splashscreen function seems to no longer work

Do you mean boot screen image? Custom image still looks fine for me.

Boot-up time seems to take less time. IMHO MSOX3T booted a bit slower with previous FW.

[mikeselectricstuff]

The custom splashscreen function seems to no longer work

Do you mean boot screen image? Custom image still looks fine for me.

Boot-up time seems to take less time. IMHO MSOX3T booted a bit slower with previous FW.

I'm talking about adding a custom screen to a unit that did not previously have one ( e.g. after secure erase), not a previous image after a FW update
 

[rattnallen]

Is this a bug?

Digital channels seems to be shifted to the left.
WaveGen set to Pulse, 2.5Mhz, 50nS width and feed into channel 1, D0 and D1.
Trigger set to rising edge on D0 and in center.
The trigger seems to trigger right but the digital waveforms is shifted to the left by about 144nS and there is something strange going on to the right of the screen.
If I change the timebase the signal is still 144nS before the triggerpoint.
Don't know if this was there before the update but I haven't seen it before.

[mikeselectricstuff]

Is this a bug?

Digital channels seems to be shifted to the left.
WaveGen set to Pulse, 2.5Mhz, 50nS width and feed into channel 1, D0 and D1.
Trigger set to rising edge on D0 and in center.
The trigger seems to trigger right but the digital waveforms is shifted to the left by about 144nS and there is something strange going on to the right of the screen.
If I change the timebase the signal is still 144nS before the triggerpoint.
Don't know if this was there before the update but I haven't seen it before.

Have you checked the analogue probe skew setting?

[rattnallen]

Yes, it's 0.0s and the thing is that the analog channel is on the triggerpoint but the digital is not and the trigger is on D0...
And there is a 144nS difference between analog and digital channels and the max skew settings is +-100nS.
And the strange right part of the digital channels? The scope is in autotrigger and in run mode.
If I stop it, the strange right part goes away, but the digital signals is still 144nS to the left of the triggerpoint.

[Amazing]

Wow, I am really glad that I held off on applying the firmware update.

Thanks to those brave souls who did the upgrade and found these bugs.

I'm still hoping to hear back from Daniel about whether the new manchester encoding option will decode and trigger on SMPTE LTC timecode.

And still not happy about being asked to pay full price for a new serial decode after buying the full package of options in December, when the full options package price has not changed at all.  At least make the new options available for a small package upgrade fee ($200?).

Am I unreasonable to be annoyed by this?

I could understand it if it was some completely new complex feature like e.g. a jitter analysis package (which would be awesome to get on the 3000T, by the way).

[mikeselectricstuff]

Just confirmed I see the same thing - digital channels 130nS early. My scope has just been calibrated by Ketysight, so not a drift over time

[rattnallen]

Thank you, mikeselectricstuff 

A rather serious bug, I think.

[mikeselectricstuff]

I just plugged in my 1152A active probe and it's now saying "unsupported probe".
I have a feeling this probe had some mods and possibly an eeprom tweak, but I'm 99% sure it worked on an earlier firmware version

Does anyone have a copy of the previous firmware version ?

[mikeselectricstuff]

I just plugged in my 1152A active probe and it's now saying "unsupported probe".
I have a feeling this probe had some mods and possibly an eeprom tweak, but I'm 99% sure it worked on an earlier firmware version

Does anyone have a copy of the previous firmware version ?

Just tried my other probe and it appeard to work, so could be an issue with that probe.

[TheSteve]

The 1152A isn't natively supported, the scope reads it as a 1157A or 1158A - the scopes can be a little picky at times. You can always try cleaning the contacts or worst case connect the probes and then power the scope on.

[D3f1ant]

Yeah 144ns early here too >sigh<

[Amazing]

I have a copy of FW version 4.08 (3000XSeriesT.04.08.2016071801.ksx), ~53MB. Would it possible and safe to downgrade?

Were any of you able to successfully downgrade your firmware?

[Keysight DanielBogdanoff]

The bugs have been reported to R&D, I'll update as appropriate. Thanks!

[Keysight DanielBogdanoff]

7.11 will release next week and fix this issue along with a couple other reported bugs, I'll post the update and release notes as soon as they're finalized.

[Amazing]

7.11 will release next week and fix this issue along with a couple other reported bugs, I'll post the update and release notes as soon as they're finalized.

Great news, thanks for the update.

[adranp]

I can confirm 100% downgrading works between 7.10 and 4.08. I did it and it was painless..

[TheSteve]

7.11 has now been posted on the Keysight website.

Download link here:
http://www.keysight.com/main/software.jspx?ckey=2573488&lc=eng&cc=CA&nid=-11143.0.00&id=2573488

Release notes:

http://www.keysight.com/main/redirector.jspx?action=ref&nid=-11143.0.00&lc=eng&cc=CA&ckey=2573486&cname=EDITORIAL&nfr=-11143.0.00

[mikeselectricstuff]

Also seems to have fixed the custom splashscreen issue.
But the grid scale text is still too dim.

[Keysight DanielBogdanoff]

Noted, Mike, I'll pass the feedback along.

Side note, and this is more for posterity: If your 4000 X-Series oscilloscope’s software version is prior to 4.00, you will need to change the suffix of the upgrade file from .ksx to .agx.

[electrolust]

I just updated -- fantastic update.  The grid scale legend is really great.  I don't find it too dim; I think it's just right.

[Dubbie]

I find the grid legend just right as well. Any brighter and it would distract from the trace.

[mikeselectricstuff]

I find the grid legend just right as well. Any brighter and it would distract from the trace.

It should be adjustable if possible

[raupi]

Bump...

New firmware available, version 7.20.20171026, release date 2017-10-26

http://www.keysight.com/main/software.jspx?ckey=2573488&lc=ger&cc=DE&nid=-32541.1150366&id=2573488

[TheSteve]

Installed the new firmware - no problems so far. Telnet still works in case anyone was wondering.

[myhobo]

Hello everyone, can anyone provide Agilent   firmware  4000XSeries.7.20.2017102615.ksx