[WT-support] Serial communication log available?

Jan R Andersson jan.andersson at microbit.se
Wed Mar 9 11:49:45 CET 2016


Hi Larry,

And thank you for that information! Most useful!

What I see is this in the COMxx_debug.txt file is data only going out from
Win-Test, not in: (Only "->" and no "<-")

2016/03/09-10:36:26: Initializing COM port #10: 38400 3-0-0
2016/03/09-10:36:26: -> FA;
2016/03/09-10:36:26: -> FB;
2016/03/09-10:36:27: -> IF;
2016/03/09-10:36:27: -> FB;
2016/03/09-10:36:28: -> IF;
2016/03/09-10:36:28: -> FB;
2016/03/09-10:36:29: -> IF;
2016/03/09-10:36:29: -> FB;
2016/03/09-10:36:30: -> IF;
2016/03/09-10:36:30: -> FB;
2016/03/09-10:36:30: -> MD2;
2016/03/09-10:36:30: -> FA00014166000;
2016/03/09-10:36:30: -> MD2;
2016/03/09-10:36:30: -> FT0;
2016/03/09-10:36:30: -> IF;
2016/03/09-10:36:31: -> FB;
2016/03/09-10:36:31: -> IF;

But a Serial Port Monitor program I have shows data going in both
directions:

[09/03/2016 11:36:26] Written data (COM10) 
    46 41 3b 46 42 3b                                 FA;FB;           
[09/03/2016 11:36:27] Read data (COM10) 
    49 46 30 30 30 31 34 31 38 34 36 37 30 20 20 20   IF00014184670    
    20 20 2d 30 30 30 30 30 30 20 30 30 30 32 30 30     -000000 000200 
    30 30 30 31 20 3b 49 46 30 30 30 31 34 31 38 34   0001 ;IF00014184 
    36 37 30 20 20 20 20 20 2d 30 30 30 30 30 30 20   670     -000000  
    30 30 30 32 30 30 30 30 30 31 20 3b 46 41 30 30   0002000001 ;FA00 
    30 31 34 31 38 34 36 37 30 3b 46 42 30 30 30 31   014184670;FB0001 
    34 31 39 33 30 34 30 3b 49 46 30 30 30 31 34 31   4193040;IF000141 
    38 34 36 37 30 20 20 20 20 20 2d 30 30 30 30 30   84670     -00000 
    30 20 30 30 30 32 30 30 30 30 30 31 20 3b 49 46   0 0002000001 ;IF 
    30 30 30 31 34 31 38 34 36 37 30 20 20 20 20 20   00014184670      
    2d 30 30 30 30 30 30 20 30 30 30 32 30 30 30 30   -000000 00020000 
    30 31 20 3b 49 46 30 30 30 31 34 31 38 34 36 37   01 ;IF0001418467 
    30 20 20 20 20 20 2d 30 30 30 30 30 30 20 30 30   0     -000000 00 
    30 32 30 30 30 30 30 31 20 3b 49 46 30 30 30 31   02000001 ;IF0001 
    34 31 38 34 36 37 30 20 20 20 20 20 2d 30 30 30   4184670     -000 
    30 30 30 20 30 30 30 32 30 30 30 30 30 31 20 3b   000 0002000001 ; 
[09/03/2016 11:36:27] Written data (COM10) 
    49 46 3b                                          IF;              
[09/03/2016 11:36:27] Read data (COM10) 
    49 46 30 30 30 31 34 31 38 34 36 37 30 20 20 20   IF00014184670    
    20 20 2d 30 30 30 30 30 30 20 30 30 30 32 30 30     -000000 000200 
    30 30 30 31 20 3b 49 46 30 30 30 31 34 31 38 34   0001 ;IF00014184 
    36 37 30 20 20 20 20 20 2d 30 30 30 30 30 30 20   670     -000000  
    30 30 30 32 30 30 30 30 30 31 20 3b 49 46 30 30   0002000001 ;IF00 
    30 31 34 31 38 34 36 37 30 20 20 20 20 20 2d 30   014184670     -0 
    30 30 30 30 30 20 30 30 30 32 30 30 30 30 30 31   00000 0002000001 
    20 3b                                              ;               

The Com port's status signals are the same when using either a virtual USB
com port provided by the Remoterig device or a physical com port in the PC.
The physical Com port works ok, the virtual seems not to be able to deliver
data from the radio/Remoterig device to Win-Test.

What do you make of that?

Jan

-----Original Message-----
From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On
Behalf Of Laurent HAAS - F6FVY
Sent: den 8 mars 2016 15:32
To: support at win-test.com
Subject: Re: [WT-support] Serial communication log available?

Hi Jan

Le 08/03/2016 10:18, Jan R Andersson a écrit :

> So I am wondering if there is some kind of serial communication log 
> available in Win-Test that could help understand this?
> Or some other log file which might contain clues as to why this happens?

Create a [Debug] section in the wt.ini file, and a key following this syntax
:

[Debug]
COMxx=a

or

COMxx=h

a = ASCII / h = Hex and xx is obviously the COM port number.

A "debug log" will be written in the /cfg directory.

Regarding your specific issue, as it is working with "legacy" serial, but
not with USB, I'm wondering if it could come from some handshake settings
that could block the stream somewhere.

Hope this helps.

73

Larry - F6FVY

--
Remember Jan. 7 2015 - #JeSuisCharlie
Remember Nov. 13 2015 - #JeSuisParis
_______________________________________________
Support mailing list
support at win-test.com
http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support



More information about the Support mailing list