6400M: non-responsive "A>B" button

  • 1
  • Question
  • Updated 7 months ago
Regarding the "A>B button located between the two VFOs on the "M" series radios: according to the manual, this button copies settings of the A Slice to the B Slice.  In my experience operating a 6400M, pressing this button occasionally works as intended; but far more frequently, pressing the A>B button has absolutely no effect on the slices.  Have others encountered this issue?
Photo of W8QB

W8QB

  • 158 Posts
  • 27 Reply Likes

Posted 7 months ago

  • 1
Photo of mikeatthebeach .

mikeatthebeach .

  • 277 Posts
  • 45 Reply Likes
Yes, it seems to be same here, please report it as a bug
Mike
(Edited)
Photo of W8QB

W8QB

  • 158 Posts
  • 27 Reply Likes
I'm confident Tim will respond to this thread over the coming days.
(Edited)
Photo of Rick  WN2C

Rick WN2C

  • 277 Posts
  • 33 Reply Likes
Mine seems to work but I am still trying to figure out the B VFO as a RIT/XIT when slice B is not active or present.
Photo of Jim K4JAF

Jim K4JAF

  • 341 Posts
  • 91 Reply Likes
Go into the Menu and choose Front Panel, then enable Use VFO Knob for VFO A Rit/Xit.
Photo of Jim K4JAF

Jim K4JAF

  • 341 Posts
  • 91 Reply Likes
Go into the Menu and choose Front Panel, then enable Use VFO Knob for VFO A Rit/Xit.
Photo of W8QB

W8QB

  • 158 Posts
  • 27 Reply Likes
Thanks Jim, but on my radio this did not resolve the problem.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
W8BQ - I cannot reproduce your problem description as provided. 

Here is the behavior I observe and it is 100% reproducible.

If Slice A (VFO A) and Slice B (VFO B) are displayed on different panadapters and they are on different frequencies, pressing the A>B button (short press) the Slice B frequency will change to the Slice A frequency.  

Pressing the A>B button again will have no effect.

-----

If Slice A (VFO A) and Slice B (VFO B) are displayed on different panadapters and they are on different frequencies, pressing the A>B button (short press) the Slice B frequency will change to the Slice A frequency. 

Pressing the A<>B button (long press) will swap the Slice A and B frequenciesPressing the A<>B button again will have no effect.

-----

If Slice A (VFO A) is displayed and Slice B (VFO B) is not displayed and there is only one panadapter shown, pressing the A>B button (short press), a Slice B will be created, offset from Slice A by the frequency offset that is defined for when a slice is created (the amount is dependent on mode). 

Pressing the A>B button (short press) again will make the frequency of Slice A and B equal with Slice B being shown because it was the last slice to change frequency.

-----

If Slice A (VFO A) is displayed and Slice B (VFO B) is not displayed and there is only one panadapter shown, pressing the A>B button (short press), a Slice B will be created, offset from Slice A by the frequency offset that is defined for when a slice is created (the amount is dependent on mode).  

Pressing the A<>B button (long press) will swap the Slice A and B frequencies.
Photo of W8QB

W8QB

  • 158 Posts
  • 27 Reply Likes
Hi Tim.  Your explanation describes four scenarios involving functionality of the A>B button.  For the latter two scenarios, my experience mirrors yours; although for scenarios 1&2, my radio does not perform like yours.  On a related note, page 141 of the user manual notes that "A long press of the A>B button swaps the A Slice and B Slice settings;" but nowhere on page 141--nor anywhere else in the manual--do I find any remark about using a SHORT press to swap the two panadapters.

At this moment I have two panadapters running on my 6400M, one set to 20m, the other to 80m.  When I short-press the A>B button, it has no effect whatsoever.  Likewise as of today, a long-press currently has no effect whatsoever.  This is a mystery, because on several occasions on previous days, the A>B functionality does occasionally work...but not always.  I have submitted a ticket online containing a video to document this curious behavior observed on my 6400M.
(Edited)