Is there a patch location for the latest Agilent DSO6104 (.20) code to enable all the features ? If not, is there a download location for the .16 code used in many of the above examples.
Thanks,
Bill
Could you please point me to the correct steps to enable the service menu?
Could you please point me to the correct steps to enable the service menu?
Service menu on MSO7000
telnet <ip> 5810
username: panther
password: pictures
-> cmd
[vxWorks]# mem modify -w 1 0x009A2187
0x009a2187: 0x00-0x01
0x009a2188: 0x00-.
“cmd”
then press enter. At [vxWorks]# prompt, type
“mem modify -w 1 0x009A2187”
then press enter.
Then type “0x01” and press enter again.
Then type “.” and press enter again.
Then open up the service menu
utility -> options -> licenses -> options
enable 'service mode', 'all licenses', and 'mso'
reboot scope
Done
====================
Only for 6000 series type this in the vxWorks console:
mem modify -w 1 0x00966E67
vxWorks response should be:
0x00966e67: 0x00-
Now type "0x01" after "0x00-" to enable service menu.
new vxWorks response should be:
0x00966e68: 0x00-
Now type "." after "0x00-" to exit.
Now go to "Options" -> "Licenses".
The reason I raise this is that the way I read the previous posts on this in this thread was that it was dependent on 6.16. My 7000B arrived with 6.17 so I booted off a 6.16 USB stick and did the setting that way as I didn't know if it would work otherwise. I'm not saying it won't work with other versions, I was asking for clarification.
The reason I raise this is that the way I read the previous posts on this in this thread was that it was dependent on 6.16. My 7000B arrived with 6.17 so I booted off a 6.16 USB stick and did the setting that way as I didn't know if it would work otherwise. I'm not saying it won't work with other versions, I was asking for clarification.
I will have a look tomorrow on my 7000B series, as to what FW is installed.
So, you always boot yours from a USB stick?
You never tried to access with telnet on FW v 6.17?
I tried both addresses (for the 7000 and 6000) and neither one gives me the service menu in my DSO6104.
I'm assuming that the magic location will vary with the software version. I am using the latest V6.20 (not the V6.16 that seems to be prevalent in this thread.
Does anyone have either the magic address for the 6000 scope with V6.20 software or a location that I can download the 4 necessary files for V6.16?
Thanks in advance,
Bill
If somebody wants to go ServiceMode way, there is more portable way: execute setServiceMode(1) in C mode console ("->" prompt). But, as it was discussed already, there is no danger patching sys.bin - we are not touching the bootloader, where "emergency" restore lives.
I have made a real good bargain just before xmas on a MSO6034A.... 800€ with all probes !
You successfully added the 4Gs/s rate to your 6034A; your modified address location was 0x00231420 for the 4 modified octets, but for what firmware version ?
I am currently using the 6.20 version, do you know which adress i should use for this version (unfortunately, the string 38 09 FF FD is present at many different places ?)
Did you succeded into the modification of the front end passive components (filtering adjustments before and after the 1NB7-8453 hybrid) ?
I wonder if removing that capacitor is enough to increase the BW to 500MHz.
Is this dependent of a certain firmware version, or is it universal?
The reason I raise this is that the way I read the previous posts on this in this thread was that it was dependent on 6.16. My 7000B arrived with 6.17 so I booted off a 6.16 USB stick and did the setting that way as I didn't know if it would work otherwise. I'm not saying it won't work with other versions, I was asking for clarification.
I don't remember ever doing so. I did have a look at the .bin images and determined that the "other" way was in different locations, I don't know if that is the case for setting the service menu on, but my concern was more about the risk in bricking the scope if it was in a different place, and the possible damage caused by poking an unknown location.
If somebody wants to go ServiceMode way, there is more portable way: execute setServiceMode(1) in C mode console ("->" prompt). But, as it was discussed already, there is no danger patching sys.bin - we are not touching the bootloader, where "emergency" restore lives.
I wonder if removing that capacitor is enough to increase the BW to 500MHz.
No, it's not that simple.
For looking at signals over 100MHz go for passive Lo-z or active FET probes for the most accurate signal display and least signal loading. For ordinary use (<100MHz) any probe will do.
For looking at signals over 100MHz go for passive Lo-z or active FET probes for the most accurate signal display and least signal loading. For ordinary use (<100MHz) any probe will do.Thanks but am I limited to the ones that Agilent (Keysight) lists? There appear to be several non Agilent probes available that have the little gold pin sticking out - e.g. these ones on Amazon. I realize these are passive but they're supposed to be good for 500 MHz? Active probes are $600 - $1,500 each. I'm not averse to spending money but am looking for guidance on best bang for my buck and I don't need 4 active probes on my 7104 on day 1.