[CoolTerm-Betas] Virtual terminal
Roger Meier
roger.meier at pobox.com
Fri Dec 2 16:19:48 EST 2022
Thanks for the step to reproduce this. I will try this over the weekend.
Meanwhile, do you know if the virtual device ptyw0 requires any type of
flow control? CoolTerm sends data in larger chunks in Line Mode and when
sending text files (as defined by the "Packet Size" option under "Transmit
Options"). I wonder if perhaps ptyw0 can't handle more than one character
at the time. Can you try the following:
- Enable the "Use transmit character delay" feature under the "Transmit
Options" and play around with the delay (3ms by default) to see if it
starts working with certain values.
Roger
On Thu, Dec 1, 2022 at 11:16 PM Franzi Edo. <edo.franzi at ukos.ch> wrote:
> Hi Roger,
> Thank you for your preliminary investigation.
> Try this:
>
> 1. open a unix terminal on your Mac
> 2. type: screen /dev/ttyw0 460800
> 3. Now open CoolTerm
> 4. Select the device /dev/ptyw0
> 5. Connect
>
> Mode Raw in CoolTerm
> - Everything you type in the screen (unix terminal) is displayed on
> CoolTerm;
> This is OK
> - Everything you type in the CoolTerm is displayed on the screen (unix
> terminal);
> This is OK
> - In ColTerm I try to send a text file (Send Text/Binary files). CoolTerm
> send only 1 char;
> This is not OK
>
> Mode Line in CoolTerm
> - Everything you type in the screen (unix terminal) is displayed on
> CoolTerm;
> This is OK
> - Everything you type in the CoolTerm is NOT completely displayed on the screen
> (unix terminal) after the CR;
> It is displayed only the first character; this is not OK
> - In ColTerm I try to send a text file (Send Text/Binary files). CoolTerm
> send only 1 char;
> This is not OK
>
> Any idea?
> I noticed that for your test you opened /dev/ttys001. On my machine I
> cannot use this device.
> The CoolTerm I use is the latest beta V2.0.1b3
>
> BR
> Edo
>
>
> On 2 Dec 2022, at 03:39, Roger Meier <roger.meier at pobox.com> wrote:
>
> Hmm, that’s weird. I’m connected to a virtual device and communicating in
> line mode just fine (see screenshot below). What is it exactly that isn’t
> working for you?
>
> <PastedGraphic-1.png>
>
>
> On Nov 30, 2022, at 5:00 AM, Franzi Edo. <edo.franzi at ukos.ch> wrote:
>
> Hi Roger,
> You have understood correctly.
> I am aware that the receiver needs more work.
> Finally, I have written my code ;-)
> By chance, you have implemented what I have suggested time ago (the
> virtual ports /dev/ttyw0… etc).
> I have just written a Unix tool that intercepts the communication and
> dispatches them to the CoolTerm windows.
> It works like a charm …
>
> Maybe just a question:
> I noticed that when I select a virtual channel on CoolTerm (i.e.
> /dev/ptyw0), I can use only the "Raw Mode" and not the "Line Mode” (in the
> menu Terminal Mode).
> Is it a bug or it is a technical issue?
>
> Anyway, thank you for the implementation of the virtual devices :-)
> Regards,
> Edo
>
>
>
> On 28 Nov 2022, at 20:23, Roger Meier <roger.meier at pobox.com> wrote:
>
> Hi Edo,
>
> Let me make sure I correctly understand the concept you are describing:
> - You have an embedded target with a single UART
> - You create multiple virtual ports on your computer that are all bridged
> to the physical UART on the target
> - You open multiple CoolTerm windows, each one connected to one of the
> virtual ports
> - This allows you to send data to the target from the different CoolTerm
> windows
> - You want the data sent from each CoolTerm window to be send with a
> different specific header string in front of the data and a specific footer
> string at the and of the data so that the target knows who sent the data.
>
> Am I understanding this correctly?
>
> Assuming this is what you are requesting, then I have good news for you. I
> have a feature on my list of future enhancements that will allow the user
> to prefix and suffix any sent data with macros they defined. So, for your
> case you could create two macros “+++0” and “---0” in the first CoolTerm
> window and have any send date prefixed and suffixed with these macros. Then
> for the 2nd CoolTerm window, you would define your macros like this: “+++1”
> and "---1”, and so on for other CoolTerm windows. The macros are saved with
> the connection setting for each CoolTerm window, so you only have to set
> this up once for each CoolTerm window.
> I don’t know when I will have an opportunity to implement this. The
> earliest to expect this would probably be v2.1.0. I’m currently wrapping up
> 2.0.1.
>
> This would take care of the transmission side of what you’re after.
> However, I don’t currently have any plans to support the receive side of
> your request. I assume that anything your target sends back is received in
> all the connected CoolTerm windows, correct? And you want for each CoolTerm
> window to recognize the data based on the correct header and footer strings
> and ignore any data that is intended for a different CoolTerm window?
>
> I’m afraid this is beyond the scope of the CoolTerm development. However,
> as you may know, CoolTerm is fully scriptable. The easiest way to script
> CoolTerm is with Python using the CoolTerm.py module that is included in
> the download. This lets you control multiple windows very easily. It should
> be pretty easy to implement the functionality you seek this way.
>
> Regards,
>
> Roger
>
>
> On Nov 27, 2022, at 1:56 AM, Franzi Edo. <edo.franzi at ukos.ch> wrote:
>
> Hi all,
> Maybe a very useful functionality to add to CoolTerm.
> On the embedded targets, often we have only 1 physical uart. The idea is
> to let CoolTerm to open more terminal sessions and encapsulate/decapsulate
> the messages sent/received on the physical uart.
> Ex.
> CoolTerm on Virtual com 1 managed by the Window 1: send “message xyz”
> CoolTerm on Virtual com 2 managed by the Window 2: send “lalala”
> CoolTerm on Virtual com 3 managed by the Window 3: send “okokokok”
>
> These messages have to be encapsulated with a programmable header/footer
> before the sending on a selected physical uart.
> So, CoolTerm should operate in this way for sending all the messages
> Example of header/footer +++0 ---0
>
>
> +++0message xyz---0+++1lalala---1+++3okokokok---3 sent on the uart
>
> At the target level is then easy to decapsulated the messages and use them
> in the appropriate environments.
>
> Of course, the opposite (from the target to the CoolTerm uses the same
> mechanism).
> What do you think?
> BR
> Edo
>
>
> _______________________________________________
> CoolTerm-Betas mailing list
> CoolTerm-Betas at the-meiers.org
> http://the-meiers.org/mailman/listinfo/coolterm-betas_the-meiers.org
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://the-meiers.org/pipermail/coolterm-betas_the-meiers.org/attachments/20221202/f90ba100/attachment.htm>
More information about the CoolTerm-Betas
mailing list