Re: [wsjt-devel] no decode
Dimension 4 works just fine with Windows 10. I've been on Windows 10 for quite some time and have no problem with Dimension 4. I'm running version 5.31.331.0. John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 8/7/2018 7:52 AM, harold deitz via wsjt-devel wrote: Chris, I have been using "Dimension 4" for time sync. Recently upgraded my OS to Windows 10. Found out that Dimension 4 won't work with Windows 10. How do I get Meinberg? Hal W5GHZ Sent from Yahoo Mail. Get the app <https://yho.com/148vdq> On Tuesday, August 7, 2018 01:53:46 PM GMT, Chris Getman wrote: I had a very similar problem. The time looked OK, but when I did a manual Time Sync everything started working Michael had me switch time sync programs to Meinberg and I haven’t had an issue since. It’s worth a try and might fix your issue also. Chris - N3PLM *From:*Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] *Sent:* Tuesday, August 7, 2018 9:38 AM *To:* wsjt-devel@lists.sourceforge.net *Cc:* Black Michael *Subject:* Re: [wsjt-devel] no decode Hmmm hamspots.net doesn't show any transmissions from you for the last 16 hours so you may not be transmitting as you think. You say your time is good but what does http://time.is tell you? de Mike W9MDB On Tuesday, August 7, 2018, 8:21:08 AM CDT, seaka...@juno.com <mailto:seaka...@juno.com> <mailto:seaka...@juno.com>> wrote: I've been using this software flawlessly for a while. I'm using it on a Mac machine with Signalink and ICOM 735. This morning when I turned on the computer and ran the program it was not decoding. The waterfall shows lots of very strong signals. Time is exact between software and computer. When I look at the mac sound settings all is normal. The software DOES transmit. Just no decoding of signals. I was using it yesterday before I shut the computer down perfectly. No indication of trouble. I also deleted the program and re installed a new download. All perimeters stayed the same upon re install. Again it does transmit. Just no decode.. Any ideas??? Mike M AC1DV "All good things are wild and free." ~ Henry David Thoreau *How To Remove Eye Bags & Lip Lines Fast (Watch)* Fit Mom Daily <http://thirdpartyoffers.juno.com/TGL3132/5b699b793d36a1b7944b9st02vuc>http://thirdpartyoffers.juno.com/TGL3132/5b699b793d36a1b7944b9st02vuc SponsoredBy Content.Ad -- 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 <mailto: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 <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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] What happens when Hound does not receive RR73?
I'm not sure what good this would do. I exchanged reports with the operation twice on 17M and once on 20M. One of the 17M contacts did not result in the RR73, just an exchange of signal reports. Of course, that exchange did not end up in the Club Log, which means it was not a valid QSO. So, I don't see what good logging a contact without the RR73 does. The other two contacts did show up in the Club Log. Also, the fox never sent a CQ that I heard in any of the three times I had a full or partial contact. I was copying him with a decent signal. On the 17M contact, he called me after my call was sent five times. On 20M it was after eight times. Pretty nice for a rare one. I'm not sure how much putting my transmit frequency above 3,000 Hz helped, but I tend to think it did help. I just hope I will be able to copy them loud enough on SSB for a contact, but so far, they have not been that strong when I m on the air. 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 7/2/2018 12:57 PM, David Tiller wrote: At least with this current dxpedition, I suggest you at least tentatively log contacts as soon as you have received a report from the fox and have sent yours. I had been trying to contact KH1/KH7Z on 20m but the only success I had were 2 'busted' sequences. I never saw a RR73 for either of them but lo and behold both tries were logged on their side. On Jul 2, 2018, at 15:49, Joshua B Nass <mailto:josh.n...@gmail.com>> wrote: I let it run six attempts then I stop it. Since the RR73 is incoming from the Fox and I have all the details I need for entry into my log, I log it, then wait for the Club Log verification. If I am in the fox log on the that band I will upload my log. On Mon, Jul 2, 2018 at 3:07 AM, Charles Suckling <mailto:char...@sucklingfamily.free-online.co.uk>> wrote: Hi All 20m conditions were a bit better today and I finally managed to work Baker with 100W, lots of feeder loss and a sloping dipole. The problem I had was, after receiving my report from KH7Z, I failed to receive RR73. Thanks to Bill’s advice to start over again (TX1 message), on the 4^th QSO attempt (this time with G4KGC in the shack) I finally got my RR73. Within about 5 sequences they came back again with a report again, and QSO attempts proceeded normally. Decoding was reasonably reliable at the time. It seems they did not receive my TX3 message, hence did not send RR73, rather than me not decoding the RR73. What became apparent was that under these circumstances my TX freq was shifted three times, then stuck on the final frequency and transmissions would have continued at infinitum: I guess this is what is expected as the User guide para 14 says: Here is an example of one of the failed attempts: 083545 Tx 3056 ~ KH7Z G3WDG IO92 083630 -13 -0.5 390 ~ G3WDG KH7Z -15 083645 Tx 390 ~ KH7Z G3WDG R-13 083700 -16 -0.6 389 ~ G3WDG KH7Z -15 083715 Tx 389 ~ KH7Z G3WDG R-16 083730 -14 -0.6 330 ~ G3WDG KH7Z -15 083745 Tx 330 ~ KH7Z G3WDG R-14 083815 Tx 630 ~ KH7Z G3WDG R-14 083845 Tx 630 ~ KH7Z G3WDG R-14 083915 Tx 630 ~ KH7Z G3WDG R-14 083945 Tx 630 ~ KH7Z G3WDG R-14 084015 Tx 630 ~ KH7Z G3WDG R-14 084045 Tx 630 ~ KH7Z G3WDG R-14 After moving to 630 it stayed there and continued transmitting until I intervened, thinking that the QSO had failed and I was unnecessarily causing QRM. Should I have waited longer for Fox to respond? In the situation where hounds to not receive their RR73, presumably a wall of QRM below 1000 develops for Fox making it more difficult for QSOs to complete? I saw other stations in the same fix as I was, repeating their TX3 messages for many periods. 73 Charlie Avast logo <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient> This email has been checked for viruses by Avast antivirus software. www.avast.com <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient> -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org <http://Slashdot.org>! http://sdm.link/slashdot <http://sdm.link/slashdot> ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
Re: [wsjt-devel] Observation on Expedition Mode
A friend of mine from my amateur radio club, Yavapai Amateur Radio Club,
Prescott, AZ, is one of the ops on the Baker Island DXpedition. He has
lots of experience working the CQ World Wide CW Contest with the Voodoo
Contest Group in African and Middle Eastern countries. I'm really
looking forward to talking to him when he gets back to get feedback on
how things were on their end.
John, WB9VGJ
John L. Broughton
www.wb9vgj.us
wb9...@arrl.net
2silverhon...@gmail.com
On 6/30/2018 12:50 PM, Black Michael via wsjt-devel wrote:
I would like to approach this idea with some set of principles that
everybody can agree on...so here goes...
#1 Maximize QSO rate
#2 Minimize blind callers
Just those two principles are enough to say we should do whatever we
can to reduce blind callers which will also help to maximize QSO rate
as they are inversely relates (i.e. fewer blind means > qso rate).
Now...to take the logic to the extreme...if all callers were blind
then the QSO rate would be zero...quite obviously an undesirable
situation. As the % of blind callers reduces the QSO rate
increases...and the QSO rate is maximized when nobody is blind (notice
we're not considering band conditions here as that is not something we
can anything about).
So...given the two extremes which should we strive to support?
"good enough" is for horseshoes and hand grenades as the saying goes.
So why would we NOT try to minimize blind callers when it's an easy
software change to do so? This would have no changes on the fox
side...only the hounds
de Mike W9MDB
On Saturday, June 30, 2018, 11:13:07 AM CDT, Bill Somerville
wrote:
Hi Mike,
we are not hear to determine how operators at a DXpedition site choose
to operate, we are not aware of conditions on the ground. If they feel
that they are getting optimum rates without calling CQ then that is
their choice. Remember that calling CQ from a rare entity can result
in a passband 100% full of pile up, they may have tried it and decided
it doesn't help the QSO rate.
73
Bill
G4WJS.
On 30/06/2018 17:05, Black Michael via wsjt-devel wrote:
But what about them receiving all these calls in the blind? Isn't
that going to interfere when they try to respond to people who can't
hear them?
Mike
On Saturday, June 30, 2018, 11:04:11 AM CDT, Bill Somerville
<mailto:g4...@classdesign.com> wrote:
On 30/06/2018 16:57, Black Michael via wsjt-devel wrote:
OK...so it appears the CQ every 5 trasnmissions is NOT enforced
unless Fox clicks the "More CQs" box.
We'd be a lot better off if this was always forced and Hounds were
restricted to only answer CQ's.
This explains why we don't see the CQ's and calling blind is
normally necessary (as long as you can see KH7Z that is).
if(m_tFoxTxSinceCQ>=m_foxCQtimeandui->cbMoreCQs->isChecked()){
de Mike W9MDB
Hi Mike,
it should be reasonable to assume that if the Baker Is. operators are
not enforcing regular CQ calls then they have plenty of callers to
keep the to-be-worked queue populated with more stations than Tx
slots and a QSO rate that is high.
--
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 <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
Virus-free. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
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] Observation on Expedition Mode
As noticed in my previous post, my experience was the fox was not
calling CQ every five minutes, but simply working station after station.
Seeing as how I could copy all his transmissions, I called him, and got
the QSO. I don't feel guilty about how I worked him. I figure as long as
I can copy him steadily and he is working stations calling, there is no
reason I should not call, as long as he is not working a specific area
that doesn't include the US.
That being said, I can't fault your idea that the fox should call CQ
every five minutes, but before I would force that to be mandatory, I'd
get input from the DXpedition to see if they think it was/should be
necessary. The one problem it could solve is stations calling blind who
can't hear the fox, but it would be nice to know if that is a real
problem. Judged by many years of SSB DXing, I have no doubts there are
stations who don't follow general guidelines, rules and regulations when
it comes to working DX, though.
John, WB9VGJ
John L. Broughton
www.wb9vgj.us
wb9...@arrl.net
2silverhon...@gmail.com
On 6/30/2018 8:57 AM, Black Michael via wsjt-devel wrote:
OK...so it appears the CQ every 5 trasnmissions is NOT enforced unless
Fox clicks the "More CQs" box.
We'd be a lot better off if this was always forced and Hounds were
restricted to only answer CQ's.
This explains why we don't see the CQ's and calling blind is normally
necessary (as long as you can see KH7Z that is).
if(m_tFoxTxSinceCQ>=m_foxCQtimeandui->cbMoreCQs->isChecked()){
de Mike W9MDB
On Saturday, June 30, 2018, 10:41:44 AM CDT, John Zantek
wrote:
Wholly concur with #2, but not necessarily #1, Mike. Yes, lots of
folks are calling in the blind. That’s not limited to FT8, guys.
But…
Depending on who’s running the digital tent (Don/Ned/?), rates of CQ
vary from every 10 minutes to generate some traffic down to NONE,
because there are stations calling. I have a pretty ideal QTH to work
Baker on any band, and I’m observing too much of the latter pattern.
I know there are lots of new folks sitting at their keyboards, waiting
for the CQ, not seeing one, then walking away. That’s not good, as it
just reduces the rate for Baker, and frustrates the new ham who’s a
potential DXer and digital apostle.
The QSB on 17M has been horrendous, with Baker’s sig, regardless of
mode, varying wildly here. On 17M, they were working the usual wall
of JA but I never did see a CQ, so I entered it manually and generated
the Std Msgs to work them successfully.
*From:*Black Michael via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net]
*Sent:* Saturday, June 30, 2018 7:15 AM
*To:* 'WSJT software development'
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] Observation on Expedition Mode
I have some observations too.
#1 Tons of ops calling KH7Z when they can't see them. I assume this
only causes problems as it's quite possible KH7Z with their honker
antennas and can see them but not the other way round. So KH7Z will
put them in the queue and try to process them taking up the limited
slots they are using right now (2 from what I've seen). IMHO the
solution to this is pretty simplewhen you turn on Hound or switch
bands you should be PREVENTED FROM TRANSMITTING UNTIL YOU GET CQ FRO
THE DX STATION. So, you would be required to double-click on a CQ
to allow transmitting. I noticed the the Baker team gave a lukewarm
endorsement of FT8 on their news update quite likely due to this problem.
#2 We need to turn on spotting for the DX station so that PSKReporter
and Hamspots can work and also so JTAlert can produce alerts when the
DX station is received. Don't need to spot the hounds of course.
Trying to figure out what band is good for local ops would be much
improved with automatic spotting for us and for the DX team who could
then see where their signal is going as more teams use internet on
site via satellite links.
de Mike W9MDB
On Saturday, June 30, 2018, 8:13:39 AM CDT, Grant Willis
mailto:vk...@bigpond.com>> wrote:
Joe,
An observation if I may about expedition mode. I see with KH1/KH7Z
that the number of Fox TX channels varies – I presume as they place
more stations in the queue. As expected, the power per channel drops
the more channels running so that the amplifiers can keep up. However,
this has an unintended consequence perhaps of potentially breaking
QSOs. A few times now I have started calling KH1/KH7Z on 20m when I am
receiving them around -09 (but with pretty low S-meter signal
strength). Usually this is with 1-2 channels running on their
downlink. If they go to 3 channels I can still receive but it falls to
say -15. If they bring up channel 4 and 5 I loose them. There just
isn’t the link budget left to receive them when the power is split
between more than 3 channels in this example.
Now the issue is, if they answer me by adding the 4^th channel – I
wont hear them under those con
Re: [wsjt-devel] Observation on Expedition Mode
I can't say I agree with Mike that one should have to answer a CQ to work the DXpedition station. I worked KH7Z on 17M this past Thursday. However, in the time I was on the frequency, I did not decode any CQ. KH7Z was working stations the entire time I was on frequency. I simply kept an eye on his signal strength which was varying from about -22 to -15. I set my transmit frequency at 3343 and started calling. It didn't take very long, just several minutes, before he called me and we completed the QSO. My report to him was -22 and his to me was -06 (I'm running a hy-gain DX-88 vertical with my IC-7300; hardly a DX big gun.) If I would have had to answer a CQ in order to work him, I could not have gotten the QSO due to the short time I had to try to make it and with him just working station after station, not needing to call CQ. I was watching the stations he was calling to make sure they weren't, say, all in Europe, as I did not know if he had called CQ for any particular region. As most all the stations he was working were in the US, I had no hesitation about calling him. As far as finding where KH7Z is operating, I've just been using the HB9DRV-9 DX Cluster spots option in m HRD logbook program (I don't run the main HRD program.) or just selecting various bands in the right hand window of it to see if and where he is operating then, if on SSB or FT8, I go to the frequency to see if he is strong enough to work. John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 6/30/2018 7:14 AM, Black Michael via wsjt-devel wrote: I have some observations too. #1 Tons of ops calling KH7Z when they can't see them. I assume this only causes problems as it's quite possible KH7Z with their honker antennas and can see them but not the other way round. So KH7Z will put them in the queue and try to process them taking up the limited slots they are using right now (2 from what I've seen). IMHO the solution to this is pretty simplewhen you turn on Hound or switch bands you should be PREVENTED FROM TRANSMITTING UNTIL YOU GET CQ FRO THE DX STATION. So, you would be required to double-click on a CQ to allow transmitting. I noticed the the Baker team gave a lukewarm endorsement of FT8 on their news update quite likely due to this problem. #2 We need to turn on spotting for the DX station so that PSKReporter and Hamspots can work and also so JTAlert can produce alerts when the DX station is received. Don't need to spot the hounds of course. Trying to figure out what band is good for local ops would be much improved with automatic spotting for us and for the DX team who could then see where their signal is going as more teams use internet on site via satellite links. de Mike W9MDB On Saturday, June 30, 2018, 8:13:39 AM CDT, Grant Willis wrote: Joe, An observation if I may about expedition mode. I see with KH1/KH7Z that the number of Fox TX channels varies – I presume as they place more stations in the queue. As expected, the power per channel drops the more channels running so that the amplifiers can keep up. However, this has an unintended consequence perhaps of potentially breaking QSOs. A few times now I have started calling KH1/KH7Z on 20m when I am receiving them around -09 (but with pretty low S-meter signal strength). Usually this is with 1-2 channels running on their downlink. If they go to 3 channels I can still receive but it falls to say -15. If they bring up channel 4 and 5 I loose them. There just isn’t the link budget left to receive them when the power is split between more than 3 channels in this example. Now the issue is, if they answer me by adding the 4^th channel – I wont hear them under those conditions. If I am part way through a QSO I can loose the RR73 for the same reason if they answer someone else on the 4^th channel– simply because the link runs out of steam. Now if I couldn’t hear them in the first place I wouldn’t have tried calling. In this case however, they can disappear under load effectively and I loose them mid QSO. For future consideration perhaps is to have the setting of number of channels vs the number of active channels maintain a constant PER CHANNEL TX power rather than the variable situation we have now. Ie I enable my fox station to run say 4 channels, but only reply on 1 channel, then the output power should be the equivalent of the power that would be in that channel if all 4 were in fact on air but aren’t. At least that way I have a constant link budget I am working with on my comms channel with the fox station rather than one that can have them drastically cut power mid QSO without reference to the conditions on the path I am working them via. If what I am describing is not how it is supposed to work already then there is another factor at work somewhere in the chain to be explored. I would be happy to discuss this further and use the KH1/KH7Z
Re: [wsjt-devel] Hound mode setting
Mike, It was pilot error. For some reason, I uses a comma instead of a period in the frequencies and never noticed. Duh... John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 6/28/2018 8:54 AM, Black Michael via wsjt-devel wrote: You probably entered the frequencies wrong. They are in MHz. So enter 14.090 for example. de Mike W9MDB On Thursday, June 28, 2018, 10:51:02 AM CDT, John L. Broughton <2silverhon...@gmail.com> wrote: I did add the Baker Island frequencies to the list in WSJT-X. However, I cannot use them using the drop down menu. Whatever standard frequency I am on, when I select one of the DXpeditions frequencies, the window turns red (that shows the band) and the frequency shown remains the same. So, I have to select the band to show the regular FT8 frequency, then manually tune the rig to the DXpedition frequency and all seems fine. I can't understand why WSJT-X won't change the frequency on my rig when I select it. I'm running the latest release of WSJT-X, Windows 10, and an ICOM IC-7300. 73, John John L. Broughton www.wb9vgj.us wb9...@arrl.net <mailto:wb9...@arrl.net> 2silverhon...@gmail.com <mailto:2silverhon...@gmail.com> On 6/28/2018 4:46 AM, Neil Zampella wrote: > You can easily take care of this by creating a separate Configuration > for Fox & Hound mode. > > Very easily done, you don't have to edit frequencies until you know of > a new DXPedition you wish to contact, and you don't have to worry > about changing any other settings that may mess up your normal FT8 usage. > > I have to Fox & Hound configurations set up, one for my KX3, and one > for my K2. > > Neil, KN3ILZ > > > On 6/28/2018 3:10 AM, Saku wrote: >> Hi >> While just entering in Baker frequencies I got an idea: >> What about adding Add Frequency dialog's Mode selection FT8-hound >> (perhaps also fox)? Selecting either one would cause also >> corresponding Checkbox set/reset in Advaced tab at normal usage time >> ( as user friendly property) >> When selecting either one at Add frequency dialog, on setting time, >> pressing OK could also prompt a splash "are you sure...etc." if fox >> or hound selecton is tried to set with ordinary frequency. And vice >> versa if not ordinary frequency prompt "should you use hound (fox?) >> mode setting" would appear. >> -- >> Saku >> OH1KH > > > -- > > 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 <mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > -- 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 <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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] Hound mode setting
I did add the Baker Island frequencies to the list in WSJT-X. However, I cannot use them using the drop down menu. Whatever standard frequency I am on, when I select one of the DXpeditions frequencies, the window turns red (that shows the band) and the frequency shown remains the same. So, I have to select the band to show the regular FT8 frequency, then manually tune the rig to the DXpedition frequency and all seems fine. I can't understand why WSJT-X won't change the frequency on my rig when I select it. I'm running the latest release of WSJT-X, Windows 10, and an ICOM IC-7300. 73, John John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 6/28/2018 4:46 AM, Neil Zampella wrote: You can easily take care of this by creating a separate Configuration for Fox & Hound mode. Very easily done, you don't have to edit frequencies until you know of a new DXPedition you wish to contact, and you don't have to worry about changing any other settings that may mess up your normal FT8 usage. I have to Fox & Hound configurations set up, one for my KX3, and one for my K2. Neil, KN3ILZ On 6/28/2018 3:10 AM, Saku wrote: Hi While just entering in Baker frequencies I got an idea: What about adding Add Frequency dialog's Mode selection FT8-hound (perhaps also fox)? Selecting either one would cause also corresponding Checkbox set/reset in Advaced tab at normal usage time ( as user friendly property) When selecting either one at Add frequency dialog, on setting time, pressing OK could also prompt a splash "are you sure...etc." if fox or hound selecton is tried to set with ordinary frequency. And vice versa if not ordinary frequency prompt "should you use hound (fox?) mode setting" would appear. -- Saku OH1KH -- 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 --- This email has been checked for viruses by AVG. https://www.avg.com -- 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] Audio issue(s) with Win10 April 2018 update
Just a couple comments. I don't have a rig blaster and I don't have a laptop; I have a Dell desktop. There was a latency problem which would not let us connect using Quick Assist as I have HughesNet satellite Internet. We used TeamViewer instead. Mike was a great help. 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 5/26/2018 5:45 AM, Black Michael via wsjt-devel wrote: He had several problems. Here's what we did. #1 Uninstall all sound drivers (with the remove files option). Reboot without rig USB plugged in. #2 Tested his speakers and microphone (PC-based) to ensure they worked using Voice Recorder -- this is a sanity check that your sound setup works the way you think it should. #3 Plugged in rig and relabeled the USB Codec drivers to make them easy to distinguish #4 Adjusted levels on Windows Playback/Record cotrols to 0dB #4 Adjusted rig blaster to 12 o-clock position. #5 Adjusted rig USB AF level to then get 30db+ on the waterfall (not all rigs can do this so this may have to be done from rig blaster) The decoding problem he had was due the signal levels being low from the rig and over amplified in the Windows controls. So that's why he was getting intermittent decodes as any gain over 0dB in the Windows controls buys you nothing so there was lots of quantization going on. He also has latency problems on his older laptop causing dropouts on transmission but they are very short so don't affect him a whole lot. de Mike W9MDB On Saturday, May 26, 2018, 7:35:17 AM CDT, Barry Smith <b...@g4iat.co.uk> wrote: In message <e0b4ef0f-8c67-2ac0-9e6b-cdaf55764...@gmail.com <mailto:e0b4ef0f-8c67-2ac0-9e6b-cdaf55764...@gmail.com>> "John L. Broughton" <2silverhon...@gmail.com <mailto:2silverhon...@gmail.com>> wrote: > All, > I want to thank Mike, W9MDB, for spending considerable time with me on > the phone and connected to my computer this morning which resulted in > resolving the audio problem. His expertise did the job; I never would > have figured it out. > Now looking forward to my 16th digital QSO with him... > 73, > John, WB9VGJ > John L. Broughton It could be useful to know what you/he did to resolve the problem in case others experience the same problem. Barry G4IAT IO83 -- -- 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 <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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] Audio issue(s) with Win10 April 2018 update
All, I want to thank Mike, W9MDB, for spending considerable time with me on the phone and connected to my computer this morning which resulted in resolving the audio problem. His expertise did the job; I never would have figured it out. Now looking forward to my 16th digital QSO with him... 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 5/24/2018 8:26 PM, Black Michael via wsjt-devel wrote: Get rid of drivertoolkit...totally unnecessary Try uninstalling the driver (remove file if you option is there) and reboot to let it reinstall. de Mike W9MDB On Thursday, May 24, 2018, 9:08:48 PM CDT, John L. Broughton <2silverhon...@gmail.com> wrote: I just ran into this problem when my Windows 10 updated today. When I start WSJT-X, I get the error 'Error in Sound input' An error opening the audio input device has occurred.' When I troubleshoot the USB Audio CODEC driver, it results in a message 'no jack information available.' When I run the DRIVERTOOLKIT, it says the driver is up to date. I tried a backup and restore on the driver and that did not help. I realize this is not a WSJT-X issue, but am hoping someone here has had this problem and figured out a way to fix the driver problem. 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net <mailto:wb9...@arrl.net> 2silverhon...@gmail.com <mailto:2silverhon...@gmail.com> On 5/24/2018 3:34 AM, Barry Smith wrote: > All I see is that you can delay the install. I'm lucky that I have 2 > PCs and I can see what happens with one before I update the other. > > I did update the PC that runs WSJT-X and I did have to change the > settings/privacy/microphone to allow use of the microphone - even > though I'm using a device (cat control, audio in and out) that uses > USB. > > Barry > G4IAT > > In message <CABcOcnBGt+S=CTw0ybRxKwcE37qGJm0RwYo4S6-Sti5bg7mhyQ@mail.g <mailto:CTw0ybRxKwcE37qGJm0RwYo4S6-Sti5bg7mhyQ@mail.g> > mail.com> > Andras Bato <ha6nn.a...@gmail.com <mailto:ha6nn.a...@gmail.com>> wrote: > >> Hi Barry, >> I've done this: >> Any comment? >> GL de HA6NN >> Andras >> On Wed, May 23, 2018 at 7:19 PM, Barry Smith <b...@g4iat.co.uk <mailto:b...@g4iat.co.uk>> wrote: >>> In message <96609faa-afc1-4e9d-900d-504291749...@bellsouth.net <mailto:96609faa-afc1-4e9d-900d-504291749...@bellsouth.net>> >>> Dave Crockett <wb4...@bellsouth.net <mailto:wb4...@bellsouth.net>> wrote: >>> >>>> Yeah, I kinda think it was a drivers issue, too. If nothing else, my >>>> experience should be considered a heads-up� to anyone having a >>>> similar issue in Win10. That option to •revert to a previous version >>>> of Windows� in Win10 has a pretty short window of opportunity and why >>>> I didn�t spend longer trying to noodle it out. >>>> Tnx all! >>>> 73, >>>> Dave WB4DFW (EM84š) >>> I had an issue with my weather satellite software (WxtoImg) which >>> refused to work after to W10 update. I noticed that the HdAudio driver >>> had been updated so suspected that, but it turned out to be >>> Settings/Privacy/Microphone (even though I use line in). It was set to >>> off. Setting it to on, but setting the individual apps listed, to off >>> (WxtoImg wasn't in the list), cured the problem. >>> >>> That's one one PC. The other PC, which I run WSJT-X on, hasn't been >>> updated yet, so don't know whether something similar might apply to >>> that. >>> >>> Barry >>> G4IAT -- 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 <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel AVG logo <https://www.avg.com/internet-security> This email has been checked for viruses by AVG antivirus software. www.avg.com <https://www.avg.com/internet-security> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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] Audio issue(s) with Win10 April 2018 update
I just ran into this problem when my Windows 10 updated today. When I start WSJT-X, I get the error 'Error in Sound input' An error opening the audio input device has occurred.' When I troubleshoot the USB Audio CODEC driver, it results in a message 'no jack information available.' When I run the DRIVERTOOLKIT, it says the driver is up to date. I tried a backup and restore on the driver and that did not help. I realize this is not a WSJT-X issue, but am hoping someone here has had this problem and figured out a way to fix the driver problem. 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 5/24/2018 3:34 AM, Barry Smith wrote: All I see is that you can delay the install. I'm lucky that I have 2 PCs and I can see what happens with one before I update the other. I did update the PC that runs WSJT-X and I did have to change the settings/privacy/microphone to allow use of the microphone - even though I'm using a device (cat control, audio in and out) that uses USB. Barry G4IAT In message <CABcOcnBGt+S=CTw0ybRxKwcE37qGJm0RwYo4S6-Sti5bg7mhyQ@mail.g mail.com> Andras Bato <ha6nn.a...@gmail.com> wrote: Hi Barry, I've done this: Any comment? GL de HA6NN Andras On Wed, May 23, 2018 at 7:19 PM, Barry Smith <b...@g4iat.co.uk> wrote: In message <96609faa-afc1-4e9d-900d-504291749...@bellsouth.net> Dave Crockett <wb4...@bellsouth.net> wrote: Yeah, I kinda think it was a drivers issue, too. If nothing else, my experience should be considered a heads-up to anyone having a similar issue in Win10. That option to •revert to a previous version of Windows in Win10 has a pretty short window of opportunity and why I didnt spend longer trying to noodle it out. Tnx all! 73, Dave WB4DFW (EM84š) I had an issue with my weather satellite software (WxtoImg) which refused to work after to W10 update. I noticed that the HdAudio driver had been updated so suspected that, but it turned out to be Settings/Privacy/Microphone (even though I use line in). It was set to off. Setting it to on, but setting the individual apps listed, to off (WxtoImg wasn't in the list), cured the problem. That's one one PC. The other PC, which I run WSJT-X on, hasn't been updated yet, so don't know whether something similar might apply to that. Barry G4IAT -- 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] Enhancement request
I am one of those males who has defective color vision (What the US Army told me when I had the color vision test when I took my enlistment physical back in the early 60s.). What I have great difficulty with is black text on a red background or red text on black or any dark background. With JTAlert, I changed the background color for stations calling me from red to orange. With red, I often had great difficulty in reading the call sign easily. With the orange background, I have no problems. I don't worry about the green receive indicator as I can pretty easily pick it out. Also, it doesn't really make much difference where it is. I do keep an eye on the transmit location, though., 73, John, WB9VGJ John L. Broughton www.wb9vgj.us wb9...@arrl.net 2silverhon...@gmail.com On 4/25/2018 11:37 PM, Tom Ramberg via wsjt-devel wrote: Without taking a stand in this discussion, it might be a point to consider that about 10% of men are red-green color blind. So any color not green or red would actually be helpful for us color blind people. 73 de Tom OH6VDA 26. apr. 2018 kl. 08:27 skrev <g...@isect.com <mailto:g...@isect.com>> <g...@isect.com <mailto:g...@isect.com>>: Hmmm. The red is a strong visual cue to transmission, so having both in red would be very confusing. How about leaving the TX one red as now, but making the ‘receive channel’ a translucent grey column between the edge of the waterfall and the line above the audio frequency numbers? I say ‘translucent’ because I’d like to see the scale markers, numbers and red TX marker through it, please. Well, that’s just a suggestion to throw in the pot, Sorry I can’t actually code it! 73, Gary ZL2iFB *From:* Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, 26 April 2018 4:57 p.m. *To:* WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>> *Cc:* Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com>> *Subject:* Re: [wsjt-devel] Enhancement request I played a bit with colors and nothing is really satisfactory. It's an optical thing...with any color right on top of the waterfall there isn't any contrast between the green (or any other color) and the waterfall. So instead how's this look? A red box when matched. Or larger red goal posts when separate. Is a different color really necessary or is the appearance of the goal posts enough? And it's an optical illusion here in that the goal posts are the same height as the box. de Mike W9MDB -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org <http://Slashdot.org>! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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
