I had a hard time seeing the windows that you used but I think I have notes that I can use to make it work. thanks for this video I really needed this info. Jim
Yeah, sorry. We kinda thought it was simple. There's one box to check in HRD Logbook. But the difficult part ends up being knowing what to change in all the other applications.
Mike, I performed all the steps as indicated, and selected the new RADIO as HamRadioDeluxe as mentioned in the user comments. All seemed ok but I had NO TRANSMIT. I played around and solved it by updateing the WSJT-X RADIO Settings: Uncheckd PTT Method RTS, and checked CAT and it solved the problem.
Thanks for taking the time to do this video. I have been using HRD, WSJTX, and GridTracker together for almost 2 weeks now and it’s working great. I am not really sure what the JTAlert software you have here is supposed to be doing that is not already being done. Should I be using it for something? What is it adding that is not already in the HRD Alert? Sorry if it’s obvious, I’m only 2 weeks in on doing the FT8.
This helped out a ton, thank you. One question, as of 2023-0219 and newest versions of all, Around the 4:50 mark you talk about QSO Forwarding...I can check the top 2 under UDP RECEIVE, then the Receive QSO Notificatlion, but when I change the Port and Target Database, the OK option is grayed out and nothing changes. Is this normal for the newer versions? Thanks for making sucha a great product. Was a bit overwhelming at first, but now I'm comfortable with it.
Hi, I have learned a lot from this video, thank you ! As far as I see my settings are all correct on both sides, but my QSO-s in WSJT-X are not going over to HRD. The band activity is well displayed in HRD as you show in your setup. What am I missing here ?? My laptop has no Ethernet connection btw.
havent' totally finished this, but it is a bit confusing. i think it's confusing because the menu selection and choices happen and many times there is no showing or words on how they got there. but i appear to have the program working - now i need to finish the last 2 minutes of the video and see what else i should do/set. thank you all, you got me way over the hump.. these hrd alerts ARE WAY COOL
Thanks both, I needed that! Two quick points, do you need to prefix the presentation to mention that HRD was selected as the rig in WSJT-X for those who might not know. Secondly, can you use a mouse pointer that has a halo round it please, as others have said, trying to see where you are clicking means looking for the appearance of a drop down box somewhere on the screen. Thanks again - Terry
Right. But if you aren't interested in the New Features & Support... you can still run the software. One of these days, we hope to offer a new feature that appeals to you.
Sad to say, I went back to the original config as I had too many issues with HRD with WSJT-X and Grid Tracker. I keep getting out-of-memory errors, updating the log took about 5 minutes per entry update/change; things really slowed down so much that it wasn't useful. I also had strange issues like WSJT-X txing in JT65 when it should have been FT8 or switching to FT4 when I changed bands. Strange and I don't know if it is becuase I am using the WSJT-X beta version or not. But, the beta works fine when it is not tied to HRD. Overall; It is typical for me to troubleshoot configurations till it gets to the point of frustrating--- when it is no longer fun--- then I box up the problem an put it in the closet for another day; if that day ever comes. I read so much in the manuals and forums and truly love the UA-cam videos; it shows me where I go wrong most of the time. Hoever, even after all the research and HRD teamviewing into my system, HRD was never able to solve the CW TX buffer problem that exists when sending long strings within Digital Master to ICOM radios. Anything over (I think it was 54 charactors) is truncated and dropped. My Yaesu doesn't do this but my 7300, 9700, and 7610 all have the problem. I think either slowing down the data flow to the radio, or using some sort of hand shake where a chunk of data is sent, a pause, then more data. I just stopped using it like the Multicasting issue I am experiencing. I continue to renew my annual HRD subscription just the same... Cheers.
Thanks for the feedback. I think the answer in the end is that all applications need to flip to multi-casting and we stop trying to use the broadcast port. That'll sovle the majority of the issues between WSJT-X (and other programs) and loggers. As for the CW TX buffer... I'll make sure that's on the list.
So I've had a weird thing happen sometimes.. Have an IC7300 and it works like it's supposed to.. mostly.. But with using the HRD to control the rig, sometimes on ft8 it gets 'confused' when transmitting. What i mean is you can hear the radio fan kick up like it's transmitting, but there is no power going out on the meters and it shows 'usb' instead of 'usb-d' when transmitting.. If you halt tx then enable it again in wsjt-x, it's fine again... until it decides to do it again... Anyone have any clues at all?
I'm having difficulty with this. I'm sending logbook broadcasts from two other machines on the LAN. I assume it is an issue with Windows Firewall blocking the UDP broadcasts. Do you have any guidance on configuring the Windows 10 firewall?
I really LOVE the three programs all tied together but I keep getting (OUT OF MEMORY) with the logbook. I run WSJT-X 24/7; it is out of memory after a couple of hours. Please help with a fix. Thank you guys so much!
You can search our support pages for "the problems with Access" and it will give you some guidance. Or if you're a support customer, a member of the team can solve this for you.
Just so I'm clear, will HRD decode only stations that are configured to alert? I read this on the HRD site, and want to be clear if HRD will, or will not simply decode all traffic?
HRD Alert isn't doing the decoding. It's only displaying the decoding that's collected by something else (like WSJT-X, etc). So if you've set that "something else" to "decode all traffic", then that's what you can display.
I tried this with WSJT-X, JTAlert and HRD log it was all working but was logging twice. So I turned off QSO forwarding and HRD Alert quit. Well got it going but then the whole logging program quit saying not responding. This is not worth the headache so I'm setting it all back up the way i had it and use the log. Don't need HRD alert when I have JT Alert anyway. Oh by the way I tried to put in a ticket at Technical Support and the link does nothing!
When using multiple applications to receive decodes from WSJT-X, one must use the multicast opions in all receiving applications and in WSJT-X. It's a networking requirement and not within our control.
I am using WIN11, Latest HRD, Grid Tracker and wjstx. CAN NOT GET GRID TRACKER to communicate with wjstx. All seems to be configured correctly. HELP 73 Jon NQ4A
@@HamRadioDeluxe In the QSO forwarding and drop down, I don't have the "override" only ignore and merge. Also, there are still times (My dads PC setup is the same), we still have to open logbook after JTAlert/WSJT-x.
When you set things up per this video, you will get double entries in Logbook . . . Submitted a ticket and HRD advised to turn off QSO Forwarding in Logbook. That seemed to correct the double entries . . . they should append this video . . .
If you have two programs sending QSOs to the log, you'll get double entries. So you would choose to have the QSOs come from JTAlert into Logbook... or WSJT-X into Logbook. But if you do both, you'll get double entries. FWIW - if you take the QSO directly from WSJT-X into Logbook, the full callsign lookup logic in Logbook runs and it gives you more complete information than you'd get just from taking it from other sources.
I agree with most all below comments. I have hearing and poor vision. It's now been dozens of attempts for me this past two days piecing some parts of this presentation. Even understanding the very first instruction has failed me. Mike please get someone who speaks clearly, with a microphone in front of them, LARGER camera views. I have tried for two years to run this program and given up until now. and have succeeded finally to get FT8 logged entries to show on your logbook. Guess that's success. Sorry for the downer but I've constantly updated every notice but never have be successful EXCEPT for seeing your logbook populate 10 entries. The 5500 LOTW QSO/QSL NEVER GOT THE PLEASURE AS THE 10 FROM THIS MORNING. oH WELL BACK TO THE PROGRAM AND REPLAYS..
Thanks. I have a pro-audio Audio Technica ATR2500x microphone that sits right in-front-of my face during these recordings. We don't use a camera for creating the videos. We use Camtasia to record the screen. I'll apply the zoom more often. Thanks.
Dont matter how many times that I watch this video I cant get it to work just even loading stations into Alert let alone logging. I am giving up, not wasting any more of my life, its manual logging for me
I had a hard time seeing the windows that you used but I think I have notes that I can use to make it work. thanks for this video I really needed this info. Jim
Glad it helped!
Thanks finally worked . This is exactly what we need Mike more video like this on how to do stuff ! Good job 👍
Yeah, sorry. We kinda thought it was simple. There's one box to check in HRD Logbook. But the difficult part ends up being knowing what to change in all the other applications.
Yeah that loop option i didn’t even know about that ! Anyways all good 👍 thanks again
Excellent!!! Had to watch and replay several parts--but it is now al working!
Excellent!
Thank you - this was really helpful !
You're welcome!
Thanks again..
Always welcome!
Mike, I performed all the steps as indicated, and selected the new RADIO as HamRadioDeluxe as mentioned in the user comments. All seemed ok but I had NO TRANSMIT. I played around and solved it by updateing the WSJT-X RADIO Settings: Uncheckd PTT Method RTS, and checked CAT and it solved the problem.
How are you handling PTT?
This is exactly the information I needed.
Thank you. 73.
Glad it was helpful!
That worked - thank you - M7CCZ
You're welcome!
Thanks for taking the time to do this video. I have been using HRD, WSJTX, and GridTracker together for almost 2 weeks now and it’s working great. I am not really sure what the JTAlert software you have here is supposed to be doing that is not already being done. Should I be using it for something? What is it adding that is not already in the HRD Alert? Sorry if it’s obvious, I’m only 2 weeks in on doing the FT8.
This helped out a ton, thank you. One question, as of 2023-0219 and newest versions of all, Around the 4:50 mark you talk about QSO Forwarding...I can check the top 2 under UDP RECEIVE, then the Receive QSO Notificatlion, but when I change the Port and Target Database, the OK option is grayed out and nothing changes. Is this normal for the newer versions? Thanks for making sucha a great product. Was a bit overwhelming at first, but now I'm comfortable with it.
Hi, I have learned a lot from this video, thank you !
As far as I see my settings are all correct on both sides, but my QSO-s in WSJT-X are not going over to HRD. The band activity is well displayed in HRD as you show in your setup.
What am I missing here ?? My laptop has no Ethernet connection btw.
havent' totally finished this, but it is a bit confusing. i think it's confusing because the menu selection and choices happen and many times there is no showing or words on how they got there. but i appear to have the program working - now i need to finish the last 2 minutes of the video and see what else i should do/set. thank you all, you got me way over the hump.. these hrd alerts ARE WAY COOL
Thanks both, I needed that! Two quick points, do you need to prefix the presentation to mention that HRD was selected as the rig in WSJT-X for those who might not know. Secondly, can you use a mouse pointer that has a halo round it please, as others have said, trying to see where you are clicking means looking for the appearance of a drop down box somewhere on the screen. Thanks again - Terry
I'll add a comment about the selection of rig in WSJT-X. I'll try to highlight the mouse pointer in the future.
Right. But if you aren't interested in the New Features & Support... you can still run the software. One of these days, we hope to offer a new feature that appeals to you.
Sad to say, I went back to the original config as I had too many issues with HRD with WSJT-X and Grid Tracker. I keep getting out-of-memory errors, updating the log took about 5 minutes per entry update/change; things really slowed down so much that it wasn't useful. I also had strange issues like WSJT-X txing in JT65 when it should have been FT8 or switching to FT4 when I changed bands. Strange and I don't know if it is becuase I am using the WSJT-X beta version or not. But, the beta works fine when it is not tied to HRD. Overall; It is typical for me to troubleshoot configurations till it gets to the point of frustrating--- when it is no longer fun--- then I box up the problem an put it in the closet for another day; if that day ever comes. I read so much in the manuals and forums and truly love the UA-cam videos; it shows me where I go wrong most of the time. Hoever, even after all the research and HRD teamviewing into my system, HRD was never able to solve the CW TX buffer problem that exists when sending long strings within Digital Master to ICOM radios. Anything over (I think it was 54 charactors) is truncated and dropped. My Yaesu doesn't do this but my 7300, 9700, and 7610 all have the problem. I think either slowing down the data flow to the radio, or using some sort of hand shake where a chunk of data is sent, a pause, then more data. I just stopped using it like the Multicasting issue I am experiencing. I continue to renew my annual HRD subscription just the same... Cheers.
Thanks for the feedback. I think the answer in the end is that all applications need to flip to multi-casting and we stop trying to use the broadcast port. That'll sovle the majority of the issues between WSJT-X (and other programs) and loggers. As for the CW TX buffer... I'll make sure that's on the list.
So I've had a weird thing happen sometimes.. Have an IC7300 and it works like it's supposed to.. mostly.. But with using the HRD to control the rig, sometimes on ft8 it gets 'confused' when transmitting. What i mean is you can hear the radio fan kick up like it's transmitting, but there is no power going out on the meters and it shows 'usb' instead of 'usb-d' when transmitting.. If you halt tx then enable it again in wsjt-x, it's fine again... until it decides to do it again... Anyone have any clues at all?
I'm having difficulty with this. I'm sending logbook broadcasts from two other machines on the LAN. I assume it is an issue with Windows Firewall blocking the UDP broadcasts. Do you have any guidance on configuring the Windows 10 firewall?
No matter whose software you're using, you can't send this data across a LAN.
I really LOVE the three programs all tied together but I keep getting (OUT OF MEMORY) with the logbook. I run WSJT-X 24/7; it is out of memory after a couple of hours. Please help with a fix. Thank you guys so much!
You can search our support pages for "the problems with Access" and it will give you some guidance. Or if you're a support customer, a member of the team can solve this for you.
Just so I'm clear, will HRD decode only stations that are configured to alert? I read this on the HRD site, and want to be clear if HRD will, or will not simply decode all traffic?
HRD Alert isn't doing the decoding. It's only displaying the decoding that's collected by something else (like WSJT-X, etc). So if you've set that "something else" to "decode all traffic", then that's what you can display.
I tried this with WSJT-X, JTAlert and HRD log it was all working but was logging twice. So I turned off QSO forwarding and HRD Alert quit. Well got it going but then the whole logging program quit saying not responding. This is not worth the headache so I'm setting it all back up the way i had it and use the log. Don't need HRD alert when I have JT Alert anyway. Oh by the way I tried to put in a ticket at Technical Support and the link does nothing!
When using multiple applications to receive decodes from WSJT-X, one must use the multicast opions in all receiving applications and in WSJT-X. It's a networking requirement and not within our control.
I am using WIN11, Latest HRD, Grid Tracker and wjstx. CAN NOT GET GRID TRACKER to communicate with wjstx. All seems to be configured correctly. HELP 73 Jon NQ4A
Search our support site for "multicasting" and you'll find the instructions for making this all work.
I have to start WSJT-x and JTAlert first and then logbook or HRD Alerts do not work. KL7TC
Then something is skipped in the config...
Like UDP forwarding in JTAlert around minute 6 in the video
@@AstroHAM I watched again, i think it's working now. Thank you.
Excellent teamwork!
@@HamRadioDeluxe In the QSO forwarding and drop down, I don't have the "override" only ignore and merge. Also, there are still times (My dads PC setup is the same), we still have to open logbook after JTAlert/WSJT-x.
@@Bill_KL7TC We're getting rid of override, ignore, and merge. Choose merge for now. It only affects what happens to YOUR grid in the QSO stream.
When you set things up per this video, you will get double entries in Logbook . . . Submitted a ticket and HRD advised to turn off QSO Forwarding in Logbook. That seemed to correct the double entries . . . they should append this video . . .
If you have two programs sending QSOs to the log, you'll get double entries. So you would choose to have the QSOs come from JTAlert into Logbook... or WSJT-X into Logbook. But if you do both, you'll get double entries. FWIW - if you take the QSO directly from WSJT-X into Logbook, the full callsign lookup logic in Logbook runs and it gives you more complete information than you'd get just from taking it from other sources.
@@HamRadioDeluxe The video should be corrected then . . . .
View, HD Alerts, Settings....
Dear god bless you…. I couldn’t even follow clicks
Good catch.
I agree with most all below comments. I have hearing and poor vision. It's now been dozens of attempts for me this past two days piecing some parts of this presentation. Even understanding the very first instruction has failed me. Mike please get someone who speaks clearly, with a microphone in front of them, LARGER camera views. I have tried for two years to run this program and given up until now. and have succeeded finally to get FT8 logged entries to show on your logbook. Guess that's success. Sorry for the downer but I've constantly updated every notice but never have be successful EXCEPT for seeing your logbook populate 10 entries. The 5500 LOTW QSO/QSL NEVER GOT THE PLEASURE AS THE 10 FROM THIS MORNING. oH WELL BACK TO THE PROGRAM AND REPLAYS..
Thanks. I have a pro-audio Audio Technica ATR2500x microphone that sits right in-front-of my face during these recordings. We don't use a camera for creating the videos. We use Camtasia to record the screen. I'll apply the zoom more often. Thanks.
Dont matter how many times that I watch this video I cant get it to work just even loading stations into Alert let alone logging. I am giving up, not wasting any more of my life, its manual logging for me
Contact support and someone will help you configure this.
@@HamRadioDeluxe I am booked in with Kevin on Tuesday he is going to do a remote, hope he can sort it that way.
Kevin fixed it via remote, I am pleased its now working. Many thanks to Kevin.
ou are blowing through the click on options like you think everyone already knows exactly where they are.