Date   
Re: QCX(-like) for 2m #alignment #vfo By Braden Glett · #37611 ·
Re: QCX/QSX Elmering and Discussion By Keith Laaks · #37612 ·
Re: Persistence seems lacking... By Fred Piering · #37613 ·
Re: Persistence seems lacking... By James Daldry W4JED · #37614 ·
Re: Persistence seems lacking... By James Daldry W4JED · #37615 ·
Re: #clock PROBLEM Clock C.1.03 firmware #firmware #clock By Hans Summers · #37616 ·
Re: #clock PROBLEM Clock C.1.03 firmware #firmware #clock By Art N4EZZ · #37617 ·
Re: #clock PROBLEM Clock C.1.03 firmware #firmware #clock By Rick Williams - VE7TK · #37618 ·
Re: #clock PROBLEM Clock C.1.03 firmware #firmware #clock By Art N4EZZ · #37619 ·
Re: Persistence seems lacking... By Fred Piering · #37620 ·
Re: Clock kit: new firmware version 1.03 By Dean Smith · #37621 ·
Re: #clock PROBLEM Clock C.1.03 firmware #firmware #clock By Rick Williams - VE7TK · #37622 ·
Re: Clock kit: new firmware version 1.03 By Hans Summers · #37623 ·
Re: Clock kit: new firmware version 1.03 By Dean Smith · #37624 ·
Re: Persistence seems lacking... By Shirley Dulcey KE1L · #37625 ·
Re: Clock kit: new firmware version 1.03 By Hans Summers · #37626 ·
Re: Persistence seems lacking... By Bill Cromwell · #37627 ·
Re: Persistence seems lacking... By Bob Macklin <macklinbob@...> · #37628 ·
Re: Persistence seems lacking... By ajparent1/KB1GMX · #37629 ·
Re: Persistence seems lacking... By Graham, VE3GTC · #37630 ·