commands:build

# Differences

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

 commands:build [2018/02/07 22:16]jon commands:build [2019/04/18 23:33] (current) Both sides previous revision Previous revision 2018/06/21 16:06 jon 2018/02/07 22:16 jon 2016/09/07 22:29 asiadmin ↷ Links adapted because of a move operation2016/09/07 22:03 asiadmin ↷ Page moved from documentation:commands:build to commands:build2016/03/14 23:41 vik 2016/03/14 23:39 vik 2016/03/14 23:21 vik 2016/03/14 23:21 vik 2016/03/14 23:19 vik 2016/03/14 23:18 vik created Next revision Previous revision 2018/06/21 16:06 jon 2018/02/07 22:16 jon 2016/09/07 22:29 asiadmin ↷ Links adapted because of a move operation2016/09/07 22:03 asiadmin ↷ Page moved from documentation:commands:build to commands:build2016/03/14 23:41 vik 2016/03/14 23:39 vik 2016/03/14 23:21 vik 2016/03/14 23:21 vik 2016/03/14 23:19 vik 2016/03/14 23:18 vik created Line 1: Line 1: + ====== Command:​BUILD (BU) ====== + --> MS2000 or RM2000 syntax# + + ^Shortcut ​ |BU| + ^Format ​ |BUILD [X]| + ^Units ​   |none| + + <-- + + --> Tiger syntax# ​ + + ^Shortcut ​ |BU| + ^Format ​ |[Addr#​]BUILD [X]| + ^Units ​   |none| + ^Type    |Card-Addressed(defaults to COMM)| + + <-- + + This command returns the firmware “Build” version. ​ BU X shows various configuration options and build-modules that are present in the firmware. ​ + + --> Additional Feature on Tiger# + + Adding the card address is optional. If no address is given, then Tiger Comm replies. If an address is present, then the specified card replies. ​ + + $BU + TIGER_COMM​ + +$ BU X + TIGER_COMM + Motor Axes: X Y A B C C 0 1 + Axis Types: x x u u u u w w + Axis Addr: 1 1 2 2 2 2 3 3 + Hex Addr: 31 31 32 32 32 32 33 33 + Axis Props: ​  ​0 ​  ​0 ​  ​0 ​  ​0 ​  ​0 ​  ​0 ​  ​0 ​  ​0​ + + As no address was given, Tiger Comm replies. It replies with its build name, all axis names present in the system (axes will always be A-Z, filterwheels 0-9). For each axis the type is given (see table in section “Identifying Controller Configuration”) and the card address in both character and hex formats. ​ Finally, an integer is given to indicate the presence of special properties or capabilities of the axis, such as CRISP auto-focus or RING BUFFER module for TTL positioning;​ these can be interpreted using the information below. ​ This command is useful to quickly identify all the axes names and types present in the system. + + <-- + + == Example == + + --> Tiger Example# + + $1bu + STD_XY​ + +$ 1bu x + STD_XY + Motor Axes: X Y + Axis Types: x x + Axis Addr: 1 1 + Hex Addr: 31 31 + Axis Props: ​  ​0 ​  0 + CMDS: XY + BootLdr V:NONE + LL COMMANDS + SEARCH INDEX + NO CLTCH SW + SHUTDOWN_TASK​ + + With an address 1 given, the specified card #1 replies. This reply just contains axis name and types present on the card. However it goes into more detail, printing all the firmware modules present on the card. + + The values listed for axis properties are decimal integer representations of a binary code which represents any special properties of the axis.  Usually these could also be identified by doing a BU X query of each card and interpreting the response, but they are listed separately on the axis property line for convenience. + + + + <-- + + --> MS2000 Example# + + BU X ​ \\ + STD_XYZ ​ shows that the firmware build was for a Standard XYZ system \\ + Motor Axes: X Y Z ​ shows axis names for motor axes \\ + Axis Types: x x z  ​ shows axis type for each of axis (see table below) (9.2c+) \\ + CMDS: XYZFTR ​ shows argument names pseudo-axis commands \\ + BootLdr V:0 ​ shows version of boot-loader program \\ + Hdwr REV.E ​ shows main-board hardware revision \\ + LL COMMANDS ​ list of optional firmware modules present \\ + RING BUFFER ​ … \\ + SEARCH INDEX ​ … \\ + IN0_INT ​ … \\ + DAC OUT ​ \\ + + + <-- + + {{page>:​tiger_ms2k_difference#​Axis Properties}} + + {{page>:​tiger_ms2k_difference#​Axis Type List}} + + {{tag>​commands tiger ms2000}}