Hello,
There is occasions one would want settings done in one session been stored and available an other session, e.g.
switching from local operation to ERS operation, e.g. in case of different PCs
SW install or update
For the time being settings are required to be set once again e.g. when installing a new SW. There is a potential risk something is missed from well proven settings and in case of external peripheral devices even something can be damaged. I'm especially thinking about the delay settings found in band manager and break.in settings windows (ESDR3 v1.0.3 beta).
Naturally best would be to store settings in the rig and reload them in to the client software every time new session is started.
I propose:
add a caution window to remind end-user there is no settings done actively e.g. in case of new SW install or update
store settings in the rig so independetly if I use local PC connected to rig or ERS PC, the same settings are shared independently of the client software
Hello, There is occasions one would want settings done in one session been stored and available an other session, e.g.
For the time being settings are required to be set once again e.g. when installing a new SW. There is a potential risk something is missed from well proven settings and in case of external peripheral devices even something can be damaged. I'm especially thinking about the delay settings found in band manager and break.in settings windows (ESDR3 v1.0.3 beta).
Naturally best would be to store settings in the rig and reload them in to the client software every time new session is started.
I propose:
73 Petri oh4mvh