Date
1 - 5 of 5
Locked Startup missing Wide Graph #Waterfall #Windows10 #install
|
Pete Singleton
Starting WSJTX from the link on the desktop works ok, includes 'Wife Graph'
Auto start by Log4OMv2 - no graph. I can't find any parameter or setting to show the wide graph, maybe I'm squinting in the wrong place. What magic is needed? 73 de M0PTB |
|
|
|
Michael Black
You mean View/Waterfall doesn't work?
toggle quoted message
Show quoted text
Maybe it's off screen? If you hover over the WSJT-X icon do you see the waterfall window? If so, right-click that window, select "Move", the left-click-and-hold and you can drag the window. Mike W9MDB On Tuesday, February 7, 2023 at 11:05:21 AM CST, Pete Singleton <pete.singleton.46@...> wrote:
Starting WSJTX from the link on the desktop works ok, includes 'Wife Graph' Auto start by Log4OMv2 - no graph. I can't find any parameter or setting to show the wide graph, maybe I'm squinting in the wrong place. What magic is needed? 73 de M0PTB |
|
|
|
Pete Singleton
Hi Mike
toggle quoted message
Show quoted text
Thanks for the clue! Yes, after the auto-start there are 2 wsjtx icons overlaid in the taskbar and clicking on the 'other' one brings up the wide-graph as a blank window. Clicking on that brings it to life. Or clicking wsjtx view¦waterfall works too. The graph oddity is only a symptom of a wider problem though. After auto-starting wsjtx, jtalert fails to communicate with it even though the UDP settings in the running wsjtx is exacly the same as what jtalert prompt on the failure. Closing wsjtx and jtalert does NOT clear the problem! I have to close Log4OM (which does the auto-start) as well, then manually starting wsjtx and jtalert works ok. There's obviously some oddity about the wsjtx instance after auto-start. I dunno if it is a wsjtx or Log4OM gremlin? 73 PeteS On 07/02/2023 17:10, Michael Black via groups.io wrote:
You mean View/Waterfall doesn't work? |
|
|
|
Michael Black
That means your LOG4OM settings are wrong.
toggle quoted message
Show quoted text
Please look at JTAlert's directions for Log4OMV2 and and follow them EXACTLY.Remove the Connections entries in Log4OMV2 and re-enter as JTAlert instructs. Mike W9MDB On Wednesday, February 8, 2023 at 10:47:57 AM CST, Pete Singleton via groups.io <pete.singleton.46@...> wrote:
Hi Mike Thanks for the clue! Yes, after the auto-start there are 2 wsjtx icons overlaid in the taskbar and clicking on the 'other' one brings up the wide-graph as a blank window. Clicking on that brings it to life. Or clicking wsjtx view¦waterfall works too. The graph oddity is only a symptom of a wider problem though. After auto-starting wsjtx, jtalert fails to communicate with it even though the UDP settings in the running wsjtx is exacly the same as what jtalert prompt on the failure. Closing wsjtx and jtalert does NOT clear the problem! I have to close Log4OM (which does the auto-start) as well, then manually starting wsjtx and jtalert works ok. There's obviously some oddity about the wsjtx instance after auto-start. I dunno if it is a wsjtx or Log4OM gremlin? 73 PeteS On 07/02/2023 17:10, Michael Black via groups.io wrote: You mean View/Waterfall doesn't work? |
|
|
|
Pete Singleton
Many thanks, Mike.
toggle quoted message
Show quoted text
Followed the instructions and auto-start fires up WSJT-X and JTALERT ok - and they talk to each other. I do try to RTFM but with this problem I couldn't work out which manual and which section. The shy Wide-graph thing is still there though! 73 de M0PTB PeteS On 08/02/2023 16:51, Michael Black via groups.io wrote:
That means your LOG4OM settings are wrong. |
|
|