| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (525/899) > >> |
| alank2:
--- Quote from: stuartk on January 17, 2014, 06:25:47 pm ---7. Connect using scpi and issue :SYSTem:OPTion:UNINSTall command which will uninstall all keys and save to flash --- End quote --- When you did this, did your scope respond with a message on the screen, something like: Options of official version have deleted. I mention this because for a long time I thought I was issuing the ":SYSTem:OPTion:UNINSTall" command, but I was doing it wrong and nothing was happening... |
| stuartk:
Yep it did. |
| AndersAnd:
What happens if you follow the last 3 steps and use DSEZ as option? Does the model name change to 2202? |
| alank2:
--- Quote from: stuartk on January 17, 2014, 06:25:47 pm ---I stopped there as the serial number and model number were not correct. True got model # 2202, I have 2022 --- End quote --- Odd. I sure don't get the 2022 thing. Did the serial stay the common mangled 14 digit 0001 type one? On my unit when I tried this step 5 fixed the serial, but the model was still wrong until I did a restart and then they were both right in the basic system info menu... I have a theory that it gets corrupted (maybe this is how the s/n gets mangled in the first place) when you try to do more than one key operation without power cycling. In other words, to keep a s/n from getting messed up, I would always power cycle after doing a key uninstall, or installing a key. One operation per reboot. |
| AndersAnd:
--- Quote from: alank2 on January 17, 2014, 06:50:33 pm ---Odd. I sure don't get the 2022 thing. Did the serial stay the common mangled 14 digit 0001 type one? --- End quote --- What model# did you select for the custom FW? 2072, 2102, 2202 or 2302? Maybe there's a bug in the FW modification tool that only occurs when selecting 2102? |
| Navigation |
| Message Index |
| Next page |
| Previous page |