Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Local Echo #38

Open
sk-jame opened this issue Jul 29, 2024 · 12 comments
Open

Feature request: Local Echo #38

sk-jame opened this issue Jul 29, 2024 · 12 comments

Comments

@sk-jame
Copy link

sk-jame commented Jul 29, 2024

Hello, I think that very important feature is missing - local echo. I don't think it should be explained, it is well known interface. So just wanna mention that it would be great to have it here.

@lefebvresam
Copy link

I have the same question

@salvathor79
Copy link

@sk-jame @lefebvresam
Please see my pull request, I've just added this feature: #42

@lefebvresam
Copy link

When it's available in the installer?

@salvathor79
Copy link

@lefebvresam I've uploaded a new version here
v0.9.0

@lefebvresam
Copy link

lefebvresam commented Oct 28, 2024

What also should be a nice to have is that you can add an arbitrary sequence when pressing enter. Because some command interpreters expect that you end a command sentence with for instance 0xFF0xFF0xFF.

@salvathor79
Copy link

@lefebvresam
v0.9.1
In this version you can specify a custom string, the string is sent as-is. So no escape character or 0x... format value.

@lefebvresam
Copy link

Can you escape them, or use hex values? I want to send 0xFF0xFF0xFF for each string termination.

@salvathor79
Copy link

v0.9.2

@lefebvresam now it's possible to specify a custom sequence of bytes to be sent on carriage return

@lefebvresam
Copy link

But how do you enter 0xFF0xFF0xFF? As ÿÿÿ?

@salvathor79
Copy link

salvathor79 commented Nov 17, 2024

In the new version (v0.9.2) you can simply add the option --tx:bytes="0xFF0xFF0xFF" or --tx:bytes="FFFFFF" or --tx:bytes="FF FF FF" or --tx:bytes="0xFF 0xFF 0xFF" as you prefer.

note: --tx is the short form of --tx_newline option

@lefebvresam
Copy link

lefebvresam commented Nov 17, 2024

I use this which is working:

ss -com:COM4 -echo:ON -tx:bytes="FFFFFF" -encoding:RAW -baud:120000

But with the sniffer I see that every character is sent immedately after entering it.
When you have one char wrong you need te retype the whole line.
There is also a wait time between characters in my application before getting a timeout.
Should it be possible to send the whole line + termination only after pressing enter?
In that case it will be possible to edit the line before sending long strings.
Then it's more like a real terminal.

Thanks in advance.

@salvathor79
Copy link

salvathor79 commented Nov 29, 2024

@lefebvresam what you are asking is technical feasible, but this apparently simple modification is against the nature of Simply Serial that is a TERMINAL CONSOLE. In all terminal console programs like Simply Serial (i.e. Teraterm or Putty) each character is transmitted immediatelly, what you are asking is more a "serial tool" like Realterm or YAT.

If you want to correct keyboard mistakes, you can implement it in your application: simply upon receiving the char '\b', that is the backspace characters in C, you should remove the last char received before '\b' from the received string. Obviously this is only feasibile if you don't use any command that can contains the '\b' char :-)

There are a lot more that you can do with escape sequence with a VT100 ANSI terminal like windows terminal and SimplySerial https://en.wikipedia.org/wiki/ANSI_escape_code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants