| Products > Test Equipment |
| Questions about configuration options on Siglent SDS1104X-E |
| (1/1) |
| three_jeeps:
I am learning my way around this siglent scope and am looking at ways to store scope configuration options. In 'internal' storage, config files seem to be given numeric names, eg. 01, 02 etc. Is there any way to overwrite the file name so that it has some meaning? Directing config information to the external USB stick allows one to name the config file. What is the difference in config file information between these two methods? Lastly, the instructions for saving to internal memory say to 'connect the signal to the oscilloscope and obtain stable display'... In order to use this feature, do I have to have a signal? What if I just want to save the scope settings? What is the difference (content wise) between the two configuration saving modes? Thanks |
| tautech:
--- Quote from: three_jeeps on October 17, 2022, 05:38:02 pm ---I am learning my way around this siglent scope and am looking at ways to store scope configuration options. In 'internal' storage, config files seem to be given numeric names, eg. 01, 02 etc. Is there any way to overwrite the file name so that it has some meaning? --- End quote --- No, only when saving to External (USB) where you can name the XML file whatever you like. See screenshot #16 --- Quote ---Directing config information to the external USB stick allows one to name the config file. What is the difference in config file information between these two methods? --- End quote --- I don't know for sure but maybe designers where concerned about the best use of the Internal space available. --- Quote ---Lastly, the instructions for saving to internal memory say to 'connect the signal to the oscilloscope and obtain stable display'... In order to use this feature, do I have to have a signal? What if I just want to save the scope settings? --- End quote --- No signal required but do consider the warning a stable display should be gained is to warn that unless it is, your settings are not optimal and therefore should not be saved as a Setup. For different but regular jobs we each might have preferred settings so being able to recall known working settings is convenient and that is the Save/Recall Setup primary function however it can also be useful for guidance when scope settings that should work don't. A recent example was I'd thought I'd found a bug and Siglent asked for a Setup file to help diagnose what the issue was and it was how the scope was set at my end, in particular a Trigger setting IIRC which after the scope was Defaulted disappeared of course. Felt like a muggins but I learnt a valuable lesson....not all settings are always visible and don't be scared to use Default to return the scope to settings that for most jobs will always work ! Which conveniently brings us to another useful and powerful feature in these scopes....User Default. Also in the Save/Recall menu>Save type = To Default Key> Factory Setup or Current Setup. (Toggle between the 2) With this we can have any feature in how the scope is set assigned to the Default key as our preferred personal setup. # of active channels, their reference (0V) level, V/div and timebase setting, Trigger level and settings and the list goes on and on. There are some considerations be to aware of and best advice is to Default the scope before setting and saving a User Default so to be sure some obscure hidden setting is not saved into a User Default. Some screenshots as examples. |
| Navigation |
| Message Index |