Bug: setting value jumps when type is int32

I initialize a voltage.step value but, when I try to set a voltage value on my SMU I get the error 'cannot sweep voltage from numberx to numbery - jumping' when the number I am setting is of type np.int32, when I change the setting value type to np.float64 I no longer get this error and my ramp works fine.

- the return of this parameter from the instrument is float.
- instrument.voltage(np.int64(numbery)) & instrument.voltage(np.float32(numbery)) give the same behavior (no ramp) .
- after changing to float or np.float64 from one of the types that don't work, the next immediate set gives the same error but, any subsequent set works fine (until the type is changed back to one of the ones that dont work, then it immediatley gives the error without even working for one more set).

No source file or test is identified in the issue. First reproduce the voltage-setting behavior with np.int32, np.int64, np.float32, and np.float64 values, then trace the instrument voltage parameter's ramp or sweep handling. Done means integer NumPy values ramp without the false "jumping" error and retain the same behavior as float values.

Written by the indexing model from the issue text.