I guess you understand this behavior.
e.g. type ls<CR>
ex1) (char delay 1000ms), (local echo = off, remote echo = yes)...normal
| time | input | send | display(remote echo) |
| 0s | l | l | l |
| 0s | s | l | |
| 0s | <CR> | l | |
| 1s | s | ls | |
| 2s | <CR> | ls<CR> | |
| 2s | ls<CR><result of ls> |
ex2) (char delay 1000ms), (local echo = on, remote echo = no)... this issue
| time | input | send | display(local echo) |
| 0s | l | l | l |
| 0s | s | ls | |
| 0s | <CR> | ls<CR> | |
| 1s | s | ls<CR> | |
| 2s | <CR> | ls<CR> | |
| 2s | ls<CR><result of ls> |
ex3) (char delay 1000ms), (local echo = on, remote echo = yes)... exceptional?
| time | input | send | display(local and remote echo) |
| 0s | l | l | ll |
| 0s | s | lls | |
| 0s | <CR> | lls<CR> | |
| 1s | s | lls<CR>s | |
| 2s | <CR> | lls<CR>s<CR> | |
| 2s | lls<CR>s<CR><result of ls> |
Well, delay setting is named "Transmit delay", it delays only transmit. Do you hope also delay local echo?
Tera Term
when using the serial port setup-> transmit delay-> msec/line feature with local echo enabled, the local echo (and therefore logfile timestamps of the local echo) are not in sync with what is actually transmitted.
It looks like the transmit delay is correctly applied to the transmitted data, but the local echo is buffered in some way and so it will first update in a burst with no delay, then the delay will begin to be applied. if sending a file, then it reports the file as being finished before it has actually finished transmitting and data stops on the output serial port. For me the delay/buffer was approx. 4 seconds when sending lines of 18bytes with 100msec/line
I think it would be more useful if the local echo reflected when data was actually being sent, and It would be very helpful to me to be able to log and timestamp the time the data was actually sent.