Re: [Elecraft] K3S and FT8
To all who replied thanks. K8ZT solved it. I simply didn't have my bandwidth wide enough. As I thought, Pilot Error. Vy 73 de Bob DJ0RD/WU5T -Original Message- From: Bob DeHaney Sent: Saturday, June 16, 2018 12:34 To: 'elecraft@mailman.qth.net' Subject: K3S and FT8 Using K8ZT's K3S Setup I'm trying to get up and running in FT8. My problem is that when I use Data A mode I get no receive decode. If I switch to USB the signals start rolling down my computer screen. After this gets fixed, we'll see how transmit goes... Vy 73 de Bob DJ0RD/WU5T __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3S and FT8
Bob, that happened to me too when Data A was in the LSB mode. Put it back in Data A and hold down the “ALT” button, causing it to switch sidebands, and see if that fixes it. Very 73 - Mike - K9JRI > On Jun 16, 2018, at 6:33 AM, Bob DeHaney wrote: > > Using K8ZT's K3S Setup I'm trying to get up and running in FT8. My problem > is that when I use Data A mode I get no receive decode. If I switch to USB > the signals start rolling down my computer screen. After this gets fixed, > we'll see how transmit goes... > > Vy 73 de Bob DJ0RD/WU5T > > __ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to k9...@mac.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] K3S and FT8
Using K8ZT's K3S Setup I'm trying to get up and running in FT8. My problem is that when I use Data A mode I get no receive decode. If I switch to USB the signals start rolling down my computer screen. After this gets fixed, we'll see how transmit goes... Vy 73 de Bob DJ0RD/WU5T __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3S and FT8
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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to rmcg...@blomand.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3S and FT8
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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3S and FT8
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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3S and FT8
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 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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to n8...@brauhaus.org __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] K3S and FT8
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:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
