You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Labber instrument server, after adding UHFLI, a path error message appears when starting the instrument. The screenshots are shown below.
The problem is that when starting the instrument, it loads the default setting in .ini file which includes the settings not only for a bared device but also for some options. In this case, the default setting includes setting with the MF option, i.e., set amplitude and frequency for 8 oscillators, but if the user has no MF option, a similar path as 'sigouts/0/amplitudes/0' will lead an error.
I have commented on the settings related to the MF option in .ini folder, have tested it and it works. However, this is just a temporary solution. I think the best way is that first identify what options are in the device and then load the default setting accordingly. I believe this issue also exists in other instruments.
The text was updated successfully, but these errors were encountered:
In the Labber instrument server, after adding UHFLI, a path error message appears when starting the instrument. The screenshots are shown below.
The problem is that when starting the instrument, it loads the default setting in .ini file which includes the settings not only for a bared device but also for some options. In this case, the default setting includes setting with the MF option, i.e., set amplitude and frequency for 8 oscillators, but if the user has no MF option, a similar path as 'sigouts/0/amplitudes/0' will lead an error.
I have commented on the settings related to the MF option in .ini folder, have tested it and it works. However, this is just a temporary solution. I think the best way is that first identify what options are in the device and then load the default setting accordingly. I believe this issue also exists in other instruments.
The text was updated successfully, but these errors were encountered: