Applied Scientific Instrumentation

User Tools

Site Tools

Trace: • ttl
commands:ttl

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
commands:ttl [2025/05/01 19:16] – add more info to mode 8 brandoncommands:ttl [2026/06/19 19:35] (current) – add space to bottom of page brandon
Line 3: Line 3:
 TTL functionality differs based on whether the controller is a Tiger (TG-1000) or MS2000/RM2000 controller, due to hardware differences. Some TTL modes are only available with certain firmware modules. TTL functionality differs based on whether the controller is a Tiger (TG-1000) or MS2000/RM2000 controller, due to hardware differences. Some TTL modes are only available with certain firmware modules.
  
-The Tiger (TG-1000) and MS2000 controller electronics have a buffered TTL input (''IN0'') and output (''OUT0'') port that are usually connected to the IN and OUT BNC connectors on the back of the controller. These ports allow voltages in the range of 0V to 5V as an input, where any voltage below 0.95v(+-0.3v) is a LOGIC LOW signal. Any signal above 1.6 V (+-0.3 V) is considered a LOGIC HIGH state. Any signals in between 0.95 to 1.6 V will maintain the same logic state that was registered from the last //known// state (Schmitt Triggered inputs). The TTL input has a 10K Ohm resistor to ground, and connecting to the input of a Schmitt Trigger 5W TTL gate. The output is CMOS-compatible 5v TTL directly from a single CMOS gate. The behavior of these connectors are determined by the ''IN0_mode'' and ''OUT0_mode'' parameters set by the ''TTL X'' and ''TTL Y'' commands respectively. There are also has several unbuffered I/O ports on the motherboard that are occasionally exposed for special purposes.+The Tiger (TG-1000) and MS2000 controller electronics have a buffered TTL input (''IN0'') and output (''OUT0'') port that are usually connected to the IN and OUT BNC connectors on the back of the controller. These ports allow voltages in the range of 0V to 5V as an input, where any voltage below 0.95v(+-0.3v) is a LOGIC LOW signal. Any signal above 1.6 V (+-0.3 V) is considered a LOGIC HIGH state. Any signals in between 0.95 to 1.6 V will maintain the same logic state that was registered from the last //known// state (Schmitt Triggered inputs). The TTL input has a 10K Ohm resistor to ground, and connecting to the input of a Schmitt Trigger 5v TTL gate. The output is CMOS-compatible 5v TTL directly from a single CMOS gate. The behavior of these connectors are determined by the ''IN0_mode'' and ''OUT0_mode'' parameters set by the ''TTL X'' and ''TTL Y'' commands respectively. There are also has several unbuffered I/O ports on the motherboard that are occasionally exposed for special purposes.
  
 <WRAP center round important 60%> <WRAP center round important 60%>
Line 36: Line 36:
  
 __//IN0_mode//__  __//IN0_mode//__ 
 +
 +----
  
 **0** - Turns off TTL IN0 controlled functions; TTL interrupt DISABLED. **0** - Turns off TTL IN0 controlled functions; TTL interrupt DISABLED.
  
-**1** - TTL IN0 initiates a Move-to-Next-Position of the stored positions in the ring buffer pointed to by the buffer_pointer.  When the buffer_pointer reaches a value equal to the number of saved positions, it resets to the first position, allowing cyclic repetitions to the saved locations.  See [[commands:rbmode|RBMODE]]  and [[commands:load|LOAD]] commands.+---- 
 + 
 +**1** - TTL IN0 initiates a Move-to-Next-Position of the stored positions in the ring buffer pointed to by the ''buffer_pointer''.  When the ''buffer_pointer'' reaches a value equal to the number of saved positions, it resets to the first position, allowing cyclic repetitions to the saved locations.  See [[commands:rbmode|RBMODE]]  and [[commands:load|LOAD]] commands. 
 + 
 +----
  
 **2** - TTL IN0 repeats most recent relative move (see [[commands:movrel|MOVREL command]]). For example, begin a session by issuing the command ''RM Y=7'', then ''MOVREL X=0 Y=0 Z=10'', and each subsequent TTL trigger will cause the Z axis to move 1 micron((strictly speaking, it will be the closest multiple of the specified distance in encoder units because that is how the move distance is stored internally)). This function can be used for repetitive relative moves of any axis or combination of axes on the controller (for MS-2000) or on the card (for Tiger).  For the "focus axis" only you may directly set the dZ value with the ''[[commands:zs|ZS]]'' command's X parameter.  **2** - TTL IN0 repeats most recent relative move (see [[commands:movrel|MOVREL command]]). For example, begin a session by issuing the command ''RM Y=7'', then ''MOVREL X=0 Y=0 Z=10'', and each subsequent TTL trigger will cause the Z axis to move 1 micron((strictly speaking, it will be the closest multiple of the specified distance in encoder units because that is how the move distance is stored internally)). This function can be used for repetitive relative moves of any axis or combination of axes on the controller (for MS-2000) or on the card (for Tiger).  For the "focus axis" only you may directly set the dZ value with the ''[[commands:zs|ZS]]'' command's X parameter. 
  
 As of ''MS2000 9.2o'' and ''Tiger v3.38'' only the axes that are enabled with [[commands:rbmode|RM Y=#]] will be moved. The default axis mask is 3, for X and Y only to match with legacy firmware. Also, the ''[[commands:backlash|BACKLASH]]'' setting is ignored during TTL-triggered relative moves, on earlier versions of the firmware you will see incorrect results with fast TTL pulses if the backlash is not set to ''0''. As of ''MS2000 9.2o'' and ''Tiger v3.38'' only the axes that are enabled with [[commands:rbmode|RM Y=#]] will be moved. The default axis mask is 3, for X and Y only to match with legacy firmware. Also, the ''[[commands:backlash|BACKLASH]]'' setting is ignored during TTL-triggered relative moves, on earlier versions of the firmware you will see incorrect results with fast TTL pulses if the backlash is not set to ''0''.
 +
 +----
  
 **3** - TTL IN0 initiates an autofocus operation on systems with autofocus installed. **3** - TTL IN0 initiates an autofocus operation on systems with autofocus installed.
  
-**4** - Enables TTL IN0 controlled Z-stacks (see the [[commands:zs|ZS command]]). When this command is first received by the controller, the ZS command state machine is reset.+---- 
 + 
 +**4** - Enables TTL IN0 controlled Z-stacks (see the [[commands:zs|ZS command]]). 
 + 
 +----
  
 **5** - Enables TTL IN0-started [[:serial_position_report|serial position reporting]]. Information is asynchronously sent out to the serial interface every ''report_time'' interval, where ''report_time'' is set with the [[:commands:rtime|RT command]].  Data returned in the serial stream are the elapsed time in milliseconds since the TTL trigger, followed by the position of each axis enabled by the ''axis_byte'' (set by the [[commands:rbmode|RM command]]).  On ''TRACKING'' systems, the PMT sum signal is also reported.  Reporting is toggled on and off by triggering the TTL input. **5** - Enables TTL IN0-started [[:serial_position_report|serial position reporting]]. Information is asynchronously sent out to the serial interface every ''report_time'' interval, where ''report_time'' is set with the [[:commands:rtime|RT command]].  Data returned in the serial stream are the elapsed time in milliseconds since the TTL trigger, followed by the position of each axis enabled by the ''axis_byte'' (set by the [[commands:rbmode|RM command]]).  On ''TRACKING'' systems, the PMT sum signal is also reported.  Reporting is toggled on and off by triggering the TTL input.
 +
 +----
  
 **6** - On the rising edge of a TTL pulse, initiate a stage scan if the scan state is ''IDLE''. This is equivalent to sending the [[commands:scan|SCAN command]] without arguments to initiate a scan. Note: unlike the scan command, subsequent triggers will not stop the stage scan. **6** - On the rising edge of a TTL pulse, initiate a stage scan if the scan state is ''IDLE''. This is equivalent to sending the [[commands:scan|SCAN command]] without arguments to initiate a scan. Note: unlike the scan command, subsequent triggers will not stop the stage scan.
 +
 +----
  
 **7** - TTL commanded [[commands:array|ARRAY]] move to next position. **7** - TTL commanded [[commands:array|ARRAY]] move to next position.
  
-<wrap lo>MS-2000 v9.54 required</wrap> \\ +----
-**8** - TTL commanded [[commands:array|ARRAY]] move to next position, that does a Z-stack at each array position (see the [[commands:zs|ZS command]]). When this command is first received by the controller, the ZS command state machine is reset.+
  
-**9** - Used with CRISP focus lock.  TTL IN0 HIGH engages lock if the system is in the READY state.  TTL IN0 LOW will cause the system to UNLOCK is locked already.+<wrap lo>MS-2000 v9.54 or Tiger v3.54 required</wrap> \\ 
 +**8** - TTL commanded [[commands:array|ARRAY]] move to next position, that does a Z-stack at each array position (see the [[commands:zs|ZS command]]). 
 + 
 +---- 
 + 
 +**9** - Used with [[:crisp_manual|CRISP]] focus lock.  TTL IN0 HIGH engages lock if the system is in the READY state.  TTL IN0 LOW will cause the system to UNLOCK if it is locked already. 
 + 
 +----
  
 **10** - Toggle TTL OUT0. If TTL OUT0 is set either LOW or HIGH, an input pulse on the TTL IN0 will cause the output to toggle to the other state.  **10** - Toggle TTL OUT0. If TTL OUT0 is set either LOW or HIGH, an input pulse on the TTL IN0 will cause the output to toggle to the other state. 
  
-**11** - ''SERVOLOCK_TTL'' mode.  Requires firmware support; as of early 2020 it is only implemented in Tiger but could be ported to MS2000/RM2000.  To engage the ''SERVOLOCK_TTL'' mode use the [[commands:lock|LK]] command which will then automatically change the TTL IN0 mode and normally will restore it afterwards.  When the ''SERVOLOCK_TTL'' mode is engaged do not change the ''TTL X'' setting.  For further documentation see the [[:servolock_ttl|SERVOLOCK_TTL documentation]].+----
  
 +<wrap lo>Tiger v3.31 required</wrap> \\
 +**11** - ''SERVOLOCK_TTL'' mode. Requires the [[:servolock_ttl|SERVOLOCK_TTL]] firmware module. To engage the ''SERVOLOCK_TTL'' mode use the [[commands:lock|LK]] command which will automatically change the TTL IN0 mode and normally will restore it afterwards. When the ''SERVOLOCK_TTL'' mode is engaged do not change the ''TTL X'' setting.
 +
 +Not yet implemented for MS2000. 
 +
 +----
 +
 +<wrap lo>MS-2000 v9.52 or Tiger v3.24 required</wrap> \\
 **12** - Behavior is exactly the same as mode 1 above except the moves are relative rather than absolute. **12** - Behavior is exactly the same as mode 1 above except the moves are relative rather than absolute.
  
 > **CAUTION:** If you are using TTL X mode 12, the values entered into the ring buffer using the [[commands:load|LOAD]] command represent RELATIVE coordinates, not ABSOLUTE coordinates. You must drive the stage to the appropriate starting position before triggering a ring buffer sequence. > **CAUTION:** If you are using TTL X mode 12, the values entered into the ring buffer using the [[commands:load|LOAD]] command represent RELATIVE coordinates, not ABSOLUTE coordinates. You must drive the stage to the appropriate starting position before triggering a ring buffer sequence.
  
-Added in v3.24 for Tiger and version 9.52 for MS2000/RM2000.  +----
  
 +<wrap lo>MS-2000 v9.2l or Tiger v3.14 required</wrap> \\
 **20** - The TTL IN0 pulse turns on the TTL OUT0 for a fixed duration set by the [[commands:rtime|''RT Y'']] command.   **20** - The TTL IN0 pulse turns on the TTL OUT0 for a fixed duration set by the [[commands:rtime|''RT Y'']] command.  
  
 Can be used with a LED illumination to act as a flash of defined duration.  For the TGLED card and MS2000/RM2000 with a Dual LED card (DLED), all LED channels remain off until a TTL pulse is received, and the TTL rising edge turns all LED channels ON and they remain ON for the duration set by the ''[[commands:rtime|RT Y]]'' command.  ((Old text, unknown meaning: TTL Y must be in 0 mode (TTL Y=0) or it might cause an issue.))  LED intensity is set by the [[commands:led|LED]] command. Can be used with a LED illumination to act as a flash of defined duration.  For the TGLED card and MS2000/RM2000 with a Dual LED card (DLED), all LED channels remain off until a TTL pulse is received, and the TTL rising edge turns all LED channels ON and they remain ON for the duration set by the ''[[commands:rtime|RT Y]]'' command.  ((Old text, unknown meaning: TTL Y must be in 0 mode (TTL Y=0) or it might cause an issue.))  LED intensity is set by the [[commands:led|LED]] command.
  
-Added in v3.14 for Tiger and version 9.2l for MS2000/RM2000.   +----
  
 +<wrap lo>MS-2000 v9.2l or Tiger v3.14 required</wrap> \\
 **21** - Similar to mode 20 except TTL pulses cycle through the channels of the TGLED card or Dual LED card.  On each TTL pulse, only ONE LED channel turns ON for a fixed time. The next TTL pulse turns on the next LED channel for a fixed time, and so on. **21** - Similar to mode 20 except TTL pulses cycle through the channels of the TGLED card or Dual LED card.  On each TTL pulse, only ONE LED channel turns ON for a fixed time. The next TTL pulse turns on the next LED channel for a fixed time, and so on.
  
-For Tiger v3.24 and later, when [[commands:rbmode|RB F=3]] the TGLED card cycles thru all channels without waiting for TTL pulses.  If an intensity is set to 0 using the ''LED'' command then that channel is automatically skipped.+For Tiger v3.24 and later, when [[commands:rbmode|RB F=3]] the TGLED card cycles through all channels without waiting for TTL pulses.  If an intensity is set to 0 using the ''LED'' command then that channel is automatically skipped. 
  
-Added in v3.14 for Tiger and version 9.2l for MS2000/RM2000.  +----
  
 +<wrap lo>MS-2000 v9.2n or Tiger v3.30 required</wrap> \\
 +**22** - Similar as mode 20 except waits for TTL pulse to go low before turning off the LED. Setting ''RT Y'' isn't required.  
  
-**22** - Similar as mode 20 except waits for TTL pulse to go low before turning off the LED. Setting ''RT Y'' isn't required.+----
  
-Added in v3.30 for Tiger and version 9.2n for MS2000/RM2000.   +<wrap lo>MS-2000 v9.2n or Tiger v3.30 required</wrap> \\ 
- +**23** - Same as mode 21 except waits for TTL pulse to go low before turning off the LED. Setting ''RT Y'' isn't required.  
- +
-**23** - Same as mode 21 except waits for TTL pulse to go low before turning off the LED. Setting ''RT Y'' isn't required. +
- +
-Added in v3.30 for Tiger and version 9.2n for MS2000/RM2000.  +
  
 +----
  
 +<wrap lo>Tiger v3.30 required</wrap> \\
 **30** - Used with Single Axis Modes 2 and 4, see the [[commands:sam|SAM command]]. **30** - Used with Single Axis Modes 2 and 4, see the [[commands:sam|SAM command]].
  
Line 99: Line 130:
 Mode 4: On the rising edge of a TTL pulse, the routine runs continuously. Mode 4: On the rising edge of a TTL pulse, the routine runs continuously.
  
-Available in Tiger firmware 3.30 and above; not yet implemented for MS2000/RM2000.+Not yet implemented for MS2000. 
 + 
 +----
  
-<wrap lo>MS-2000 9.2n required</wrap> \\+<wrap lo>MS-2000 v9.2n required</wrap> \\
 **103** - Repeating Autofocus. This mode does not use TTL IN. When set, the controller will automatically attempt an autofocus routine every //K// milliseconds indefinitely until TTL X is changed. The repetition time, //K//, is set using [[commands:rtime| RTIME X]]. Example: **RT X=5000** will set the repetition rate to 5 seconds. This is effectively the same as using **TTL X=3** with an oscillator connected to TTL IN. **103** - Repeating Autofocus. This mode does not use TTL IN. When set, the controller will automatically attempt an autofocus routine every //K// milliseconds indefinitely until TTL X is changed. The repetition time, //K//, is set using [[commands:rtime| RTIME X]]. Example: **RT X=5000** will set the repetition rate to 5 seconds. This is effectively the same as using **TTL X=3** with an oscillator connected to TTL IN.
 +
 +----
  
 ===== TTL Output Mode =====  ===== TTL Output Mode ===== 
  
 __//OUT0_mode//__ __//OUT0_mode//__
 +
 +----
  
 **0** - TTL OUT0 unconditionally set LOW. **0** - TTL OUT0 unconditionally set LOW.
 +
 +----
  
 **1** - TTL OUT0 unconditionally set HIGH. **1** - TTL OUT0 unconditionally set HIGH.
 +
 +----
  
 **2** - generates TTL pulse at end of a commanded move (''MOVE'', ''MOVREL'', move via ring buffer, or via array module). The pulse duration is set with command ''[[commands:rtime|RT Y]]''. Note that any move that is initiated before the pulse duration is complete, will reset the duration timer and make the TTL output low immediately. For sequenced (automatic) array moves, use ''[[commands:rtime|RT Z]]'' to set the delay before the next array element is sequenced. **2** - generates TTL pulse at end of a commanded move (''MOVE'', ''MOVREL'', move via ring buffer, or via array module). The pulse duration is set with command ''[[commands:rtime|RT Y]]''. Note that any move that is initiated before the pulse duration is complete, will reset the duration timer and make the TTL output low immediately. For sequenced (automatic) array moves, use ''[[commands:rtime|RT Z]]'' to set the delay before the next array element is sequenced.
  
-**3** - <del>output TTL OUT0 gated HIGH during axis index 0 (X) constant speed move</del> **not implemented but hardware-level TTL signal is available**.+----
  
-**4** - <del>output TTL OUT0 gated HIGH during axis index 1 (Y) constant speed move</del>**not implemented but hardware-level TTL signal is available**.+**3** - <del>output TTL OUT0 gated HIGH during axis index 0 (X) constant speed move</del> **not implemented but ''[[../synchronized_zaxis_focus_sweeps|hardware-level TTL signal]]'' is available**.
  
-**5** - <del>output TTL OUT0 gated HIGH during axis index 2 (Z) constant speed move</del>**not implemented but hardware-level TTL signal is available**.+---- 
 + 
 +**4** - <del>output TTL OUT0 gated HIGH during axis index 1 (Y) constant speed move</del> **not implemented but ''[[../synchronized_zaxis_focus_sweeps|hardware-level TTL signal]]'' is available**. 
 + 
 +---- 
 + 
 +**5** - <del>output TTL OUT0 gated HIGH during axis index 2 (Z) constant speed move</del> **not implemented but ''[[../synchronized_zaxis_focus_sweeps|hardware-level TTL signal]]'' is available**. 
 + 
 +----
  
 **8** - TTL OUT0 timed arrival pre-pulse output.  See ''RT'' command. Requires ''PREPULSE'' firmware module. **8** - TTL OUT0 timed arrival pre-pulse output.  See ''RT'' command. Requires ''PREPULSE'' firmware module.
 +
 +----
  
 **9** - TTL OUT0 PWM and MicroServo or Solenoid output.  See the ''LED'' or the ''SECURE'' command. Requires ''LED_DIMMER'' or ''USERVO'' or ''SOL_LK'' firmware module. On WK, with LED_DIMMER, the PWM frequency is 1KHz. **9** - TTL OUT0 PWM and MicroServo or Solenoid output.  See the ''LED'' or the ''SECURE'' command. Requires ''LED_DIMMER'' or ''USERVO'' or ''SOL_LK'' firmware module. On WK, with LED_DIMMER, the PWM frequency is 1KHz.
 +
 +----
  
 **10** - Output TTL OUT0 gated HIGH upon completion of video AUTOFOCUS function.  ''AUTOFOCUS'' hardware and firmware required. **10** - Output TTL OUT0 gated HIGH upon completion of video AUTOFOCUS function.  ''AUTOFOCUS'' hardware and firmware required.
 +
 +----
  
 **11** - Generates TTL OUT0 pulse at end of commanded move providing CRISP is in ‘F’ state (active and within tolerance).  Waits for CRISP ‘F’ state after move completion to send a pulse.  Generally not useful with TG-1000 controllers because the XY and focus axes are on different cards.  ON MS-2000 the behavior of the ''STATUS'' command is modified when this TTL mode is set: 'N' is returned when CRISP is in the In-Focus 'F' state and otherwise 'B' is returned. The pulse duration is set with command ''[[commands:rtime|RT Y]]''. Note that any move that is initiated before the pulse duration is complete, will reset the duration timer and make the TTL output low immediately. For sequenced (automatic) array moves, use ''[[commands:rtime|RT Z]]'' to set the delay before the next array element is sequenced. **11** - Generates TTL OUT0 pulse at end of commanded move providing CRISP is in ‘F’ state (active and within tolerance).  Waits for CRISP ‘F’ state after move completion to send a pulse.  Generally not useful with TG-1000 controllers because the XY and focus axes are on different cards.  ON MS-2000 the behavior of the ''STATUS'' command is modified when this TTL mode is set: 'N' is returned when CRISP is in the In-Focus 'F' state and otherwise 'B' is returned. The pulse duration is set with command ''[[commands:rtime|RT Y]]''. Note that any move that is initiated before the pulse duration is complete, will reset the duration timer and make the TTL output low immediately. For sequenced (automatic) array moves, use ''[[commands:rtime|RT Z]]'' to set the delay before the next array element is sequenced.
  
 +----
  
 **12** - TTL OUT0 high when CRISP is in the ''F'' state, low otherwise. **12** - TTL OUT0 high when CRISP is in the ''F'' state, low otherwise.
 +
 +----
  
 **20** - TTL OUT0 set during SPIM state machine operation.  Requires ''MM_SPIM ''firmware module (TG-1000 only).  Was code 10 until v3.12. **20** - TTL OUT0 set during SPIM state machine operation.  Requires ''MM_SPIM ''firmware module (TG-1000 only).  Was code 10 until v3.12.
 +
 +----
  
 **21** - TTL1 backplane signal (PLC address 42) set high at the end of a ring buffer move or AIJ-initiated move (for laser trigger).  Requires ''MM_TARGET'' firmware module (TG-1000 only).  Was code 11 until v3.12.  As of firmware v3.36 outputs to the TTL1 backplane signal instead of to the usual TTL output. **21** - TTL1 backplane signal (PLC address 42) set high at the end of a ring buffer move or AIJ-initiated move (for laser trigger).  Requires ''MM_TARGET'' firmware module (TG-1000 only).  Was code 11 until v3.12.  As of firmware v3.36 outputs to the TTL1 backplane signal instead of to the usual TTL output.
 +
 +----
  
 <wrap lo>Tiger v3.17 required</wrap>\\ <wrap lo>Tiger v3.17 required</wrap>\\
-**22** - In this mode, TTL OUT0 is controlled by [[:singleaxis|Single-axis function]] module. With the [[commands:sap|SAP]] command the user can generate a TTL pulse that is synchronized with [[:singleaxis|Single-axis function]] actuator motion. The pulse duration is set with command [[commands:rtime|RT Y]].+**22** - In this mode, TTL OUT0 is controlled by the [[:singleaxis|single-axis function]] module. With the [[commands:sap|SAP]] command the user can generate a TTL pulse that is synchronized with [[:singleaxis|single-axis function]] actuator motion. The pulse duration is set with command [[commands:rtime|RT Y]]. 
 + 
 +----
  
 <wrap lo>Tiger v3.38 required</wrap>\\ <wrap lo>Tiger v3.38 required</wrap>\\
 **30** - TTL OUT1 high when the position of first axis is more than the PC setting away from its target position. **30** - TTL OUT1 high when the position of first axis is more than the PC setting away from its target position.
 +
 +----
  
 <wrap lo>Tiger v3.38 required</wrap>\\ <wrap lo>Tiger v3.38 required</wrap>\\
 **31** - TTL OUT1 high when the position of second axis is more than the PC setting away from its target position. **31** - TTL OUT1 high when the position of second axis is more than the PC setting away from its target position.
 +
 +----
  
 <wrap lo>Tiger v3.38 required</wrap>\\ <wrap lo>Tiger v3.38 required</wrap>\\
 **32** - TTL OUT1 high when the position of third axis is more than the PC setting away from its target position. **32** - TTL OUT1 high when the position of third axis is more than the PC setting away from its target position.
 +
 +----
  
 <wrap lo>Tiger v3.38 required</wrap>\\ <wrap lo>Tiger v3.38 required</wrap>\\
 **33** - TTL OUT1 high when the position of fourth axis is more than the PC setting away from its target position. **33** - TTL OUT1 high when the position of fourth axis is more than the PC setting away from its target position.
 +
 +----
  
 ===== TTL Output Polarity ===== ===== TTL Output Polarity =====
Line 154: Line 226:
 __//OUT0_polarity//__ __//OUT0_polarity//__
  
-**1** - default polarity+**1** - Default polarity
  
-**-1** - inverts the polarity of TTL OUT0+**-1** - Invert the polarity of TTL OUT0
  
 ===== TTL Auxiliary (Tiger Only) ===== ===== TTL Auxiliary (Tiger Only) =====
Line 184: Line 256:
 ===== Report Mode (MS-2000 Only) ===== ===== Report Mode (MS-2000 Only) =====
  
-__//report_mode//__ - This mode requires the ''TTL_OUT_REPORT'' firmware module.+__//report_mode//__ - This mode requires the ''TTL_OUT_REPORT'' firmware module.  
 +<wrap lo>MS-2000 v9.52 required</wrap>.
  
 **T** - Enables serial reporting on every output TTL pulse when set to be non-zero.  Will output on separate serial port if enabled with compile-time flag. **T** - Enables serial reporting on every output TTL pulse when set to be non-zero.  Will output on separate serial port if enabled with compile-time flag.
Line 195: Line 268:
   * X array index as 16-bit unsigned int (AIJ X? equivalent)   * X array index as 16-bit unsigned int (AIJ X? equivalent)
   * Y array index as 16-bit unsigned int (AIJ Y? equivalent)   * Y array index as 16-bit unsigned int (AIJ Y? equivalent)
 +
 +\\
 +The next value is the Z-stack index (ZS T? equivalent, related to the ZS command)
  
 Next the encoder value for all axes in order as 32-bit signed integer in twos-complement, 4 bytes per axis (can be converted to reported position using multiplier) Next the encoder value for all axes in order as 32-bit signed integer in twos-complement, 4 bytes per axis (can be converted to reported position using multiplier)
Line 212: Line 288:
   * To validate the checksum repeat the same steps but include the 16-bit checksum value in the running sum. The computed checksum should be 0000.  If not there was an error in checksum generation or transmission of the data.   * To validate the checksum repeat the same steps but include the 16-bit checksum value in the running sum. The computed checksum should be 0000.  If not there was an error in checksum generation or transmission of the data.
    
-Example: firmware includes ''ARRAY_MODULE'', ''CRISP'' and has X Y and Z axes.  TTL Y=2 sets a TTL pulse at the end of the move.  TTL T=51 sets this report format.  The report will be a string of numbers like this (spaces for readability only)+Example: firmware includes ''ARRAY_MODULE'', ''CRISP'' and has X Y and Z axes.  ''TTL Y=2'' sets a TTL pulse at the end of the move.  ''TTL T=51'' sets this report format.  The report will be a string of numbers like this (spaces for readability only)
  
-0002 0001 0003 1E00 FFFF FFFF FFFF FFEE FC81 0679 0D DF0F 0D+''0002 0001 0003 1E00 FFFF FFFF FFFF FFEE FC81 0679 0D DF0F 0D''
  
 where coordinate is (2,1) in the array, the X encoder value is 3268608 in decimal (corresponding to almost exactly 9mm position with 2 TPI rotary stage), Y encoder value is -1 in decimal, Z encoder value is -18 in decimal, CRISP error value is -895 in decimal, CRISP sum value is 1657 decimal, and the checksum is hex DF0F.  To validate the checksum add each of these 16-bit unsigned numbers (excluding the 0D delimeters) which results in 5FFFA in hex.  FFFA plus 5 is FFFF, and upon bitwise inversion the value becomes 0 as expected. where coordinate is (2,1) in the array, the X encoder value is 3268608 in decimal (corresponding to almost exactly 9mm position with 2 TPI rotary stage), Y encoder value is -1 in decimal, Z encoder value is -18 in decimal, CRISP error value is -895 in decimal, CRISP sum value is 1657 decimal, and the checksum is hex DF0F.  To validate the checksum add each of these 16-bit unsigned numbers (excluding the 0D delimeters) which results in 5FFFA in hex.  FFFA plus 5 is FFFF, and upon bitwise inversion the value becomes 0 as expected.
Line 227: Line 303:
  
 For MS2000/RM2000, the controller replies with the inverse polarity, <wrap reply> :A 1 </wrap> when the signal is low and <wrap reply> :A 0 </wrap> when the signal is high.  This is a logical bug in the firmware, but because it was in the field so long before being noticed we made the intentional decision to keep the behavior unchanged. For MS2000/RM2000, the controller replies with the inverse polarity, <wrap reply> :A 1 </wrap> when the signal is low and <wrap reply> :A 0 </wrap> when the signal is high.  This is a logical bug in the firmware, but because it was in the field so long before being noticed we made the intentional decision to keep the behavior unchanged.
 +\\
  
 {{tag>commands led tiger ms2000 tgled crisp ttl spim array servolock_ttl}} {{tag>commands led tiger ms2000 tgled crisp ttl spim array servolock_ttl}}
Address: 29391 W Enid Rd. Eugene, OR 97402, USA | Phone: +1 (541) 461-8181
commands/ttl.1746141379.txt.gz · Last modified: by brandon