K3S and FT8
Locked
 
|
I've made a few QSOs with FT8 but have had less then stellar success. In
looking for possibly causes I took a close look at timing, since a lot of the chatter in the WSJT Yahoo group is about the need for close time synchronization. I noted that when my transmit interval occurred, there seemed to be about a one and a half second delay before the K3 began to transmit. I began an exchange of email with Bill, G4WJS, about this issue. I quote from one of his: "If you are seeing a 1.5s delay then that is because CAT commands sent before PTT, even if PTT is "virtual" due to using VOX, are taking roughly that long. The K3 series is problematic in that certain CAT commands can take a long time to complete, these are mostly mode change related, even if the mode does not actually change, as a DSP reset that takes 0.5s or so has to be completed before the CAT command returns success. I suggest setting "Settings->Radio->Mode" to "None" and setting the rig to USB-DATA-A sub-mode manually on both VFOs, as a test to see if things speed up for you." I tried his suggestion and didn't see much change, then I decided to turn off Split in the program. This reduced the apparent delay to <0.5 second. I say apparent because these are eyeball measurements, best made by looking at the clock display while listening for the TX audio to drop out. The message is 12.6 seconds long so if it ends at or around 13 seconds I would guess good enough. Anyone else see any of this? Wes, N7WS ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
Fake it just moves the A VFO before transmit (if needed) and back for receive.
The delays seem just a problematic. On 7/31/2017 12:32 PM, Daniel Brown wrote: > I saw the same thing when I had it set to split. I'll have to admit > though that my rig is an IC-7000, not a K3 (yet). > > Changed over to "fake it" for the split operation setting, and it > seems to do better, with faster xmits. > > > > On Mon, Jul 31, 2017 at 3:19 PM, Wes Stewart <[hidden email]> wrote: >> I've made a few QSOs with FT8 but have had less then stellar success. In >> looking for possibly causes I took a close look at timing, since a lot of >> the chatter in the WSJT Yahoo group is about the need for close time >> synchronization. >> >> I noted that when my transmit interval occurred, there seemed to be about a >> one and a half second delay before the K3 began to transmit. I began an >> exchange of email with Bill, G4WJS, about this issue. I quote from one of >> his: >> >> "If you are seeing a 1.5s delay then that is because CAT commands sent >> before PTT, even if PTT is "virtual" due to using VOX, are taking >> roughly that long. The K3 series is problematic in that certain CAT >> commands can take a long time to complete, these are mostly mode change >> related, even if the mode does not actually change, as a DSP reset that >> takes 0.5s or so has to be completed before the CAT command returns >> success. I suggest setting "Settings->Radio->Mode" to "None" and setting >> the rig to USB-DATA-A sub-mode manually on both VFOs, as a test to see >> if things speed up for you." >> >> I tried his suggestion and didn't see much change, then I decided to turn >> off Split in the program. This reduced the apparent delay to <0.5 second. I >> say apparent because these are eyeball measurements, best made by looking at >> the clock display while listening for the TX audio to drop out. The message >> is 12.6 seconds long so if it ends at or around 13 seconds I would guess >> good enough. >> >> Anyone else see any of this? >> >> Wes, N7WS >> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Wes Stewart-2
Hi Wes,
By a combination of trial and error personal preference, this is what I settled on as soon as I started with WSJT-X. I choose to NOT use split because I like to have the sub-RX down on the CW segment below 50.1 while I'm using the main RX with WSJT-X. The trial and error part was that I discovered that the K3 would not TX if I sent any commends to it from WSJT-X. SO -- I'm using DATA-A and VOX. I see the sub-second delay that you do. BTW -- I use VOX for ALL modes, CW, SSB, RTTY, and WSJT modes. No problems. 73, Jim K9YC On 7/31/2017 12:19 PM, Wes Stewart wrote: > I suggest setting "Settings->Radio->Mode" to "None" and setting > the rig to USB-DATA-A sub-mode manually on both VFOs ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
Freshly updated K3 by factory.
Yes, I know the VFO lnk is now a menu item… but: 1) use menu to turn VFO linking on. works as expected. Turning VFO A properly changes VFO B. 2) turn SUB ON. works as expected, can adjust VFO B separately, and then VFO A will move both properly. 3) Turn Diversity on ( Long press on on SUB ). VFO A and VFO B are no longer linked. Even after turning Diversity OFF, they are unlinked; checking COFNIG shows VFO LNK is OFF in config. the only way after using Diversity ON is to go into CONFIG meny to turn VFO LNK ON. What am I missing ? 73, de KU1T _zjt -- ******************************************************************** Zbigniew J. Tyrlik DoD# 0759 R1200GS IBA 31595 Free thinker, traveler, poet, happy father and husband.... point'n'click view of the world http://www.kleks.org/fotos/ ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Administrator
|
VFO A controls both receivers in diversity mode, but VFO B can be tuned separately. Typically it would be used as a holding register for another frequency of interest, or for the transmit frequency in SPLIT mode.
See the third paragraph on page 40 (under “Diversity Receive”). 73, Wayne N6KR > On Sep 21, 2017, at 6:17 PM, Zbigniew Tyrlik <[hidden email]> wrote: > > Freshly updated K3 by factory. > > > Yes, I know the VFO lnk is now a menu item… > > > but: > > 1) use menu to turn VFO linking on. > works as expected. Turning VFO A properly changes VFO B. > 2) turn SUB ON. > works as expected, can adjust VFO B separately, and then VFO A will move both properly. > > 3) Turn Diversity on ( Long press on on SUB ). > VFO A and VFO B are no longer linked. Even after turning Diversity OFF, they are unlinked; checking COFNIG shows VFO LNK is OFF in config. > the only way after using Diversity ON is to go into CONFIG meny to turn VFO LNK ON. > > What am I missing ? > > 73, de KU1T > _zjt > -- > ******************************************************************** > Zbigniew J. Tyrlik DoD# 0759 R1200GS IBA 31595 > Free thinker, traveler, poet, happy father and husband.... > point'n'click view of the world http://www.kleks.org/fotos/ > > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Wes Stewart-2
On 31/07/17 20:19, Wes Stewart wrote:
> I noted that when my transmit interval occurred, there seemed to be > about a one and a half second delay before the K3 began to transmit. I > began an exchange of email with Bill, G4WJS, about this issue. I quote > from one of his: > > "If you are seeing a 1.5s delay then that is because CAT commands sent > before PTT, even if PTT is "virtual" due to using VOX, are taking > roughly that long. The K3 series is problematic in that certain CAT > commands can take a long time to complete On 12/8/17, Bill G4WJS posted a message to the hamlib-developer list concerning a patch to k3.c to "Take out unnecessary delays in K(X)3(S) back end". This was incorporated into versions of hamlib subsequently distributed with WSJT-X. I've found that it greatly improved control of the K3S. So, use WSJT-X 1.8.0-rc2 or later, and use the version of hamlib/rigctl/rigctld distributed with it. 73, Richard G4DYA ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by wayne burdick
> On Sep 21, 2017, at 10:34 PM, Wayne Burdick <[hidden email]> wrote: > > VFO A controls both receivers in diversity mode, but VFO B can be tuned separately. Typically it would be used as a holding register for another frequency of interest, or for the transmit frequency in SPLIT mode. > > See the third paragraph on page 40 (under “Diversity Receive”). > Thank you very much for the replay.. but my question is - why entering and exiting Diversity does not restore initial state of VFO:LNK ? ( The CONFIG menu item, initialy set to ON, after one uses diversity receive is set to OFF ). Is it an intended side effect of turning DIversity ON ? With my limited experience, I’d expect that an ON-OFF transition does restore all affected configuration items to their initial values.. 73, de KU1T _zjt > 73, > Wayne > N6KR > > > > >> On Sep 21, 2017, at 6:17 PM, Zbigniew Tyrlik <[hidden email]> wrote: >> >> Freshly updated K3 by factory. >> >> >> Yes, I know the VFO lnk is now a menu item… >> >> >> but: >> >> 1) use menu to turn VFO linking on. >> works as expected. Turning VFO A properly changes VFO B. >> 2) turn SUB ON. >> works as expected, can adjust VFO B separately, and then VFO A will move both properly. >> >> 3) Turn Diversity on ( Long press on on SUB ). >> VFO A and VFO B are no longer linked. Even after turning Diversity OFF, they are unlinked; checking COFNIG shows VFO LNK is OFF in config. >> the only way after using Diversity ON is to go into CONFIG meny to turn VFO LNK ON. >> >> What am I missing ? >> >> 73, de KU1T >> _zjt >> -- >> ******************************************************************** >> Zbigniew J. Tyrlik DoD# 0759 R1200GS IBA 31595 >> Free thinker, traveler, poet, happy father and husband.... >> point'n'click view of the world http://www.kleks.org/fotos/ >> >> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > -- ******************************************************************** Zbigniew J. Tyrlik DoD# 0759 R1200GS IBA 31595 Free thinker, traveler, poet, happy father and husband.... point'n'click view of the world http://www.kleks.org/fotos/ ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Administrator
|
>> On Sep 21, 2017, at 10:34 PM, Wayne Burdick <[hidden email]> wrote:
>> >> VFO A controls both receivers in diversity mode, but VFO B can be tuned separately. Typically it would be used as a holding register for another frequency of interest, or for the transmit frequency in SPLIT mode. >> >> See the third paragraph on page 40 (under “Diversity Receive”). >> > > > Thank you very much for the replay.. > > but my question is - why entering and exiting Diversity does not restore initial state of VFO:LNK ? In the past we’ve had customers turn on VFO LNK because they thought they needed to use this in conjunction with diversity mode. Since VFO LNK was rarely used intentionally, we decided to just turn it off when coming out of diversity mode, since on average it was probably turned on unnecessarily. If you use linking a lot, you might consider using a programmable function switch to turn it on/off quickly. You can even set up a macro (using K3 Utility) to do several operations at once, e.g. turn on diversity, turn on linking, set VFO B = VFO A, select an antenna, turn the preamp on, etc. Macros can be very long. 73, Wayne N6KR ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
> On Sep 22, 2017, at 11:30 AM, Wayne Burdick <[hidden email]> wrote: > >>> On Sep 21, 2017, at 10:34 PM, Wayne Burdick <[hidden email]> wrote: >>> >>> VFO A controls both receivers in diversity mode, but VFO B can be tuned separately. Typically it would be used as a holding register for another frequency of interest, or for the transmit frequency in SPLIT mode. >>> >>> See the third paragraph on page 40 (under “Diversity Receive”). >>> >> >> >> Thank you very much for the replay.. >> >> but my question is - why entering and exiting Diversity does not restore initial state of VFO:LNK ? > > > In the past we’ve had customers turn on VFO LNK because they thought they needed to use this in conjunction with diversity mode. Since VFO LNK was rarely used intentionally, we decided to just turn it off when coming out of diversity mode, since on average it was probably turned on unnecessarily. > I see :-). > If you use linking a lot, you might consider using a programmable function switch to turn it on/off quickly. You can even set up a macro (using K3 Utility) to do several operations at once, e.g. turn on diversity, turn on linking, set VFO B = VFO A, select an antenna, turn the preamp on, etc. Macros can be very long. > Yep, that I will do. Just wanted to make sure that it was intentional, not a “feature”. Took me by surprise - consider mentioning it in manual.. but that the way it works ( Diversity turns the Link off ) is perfectly understandable, especially if that was creating some confusion. Thank you very much again, best to you and whole team ! > 73, > Wayne > N6KR 73, de KU1T _zjt -- ******************************************************************** Zbigniew J. Tyrlik DoD# 0759 R1200GS IBA 31595 Free thinker, traveler, poet, happy father and husband.... point'n'click view of the world http://www.kleks.org/fotos/ ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Richard Lamont
I'm using WSJT-X verson 1.8.0-rc2 with CAT control and having no
issues. Nothing exotic in my configuration, just using the single USB cable between the laptop computer and the radio. I allow WSJT-X to log the contact and then I export the generated ADI file to my LOTW and QRZ.COM logs. I've almost completed my WAS using FT-8 mode on 6 meters. Plus I've worked a lot of DX on other bands. I find it is a fun, fast and very easy mode to make contacts. Of course, if you are in to "rag chewing", forget it. It is not a rag chew mode. 73 Bob, K4TAX On 9/22/2017 2:48 AM, Richard Lamont wrote: > On 31/07/17 20:19, Wes Stewart wrote: > >> I noted that when my transmit interval occurred, there seemed to be >> about a one and a half second delay before the K3 began to transmit. I >> began an exchange of email with Bill, G4WJS, about this issue. I quote >> from one of his: >> >> "If you are seeing a 1.5s delay then that is because CAT commands sent >> before PTT, even if PTT is "virtual" due to using VOX, are taking >> roughly that long. The K3 series is problematic in that certain CAT >> commands can take a long time to complete > On 12/8/17, Bill G4WJS posted a message to the hamlib-developer list > concerning a patch to k3.c to "Take out unnecessary delays in K(X)3(S) > back end". This was incorporated into versions of hamlib subsequently > distributed with WSJT-X. I've found that it greatly improved control of > the K3S. > > So, use WSJT-X 1.8.0-rc2 or later, and use the version of > hamlib/rigctl/rigctld distributed with it. > > 73, > Richard G4DYA > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |