Random "Transmit Slice Has Not Been Selected Message" - Why??

Al Dewey

I've been running with the Version 3.0.19 software on my 6600M  for a couple weeks now and, for the most part, it has behaved OK.  However , today I started getting a "Transmit Slice Has Not Been Selected Message" whenever I try to key the radio.  The RF Power grays out (i.e. from red to gray) and I get no output from the radio.  The RED TX button IS lit on the radio. When I toggle back and forth between the two RED TX buttons, the problem still remains.


When I press the MIC / SPEED button on the 6600M, there is a red message at the bottom of the screen that says "Inhibit: Out-of-band".  However, the frequency appears to be well within the band based on what I am receiving as well as the fact that N1MM is tracking the frequency correctly.


If I power down the radio, it will sometimes work for a while again but after a few minutes, the "Transmit Slice Has Not been Selected" message re-appears and I can no longer transmit.

Any idea why this is happening?  Is there something I can do short of a master reset or a downgrade back to Version 2?

Sure hope to get up and going again by WPX CW in about 10 days.

73,

Al, K0AD

Tim - W4TME

Are you certain there isn't another client connected to your radio?

Al Dewey

Andy - KU7T

Al Dewey

Al Dewey

Tim and Andy;

Another strange things happens which may or may not be related to this problem.

First of all, I restarted the radio and now I do not have the "Transmit Slice Has Not Been Selected" error at least for now.  I am getting ready to try the 1 hour CWT at 10 PM to see how it holds up.

The strange thing is that the MOX light randomly comes on.  The two slices are on 14025 and 7025 and the mode is set to CW.  When the MOX light (randomly) comes on, I notice that when I talk the S meter follows my speech.  It's like someone or something is signed on to my radio and randomly putting it on the air on SSB.   


I temporarily put both slices in SSB mode and note that VOX is NOT checked on either slice.  Yes, if I whistle, the MOX light goes on.  Very confused right now.

73,

AL, K0AD

Al Dewey

Tim - W4TME

If you revert to v2.4.9, you must do a factory reset of the radio because the databases are not downward compatible.  Then you can import your profiles exported from SmartSDR v2.4.9 or below.  Do not import an export made from SmartSDR v3 to a radio running SmartSDR v2.4.9 or below.

N9VC

I learned that the hard way, doing just that. Talk about a
nightmare (self-induced) Went back to version 3 and
decided a couple of quirks were not so bad. As always,
heed the advice from Tim, won't steer you wrong.

73, Jim N9VC

Al Dewey

Tim K9WX

Al Dewey

Thanks, Tim.

I have been playing with this today and have a new theory of why I am having the problem.  Even though I have  both slices configured for CW (on 20 and 40 meters), I was noticing that the MOX light would randomly light on the 6600M  and the problem would happen shortly thereafter.  I am using the FLEX internal WinKeyer.  I determined that the MOX was going on due to the VOX somehow being tripped even though VOX is disabled and both slices are on CW.  If I talked, the MOX light would go on and I would start having the problem.

So as a simple work around, I simply unplugged the microphone while doing SO2R CW. Now I cannot make it fail even with very quick toggling of TX with the CRTL Right and Left Arrows keys in N1MM while sending messages from the F keys.

I also played around with the radio swap time settings in N1MM as KU7T had suggested and it didn't seem to make a difference.  

I probably won't be able to give it a good test until next Wednesday's CWT which is cutting it a bit close for WPX CW next weekend.

73,

AL, K0AD

Tim K9WX

Thanks, Al, that is interesting. I can't say if that was happening with me but if it was (VOX tripping) I did not notice it. I am in Dayton right now but will check this out when I get back home. My radio is a 6600 non-M so there is that difference to take into account.