[BUG]: Auto-generated functions for TSP devices containing arguments with defaults require all optional arguments to be provided values if any are desired to be changed

[GaliumNick]

Description of the bug

Hello,
I am trying to get the sample code smu_2460_solar_panel_sweep.py to work without fail_abort restraint. Any idea how to turn off fail_abort? I set it to 0, '0', 'smu.OFF', 'False', False, and inst.commands.smu.OFF with no effect.

The parameter calls for a str, but when I input a string, it just spits out:

I changing the function to `sweeplinearstep()' and it shows the same error. When I put in 0 nothing changes. The sweep still stops when the smu hits compliance.

Steps To Reproduce

1. Run sample code smu_2460_solar_panel_sweep.py
2. Go to sweeplinear() parameters and add fail_abort=inst.commands.smu.OFF
3. Read terminal
4. Complain on GitHub

[GaliumNick]

I found the error in the source code:

As you can see in the first screen shot up top in my post, all optional arguments are set to None. The problem occurs in the next lines of the sweeplinear() function:

I set fail_abort=inst.commands.smu.OFF, however because of the code line if x is not None, the function doesn't write anything for empty arguments. This causes it to end up writing 'smu.OFF' to the first optional argument count instead. This is why there's a TypeError.

All that is needed to fix this issue is to set every argument to their default in the argument list:

[nfelt14]

I am re-opening this issue, since it is not fixed yet.

[nfelt14]

The workaround is just to provide all default values when you call the function, but that isn't a true fix.