1 file changed
+1
-1
lines changedDiff for: artiq/devices/pxi6733/driver.py
+1-1
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
93 | 93 |
| |
94 | 94 |
| |
95 | 95 |
| |
96 |
| - | |
| 96 | + | |
97 | 97 |
| |
98 | 98 |
| |
99 | 99 |
| |
|
artiq/devices/pxi6733/driver.py
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
93 | 93 |
| |
94 | 94 |
| |
95 | 95 |
| |
96 |
| - | |
| 96 | + | |
97 | 97 |
| |
98 | 98 |
| |
99 | 99 |
| |
|
4 commit comments
sbourdeauducq commentedon Aug 19, 2015
1 is an arbitrary scale and can be very large if the samples are small. I'd apply this workaround only when min=max.
jordens commentedon Aug 19, 2015
That's irrelevant. It is a 16 bit DAC with fixed output range.
But what might become relevant (not here and 6733 through) is the fact that min and max should not be automatically derived from the values. For cards that have variable output range, they could change the range depending on the output which may not be what one wants or what is expected.
fallen commentedon Aug 20, 2015
@jordens so you think we should allow one to use an output range (min/max pair) which does not correspond to the sample values?
jordens commentedon Aug 20, 2015
Yes. For 6733, you can safely (if your experiment can survive that range) set min=-10 and max=10 (but i have seen funny things at +10V, suspecting signed integer effects) globally. For other cards this can be different.