|
|
Post by ac1dv on Jan 27, 2024 20:00:46 GMT
After working flawless for months all of a sudden I can never tell if it will continue to send a CQ or even a QSO.. Sometimes it works fine. other times It will send one or two or even 3 CWs than it will stop. It would not respond to a call to me at that time either. If I stare at the screen and keep hitting ENABLE TRANSMIT it will run one or two and may stop. It may just continue to send normally. I have AUTOSEC set at 3. I updated the software I was using and it was fine for a bit but started acting up all over again. Does anyone have any suggestions? This is extremely frustrating.
|
|
|
|
Post by Wolfgang OE1MWW on Jan 27, 2024 20:45:00 GMT
'Autoseq [3] Call based on end of decoding' - what is your 'Lag' info ? If your PC is slow,
this may indicate that you are late in TX most of the time. As you can see, there are 4 differnt
possible settings plus 7 extra options in 'AutoSeq' menu, to adjust for your operation.
So, something on your PC is not OK. There are no known bugs in JTDX for Autoseq.
Either you are fishing RF into your cabling or other details in your System, like timing
may lead to the results you mentioned. (you did not tell us what version of JTDX and what operating
system you are using)
The autoseq is unfortunately not a 100% reproduceable program sequence. Several aspects,
like the reply of the called station to others, timing shifts and other constelation may
change what we expect and what may happen. Btw. same story in WSJT-X and other derivates.
Btw. the myth to un- and re-install does absolutely no help at all. If the JTDX.ini exist,
it will be used after the next install. All the settings are in the JTDX.ini, this file
is not removed or replaced by un-install / re-install.
|
|
|
|
Post by ac1dv on Jan 28, 2024 15:24:38 GMT
I am running JTDXv2.2.159
Windows 7 pro
Also, I don't know if it makes a difference but when I run wsjtx sequencing works perfect all the time.
You asked about Lag Info. Is that something I can look at? Never heard of it.
Txn for helping
|
|
|
|
Post by Wolfgang OE1MWW on Jan 28, 2024 18:39:30 GMT
"Never heard of it." - you have it on the screen ;-)
Move your mouse slowly over the row above the decode window. A pop up with explanations will be shown.
negative Lag = your computer is pretty fast.
positive Lag = your decoding takes longer than the cycle time of 15 seconds
|
|
|
|
Post by Wolfgang OE1MWW on Jan 28, 2024 18:50:25 GMT
many fields in JTDX having this pop-up help - just move slowly the mouse over the fields
on the right side of the screen of JTDX.
|
|
|
|
Post by ac1dv on Jan 29, 2024 17:36:57 GMT
many fields in JTDX having this pop-up help - just move slowly the mouse over the fields on the right side of the screen of JTDX. My Lag is around .03 avg. highest I saw it go was .4 but only briefly. When it went to .4 it was still dropping out like it was with a lower lag time.
I understand what you mean by the computer has problems. It is an old laptop. But it hasn't been changed or altered in any way before this problem started. And the computer is dedicated to strictly this. Nothing else is running on it. Very strange. I am also running FT4 and FT8 and the same problem is there. Now today I'm noticing it will call 3 CQs and stop. I restart it and the same 3 CQs. If someone answers on the 3rd CQ it won't answer unless I hit ENABLE.
I just ran wsjtx for a couple of contacts and just before shutting down went back to JTDX.. It ran perfect. Gotta love computers. Tomorrow it'll probably mess up ad usual. But I switch back to sjtx and back and see.
|
|
|
|
Post by Arvo ES1JA on Jan 29, 2024 19:22:08 GMT
If Enable Tx goes off with no clear reason then enable debug messages to ALLCALL file and there should be explained why Enable Tx is going off.
|
|
|
|
Post by ac1dv on Jan 30, 2024 18:11:36 GMT
If Enable Tx goes off with no clear reason then enable debug messages to ALLCALL file and there should be explained why Enable Tx is going off. How do I do this. I don't see an ALL CALL anything. |
|
|
|
Post by Arvo ES1JA on Jan 30, 2024 20:14:24 GMT
Enable debug here and then look 202401_ALL.TXT file in log dir. Seems JTDX is to complicated.
|
|
|
|
Post by ac1dv on Jan 30, 2024 20:38:32 GMT
Enable debug here and then look 202401_ALL.TXT file in log dir. Seems JTDX is to complicated.
If figures. today it's working fine. But I changed the setting to debug and will look at it the next time it acts up.. Thanks for your patience with me.. |
|
|
|
Post by ac1dv on Jan 31, 2024 19:39:12 GMT
Can you translate what I got? when it stops transmitting a CQ I get .... handle_transceiver_update PTT off split off s.frequency:14080000 s.frequency:0
I have my rig on CAT control test Cat works fine. There is not one thing I can point to to say that is the problem.. It is totally random. It could sequence a few times and stop. It could stop after one transmission..If I make a contact sometimes it sequences right through perfect other times it stops.
A couple of time if I run this program after JSTX it will sequence perfect. Other times it stops random.
|
|
|
|
Post by Arvo ES1JA on Jan 31, 2024 21:54:24 GMT
Jtdx sees that cat reporting tx gone off, like someone has stopped tx from rig. It can be RF destroys computer rig cat connection. Can be also power supply problem.
|
|
|
|
Post by ac1dv on Feb 1, 2024 12:37:01 GMT
Jtdx sees that cat reporting tx gone off, like someone has stopped tx from rig. It can be RF destroys computer rig cat connection. Can be also power supply problem. You mentioned power supply. Are you referring to the Rigs power supply. I recently had to replace the bridge rectifier in mine. And come to think of it, not sure, it's only been after that that the problem started. |
|
|
|
Post by Arvo ES1JA on Feb 1, 2024 18:07:04 GMT
Yep I ment rigs power supply. If it is power supply problem, then dropping rigs power to ~50% of max should remove problem.
|
|
|
|
Post by ac1dv on Feb 2, 2024 14:54:28 GMT
Yep I ment rigs power supply. If it is power supply problem, then dropping rigs power to ~50% of max should remove problem. After running some tests pretty sure that isn't the problem. I'm running 10 watts. It's a 20 Amp supply. It runs a 2 meter rig transmitting 60 and AM on 80meter at 100 watts. Plus. it does start operating fine after a while. What is really crazy is I have no problem with the exact set up using wsjt-X. AND... if I use that software for a bit and than turn on jtdx than it seems to run normal; sometimes after a few transmissions. |
|
