[CoolTerm-Betas] Virtual terminal

[Roger Meier]

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? 




> 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/20221201/c5c81cc6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.png
Type: image/png
Size: 413542 bytes
Desc: not available
URL: <http://the-meiers.org/pipermail/coolterm-betas_the-meiers.org/attachments/20221201/c5c81cc6/attachment.png>