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
Added a minimum_clock_high_time attribute the the NovaTechDDS9M labscript device class.
This is the corresponding change for labscript-suite/labscript#88
Technically I think this can be as low as 100ns but I'm concerned that some of the tri-state buffer hardware (or similar) that some labs have in front of their NovaTechs might mean this is actually slower. 1us seems like a safe bet while allowing people to command output on other clocklines within a reasonable time frame.
Copy file name to clipboardExpand all lines: labscript_devices/NovaTechDDS9M.py
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,13 @@ class NovaTechDDS9M(IntermediateDevice):
37
37
allowed_children= [DDS, StaticDDS]
38
38
clock_limit=9990# This is a realistic estimate of the max clock rate (100us for TS/pin10 processing to load next value into buffer and 100ns pipeline delay on pin 14 edge to update output values)
39
39
40
+
# This is longer than the technical requirement on the NovaTech. However, I
41
+
# suspect the tri-state buffer or similar electronics that some groups have
42
+
# in front of their NovaTech clock inputs might limit how fast this can be.
43
+
# 1us should be a good compromise, but can always be overridden by a
0 commit comments