When it happens can you go into the radio setting and see if TX1 has been set to Disabled?
If so, does resetting it to ENABLED fix the problem.
I had a similar situation a while back and have a work around but want to see if this is the same issue first.
Regards, Al / NN4ZZ
al (at) nn4zz (dot) com
6700 - HW......... V 184.108.40.206
SSDR / DAX...... V 220.127.116.11
CAT................... V 18.104.22.168
I still haven't figured out exactly why I stumble into this from time to time. But my workaround fix is to double check what I have DDUtil doing. I think it's just a DDUtil feature or setting that collides with a saved profile/persistence setting. Sometimes all I need to do is re-toggle OPER/STBY in DDutil.
73, Jay - NO5J
19 RCA 1 DDTG08:053:054;
53 RCA ON DD6TXL0:1;
54 RCA OFF DD6TXL0:0;
I also use this command to allow me to toggle a remote tune with my MFJ-998 when using my amp. I ALWAYS tune using this macro so I never hit the tuner with full power. 17 is the toggle 65 turns off
17 TUNE DDTG04:065:066;
65 TUNE ON DD6TXL0:0;DD6TXT1;
66 TUNE OFF DD6TXT0;DD6TXL0:1;ZZXS0;
DD6TXL0 sets rca off or on DD6TXT sets tune off or on ZZXS turns the XIT off or on
So if I tune on an active freq I first set the XIT to a clear freq and turn it on, hit button 17 and the RCA turns off (therefore shutting off my amp) TUNE turns off, and my tuner will cycle if necessary. I can watch the SWR change if I am running remote. Once tuned I hit 17 again and the TUNE turns off and the RCA turns back on and any XIT I may have engaged is cleared.
I have a third toggle for setting XIT +2
18 XIT+2 DDTG13:073:074;
73 XIT+2 ZZXS1;ZZXG+02000;
74 XIT off ZZXS0;
This one automatically sets the XIT to +2000hz and turns it on, and then turns XIT off when toggled. +2000 is not always clear but quite often it is clear so I don't tune up any anyone. The tuning sequence then becomes: if freq is busy press 18 then 17 then 17 again. If freq clear press 17 then press 17 again, and I never worry about hitting my tuner with too much power.
I had this problem for a short time, happening randomly - at least it seemed so. I don't use DDUtil. It happened with the TX1 being disabled in the setup each time. My guess is that it somehow got into a saved profile after I setup TX2 to handle another box during xmit.
The problem has not reoccurred for some time. I suspect I resaved a problem profile and TX1 has worked perfectly since.
73 Eddy NZ1Q