Re: [wsjt-devel] F/H mode in wrong period
Yes, 3Y0J had this problem while their DT was within limits. And indeed some clever op's managed to work them. Is it possible that these op's used MSHV to match the wrong period? 73, Ton pa0tbr On Mon, 10 Apr 2023 at 14:44, William Smith via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Wasn’t there a dxpedition recently that inadvertently had their clocks off > by 13 (?) seconds, and no one could work for them because they looked like > they were on the “wrong“ period? > > A few people were able to work around the limitations above, or set their > own clocks off by an equivalent amount, and were able to work them. > > So Murphy will always stick his nose in, and there’s almost always a > workaround. > > 73, Willie N1JBJ > > On Apr 10, 2023, at 7:13 AM, Alan McDonald via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > And for additional clarity - something many OP may not try. If you try to > switch to Fox mode on a std frequency, you will be met with this popup > > > > > You will not be able to TX in until you switch back to Normal mode or > change to a non-std frequency. > Alan > > On Mon, 10 Apr 2023 at 20:27, 5p1kzx Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Hi Ton >> >> Those msg for different stations in a single stream and on the same time >> is mandatory for FT8DX Mode (WSJT-X F/H) but they can also be made by the >> MSHV Software and if a Station is TXing on the 15/45 periode and send out >> those msg for different station it can't be WSJT-X and it's not the real >> FT8DX Mode. A station in real Fox/Hound Mode (FT8DX) can't TX on 15/45 >> periode and can't on a standard FT8 QRG. A real Fox/Hound Station will >> always in TX 00/15 periods and always on a non-standard FT8 QRG. So if the >> DX-station is wringting somewhere that he or they will work on F/H mode on >> a standard FT8 QRG it cant be. That will be MSHV MADX (Multi-Slot) Mode >> witch is Pseudo Fox/Hound Mode - It looks like F/H Mode and it acts like >> F/H Mode but it ain't the real thing. >> >> 73 de 5p1kzx Michael >> >> >> Den 10-04-2023 kl. 10:28 skrev Ton PA0TBR via wsjt-devel: >> >> The messages had different reports for different stations in a single >> stream., my understanding is that this must be WJST-X F/H.. >> Please correct me if i am wrong. >> >> 73, Ton pa0tbr >> >> >> Op zo 9 apr. 2023 om 15:06 schreef Reino Talarmo via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> >> >>> And they are using the ”wrong” period on purpose an politely so that >>> you see immediately that the normal FT8 should be used by “hounds”. >>> >>> 73, Reino OH3mA >>> >>> >>> >>> *From:* Alan McDonald via wsjt-devel [mailto: >>> wsjt-devel@lists.sourceforge.net] >>> *Sent:* sunnuntai 9. huhtikuuta 2023 15.05 >>> *To:* WSJT software development >>> *Cc:* Alan McDonald >>> *Subject:* Re: [wsjt-devel] F/H mode in wrong period >>> >>> >>> >>> I think you are assuming that they are using Fox and Hound with WSJT >>> flavours. They are more likely using MSHV which does not require odd/even >>> F/H. >>> >>> They just look like they are F/H but are just multi stream. You can work >>> them as normal >>> >>> Alan >>> >>> >>> >>> On Sun, 9 Apr 2023 at 19:32, Ton PA0TBR via wsjt-devel < >>> wsjt-devel@lists.sourceforge.net> wrote: >>> >>> It becomes more often that I see Fox/Hound stations making QSO's in the >>> wrong period. >>> When I check my own time it is exact, according to time.is >>> Today again, I noticed a Fox in the wrong (odd) period together with >>> some Hounds transmitting in the for them correct (odd) period. >>> >>> But a few Hounds managed to transmit in the wrong (even) period enabling >>> a QSO. >>> >>> I wonder how these Hounds are able to follow in the wrong period? >>> >>> 73, >>> Ton pa0tbr >>> >>> ___ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> >>> >>> -- >>> >>> regards >>> Alan McDonald >>> ___ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://list
Re: [wsjt-devel] F/H mode in wrong period
OK, thank you all, I didn’t know that. 73, Ton pa0tbr Op ma 10 apr. 2023 om 11:37 schreef Alan McDonald > MSHV also does what they call Multi-stream and also multi channel or “slot” > > To work a station running MSHV, you do not have to obey the rules of Fox > and Hound associated with WSJT-?. > > You work them as normal but they are able to reply to 2 station at once on > one sub-frequency or multiple slots simultaneously. > > > > Alan McDonald > > VK1AO > > *From:* Ton PA0TBR via wsjt-devel > *Sent:* Monday, April 10, 2023 6:28 PM > *To:* WSJT software development > *Cc:* Ton PA0TBR > *Subject:* Re: [wsjt-devel] F/H mode in wrong period > > > > The messages had different reports for different stations in a single > stream., my understanding is that this must be WJST-X F/H.. > > Please correct me if i am wrong. > > > > 73, Ton pa0tbr > > > > > > Op zo 9 apr. 2023 om 15:06 schreef Reino Talarmo via wsjt-devel < > wsjt-devel@lists.sourceforge.net> > > And they are using the ”wrong” period on purpose an politely so that you > see immediately that the normal FT8 should be used by “hounds”. > > 73, Reino OH3mA > > > > *From:* Alan McDonald via wsjt-devel [mailto: > wsjt-devel@lists.sourceforge.net] > *Sent:* sunnuntai 9. huhtikuuta 2023 15.05 > *To:* WSJT software development > *Cc:* Alan McDonald > *Subject:* Re: [wsjt-devel] F/H mode in wrong period > > > > I think you are assuming that they are using Fox and Hound with WSJT > flavours. They are more likely using MSHV which does not require odd/even > F/H. > > They just look like they are F/H but are just multi stream. You can work > them as normal > > Alan > > > > On Sun, 9 Apr 2023 at 19:32, Ton PA0TBR via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > It becomes more often that I see Fox/Hound stations making QSO's in the > wrong period. > When I check my own time it is exact, according to time.is > Today again, I noticed a Fox in the wrong (odd) period together with some > Hounds transmitting in the for them correct (odd) period. > > But a few Hounds managed to transmit in the wrong (even) period enabling a > QSO. > > I wonder how these Hounds are able to follow in the wrong period? > > 73, > Ton pa0tbr > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > > -- > > regards > Alan McDonald > > ___ > 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
Re: [wsjt-devel] F/H mode in wrong period
The messages had different reports for different stations in a single stream., my understanding is that this must be WJST-X F/H.. Please correct me if i am wrong. 73, Ton pa0tbr Op zo 9 apr. 2023 om 15:06 schreef Reino Talarmo via wsjt-devel < wsjt-devel@lists.sourceforge.net> > And they are using the ”wrong” period on purpose an politely so that you > see immediately that the normal FT8 should be used by “hounds”. > > 73, Reino OH3mA > > > > *From:* Alan McDonald via wsjt-devel [mailto: > wsjt-devel@lists.sourceforge.net] > *Sent:* sunnuntai 9. huhtikuuta 2023 15.05 > *To:* WSJT software development > *Cc:* Alan McDonald > *Subject:* Re: [wsjt-devel] F/H mode in wrong period > > > > I think you are assuming that they are using Fox and Hound with WSJT > flavours. They are more likely using MSHV which does not require odd/even > F/H. > > They just look like they are F/H but are just multi stream. You can work > them as normal > > Alan > > > > On Sun, 9 Apr 2023 at 19:32, Ton PA0TBR via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > It becomes more often that I see Fox/Hound stations making QSO's in the > wrong period. > When I check my own time it is exact, according to time.is > Today again, I noticed a Fox in the wrong (odd) period together with some > Hounds transmitting in the for them correct (odd) period. > > But a few Hounds managed to transmit in the wrong (even) period enabling a > QSO. > > I wonder how these Hounds are able to follow in the wrong period? > > 73, > Ton pa0tbr > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > > -- > > regards > Alan McDonald > ___ > 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
[wsjt-devel] F/H mode in wrong period
It becomes more often that I see Fox/Hound stations making QSO's in the wrong period. When I check my own time it is exact, according to time.is Today again, I noticed a Fox in the wrong (odd) period together with some Hounds transmitting in the for them correct (odd) period. But a few Hounds managed to transmit in the wrong (even) period enabling a QSO. I wonder how these Hounds are able to follow in the wrong period? 73, Ton pa0tbr ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] UDP Status message defect. WD status not set when in Hound mode.
The desired operation would be that the TX watchdog setting is also used for Hound mode. 73, Ton PA0TBR On Tue, 17 Jan 2023 at 20:37, Laurie, VK3AMA via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Running v2.6.0 in my tests. The defect also confirmed by a JTAlert test > team member running v2.6.1 > > Testing here with a WD time of 4 minutes, which I know is much longer that > the hard-coded Hound WD time, When in Hound mode and the WD is triggered > and Tx is disabled there is no UDP status for the WD triggered sent. The WD > count down in the bottom right of the WSJTX window continues to count down > after TX has stopped but when it reaches 0 the WD UDP Status is not sent > which to me seems correct as WSJTX was not TX enabled at the time because > of the earlier disabling of TX by the Hound mode WD triggering. > > Looks to me like there are at least 2 WD timers in the WSJTX code. One for > normal operation that uses the user-settable the WD time setting, The > second WD timer is when in Hound mode and this is a hard-coded value and > does not appear to be setting the UDP Status TX Watchdog flag when the WD > is triggered. > > de Laurie VK3AMA > (JTAlert author) > ___ > 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
Re: [wsjt-devel] Subprocess error 2 when using Q65
Hi Joe, I understand your argument, but being new to 23cm EME (first QSO last Friday) the crashes were very confusing. I saw a station in the waterfall and clicked on it, maybe 3/4 minute later I had a crash. Restarting the instance or even rebooting the machine did not help, the instance would crash again because the Rx offset was still set above 4500. This happened quite a few times before I realised what was happening. In FT8 this problem is avoided by limiting the Rx value to 5000 Hz and without causing a crash. Maybe similar measures could be implemented for Q65 as well? Btw the crash with Q65 occurs with Rx > 4469 Hz to be more exact. So, limiting the Rx value to 4469 would help. I have no reason to complain Joe. Thanks to Q65 I was able to work 18 initials on 23 cm EME with only 3W into the feed of my HB 3.5m dish. The smallest station I worked used a 2.91m dish. Thank you and your team for your this great software to make this possible! 73. Ton pa0tbr On Tue, 21 Dec 2021 at 21:20, Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Ton, > > The crash you observed is caused by setting Rx frequency to a value so > high that the highest tone of the mode in use would be above 5000 Hz. > In general, WSJT-X is designed to work with maximum Rx passbands up to > 5000 Hz, but not beyond. Best to stay within that limit. > > -- 73, Joe, K1JT > > On 12/20/2021 4:48 PM, Ton PA0TBR via wsjt-devel wrote: > > When the Rx frequency is set above 4500 Hz then WSJT-X gives a > > Subprocess error 2 at t = hh:mm:56. > > I can repeat this when I click the waterfall above 4500 Hz or set the Rx > > frequency above 4500 Hz. > > I could not repeat this behaviour in FT8. > > > > I run WSJT-X v2.5.3 with the Q65 (60C) decoder (in 3 instances). > > The receiver bandwidth in the Advanced settings is set to 5000 Hz. > > > > The details are: > > > > Running: C:\WSJT\wsjtx\bin\jt9 -s "WSJT-X - ANAN-100D-B" -w 1 -m 3 -e > > C:\WSJT\wsjtx\bin -a "C:\Users\Ton\AppData\Local\WSJT-X - ANAN-100D-B" > > -t "C:\Users\Ton\AppData\Local\Temp\WSJT-X - ANAN-100D-B" > > At line 150 of file C:\Users\joe\src\bitbucket.org > > <http://bitbucket.org>\k1jt\wsjtx\lib\qra\q65\q65.f90 > > Fortran runtime error: Index '3100' of dimension 1 of array 's1' outside > > of expected range (3000:1) > > > > Error termination. Backtrace: > > Could not print backtrace: libbacktrace could not find executable to open > > #0 0x > > #1 0x > > #2 0x > > #3 0x > > #4 0x > > #5 0x > > #6 0x > > #7 0x > > #8 0x > > #9 0x > > #10 0x > > #11 0x > > #12 0x > > #13 0x > > > > Please let me know if I can be of help by collecting more info. > > 73, > > Ton pa0tbr > > > > > > ___ > > 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 > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Subprocess error 2 when using Q65
When the Rx frequency is set above 4500 Hz then WSJT-X gives a Subprocess error 2 at t = hh:mm:56. I can repeat this when I click the waterfall above 4500 Hz or set the Rx frequency above 4500 Hz. I could not repeat this behaviour in FT8. I run WSJT-X v2.5.3 with the Q65 (60C) decoder (in 3 instances). The receiver bandwidth in the Advanced settings is set to 5000 Hz. The details are: Running: C:\WSJT\wsjtx\bin\jt9 -s "WSJT-X - ANAN-100D-B" -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a "C:\Users\Ton\AppData\Local\WSJT-X - ANAN-100D-B" -t "C:\Users\Ton\AppData\Local\Temp\WSJT-X - ANAN-100D-B" At line 150 of file C:\Users\joe\src\bitbucket.org \k1jt\wsjtx\lib\qra\q65\q65.f90 Fortran runtime error: Index '3100' of dimension 1 of array 's1' outside of expected range (3000:1) Error termination. Backtrace: Could not print backtrace: libbacktrace could not find executable to open #0 0x #1 0x #2 0x #3 0x #4 0x #5 0x #6 0x #7 0x #8 0x #9 0x #10 0x #11 0x #12 0x #13 0x Please let me know if I can be of help by collecting more info. 73, Ton pa0tbr ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Strange interaction between 2 instances when using 'Fake it' split operation
We have the same transceiver Mike, ANAN100D. Please try it. because I am puzzled. 73, Ton PA0TBR On Sun, 18 Apr 2021 at 00:21, Black Michael wrote: > You never did say what rig you have. > > I've got an ANAN100D and 7000DLE MKII maybe I can reproduce this problem > and see if there's a fix. > I'm using Thetis 2.8.11 but can compiler it too. > > Mike W9MDB > > > > > On Saturday, April 17, 2021, 05:09:16 PM CDT, Ton PA0TBR > wrote: > > > Hi Mike, > > I monitored the CAT messages, all messages behave as expected, when I > transmit using instance 1, VFO 2 (on port 2) is not given a new frequency > (FA) command and replies to the FA queries continue to give the same > frequency for VFO2, while WSJT-X instance 2 shows a different frequency. > The checks were done with the TS2000 selection for CAT. > > Questions: > 1) Do you agree that it is easier to set the Thetis Transmit & Receive > Filters to something like 0 - 5000 Hz and set WSJT-X Split operation to > None? > 2) Can you see the problem on your system? > 3) I assume that the UDP settings I described in my initial message are > correct? Could it be UDP between the 2 WSJT-X instances? > > 73, > Ton PA0TBR > > > On Thu, 15 Apr 2021 at 23:07, Ton PA0TBR wrote: > > Hi Mike, nice to hear from you! > > I will check the CAT communication, you might have a point there. > > Maybe it's easier to set the Thetis Transmit & Receive Filters to > something like 0 - 5000 Hz and WSJT-X Split operation to None? > > The answers to your questions > 1) I use the 2 instances to monitor different bands, different frequency > segments in one band, different modes etc. > > 2) Rig selection is TS2000, I am using this setup for many years and > obvious overlooked the new rig selections. > I didn't expect CAT control to play a role in this because only the > instance of WSJT-X is playing tricks and manual band / frequency changes > initiated on either instance or VFO work as expected. > I changed to PowerSDR/Thetis, but see no difference. > What changes were made in the PowerSDR/Thetis selection? Did you implement > something like I did in Thetis, as below? > > 3) CAT control has been working fine for me. It includes a small mod where > the Thetis CAT port defines the instance and which VFO (A or B) to use. (I > use this since 2014, initially on PowerSDR). > > > To avoid any confusion, Hound mode is not necessary to see what I > described. > > 73, > Ton PA0TBR > > > > On Thu, 15 Apr 2021 at 14:40, Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > Couple of thoughts > > #1 Why are two instances being run? What's the use case? > #2 What rig selection are you using? Should be either Flex or PowerSDR. > #3 You might have more success running FLRig and connecting both WSJT-X > instances to the one FLRig...that way you end up with just 1 program > actually controlling the rig. Theres a PowerSDR rig selection in FLRig > that I contributed. > > Mike W9MDB > > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Strange interaction between 2 instances when using 'Fake it' split operation
Hi Mike, I monitored the CAT messages, all messages behave as expected, when I transmit using instance 1, VFO 2 (on port 2) is not given a new frequency (FA) command and replies to the FA queries continue to give the same frequency for VFO2, while WSJT-X instance 2 shows a different frequency. The checks were done with the TS2000 selection for CAT. Questions: 1) Do you agree that it is easier to set the Thetis Transmit & Receive Filters to something like 0 - 5000 Hz and set WSJT-X Split operation to None? 2) Can you see the problem on your system? 3) I assume that the UDP settings I described in my initial message are correct? Could it be UDP between the 2 WSJT-X instances? 73, Ton PA0TBR On Thu, 15 Apr 2021 at 23:07, Ton PA0TBR wrote: > Hi Mike, nice to hear from you! > > I will check the CAT communication, you might have a point there. > > Maybe it's easier to set the Thetis Transmit & Receive Filters to > something like 0 - 5000 Hz and WSJT-X Split operation to None? > > The answers to your questions > 1) I use the 2 instances to monitor different bands, different frequency > segments in one band, different modes etc. > > 2) Rig selection is TS2000, I am using this setup for many years and > obvious overlooked the new rig selections. > I didn't expect CAT control to play a role in this because only the > instance of WSJT-X is playing tricks and manual band / frequency changes > initiated on either instance or VFO work as expected. > I changed to PowerSDR/Thetis, but see no difference. > What changes were made in the PowerSDR/Thetis selection? Did you implement > something like I did in Thetis, as below? > > 3) CAT control has been working fine for me. It includes a small mod where > the Thetis CAT port defines the instance and which VFO (A or B) to use. (I > use this since 2014, initially on PowerSDR). > > > To avoid any confusion, Hound mode is not necessary to see what I > described. > > 73, > Ton PA0TBR > > > > On Thu, 15 Apr 2021 at 14:40, Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Couple of thoughts >> >> #1 Why are two instances being run? What's the use case? >> #2 What rig selection are you using? Should be either Flex or PowerSDR. >> #3 You might have more success running FLRig and connecting both WSJT-X >> instances to the one FLRig...that way you end up with just 1 program >> actually controlling the rig. Theres a PowerSDR rig selection in FLRig >> that I contributed. >> >> Mike W9MDB >> >> ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Strange interaction between 2 instances when using 'Fake it' split operation
Hi Mike, nice to hear from you! I will check the CAT communication, you might have a point there. Maybe it's easier to set the Thetis Transmit & Receive Filters to something like 0 - 5000 Hz and WSJT-X Split operation to None? The answers to your questions 1) I use the 2 instances to monitor different bands, different frequency segments in one band, different modes etc. 2) Rig selection is TS2000, I am using this setup for many years and obvious overlooked the new rig selections. I didn't expect CAT control to play a role in this because only the instance of WSJT-X is playing tricks and manual band / frequency changes initiated on either instance or VFO work as expected. I changed to PowerSDR/Thetis, but see no difference. What changes were made in the PowerSDR/Thetis selection? Did you implement something like I did in Thetis, as below? 3) CAT control has been working fine for me. It includes a small mod where the Thetis CAT port defines the instance and which VFO (A or B) to use. (I use this since 2014, initially on PowerSDR). To avoid any confusion, Hound mode is not necessary to see what I described. 73, Ton PA0TBR On Thu, 15 Apr 2021 at 14:40, Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Couple of thoughts > > #1 Why are two instances being run? What's the use case? > #2 What rig selection are you using? Should be either Flex or PowerSDR. > #3 You might have more success running FLRig and connecting both WSJT-X > instances to the one FLRig...that way you end up with just 1 program > actually controlling the rig. Theres a PowerSDR rig selection in FLRig > that I contributed. > > Mike W9MDB > > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Strange interaction between 2 instances when using 'Fake it' split operation
I am sorry to hear that Andy. Thanks for confirming that it's not just me seeing this. 73, Ton PA0TBR On Wed, 14 Apr 2021 at 23:41, Andras Bato wrote: > I've lost a fine DX QSO with the C92RU expedition station thanks to the > same QSY phenomena! > 73, > Andy HA6NN > > On Wed, Apr 14, 2021 at 8:04 PM Ton PA0TBR wrote: > >> Can someone help me with the following observation? Is this a problem >> with my settings, is it a bug or is there some other reason? >> >> I have 2 instances '1' and '2' which are connected to an ANAN transceiver >> with CAT over separate virtual COM ports. The system works very well when >> split operation is set to 'None'. >> >> When split operation is set to 'Fake it' then during transmission on >> instance 1 BOTH instances change their dial frequency according to their >> respective Audio TX Frequency settings. >> I had not expected instance 2 to change frequency. >> The radio VFO 2 does not change. >> This applies when the last band switch was done using the instance 2 band >> control. >> >> When I do a band switch using the radio (VFO 2), say from 20m to 17m, >> WSJT-X instance 2 follows accordingly, but now a transmission on instance 1 >> becomes even more confusing. >> During transmission on instance 1, the dial frequency for instance 1 >> changes as before but instance 2 changes back to 20m, again with the >> corresponding offset. >> >> My station: >> 2 * WSJT-X v2.4.0-rc4 >> Windows 8.1 >> >> Unique identifiers have been assigned to the 2 instances. >> >> UDP settings are the same for the 2 instances. >> UDP server: 239.255.0.0 >> UDP Server port number: 2237 >> Outgoing interfaces: loobback_0 >> Multicast TTL: 1 >> All 3 UDP checkboxes are checked. >> >> 73, >> Ton PA0TBR >> ___ >> 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 > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Strange interaction between 2 instances when using 'Fake it' split operation
Can someone help me with the following observation? Is this a problem with my settings, is it a bug or is there some other reason? I have 2 instances '1' and '2' which are connected to an ANAN transceiver with CAT over separate virtual COM ports. The system works very well when split operation is set to 'None'. When split operation is set to 'Fake it' then during transmission on instance 1 BOTH instances change their dial frequency according to their respective Audio TX Frequency settings. I had not expected instance 2 to change frequency. The radio VFO 2 does not change. This applies when the last band switch was done using the instance 2 band control. When I do a band switch using the radio (VFO 2), say from 20m to 17m, WSJT-X instance 2 follows accordingly, but now a transmission on instance 1 becomes even more confusing. During transmission on instance 1, the dial frequency for instance 1 changes as before but instance 2 changes back to 20m, again with the corresponding offset. My station: 2 * WSJT-X v2.4.0-rc4 Windows 8.1 Unique identifiers have been assigned to the 2 instances. UDP settings are the same for the 2 instances. UDP server: 239.255.0.0 UDP Server port number: 2237 Outgoing interfaces: loobback_0 Multicast TTL: 1 All 3 UDP checkboxes are checked. 73, Ton PA0TBR ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Callsigns substituted by <...>
Hello Bill, Thank you for the clear explanation, as always. One question remains, how long will an entry in the hash table exist for? In particular is it cleared after a band change? I sometimes do bandhopping to monitor different bands. Thanks again and 73, Ton pa0tbr On Sat, 15 Dec 2018 at 18:50, Bill Somerville wrote: > On 15/12/2018 17:11, Ton PA0TBR wrote: > > I am trying to work out why some callsigns are shown as <...> in WSJT-X > > Sometimes <...> is reflected in JTAlert as ... other times it is not > > shown in JTAlert. > > > > For example: > > 103615 -12 1.8 1590 ~ <...> LZ1PPZ > > 103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18 > > 103715 -5 1.9 1589 ~ <...> LZ1PPZ R-20 > > 103745 -8 1.8 1588 ~ OG55W 73 > > > > Looks like LZ1PPZ worked OG55W, but why was the call of OG55W not > > shown in the initial messages? > > And why is LZ1PPZ enclosed by <> in the last message? > > > > Other examples: > > 112030 -12 0.3 915 ~ G3PLP <...> -16 > > 112100 -14 0.3 915 ~ ZS9YOTA RR73 > > Why was ZS9YOTA substituted by <...> ? > > > > 111800 -17 0.1 650 ~ CQ SD4C JP80 Sweden > > 111830 -14 0.1 650 ~ <...> > > What happened here? > > > > I use WSJT-X v2.0.0.0 in FT8 mode > > > > 73, > > Ton pa0tbr > > Hi Ton, > > in the WSJT-X 77-bit FT8 (and MSK144) protocol non-standard callsigns > like OG55W and ZS9YOTA require one of the callsigns in a two-callsign > message to be compressed to a hash code to make space for the rest of > the message information. The hash code is a one-way algorithm so the > callsign cannot be looked up until a message with the callsign in full > has been received, until then the hash code is indicated as <...>. Once > the hash table is populated, the callsigns received as hash codes are > printed between '<' and '>' characters. The QSO flow and choice of which > of the two callsigns is hashed is arranged so that a station hearing > either end of the QSO will eventually get the hash table populated for > both callsigns. Also the flow and choice of which callsign to hash means > that during a QSO each station will send and receive each callsign > un-hashed at least once, in fact this is a corollary of the previous > sentence. > > 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
[wsjt-devel] Callsigns substituted by <...>
I am trying to work out why some callsigns are shown as <...> in WSJT-X Sometimes <...> is reflected in JTAlert as ... other times it is not shown in JTAlert. For example: 103615 -12 1.8 1590 ~ <...> LZ1PPZ 103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18 103715 -5 1.9 1589 ~ <...> LZ1PPZ R-20 103745 -8 1.8 1588 ~ OG55W 73 Looks like LZ1PPZ worked OG55W, but why was the call of OG55W not shown in the initial messages? And why is LZ1PPZ enclosed by <> in the last message? Other examples: 112030 -12 0.3 915 ~ G3PLP <...> -16 112100 -14 0.3 915 ~ ZS9YOTA RR73 Why was ZS9YOTA substituted by <...> ? 111800 -17 0.1 650 ~ CQ SD4C JP80 Sweden 111830 -14 0.1 650 ~ <...> What happened here? I use WSJT-X v2.0.0.0 in FT8 mode 73, Ton pa0tbr ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Simple question
Hi Mike, I think your tool is quite useful, I only had a bit of a fight to get the offset I had created back to zero. It was difficult to work out how large the created offset was and undo it. I used "time.is" to assist and noted that I had to reload the page for it to show the new time. Would it be possible to display the total created offset in your tool and have a button to undo the offset? 73, Ton pa0tbr On 5 August 2018 at 19:38, Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Version 1.2 on my QRZ page fixed the ctrl-click problem. > > de Mike W9MDB > > > > > On Sunday, August 5, 2018, 12:10:45 PM CDT, Brian G3VGZ < > yar...@planet3.freeuk.co.uk> wrote: > > > Alt click doesn't seem to work here. only way to reverse seems to be add a > - > in front of the number. > > > Black Michael via wsjt-devel wrote: > > > I did limit it to 0.5 seconds -- but you can keep on clicking the button > > to do it multiple times. > > > > Tell ya' what...I've just uploaded a new version to my QRZ page and > > expanded it to allow 10 seconds. Also you can Ctrl-Click the button now > to > > reverse the sign of the time value. So +3 seconds will effectively > become > > -3 seconds for example. > > > > https://www.dropbox.com/s/utl1mqzwizrs1kn/TimeFudgeSetup1_1.exe?dl=1 > > > > de Mike W9MDB > > > > > -- > Brian G3VGZ > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Test with DXpedition mode 12 May
Hi Bobby, That does work nicely if you prepare for an upcoming DXpedition. But when you come across a DXpedition in progress you want to switch quickly without loosing any information. If you then use Configurations, the software restarts which not only takes time but you also revert to some previously configured frequency, callsign, reset the Band Activity window etc. 73, Ton PA0TBR On 12 May 2018 at 23:36, Bobby Chandler <bob...@bellsouth.net> wrote: > PA0TBR > I just set a config for Fox/Hound and only put the frequencies for > DXpedition mode in it. Just switch to the config and all OK. > > Bobby/N4AU > > > > bob...@bellsouth.net > n...@arrl.net > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Test with DXpedition mode 12 May
Many thanks for the tests today. I run in the test with v1.9.0-rc4 r8642 With the weak signals today I did notice a problem. During the QSO with K1JT, I was still repeating Tx3 when Joe informed me by pingjockey that I was in the log. Normally I would restart from Tx1 when I time out and have not seen the RR73. The Tx3 msg is repeated 12 times before it times out. I now understand that the Fox gives up after 3 RR73 messages. Question: Should Tx3 not stop after 3 or maybe 6 attempts? That would trigger me to restart with Tx1. After my QSO with G4WJS I changed my call for a 2nd test and ended up transmitting on 14.074 and missed on a 2nd QSO. Cause: When the menu is exited via an OK button then the frequency is changed to the default frequency. A configurable color for decodes of FT8 messages in Fox mode would be very useful so that DXpedition mode can be identified and Dog mode enabled. An easier method to switch to Hound mode and back would be nice. Maybe a checkbox on the main window or an FT8-Hound option in the Mode drop down menu. When I entered a frequency in the "band box" of WSJT-X the "Enable Tx" button is triggered. I now see that it is triggered by the Enter button. That came a bit unexpected and made me wonder why my transmitter was running... This also happens in other modes. Question: Is tis intentional and can it be configured to ignore the nEter button? 73, Ton PA0TBR -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Third Public Test of FT8 DXpedition Mode: May 5, 1400-1700 UTC
Correction: 3) A configurable color for decodes of FT8 messages in Hound mode would be nice. should read: 3) A configurable color for decodes of FT8 messages in *Fox* mode would be nice. Sorrry about that. 73, Ton PA0TBR On 5 May 2018 at 22:47, Ton PA0TBR <pa0...@mubo.nl> wrote: > Hello Joe et all, > > Many thanks for the test, my findings are as follows: > > The protocol worked fine for me > I received W1/KH7Z with a strong signal >0 but received -24 while I used > 85W We could not complete the QSO. Did W1/KH7Z have a problem with > his receiver? > > The contact with W7.KH7Z went very easy. I noticed a double confirmation: > 155400 PA0TBR RR73; WA6ACU -21 > 155430 PA0TBR KH7Z RR73 > > The contact with K1JT went very smooth, no double confirmation. Thank you > for that QSO Joe! > > Some concerns or suggestions for improvement: > > 1) I run 2 concurrent copies of WSJTX-RC4 and JTAlert with an ANAN-100D. > Instance A was set to 14.115 and Hound mode, Instance B was also set to > 14.115 but with Normal FT8 mode > The frequencies displayed were somewhat confusing during transmit: > During receive all read 14.115 (as expected) > During transmit > WSJTX-A and the ANAN VFO-A jumped to 14.1155 (depends on TX frequency and > probably to do with "Fake it" Split operation) > *WSJTX-B jumped to 14.0745, ANAN VFOB stayed at 14.115 (seems that CAT B > is disabled when A transmits) * > Note that my specific ANAN software uses 2 CAT ports for the 2 instances > of WSJTX. Port 1 controls RX1, Port 2 controls RX2 of the ANAN by > translating the messages on port 2 back and forth. > > Upon further testing I got different results. I also run into a condition > that when transmitting with B, the system woud transmit one frequency for > 15 seconds, immediately followed by a transmission with a 2nd frequency for > 15 seconds etc. After a change in frequency this condition also > disappeared > > *Question:* Should I do some thorough testing with the dual system?? Or > are concurrent receivers with Hound mode still under construction? > > 2) When the Settings window is closed using the OK button, the frequency > is changed to the standard frequency. > So when I set the frequency 14.116 and then change to Hound mode, the > frequency is reset to 14.074.. > > 3) A configurable color for decodes of FT8 messages in Hound mode would be > nice. > > 4) An easier method to switch to Hound mode and back would be nice. Maybe > a checkbox on the main window or an FT8-Hound option in the Mode drop down > menu. > > 5) I am a bit concerned about the absence of slider control for the > received audio level. Since the slider control is no longer available I > have to attenuate the VAC Rx Audio by 20dB at my receiver side. That means > that I have a very low level in the VAC. > With 0dB attenuation I have approx 50% VAC signal or 80dB in WSJTX > With 20dB attenuation I see between 0 and 10% signal in the Sound panel > and between 40 and 60 dB in WSJTX. > > *Question: *Where can I adjust the audio level in WSJTX either in menu or > source code? I like to do some comparison tests with different audio levels. > > Sorry about the long email, I trust that it is useful though. > > 73, > Ton PA0TBR > > On 3 May 2018 at 14:12, Joe Taylor <j...@princeton.edu> wrote: > >> Hi all, >> >> I write to remind you of the third public test of *FT8 DXpedition Mode* >> scheduled for Saturday, May 5, 1400-1700 UTC. You are cordially invited to >> participate -- the more participants, the better! >> >> Our main goal is to simulate pileups in which many "Hounds" call and >> attempt to work a desirable rare DX station, the "Fox". The test will help >> us to validate software features that aim to maximize the practical QSO >> rate in such situations. We hope you can be there and try to work all >> three Foxes. >> >> Here's the detailed schedule: >> >> >> DateUTC Freq Fox Call OpLoc PEP Antenna >> (MHz) (W) >> >> May 5 1400 14.090 W1/KH7Z N1DG FN42 500 SteppIR >> May 5 1500 14.090 W7/KH7Z AA7A DM43 500 3el >> May 5 1600 14.090 K1JT K1JT FN20 100 Dipole >> >> >> All participating stations must use WSJT-X v1.9.0-rc4. If you don't yet >> have this program version, download links for Windows, Linux, and Mac OS >> are available near the bottom of the page here: >> https://physics.princeton.edu/pulsar/k1jt/wsjtx.html >> >> If you are compili
Re: [wsjt-devel] Third Public Test of FT8 DXpedition Mode: May 5, 1400-1700 UTC
Hello Joe et all, Many thanks for the test, my findings are as follows: The protocol worked fine for me I received W1/KH7Z with a strong signal >0 but received -24 while I used 85W We could not complete the QSO. Did W1/KH7Z have a problem with his receiver? The contact with W7.KH7Z went very easy. I noticed a double confirmation: 155400 PA0TBR RR73; WA6ACU -21 155430 PA0TBR KH7Z RR73 The contact with K1JT went very smooth, no double confirmation. Thank you for that QSO Joe! Some concerns or suggestions for improvement: 1) I run 2 concurrent copies of WSJTX-RC4 and JTAlert with an ANAN-100D. Instance A was set to 14.115 and Hound mode, Instance B was also set to 14.115 but with Normal FT8 mode The frequencies displayed were somewhat confusing during transmit: During receive all read 14.115 (as expected) During transmit WSJTX-A and the ANAN VFO-A jumped to 14.1155 (depends on TX frequency and probably to do with "Fake it" Split operation) *WSJTX-B jumped to 14.0745, ANAN VFOB stayed at 14.115 (seems that CAT B is disabled when A transmits) * Note that my specific ANAN software uses 2 CAT ports for the 2 instances of WSJTX. Port 1 controls RX1, Port 2 controls RX2 of the ANAN by translating the messages on port 2 back and forth. Upon further testing I got different results. I also run into a condition that when transmitting with B, the system woud transmit one frequency for 15 seconds, immediately followed by a transmission with a 2nd frequency for 15 seconds etc. After a change in frequency this condition also disappeared *Question:* Should I do some thorough testing with the dual system?? Or are concurrent receivers with Hound mode still under construction? 2) When the Settings window is closed using the OK button, the frequency is changed to the standard frequency. So when I set the frequency 14.116 and then change to Hound mode, the frequency is reset to 14.074.. 3) A configurable color for decodes of FT8 messages in Hound mode would be nice. 4) An easier method to switch to Hound mode and back would be nice. Maybe a checkbox on the main window or an FT8-Hound option in the Mode drop down menu. 5) I am a bit concerned about the absence of slider control for the received audio level. Since the slider control is no longer available I have to attenuate the VAC Rx Audio by 20dB at my receiver side. That means that I have a very low level in the VAC. With 0dB attenuation I have approx 50% VAC signal or 80dB in WSJTX With 20dB attenuation I see between 0 and 10% signal in the Sound panel and between 40 and 60 dB in WSJTX. *Question: *Where can I adjust the audio level in WSJTX either in menu or source code? I like to do some comparison tests with different audio levels. Sorry about the long email, I trust that it is useful though. 73, Ton PA0TBR On 3 May 2018 at 14:12, Joe Taylor <j...@princeton.edu> wrote: > Hi all, > > I write to remind you of the third public test of *FT8 DXpedition Mode* > scheduled for Saturday, May 5, 1400-1700 UTC. You are cordially invited to > participate -- the more participants, the better! > > Our main goal is to simulate pileups in which many "Hounds" call and > attempt to work a desirable rare DX station, the "Fox". The test will help > us to validate software features that aim to maximize the practical QSO > rate in such situations. We hope you can be there and try to work all > three Foxes. > > Here's the detailed schedule: > > > DateUTC Freq Fox Call OpLoc PEP Antenna > (MHz) (W) > > May 5 1400 14.090 W1/KH7Z N1DG FN42 500 SteppIR > May 5 1500 14.090 W7/KH7Z AA7A DM43 500 3el > May 5 1600 14.090 K1JT K1JT FN20 100 Dipole > > > All participating stations must use WSJT-X v1.9.0-rc4. If you don't yet > have this program version, download links for Windows, Linux, and Mac OS > are available near the bottom of the page here: > https://physics.princeton.edu/pulsar/k1jt/wsjtx.html > > If you are compiling the program for yourself, be sure to use code > revision r8642 or later, taken from the repository's WSJT-X development > branch. All code revisions since r8642 perform identically in FT8 > DXpedition Mode. > > Detailed operating instructions are posted here: > http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf > Some details in these instructions have changed, so be sure to read and > follow the latest revision (dated April 26, 2018) carefully! Don't just > try to wing it. > > As you will know after reading the instructions, Fox can conduct up to 5 > QSOs simultaneously, using frequency slots spaced by 60 Hz. Fox transmits > in the frequency range 300-900 Hz above the USB dia
Re: [wsjt-devel] Windows 10, PortAudio and my PC
Hi Bill, Many thanks for your replies. I had tried to rollback / reinstall / use the driver from Realtek and booting after I deleted the driver. I will certainly try to build WSJT-X with the port audio you provided. I can do that in a few weeks after which I will let you know of the results. At least I know that there might be a solution. Many thanks! 73, Ton pa0tbr On 15 June 2016 at 00:05, <wsjt-devel-requ...@lists.sourceforge.net> wrote: >From: Bill Somerville <g4...@classdesign.com> > Subject: Re: [wsjt-devel] Windows 10, PortAudio and my PC > > On 14/06/2016 07:58, Ton PA0TBR wrote: > > After I updated my PC from Windows 8.1 64 bit Pro to Windows 10 64 bit > > Pro, when I start WSPRX 08r3058 I get the following messages: > > - Unable to initialize PortAudio > > - PortAudio says requested soundcard format not supported > > - Failed to start audio input stream > > WSPRX will then start, but without any audio devices, including no VAC's. > > > > My PC is a Zotac ID90 with i7-3770T CPU and uses a RealTek High > > Definition Audio device. > > I have reinstalled and also updated the driver but still have the same > > result. I installed a USB Audio device as default but also with the > > same result. > > > > It seems to be related to PortAudio as I also have a problem with > > HPSDR which stops when it initializes PortAudiio. HPSDR appears to run > > in compatibility mode though. > > WSJTX works fine and I assume that it doesn't use the PortAudio library. > > > > Zotac offers no support Although they released their product only > > 3 years ago, they claim it is discontinued and can't provide any help > > related to Windows 10. > > > > Is there any experience here with such PortAudio problem and is there > > a solution? > > Hi Ton, > > I am not aware of this issue but reading about it, it seems to be a > driver issue and, if you have no updated sound card driver available for > Windows 10, you may be stuck with this issue. The best advice seems to > be to roll back the driver and use compatibility mode. Another > possibility is to un-install the audio driver and let Windows re-install > - some users have reported that the problem only occurs of systems that > have been upgraded to Windows 10. > > If you can get to the point where you no longer get the first error > "Unable to initialize PortAudio" then there are possible solutions by > selecting only from the devices accessed via the DirectSound Windows > audio API. It appears that the problem is related to the WSAPI audio API > route to the sound devices. > > 73 > Bill > G4WJS. > > On 14/06/2016 10:57, Bill Somerville wrote: > > If you can get to the point where you no longer get the first error > > "Unable to initialize PortAudio" then there are possible solutions by > > selecting only from the devices accessed via the DirectSound Windows > > audio API. It appears that the problem is related to the WSAPI audio > > API route to the sound devices. > > Hi again Ton, > > here is a build of PortAudio for Windows with only the MME Audio API > supported: > > > https://dl.dropboxusercontent.com/u/4192709/portaudio-e111b3a-w32-MME-only.zip > > if you are able to build WSPRX then please do so using this package for > PortAudio and see how it goes. If that doesn't work then I can provide > versions of PortAudio with other single API support options to try. > > 73 > Bill > G4WJS. > > > > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Windows 10, PortAudio and my PC
Hello all, After I updated my PC from Windows 8.1 64 bit Pro to Windows 10 64 bit Pro, when I start WSPRX 08r3058 I get the following messages: - Unable to initialize PortAudio - PortAudio says requested soundcard format not supported - Failed to start audio input stream WSPRX will then start, but without any audio devices, including no VAC's. My PC is a Zotac ID90 with i7-3770T CPU and uses a RealTek High Definition Audio device. I have reinstalled and also updated the driver but still have the same result. I installed a USB Audio device as default but also with the same result. It seems to be related to PortAudio as I also have a problem with HPSDR which stops when it initializes PortAudiio. HPSDR appears to run in compatibility mode though. WSJTX works fine and I assume that it doesn't use the PortAudio library. Zotac offers no support Although they released their product only 3 years ago, they claim it is discontinued and can't provide any help related to Windows 10. Is there any experience here with such PortAudio problem and is there a solution? 73, Ton pa0tbr -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Patch for WSJT-X
Hello Bill and Joe, Thank you for committing the patches in the development branch. 73, Ton PA0TBR Date: Fri, 10 Apr 2015 21:31:17 +0100 From: Bill Somerville g4...@classdesign.com Subject: Re: [wsjt-devel] Patch for WSJT-X To: wsjt-devel@lists.sourceforge.net Message-ID: 55283315.8070...@classdesign.com Content-Type: text/plain; charset=windows-1252 Hi Ton Joe, I have committed this patch into the development branch. I have implemented it slightly differently from what I believe is in ^/branches/wsjtx_exp so as to use the same band info model that is used elsewhere. This will almost certainly conflict when it comes to merge ^/branches/wsjtx_exp back to ^/branches/wsjtx, I recommend that the version in ^/branches/wsjtx be retained. Thanks for the patch Ton. 73 Bill G4WJS. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wsjt-devel Digest, Vol 14, Issue 12
Hello Bill, Thanks again for a fine explanation. I had a look at the country list and noted that some 53 country names are 'too long'. It won't be easy to abbreviate these country names, such that it remains clear for everybody. Leaving the view port scrolled to the far left looks like the way to go because then the user can scroll to see the full name. I didn't have much time yet but I like to explore that a bit further. I let you know if I succeed or not. 73, Ton PA0TBR Date: Tue, 07 Apr 2015 16:57:12 +0100 From: Bill Somerville g4...@classdesign.com Subject: Re: [wsjt-devel] Horizontal scroll bar in WSJT-X Band To: wsjt-devel@lists.sourceforge.net Message-ID: 5523fe58.1000...@classdesign.com Content-Type: text/plain; charset=windows-1252 On 07/04/2015 16:30, Ton PA0TBR wrote: Hello Bill, Hi Ton, Thanks for your quick answer and the work you have been doing to reduce the length. Where in the source can I find the country list? The country list is taken from a standard CTY.DAT file (it is embedded in the application) which you can override with a user version if you wish. The extra abbreviation as it stands now is: // do some obvious abbreviations countryName.replace (Islands, Is.); countryName.replace (Island, Is.); countryName.replace (North , N. ); countryName.replace (Northern , N. ); countryName.replace (South , S. ); countryName.replace (East , E. ); countryName.replace (Eastern , E. ); countryName.replace (West , W. ); countryName.replace (Western , W. ); countryName.replace (Central , C. ); countryName.replace ( and , ); countryName.replace (Republic, Rep.); countryName.replace (United States, U.S.A.); countryName.replace (Fed. Rep. of , ); countryName.replace (French , Fr.); countryName.replace (Asiatic, AS); countryName.replace (European, EU); countryName.replace (African, AF); which is in displaytext.cpp. They seemed to be good choices after reviewing a current CTY.DAT file. More similar unambiguous replacement could be added. The position of the heading is not so important, but when I look at decoded callsigns, I like to see when the decode took place. Enlarging the window is no option for me, running 2 instances, logbook and PowerSDR, my monitors are crowded as it is. Maybe an option to allow truncation? It's probably not that easy to know what will fit, with the different font sizes, fonts and environments. You are correct that is potentially a complex calculation, but my problem with truncation is that there is no indication that truncation has happened, the horizontal scroll bar is the idiomatic way of indicating truncation of a text field. I did have a brief attempt at ensuring that the scroll view port is left scrolled as far to the left as possible after new decodes but hit some issues with implementation. If you think this would help I can have another go at that. I have recently improved the ability to set the decoded text font fixing some defects. You may find that selecting smaller font for decoded text is your best option. I have plans to make the activity windows into proper table views as the current implementation using a text edit widget is not the most suitable for displaying this sort of information. Text edits provide a vast number of features that we don't need but complicate populating and manipulating them a great deal. A table view will allow user setting of column width and even hiding columns. A table view would even allow wrapping within a column if we wished or a tool tip to display extra information about the decode line. Another option with a table view could be to have only a single activity window with a filter button that filters it to decodes and Tx messages on the current Rx frequency i.e. the same window could then double as a band activity and on frequency activity monitor. 73, Ton PA0TBR 73 Bill G4WJS. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Horizontal scroll bar in WSJT-X Band
Hello Bill, Thanks for your quick answer and the work you have been doing to reduce the length. Where in the source can I find the country list? The position of the heading is not so important, but when I look at decoded callsigns, I like to see when the decode took place. Enlarging the window is no option for me, running 2 instances, logbook and PowerSDR, my monitors are crowded as it is. Maybe an option to allow truncation? It's probably not that easy to know what will fit, with the different font sizes, fonts and environments. 73, Ton PA0TBR Date: Mon, 06 Apr 2015 22:23:27 +0100 From: Bill Somerville g4...@classdesign.com Subject: Re: [wsjt-devel] Horizontal scroll bar in WSJT-X Band Activitywindow To: wsjt-devel@lists.sourceforge.net Message-ID: 5522f94f.6090...@classdesign.com Content-Type: text/plain; charset=windows-1252; format=flowed On 06/04/2015 21:19, Ton PA0TBR wrote: Hello all, Hi Ton, For quite some time now the Band Activity window in WSJT-X sometimes has a horizontal scrollbar and when this happens, the window contents is scrolled to the right. The UTC column is then no longer visible, which is a bit of a nuisance. A decode like the following, which has a long country name seems to trigger this: 1603 -4 0.9 834 # CQ E77AW JN83 !Bosnia-Herzegovina I am not sure that this 'feature' was always present, maybe long country names were abbreviated in the past? My current version is 1.5.0 r4998, but this is happening for quite some time. My question is if something can be done to avoid the horizontal scrolling. Yes, I added that recently. The problem was that lines were getting truncated, particularly when the font size is increased. Country names are abbreviated to some extent and limited in length. I also changed the abbreviation logic to do some more common abbreviations rather than turning word into initials e.g. European - EU, North -N., South - S., U.S.A. etc.. If you wish to remove the scroll bar, make the main window a bit wider or turn off country lookups or reduce the decoded text font size in settings. Unfortunately because of the separate widgets used to display heading line and the decoded text, it is not really practical to scroll the headings in line with the decodes. 73, Ton PA0TBR 73 Bill G4WJS. -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Patch for WSJT-X
Hello Joe, Many thanks for your confirmation! I appreciate the efforts of you and your team very much. 73, Ton PA0TBR On Mon, Mar 9, 2015 at 7:08 PM, wsjt-devel-requ...@lists.sourceforge.net wrote: Message: 7 Date: Mon, 09 Mar 2015 14:08:15 -0400 From: Joe Taylor j...@princeton.edu Subject: Re: [wsjt-devel] Patch for WSJT-X To: WSJT software development wsjt-devel@lists.sourceforge.net Message-ID: 54fde18f.4030...@princeton.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Ton, Thanks for the suggested patch. It's a useful addition, and I have included it in my current working branch. (It may be a while before I do a merge into the main development branch, though.) -- 73, Joe, K1JT On 3/2/2015 5:10 AM, Ton PA0TBR wrote: Hi all, I have a small patch for WSJT-X which I think would also be useful for other users and would like to see it added in the mainstream. The patch puts the band info in the last n characters of the separator line in the decodes windows, like: -10m 0900 -8 0.2 745 # CQ UN7BK MO51 ~Kazakhstan 0900 -16 0.4 1032 # OZ1SMS VK3FZ QF22 -20m 0902 -1 0.3 1200 # SM7MME R7RIB KN64 0902 -16 0.3 1794 # CQ DG7EL JO31 ~F.. of Germany -20m 0903 -17 0.2 955 # UA9OES UA6LJX 73 0903 -13 -0.2 1585 # VK6PG IW1APE JN35 -15m 0904 -21 0.5 1485 # CQ DL7UKA JO50 ~F.. of Germany -15m 0905 -2 0.5 784 # RA9CHS RW6AB R-05 0905 -18 0.6 1461 # CQ OO6A JO11 ~Belgium -10m 0906 -20 -0.2 748 # CQ UN7BK MO51 ~Kazakhstan 0906 -10 0.4 1643 # UA0CGR ZS1BHJ JF97 -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Patch for WSJT-X
Hi all,
I have a small patch for WSJT-X which I think would also be useful for
other users and would like to see it added in the mainstream.
The patch puts the band info in the last n characters of the separator line
in the decodes windows, like:
-10m
0900 -8 0.2 745 # CQ UN7BK MO51 ~Kazakhstan
0900 -16 0.4 1032 # OZ1SMS VK3FZ QF22
-20m
0902 -1 0.3 1200 # SM7MME R7RIB KN64
0902 -16 0.3 1794 # CQ DG7EL JO31 ~F.. of Germany
-20m
0903 -17 0.2 955 # UA9OES UA6LJX 73
0903 -13 -0.2 1585 # VK6PG IW1APE JN35
-15m
0904 -21 0.5 1485 # CQ DL7UKA JO50 ~F.. of Germany
-15m
0905 -2 0.5 784 # RA9CHS RW6AB R-05
0905 -18 0.6 1461 # CQ OO6A JO11 ~Belgium
-10m
0906 -20 -0.2 748 # CQ UN7BK MO51 ~Kazakhstan
0906 -10 0.4 1643 # UA0CGR ZS1BHJ JF97
The changes are as follows:
===
displaytext.cpp (from line 25)
Old:
void DisplayText::insertLineSpacer()
{
QString tt=;
QString bg=#d3d3d3;
_insertText(tt,bg);
}
Replace with:
void DisplayText::insertLineSpacer(QString tt)
{
QString bg=#d3d3d3;
_insertText(tt,bg);
}
displaytext.h (from line 16)
Old:
void insertLineSpacer();
Replace with:
void insertLineSpacer(QString tt);
mainwindow.cpp (from line 1360)
Old:
if(m_config.insert_blank () m_blankLine)
{
ui-decodedTextBrowser-insertLineSpacer();
m_blankLine=false;
}
Replace with:
if(m_config.insert_blank () m_blankLine)
{
QString band = ADIF::bandFromFrequency ((m_dialFreq +
ui-TxFreqSpinBox-value ()) / 1.e6);
band = band.rightJustified(40, '-');
ui-decodedTextBrowser-insertLineSpacer(band);
m_blankLine=false;
}
===
I run 2 instances of WSJT-X and found it difficult to keep track when I
changed to another band.
Recently I run an AutoIt script which performs band hopping on my
transceiver (openHPSDR + ANAN-100D) which makes it even more desirable to
have the band data in the decodes window.
I hope that one of the developers can assist to get this in the mainstream.
73,
Ton PA0TBR
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
