After upgrading to 3.6.5, I discovered that the LHR command does not work (no data is sent). In addition, any further text sent by the station I am in QSO with is not displayed, and no "WD4XXX is typing" box appears.
Cold booting the Win 10 Pro system did not fix the issue.
The VARA-HF modem seems to be working properly, as I can hear my side acknowledge received data (I was testing with a station 5 miles away).
73, Joe
I am not sure I follow. you send LHR or the other side send you ? and after this your side is not showing anymore incoming traffic ? can you please describe in more details ?
Sorry for the confusion, Irad. The other station sent <.LHR> which printed on my screen. My station did not respond.
The other station sent some additional text over the next few minutes, and nothing showed on my screen, but I heard VARA-HF ACKing the received data. (I always have the receiver volume up just high enough to hear traffic, including my transmitted signal. This was a habit I developed waaaay back in the days of HF Packet, HI).
Text *I* sent to him appeared in the top window, as expected.
... Joe
Ok. understood. Thank you !
can you please send me the VarAC_last_heard.log ?
please let me know if it is consistent
if it happens again - please send me :
a screenshot
VarAC.log
VarAC_last_heard.log
Here you go.
Both QSO log (first), and Last Heard Log
26/04/2022 23:39:44 - N7TES> Well - I will install the new update today. BTW - I saw your name on the Ham Radio Course YouTube this weekend. Josauh was talking about this app. I need to confirgure for a monitor panel as he deminstated.
26/04/2022 23:40:15 - N7TES> <LHR>
26/04/2022 23:40:39 - WD4KAV> hihi I also did a connect to him after the show was over, and we chatted for a bit.
26/04/2022 23:40:53 - WD4KAV> send the lhr again
26/04/2022 23:42:07 - WD4KAV> not seeing any print now from you ??
26/04/2022 23:42:55 - WD4KAV> Let me re-connect.
26/04/2022 23:43:04 - DISCONNECTED FROM N7TES
26/04/2022 23:43:18 - CONNECTED TO N7TES
26/04/2022 23:43:34 - WD4KAV> de WD4KAV <R+17>
26/04/2022 23:44:42 - WD4KAV> Something is foo-bar. I hear your tones, but no text on screen. I'm going to re-install previous version after I check for any additional update to the latest version.
26/04/2022 23:45:19 - DISCONNECTED FROM N7TES
26/04/2022 23:50:08 - INCOMING CONNECTION REQUEST.. Hold tight!
26/04/2022 23:50:20 - CONNECTED TO N7TES
26/04/2022 23:50:28 - WD4KAV> Hello!
<NAME:Joe>
<QTH:Puyallup, WA>
<LOC:CN87tc><SND>
Be right with you..... de WD4KAV
26/04/2022 23:50:44 - N7TES> de N7TES <R+16>
I just installed v3.6.5
26/04/2022 23:50:51 - WD4KAV> <R+14>
26/04/2022 23:50:55 - N7TES> NAME:John
QTH:Puyallup, WA
LOC:CN87td>
26/04/2022 23:51:02 - WD4KAV> Back on version 3.5 Do that LHR command again.
26/04/2022 23:51:19 - N7TES> <LHR>
26/04/2022 23:51:52 - WD4KAV> Odd... no response. Wonder what the deal is?
26/04/2022 23:52:46 - WD4KAV> Let me disconnect and make sure that it is still enabled.
26/04/2022 23:53:28 - WD4KAV> Better yet, let me cold boot the win 10 pro pc and start over. No data from you at all.
26/04/2022 23:59:05 - CONNECTED TO N7TES
26/04/2022 23:59:12 - N7TES> ok
de N7TES
26/04/2022 23:59:21 - WD4KAV> de WD4KAV <R+10>
26/04/2022 23:59:27 - N7TES> <R+11>
26/04/2022 23:59:38 - WD4KAV> <QSYD>
27/04/2022 00:00:42 - WD4KAV> On 3.6.5 now
27/04/2022 00:00:47 - N7TES> NAME:John
QTH:Puyallup, WA
LOC:CN87td>
27/04/2022 00:01:10 - N7TES> Good copy at my end.
27/04/2022 00:01:24 - WD4KAV> <NAME:Joe>
<QTH:Puyallup, WA>
<LOC:CN87tc>
27/04/2022 00:01:28 - N7TES> I'm also on v3.6.5
27/04/2022 00:01:56 - WD4KAV> Try Last Heard Peeking
27/04/2022 00:02:07 - N7TES> ok
27/04/2022 00:02:14 - N7TES> <LHR>
27/04/2022 00:02:31 - WD4KAV> Nothing.....
27/04/2022 00:03:49 - WD4KAV> Same issue now. I hear your tones, but nothing printing here. No "N7TES is typing" either. Think I will submit a bug report.
27/04/2022 00:04:24 - DISCONNECTED FROM N7TES
LAST HEARD LOG
2022-04-26,BEACON,20m,22:50,W4HTP,500,-05
2022-04-26,BEACON,20m,22:51,W6VRF,500,-06
2022-04-26,CQ,20m,22:51,K5KWG,500,-21
2022-04-26,CQ,40m,23:26,N7TES,500,+01
2022-04-26,CQ,40m,23:27,N7TES,500,+02
2022-04-26,CQ,40m,23:27,N7TES,500,-0
Addendum: I had a station send the LHR command today while I was running version 3.5 and it worked as expected. Will wait on 3.6 till I see what you suggest.
7i3, Joe
I need to see the VarAC.log. if it failed - there is a clue there in a form of exception. Send me the log file to my email and I will look in the timeframe of the event to see what went wrong. seems like a corrupted LH entry that caused that. Please also send me by mail the ENTIRE last heard log file as I asked. In need those 2 files :
VarAC.log
VarAC_last_heard.log
send them please to my email iradirad@gmail.com
Unable to reproduce. will keep this bug open for now. LMK if it happens again.
If it does - it is most likely a bad record in the LH file and I need you to send the last 200 records of your file (best to send all). the LHR method scans the last rows one by one and parse them. if a line is corrupted it may fail the whole process.
Ok, Irad. THANKS for looking into into that glitch.
73!