radio comes on with transmit on the wrong "vfo"

Stephen Hawkins NG0G

Operating on some band split with DX on A and pileup and transmit on B.  I shut down for the night.  When I power up the next morning everything is as I let it except transmit is now on A.  To get back to how I left it I have to reload the profile.   Much to my embarassment this caused me to inadvertently transmit on the DX stations frequency.  On power up the radio is coming up on the band I was on at shut down and on the same frequencies as if it reloaded the profile but it has moved transmit  to "A", so it clearly did not reload the profile.

W5AP

Stephen Hawkins NG0G

I don't think either of us is doing anything wrong, or that we missed configured something.  I think it is a bug that I would like fixed.

Ken Wells

Global profiles do not automatically load at boot up. They only load when directly commanded to load.

N8SDR

Pat N6PAT

Stephen Hawkins NG0G

The problem is that it looks like it loads the profile.  The band is where  you left it and the two frequencies are exactly where you were.  Everything is the same but the "transmit" is now on "A" instead of "B".

Stephen Hawkins NG0G

The day that I made the original post I was, and am, on V2.6.1.146

Tim - W4TME

If you are operating Split, Slice A is the transmit slice and B is the RX slice.  If you change that up, you have to disable the Split feature.

Stephen Hawkins NG0G

N8SDR

I had an odd thing in 2.6.1 as well on 40 meters working split tRX on A TX on B all was fine I then tried going to 20 meters while the display showed 20 the RX was still 40 it went into cross banding I had to go back to 40 and **** the A slice then back to 20 to get it to work correctly at first I thought perhaps a glitch But since your post I wonder if it is in the new software I stopped using 2.6.1 because the audio drops and BSOD so I can't check it out again

Stephen Hawkins NG0G

Geoff AB6BT

A is one slice and B is another slice. Looks like two slices to me.

Stephen Hawkins NG0G

Geoff AB6BT

Bill -VA3WTB

Stephen Hawkins NG0G

I have a 6400M and Bill your explination was the info I was looking for.   Almost.  If I shut the radio down as it is in the photo above then restart it without reloading the profile it comes up with two working slices / receivers and they are on the frequencies I was using when I shut down.  I can hear on them both independently.  The only thing changed is the fact that the radio moved "TX" from B to A. which is how all this got started.

Bill -VA3WTB

Unless something is telling it change active slice like a profile, then if you make sure you shut down with A as active slice, then when you restart it should start in the same condition you turned it off. If your profile is saved with slice B as active, then it will start like that.

Stephen Hawkins NG0G

The profile is written to start up the radio exactly as you see it on the photo.  Operating split with B slice the TX.  If I shut down the radio exactly as you see it in the photo then in a minute or a day I start it back up it comes up exactly as I left it with two slices and they are on the frequencies I was using when I shut it down.  The only difference is that now "A" has TX not "B" to put it back right I need to reload the profile.  Since at first glance everything looked just as i had left it I did not notice that the radio have moved TX.  So I as mentioned when I started this thread much to my embarrassment this caused me to inadvertently transmit on the DX stations frequency.  

Bill -VA3WTB

Ok, that is an intended action. The software has persistances that remembers how your radio was last used, it calles up the last known state. If you want to reset it to the way a profile was saved then a profile selection is needed. Just need to remember that.

Stephen Hawkins NG0G

The last known state was with TX on "B"  When the radio comes up after a shutdown it comes up in almost the last known state but not quite, for it has changed TX to "A".

Bill -VA3WTB

That sounds like a persistance data base problem. Do a factory reset to clean out the persistance data base, then bring back your profiles. See if this corrects it.

Stephen Hawkins NG0G

OK. I'll give that a shot.   Let me get my HazMat Suit and see if I can find a Windows computer.

Robby

Ken Wells

Check your CAT and N1MM configurations.  You may have the CAT port used for CW sending, or the N1MM program configuration set up to auto-switch to Slice A as default.  If so, then it will automatically send on Slice A because it is being told to do so by the configuration. 

(This is just like using Auto-Switch to link to your FT8 Program that is always on a particular slice to make sure you always send on the designated slice.)

Robby

Ken Wells

Hi Robby. I was actually responding to someone above but it put my post under yours. I had not seen your line about Auto-Switch. It looks like we both came up with the same solution! Have a great day!