Hi Bill,
Yes, Mike clarified the reason for that particular heartbeat in his last
message and thank you for that.
HI Mike: I downloaded the latest DLL and replaced the current one in the bin
folder and the results were the same. The previous test was done with a
replacement DLL that I downloaded on 11/12. In hope to mitigate the behavior
that I noticed with the original DLL that was installed with WSJT-X Ver 2.5.2
on 11/04 with the DLL dated 11/03.
One other point if you gentlemen allow me, I don't see where WSJT-X ascertain
which VFO A or B is current set to being used for RX and TX and/or If Split is
already set in the radio.
// Prepare for TX Cycle
00816 12:23:30:040 : >>: IF;00817 12:23:30:045 : <: IF00007074000
-006200000020010080;00818 12:23:30:046 : <<: IF00007074000
-006200000020010080;00819 12:23:30:050 : >>: FB;00820 12:23:30:052 : <:
FB00007074500;00821 12:23:30:053 : <<: FB00007074500;00822 12:23:30:056 : >>:
FR0;00823 12:23:30:056 : >>: FT1; // Split Turned On 00824
12:23:30:057 : >>: ID;00825 12:23:30:081 : <: ID021;00826 12:23:30:082 : <<:
ID021;00827 12:23:30:099 : >>: FT0; // Split Turned Off00828
12:23:30:099 : >>: ID;00829 12:23:30:099 : <: ID021;00830 12:23:30:099 : <<:
ID021;00831 12:23:30:130 : >>: FR1; // Split Turned On in reverse
00832 12:23:30:130 : >>: ID;00833 12:23:30:137 : <: ID021;00834 12:23:30:137 :
<<: ID021;00835 12:23:30:168 : >>: FT1; // Split Turned Off00836
12:23:30:168 : >>: ID;00837 12:23:30:168 : <: ID021;00838 12:23:30:168 : <<:
ID021;00839 12:23:30:200 : >>: MD;00840 12:23:30:200 : <: MD2;00841
12:23:30:200 : <<: MD2;00842 12:23:30:231 : >>: DA;00843 12:23:30:231 : <:
DA1;00844 12:23:30:231 : <<: DA1;00845 12:23:30:269 : >>: MD2;00846
12:23:30:269 : >>: ID;00847 12:23:30:269 : <: ID021;00848 12:23:30:269 : <<:
ID021;00849 12:23:30:300 : >>: DA1;00850 12:23:30:300 : >>: ID;00851
12:23:30:300 : <: ID021;00852 12:23:30:300 : <<: ID021;00853 12:23:30:331 : >>:
FR0; // Split Turned On - Back to normal 00854 12:23:30:331 : >>:
FT1;00855 12:23:30:331 : >>: ID;00856 12:23:30:353 : <: ID021;00857
12:23:30:353 : <<: ID021;
// Start TX Cycle 00858 12:23:30:385 : >>: TX1;
Sam W2JDB
-----Original Message-----
From: Bill Somerville via wsjt-devel <wsjt-devel@lists.sourceforge.net>
To: wsjt-devel@lists.sourceforge.net
Cc: Bill Somerville <g4...@classdesign.com>
Sent: Tue, Nov 16, 2021 10:16 am
Subject: Re: [wsjt-devel] VFOs reversing
Sam,
you have not understood my comments and the reason for the dummy command,
please read my explanation again.
73
Bill
G4WJS.
On 16/11/2021 15:00, Sam W2JDB via wsjt-devel wrote:
Hi Bill,
Any invalid command will result in a '?;' response, even a SET command. i.e.
if you send 'AC000' and the tuner is already in a 'AC000' state in reply to
'AC;' command, you will get a '?;' response. I used that example because I
ran into that problem and it took me a while to figure why/where that was
coming from.
73, Sam W2JDB
-----Original Message-----
From: Bill Somerville via wsjt-devel <wsjt-devel@lists.sourceforge.net>
To: wsjt-devel@lists.sourceforge.net
Cc: Bill Somerville <g4...@classdesign.com>
Sent: Tue, Nov 16, 2021 9:26 am
Subject: Re: [wsjt-devel] VFOs reversing
On 16/11/2021 14:07, Sam W2JDB via wsjt-devel wrote:
> I also wondering about the multiple
> 'ID' requests, is that your version of heartbeat ? Just wondering.
Hi Sam,
the Kenwood protocol does not respond to CAT commands that set things,
so there is a problem with reading any invalid response ('?') since we
have no way of knowing how long to wait for a response which may never
come. Hamlib gets around this ambiguity with a simple device, after CAT
commands that do not elicit a reply when they work, a basic command that
does elicit a reply is sent. Then we can read a reply and either get the
command failed reply (and discard the expected reply), or the expected
reply from the second command. This simple technique means that CAT
commands can proceed without any wait time, despite extra traffic being
sent.
Other CAT protocols are more robust and always send either an ACK or
NACK response to all commands, so with them there is no ambiguity.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
