|
locked
Re: wsjtx ssl
on5po
TKS 73
ON5PO,
De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de neil_zampella <neilz@...>
Envoyé : vendredi 4 janvier 2019 18:37 À : Support@HamApps.groups.io Objet : Re: [HamApps] wsjtx ssl Two things ... First .. this is the JT-Alert support group. Questions on WSJT-X should really go to the WSJT Yahoo group to keep this free for JT-Alert issues, and from bogging down with questions about WSJT-X problems. Second: in the User Manual's Section 3.1 - WIndows Installation, there are three steps to take for the SSL update. 1. Download the OpenSSL file - as the User Manual said it MUST be the 32 bit version 2. If that doesn't work, you may need some Microsoft support files installed .. the link to that installer is also given in the note in the User Manual 3. If that doesn't work, you should manually download the LoTW user file using the link given in the User Manual, and place it in the LOG DIRECTORY for WSJT-X. Hope this helps, Neil, KN3ILZ
|
|
|
|
locked
Re: wsjtx ssl
neil_zampella
Two things ... First .. this is the JT-Alert support group. Questions on WSJT-X should really go to the WSJT Yahoo group to keep this free for JT-Alert issues, and from bogging down with questions about WSJT-X problems. Second: in the User Manual's Section 3.1 - WIndows Installation, there are three steps to take for the SSL update. 1. Download the OpenSSL file - as the User Manual said it MUST be the 32 bit version 2. If that doesn't work, you may need some Microsoft support files installed .. the link to that installer is also given in the note in the User Manual 3. If that doesn't work, you should manually download the LoTW user file using the link given in the User Manual, and place it in the LOG DIRECTORY for WSJT-X. Hope this helps, Neil, KN3ILZ
|
|
|
|
locked
Re: wsjtx ssl
kl7qw <kl7qw@...>
i just unchecked the donation box and mine works fine Dave KL7QW
On Friday, January 4, 2019, 4:14:34 AM CST, on5po <on5po@...> wrote:
thank you,Mac,
this morning, nothing worked, I had to resume the program wsjtx, now ok
Thank you for your reply
73ON5PO,
De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de Mac, DL1EFA <dl1efa@...>
Envoyé : vendredi 4 janvier 2019 11:02 À : Support@HamApps.groups.io Objet : Re: [HamApps] wsjtx ssl @Janny, ON5PO
Win32OpenSSL is open source and thus it is free. There is no need to pay any Money for it.
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2q.exe will do the job without any payment required.
The only reason why it is not part of the installer of WSJT-X is, that encryption technology (SSL is encryption) is export restricted. So you need to install it on your own.
vy 73 de Mac, DL1EFA
Von: on5po
Hello everyone, About the program for the "ssl", asked with version 2.0 of wsjtx, is it paying? I paid the $ 10, it works, I thought it was just a donation. A friend, did the same operation by unchecking the, the program does not seem to work. Who can confirm me, if the (payment) must be done imperatively, to have the "ssl" so that I can circulate the information. Thank you, 73
|
|
|
|
locked
Re: Exclamation Mark still showing
Michael Black
Callsign database update probably. This will tell you what you need Settings/Program Updates de Mike W9MDB
On Friday, January 4, 2019, 10:10:59 AM CST, Carey Fisher <careyfisher@...> wrote:
Laurie, I'm set up for RU but the exclamation mark is still showing in the header even though I have the latest JTAlert. Screen snip attached. Am I missing something? 73, Carey, WB4HXE
|
|
|
|
locked
Re: Exclamation Mark still showing
Check which Call Sign Data Base version you have. May need update. Thanks 73
On Fri, Jan 4, 2019 at 8:15 AM Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
|
|
|
|
locked
Re: Exclamation Mark still showing
Hasan Schiers N0AN
Same here (latest version and (!) still showing. 73, N0AN Hasan
On Fri, Jan 4, 2019 at 10:10 AM Carey Fisher <careyfisher@...> wrote: Laurie,
|
|
|
|
locked
Exclamation Mark still showing
Carey, WB4HXE
Laurie,
I'm set up for RU but the exclamation mark is still showing in the header even though I have the latest JTAlert. Screen snip attached. Am I missing something? 73, Carey, WB4HXE
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
AI3KS
Laurie,
Thanks for the help. I figured out that my problem was self inflicted. In my manual qsos I was not entering the full exchange in the WSJT-X Log screen, only the state. 73, Steve, AI3KS
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
AI3KS
Carey,
Thanks for the help. I figured out that my problem was self inflicted. In my manual qsos I was not entering the full exchange in the WSJT-X Log screen, only the state. 73, Steve, AI3KS
|
|
|
|
locked
Re: Sound card problem.
Michael Black
If you are sure you should be seeing alerts then you should send in a bug report via Help/Contact Support. Be sure to give an example message of what you think should be alerted in the description box. de Mike W9MDB
On Friday, January 4, 2019, 5:49:26 AM CST, Dermot Flanagan <dermotflanagan@...> wrote:
Yes, have checked Ham Apps sound is installed. The test sound card works just fine , but no actual alerts ie for CQ or DX etc. I am Running Windows 10 Pro if that has any relevance. I still live in hope. Thanks, D
|
|
|
|
locked
Re: Sound card problem.
Dermot Flanagan <dermotflanagan@...>
Yes, have checked Ham Apps sound is installed. The test sound card works just fine , but no actual alerts ie for CQ or DX etc. I am Running Windows 10 Pro if that has any relevance. I still live in hope. Thanks,
D
|
|
|
|
locked
Re: wsjtx ssl
on5po
thank you,Mac,
this morning, nothing worked, I had to resume the program wsjtx, now ok
Thank you for your reply
73ON5PO,
De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de Mac, DL1EFA <dl1efa@...>
Envoyé : vendredi 4 janvier 2019 11:02 À : Support@HamApps.groups.io Objet : Re: [HamApps] wsjtx ssl @Janny, ON5PO
Win32OpenSSL is open source and thus it is free. There is no need to pay any Money for it.
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2q.exe will do the job without any payment required.
The only reason why it is not part of the installer of WSJT-X is, that encryption technology (SSL is encryption) is export restricted. So you need to install it on your own.
vy 73 de Mac, DL1EFA
Von: on5po
Hello everyone, About the program for the "ssl", asked with version 2.0 of wsjtx, is it paying? I paid the $ 10, it works, I thought it was just a donation. A friend, did the same operation by unchecking the, the program does not seem to work. Who can confirm me, if the (payment) must be done imperatively, to have the "ssl" so that I can circulate the information. Thank you, 73
|
|
|
|
locked
Re: wsjtx ssl
Mac, DL1EFA <dl1efa@...>
@Janny, ON5PO
Win32OpenSSL is open source and thus it is free. There is no need to pay any Money for it.
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2q.exe will do the job without any payment required.
The only reason why it is not part of the installer of WSJT-X is, that encryption technology (SSL is encryption) is export restricted. So you need to install it on your own.
vy 73 de Mac, DL1EFA
Von: on5po
Hello everyone, About the program for the "ssl", asked with version 2.0 of wsjtx, is it paying? I paid the $ 10, it works, I thought it was just a donation. A friend, did the same operation by unchecking the, the program does not seem to work. Who can confirm me, if the (payment) must be done imperatively, to have the "ssl" so that I can circulate the information. Thank you, 73
|
|
|
|
locked
Re: Re KI4GE
Hi Laurie,
toggle quoted messageShow quoted text
Great stuff! Although I appreciate that this particular case is rare, your new database would be very useful for those US stations that go mobile to activate various squares, which I am sure is more common. I hope you had a great festive season, and wish you all the best for 2019. 73 de Phil GU0SUP
-----Original Message-----
From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@gmail.com> Sent: Thursday, 3 January, 2019 22:41 To: Support@HamApps.groups.io Subject: Re: [HamApps] Re KI4GE On 4/01/2019 9:26 am, Phil Cooper wrote: Phil, There is something that can be done, and I am working on it at the moment. Rather than relying on a database of Callsigns versus States created with regular updates from the FCC, which for the vast majority is accurate, a database that determines the State based on the on-air grid is being coded. This will allow for those operators who change the State from which they are operating while their Callsign doesn't reflect the change. This Grid based State database lookup will still not be 100% accurate as there are many grids that can be in 2,3,4 States. When that occurs, the lookup will default to using the State that encompasses the largest area of the 4 character Grid used on air. This is still a WIP that has taken a bit of a holiday in recent weeks with the Holiday activities taking up a lot of my time, so I don't know when it will go live within JTAlert. de Laurie VK3AMA
|
|
|
|
locked
wsjtx ssl
on5po
Hello everyone,
About the program for the "ssl", asked with version 2.0 of wsjtx, is it paying?
I paid the $ 10, it works, I thought it was just a donation.
A friend, did the same operation by unchecking the, the program does not seem to work.
Who can confirm me, if the (payment) must be done imperatively, to have the "ssl"
so that I can circulate the information.
Thank you, 73 on5po, Janny
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
Bernd - KB7AK
Thanks Laurie, might be worth while to add a sentence or two to the help file, I am sure there are others who may fall into the same trap I did since my default logging program doesn't really care which mode WSJT runs in, so it wasn't obvious to me.
It'll all be good, I am looking forward to use this combo of apps for the contest.
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
JTAlert Support (VK3AMA)
Responses inline...
On 4/01/2019 4:27 pm, Bernd - KB7AK wrote: When I had the situation earlier when no states were transferred, at that time I hadn't set WSJT into contest mode, I was just having regular QSO's and tried to log them, each one failed with an error of "invalid abbreviation" in N3FJP. Once I put WSJT into contest mode, and simulated a successful QSO, by first selecting a station, then clicking Log QSO in WSJT, then filling in the blanks for the 4 fields I described before, then I was able to log a QSO and data was transferred properly. I even created a Cabrillo log file and it looked perfectly Ok.Trying to Log to a N3FJP Contest Log when WSJT-X is NOT in contest mode will not work. JTAlert has checks to see if WSJT-X is in Contest mode and which Contest is selected, this affects what JTAlert does under the hood and the structure of the logging command sent to the Contest Log. By not having WSJT-X in Contest mode, JTAlert defaults to the normal logging command for ACLog and the Contest Log specific commands are not sent. This is why the Contest Log was missing data. What still puzzles me is the fact when I click a station, the following happens: The call sign is properly populated, RST R is populated with 599, ST/PR/# is empty, RST S is populated with 599, and Country is populated with the proper country name. I suspect that once the first real exchange happens, all fields will be properly updated. I wish we had a test run like they did before the contest in December to see how it works under real life conditions. I trust you that you tested everything and that it will work on Saturday.All N3FJP Loggers utilise the same (exact) lookup functions when a DX Call is initially sent to it. This is what you observed when the DX Call in WSJT-X was changed. de Laurie VK3AMA
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
Michael Black
There is a test run scheduled. Enclosed below de Mike W9MDB ================================================ Please share this notice with your local groups, as appropriate. Same time and same drill as in recent years. This coming Friday, let's have two practice sessions to check out station equipment, software and operator(s). New in 2019! Practice for both RTTY and FT8! Here's the schedule: 2200-2230 UTC, Friday, 5 January - RTTY focus 2230-2300 UTC, Friday, 5 January - FT8 focus 0200-0230 UTC, Saturday, 6 January (Friday evening NA time) - RTTY focus 0230-0300 UTC, Saturday, 6 January (Friday evening NA time) - FT8 focus "Focus" means lets focus on that mode for the 30 minutes - but if you want to practice switching back and forth between modes by all means do so. I expect you'll find others of a like mind. Operate just like it's the real thing that starts on Saturday. Use whatever bands are open and active for you at each time slot. For FT8, the following dial frequencies as recommended by Joe K1JT in the January 2019 QST would be a good starting place: 3590, 7080**, 14130, 21130, 28160. You might want to have a special message prepared to respond to stations telling you that the contest hasn't yet started. (Or, perhaps even practice your typing ;) Most of all, have fun over the weekend in the RTTY Round-Up! Take some photos of your operation and send them and/or a summary of your experience to me, Jeff WK6I - especially anything around your decisions on how to use (or not use) FT8. It will help me write up the contest for the QST article. 73 jeff wk6i ** Below is a link to the article by Joe K1JT for reference. You may notice that the recommended frequencies for 80 and 40 meters are in typical RTTY subbands. FT8 ops may want to slide up above 7100 or below 3580 if they are having trouble getting a foothold in the recommended ranges. Jeff Stai ~ WK6I ~ wk6i.jeff@... Ask me about Green Keys Night - Jan 1, 2019 0000-2359 UTC! RTTY op at W7RN Twisted Oak Winery ~ http://www.twistedoak.com/
|
|
|
|
locked
Re: JTAlert and N3FJP ARRL RTTY Log
Bernd - KB7AK
When I had the situation earlier when no states were transferred, at that time I hadn't set WSJT into contest mode, I was just having regular QSO's and tried to log them, each one failed with an error of "invalid abbreviation" in N3FJP. Once I put WSJT into contest mode, and simulated a successful QSO, by first selecting a station, then clicking Log QSO in WSJT, then filling in the blanks for the 4 fields I described before, then I was able to log a QSO and data was transferred properly. I even created a Cabrillo log file and it looked perfectly Ok.
What still puzzles me is the fact when I click a station, the following happens: The call sign is properly populated, RST R is populated with 599, ST/PR/# is empty, RST S is populated with 599, and Country is populated with the proper country name. I suspect that once the first real exchange happens, all fields will be properly updated. I wish we had a test run like they did before the contest in December to see how it works under real life conditions. I trust you that you tested everything and that it will work on Saturday. I hope that clears up any confusion I might have caused.
|
|
|
|
locked
Re: Sound card problem.
Michael Black
Have you set up the audio alerts for the alerts you want? Selected the default sound for each? de Mike W9MDB
On Thursday, January 3, 2019, 1:03:07 PM CST, Dermot Flanagan <dermotflanagan@...> wrote:
Have installed FT v22 & JT Alertv 2.12.10 All is working except the sound card which is fine on test but no audio when FT8 running. I have reinstalled both FT and JT but still no audio. Can you help please? Thanks
|
|
|