Version Differences for Menu Commands

(→Details:)
(→Details:)
Line 46:
  |-    |- 
  |}    |} 
-      
- *1: It is possible to send multiple command IDs between a single header and terminator, except for a single command (1-digit) IDs.      
       
    + <br />  
    + *1): It is possible to send multiple command IDs between a single header and terminator, except for a single command (1-digit) IDs.  
       
  **Input examples:    **Input examples: 
  ***1-digit command : <Esc>?<CR>?     ***1-digit command : <Esc>?<CR>?  
Line 57:
  <br />    <br /> 
       
- *(2) Command Usage Precautions   + *2): Command Usage Precautions  
  ** When sending multiple commands in a sequence, the subsequent command is not received while the previous command is still being executed. Since the RTS output will be in busy state while a command is executed when the Handshake is set to BUSY/READY or MODEM, it is recommended to refer to this signal for the right timing.    ** When sending multiple commands in a sequence, the subsequent command is not received while the previous command is still being executed. Since the RTS output will be in busy state while a command is executed when the Handshake is set to BUSY/READY or MODEM, it is recommended to refer to this signal for the right timing. 
  ** Any settings configured by commands are not retained in the nonvolatile memory. Therefore, these will be lost when the scan engine power is turned off. When the power comes back on, the scan engine will be in the configuration state saved in the nonvolatile memory. In order to save the settings with commands, send “Z2” to save all the parameters in nonvolatile memory.    ** Any settings configured by commands are not retained in the nonvolatile memory. Therefore, these will be lost when the scan engine power is turned off. When the power comes back on, the scan engine will be in the configuration state saved in the nonvolatile memory. In order to save the settings with commands, send “Z2” to save all the parameters in nonvolatile memory.