Date
1 - 8 of 8
Locked logging #WSJTX_config
|
WSJT-x logs but does not send to HRD logbook
|
|
|
|
Dave Garber <ve3wej@...>
check udp settings
Dave Garber VE3WEJ / VE3IE On Wed, Jul 13, 2022 at 3:02 PM Frederick C Hollendorfer < phredyh@...> wrote: WSJT-x logs but does not send to HRD logbook |
|
|
|
Alex DH2ID
JT-AlertX is the answer: http://hamapps.com/
I've been using it for years, works like a charm :-) Vy 73, Alex - DH2ID |
|
|
|
Dave KD2SGM
Frederick,
I, along with many others, had a similar issue with due to the HRD update that included HRD Alert. Seems that HRD grabbed the port normally used to broadcast this info to other programs and was not allowing it to be used by others. In my case N1MM, WSJT-X, and HRD we’re affected. In addition there were quite a few GridTracker folks affected too. My fix was to revert back to a previous version of HRD. Others moved forward and changed the HRD setting to allow multicasting. In addition the port needed to be changed in each program to allow the transfer of data. I believe the one being used is 224.0.0.73. Check the HRD, N1MM, and GridTracker forums, in addition to this one. Search on HRD Alert and you should get quite a bit of information. One other thing you may want to try that I also used as a work around is to load HRD last. That seemed to work too. Good Luck, Dave, KD2SGM |
|
|
|
Michael Black
Everybody should try using multicast address like 224.0.0.1 now as many programs are starting to share the broadcast data from WSJTX.
toggle quoted message
Show quoted text
HRD, GridTracker, JTAlert, and more. Mike W9MDB On Friday, July 15, 2022 at 12:36:28 PM CDT, Dave KD2SGM <dfreeswick@...> wrote:
Frederick, I, along with many others, had a similar issue with due to the HRD update that included HRD Alert. Seems that HRD grabbed the port normally used to broadcast this info to other programs and was not allowing it to be used by others. In my case N1MM, WSJT-X, and HRD we’re affected. In addition there were quite a few GridTracker folks affected too. My fix was to revert back to a previous version of HRD. Others moved forward and changed the HRD setting to allow multicasting. In addition the port needed to be changed in each program to allow the transfer of data. I believe the one being used is 224.0.0.73. Check the HRD, N1MM, and GridTracker forums, in addition to this one. Search on HRD Alert and you should get quite a bit of information. One other thing you may want to try that I also used as a work around is to load HRD last. That seemed to work too. Good Luck, Dave, KD2SGM |
|
|
|
Kevin Scott Hughes
Where does that go? I'm just starting to figure out "Reporting". Thanks, Kevin, K7KSH
toggle quoted message
Show quoted text
www.reverbnation.com/kevinscotthugheshttp://www.facebook.com/kevinscotthughes3Confidentiality Notice. NOTICE: The information contained in this e-mail and any document attached hereto is intended only for the named recipient(s). It is the property of Kevin Scott Hughes LLC and shall not be used, disclosed or reproduced without the express written consent of Kevin Scott Hughes LLC. If you are not the intended recipient or the employee or agent responsible for delivering this message in confidence to the intended recipient(s)), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me by reply e-mail or telephone 360-435-2044 and immediately delete this message and all its attachments. Thank you, Kevin Scott Hughes On Friday, July 15, 2022 at 11:50:53 AM MDT, Michael Black via groups.io <mdblack98@...> wrote:
Everybody should try using multicast address like 224.0.0.1 now as many programs are starting to share the broadcast data from WSJTX. HRD, GridTracker, JTAlert, and more. Mike W9MDB On Friday, July 15, 2022 at 12:36:28 PM CDT, Dave KD2SGM <dfreeswick@...> wrote: Frederick, I, along with many others, had a similar issue with due to the HRD update that included HRD Alert. Seems that HRD grabbed the port normally used to broadcast this info to other programs and was not allowing it to be used by others. In my case N1MM, WSJT-X, and HRD we’re affected. In addition there were quite a few GridTracker folks affected too. My fix was to revert back to a previous version of HRD. Others moved forward and changed the HRD setting to allow multicasting. In addition the port needed to be changed in each program to allow the transfer of data. I believe the one being used is 224.0.0.73. Check the HRD, N1MM, and GridTracker forums, in addition to this one. Search on HRD Alert and you should get quite a bit of information. One other thing you may want to try that I also used as a work around is to load HRD last. That seemed to work too. Good Luck, Dave, KD2SGM |
|
|
|
@ Alex DH2ID
But it is NOT working with logger32. -- 73 de Daniel, HB9DDS |
|
|
|
Michael Black
You'll have to convince logger32 to add multicast.
toggle quoted message
Show quoted text
Mike W9MDB On Saturday, July 16, 2022 at 03:25:42 PM CDT, HB9DDS <hb9dds@...> wrote:
@ Alex DH2ID But it is NOT working with logger32. -- 73 de Daniel, HB9DDS |
|
|