I take a laptop between locations with different Joulescopes connected and in different configurations. It would be nice if I could save some of the settings to a file to make it faster to reconfigure.
This would include major settings like the sample rate, current & voltage range settings, sources, GPIOs and it would also be nice to capture widget settings like the trigger.
Hi @Jeremy - Thanks for the idea. I added Joulescope UI issue #312 to capture this.
I can definitely see a widget-specific save/load features, such as for the Trigger widget.
A more general save/load feature gets more difficult. The settings shown in the Device control widget are specific to each Joulescope. When you can adjust the defaults in Settings, specific settings for each Joulescope do not transfer, even within the same Joulescope UI instance. Also, many widgets allow you to specify which connected Joulescope to use.
In order to load settings and keep the same UI setup, you would need the same number of connected Joulescopes operating in the same modes. You would also need to provide a mapping between “saved” Joulescopes to “load” Joulescopes, perhaps through a load settings dialog.
I think that this would help with the same Joulescope & test configuration across different computers. However, it does not help much with different configurations across different computers.
Does this match what you have in mind?
To me having device specific settings would be desirable as I have different configurations in the different locations. If it’s not device specific I would have some concern about getting the same configuration that each unit had previously. Having the same setup with different sets of Joulescopes would require multiple configuration files - that seems OK to me. If the configuration files are human readable / editable then reconciling different configurations would be possible.
Hi @Jeremy - The existing Joulescope UI configuration is stored as a JSON file. On Windows, it is located at:
%LOCALAPPDATA%\Joulescope\config\joulescope_ui_config.json
You are free to manipulate this file using Python or your programming language of choice. Other than the file paths and the UI window state (ads_state, geometry) it is mostly transferrable between computers.
If you mess it up this file so much that it prevents the Joulescope UI from launching, you can delete the file or start the UI while holding down the Shift key.
I am not exactly sure what you mean by this. Are you saying you want to apply the same settings to every connected Joulescope? Are you saying that you want to apply different settings to Joulescopes by their role in your test setup? Something else?
Thanks! I think editing the .json files will work for me. I’ll try keeping two reference sets with different names and copy to the working file based on location. Probably with a .git repo to track changes and allow reverting to previous versions.
I use different Joulescopes for different roles. Mostly they are static, but I sometimes take one or two between locations.
1 Like