Differences

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

--- tiger_ms2k_difference [2024/10/24 16:28] – [Special "All-Axis" Letter] jon
+++ tiger_ms2k_difference [2026/09/01 15:51] (current) – [A Note Regarding Units] fix MOVEREL -> MOVREL brandon
@@ Line 64: / Line 64: @@
 ===== Addresses beyond 0-9 =====
-Addresses 0x81 to 0xF5 have been reserved for Tiger cards.  Comm card firmware prior to v3.42 only allows addresses '1'-'9' to be accessed.  Comm card firmware v3.42 allows addresses '1' - '9' as well as hex 0x81 - 0x86, which is as many cards as can fit into a single Tiger controller.  (Note that controllers can be daisy-chained if required, but we'll do that when a customer needs it...)
+Comm card firmware prior to v3.42 only allows addresses '1' - '9' to be accessed, which is hex 0x31 - 0x39.  Beginning with comm card firmware v3.42 you can use addresses '1' - '9' as well as addresses hex 0x81 - 0x86, which is as many cards as can fit into a single Tiger controller.  (Note that controllers can be daisy-chained if required, and ASI can extend further the accessible range when a customer needs it.)
-It can be tricky to interact with addresses 0x81 and above because they are not ASCII characters.  If you can send the appropriate non-ASCII character through your control software, prepending card-addressed commands with that character, then nothing else is needed: the controller will correctly interpret those non-ASCII character as addresses.  However, provision was added in comm card firmware v3.42 to allow easy access to this extended address space sending only ASCII characters: if you enter the back-tick character at the start of a command '`' then the next 2 characters are interpreted as hexadecimal values for the address.  For example, to query the configuration of address '4' = 0x34 you can either issue ''4 CCA X?'' or you can equivalently send ''`34 CCA X?''.  For address 0x81 you can send ''`81 CCA X?''.
+It can be tricky to interact with addresses 0x81 and above because the address is not an ASCII characters.  If you can send the appropriate non-ASCII character through your control software, prepending card-addressed commands with that character, then nothing else is needed: the controller will correctly interpret those non-ASCII character as addresses.  However, provision was added in comm card firmware v3.42 to allow easy access to this extended address space sending only ASCII characters: if you enter the back-tick character at the start of a command '`' then the next 2 characters are interpreted as hexadecimal values for the address.  For example, to query the configuration of address '4' = 0x34 you can either issue ''4 CCA X?'' or you can equivalently send ''`34 CCA X?''.  For address 0x81 you can send ''`81 CCA X?''.
 ===== Table 1 TG-1000 Addresses =====
@@ Line 129: / Line 129: @@
 == Axis Properties ==
-|Bit 0:	|CRISP auto-focus firmware                         |
+|Bit 0:	|''CRISP'' autofocus firmware                         |
-|Bit 1:	|RING BUFFER firmware                              |
+|Bit 1:	|''RING BUFFER'' firmware                              |
-|Bit 2:	|SCAN firmware                                     |
+|Bit 2:	|''SCAN'' firmware                                     |
-|Bit 3:	|ARRAY firmware or MM_TARGET firmware              |
+|Bit 3:	|''ARRAY'' firmware or ''MM_TARGET'' firmware              |
-|Bit 4:	|SPIM firmware (v2.81+)                            |
+|Bit 4:	|''SPIM'' firmware <wrap lo>v2.82</wrap>              |
-|Bit 5:	|SINGLEAXIS and/or MULTIAXIS firmware (v2.81+)     |
+|Bit 5:	|''SINGLEAXIS'' and/or ''MULTIAXIS'' firmware <wrap lo>v2.82</wrap> |
-|Bit 6:	|LED illumination (v2.87+)                         |
+|Bit 6:	|''LED'' illumination <wrap lo>v2.88</wrap>            |
 |Bit 7:	|Reserved                                          |
@@ Line 161: / Line 161: @@
 ==== A Note Regarding Units ====
-The most common commands including ''MOVE'', ''MOVEREL'', ''HERE'', and ''WHERE'' use axis units, which can be changed using the ''UM'' command.  However, some commands such as ''SETUP'', ''SETLOW'', and ''PCROS'' always use units of mm.  By default, axis units where position is given in distance (e.g. for motorized stages and piezo stages) are represented in 0.1um increments, or 10,000 units per millimeter of travel.  For mirror scanner axes, default axis units are 0.001 degrees (uncalibrated), or 1000 units per degree of travel.  When a time is required, the unit is generally milliseconds.  Some commands use integer codes or other input units as described below.
+The most common commands including ''MOVE'', ''MOVREL'', ''HERE'', and ''WHERE'' use axis units, which can be changed using the ''UM'' command.  However, some commands such as ''SETUP'', ''SETLOW'', and ''PCROS'' always use units of mm.  By default, axis units where position is given in distance (e.g. for motorized stages and piezo stages) are represented in 0.1um increments, or 10,000 units per millimeter of travel.  For mirror scanner axes, default axis units are 0.001 degrees (uncalibrated), or 1000 units per degree of travel.  When a time is required, the unit is generally milliseconds.  Some commands use integer codes or other input units as described below.
 {{tag>serial commands manual tiger tech_note}}

Address: 29391 W Enid Rd. Eugene, OR 97402, USA | Phone: +1 (541) 461-8181