Date
1 - 12 of 12
JTDX Slow to display callsigns.
G4GIR
Anyone help with another problem?
JTDX is taking up to 10 seconds for callsigns to be displayed in the de-code window and the Decode light remains Blue for the same amount of time.
I tried another Logger 32 configuration for another rig and all is OK.
Any Ideas please.
73 Ian G4GIR |
|
Bob
... and what version of JTDX are you using? SeventyThree(s).
|
|
G4GIR
Hello Bob
I have just set up a new Shortcut from UDP Band Map and it is working fine, but of course lost all the colours etc. So looks like it maybe in a problem in the in the JTDX - TS-990_1.ini file?
Guess I can live with re-building it!!
Ian
|
|
Bob
You might want to scout around and see if you can find a newer version of JTDX. 73.
|
|
Jan <hamlogger@...>
The newest version of JTDX is 2.2.160 RC3
73 Jan PA4JJ Op 8-11-2022 om 18:02 schreef Bob:
-- 73 Jan PA4JJ ______________________________________________________ My dxspider clusters running 24/7 on a raspberry pi 2 pa4jj-2 telnet 77.174.195.163 port 7300 pa4jj-3 telnet 77.174.195.163 port 7388 |
|
Source? The latest I have found so far is only 2.2.159. Thanks. út 8. 11. 2022 v 19:22 odesílatel Jan <hamlogger@...> napsal:
|
|
G4GIR
Hello Jan, do you have a link to that, I can only find 159 too?
73
Ian G4GIR
|
|
NICK K. PLUMIDAKIS
Dear Jan H. Do you know from where can we download that version ??? My best 73's De Nick SV1VS -------- Original message -------- From: Jan <hamlogger@...> Date: 11/8/22 20:22 (GMT+02:00) To: hamlogger@groups.io Subject: Re: [hamlogger] JTDX Slow to display callsigns. 73 Jan PA4JJ Op 8-11-2022 om 18:02 schreef Bob:
-- 73 Jan PA4JJ ______________________________________________________ My dxspider clusters running 24/7 on a raspberry pi 2 pa4jj-2 telnet 77.174.195.163 port 7300 pa4jj-3 telnet 77.174.195.163 port 7388 |
|
G4GIR
Naahh upgraded to the latest I can find but no difference.
The problem is in the INI FILE, with the new config no problem. Been comparing the 2 ini's but what is causing the problem ??? At least I can copy and paste the stuff I need from the bad file to the new file.
Cheers
73
Ian G4GIR
|
|
ja1nlx
Ian I suppose you are talking about BandActivity window in JTDX. If so then find JTDX.ini and delete it. JTDX now starts with it's default settings. If not then ignore my 2 cents. How to find JTDX.ini ? Click File in JTDX menu. Click Open log directory. You see JTDX.ini there. 73 de aki JA1NLX
|
|
Bob
Somewhere along the line I apparently have missed the background to this thread, so I don't know/see the full context. But, for issues related to JTDX performance (within the constraints of your PCs ability to deliver) see section 34.7.6 (Page 677) of the help file. SeventyThree(s).
|
|
G4GIR
Aki/Bob
Thanks for the suggestions, para 34.7.6 sorted it, turned out to be SWL Mode turned on!! Must have accidentally clicked it when erasing the Decode window.
Cheers
73
Ian G4GIR
|
|