Re: [wsjt-devel] VFO-B behavior

2019-03-07 Thread Marco Calistri
Original Message From: John Bastin via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Wednesday, March 6, 2019, 7:52 PM To: WSJT software development Cc: John Bastin Subject: [wsjt-devel] VFO-B behavior > On 5Mar 2019, at 09:40, Marco Cali'stri wrote:

Re: [wsjt-devel] VFO-B behavior

2019-03-06 Thread Neil Zampella
The  WSJT Meteor Scatter and Weak Signal Group is the one you want. Neil, KN3ILZ On 3/6/2019 6:32 PM, John Bastin wrote: On 6Mar 2019, at 18:17, Neil Zampella wrote: The semi-official WSJT support group is on Yahoo groups.The ones on Groups.io are not (as far as I know) offical support g

Re: [wsjt-devel] VFO-B behavior

2019-03-06 Thread John Bastin via wsjt-devel
On 6Mar 2019, at 18:17, Neil Zampella wrote: > > The semi-official WSJT support group is on Yahoo groups.The ones on > Groups.io are not (as far as I know) offical support groups. Which one of these Yahoo groups do you recommend? WSJT-HF Open forum for anyone to post and share information

Re: [wsjt-devel] VFO-B behavior

2019-03-06 Thread Neil Zampella
The semi-official WSJT support group is on Yahoo  groups.    The ones on Groups.io are not (as far as I know) offical support groups. This has always been the development support group, which I do believe was originally used to report bugs, and not for actual program support other than bug issues

Re: [wsjt-devel] VFO-B behavior

2019-03-06 Thread John Bastin via wsjt-devel
On 5Mar 2019, at 09:40, Marco Cali'stri wrote: > as well as for the > possibility to have a separate mailing list dedicated specifically to > WSJT-X usage, in order to let the development topics free of everything > which is not strictly related to programming, Not to be nit-picky, but how many

Re: [wsjt-devel] VFO-B behavior

2019-03-05 Thread Marco Calistri
> > N4EFS > >   > > *From:*Rebecca Milligan [mailto:rebeccamilli...@comcast.net] > *Sent:* Monday, March 4, 2019 6:47 PM > *To:* 'WSJT software development' > *Subject:* RE: [wsjt-devel] VFO-B behavior > >   > > I think it would be difficult for the

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Carey Fisher
Paul, I don't know what's different about your 7300 but mine takes too long switching VFOs to make "rig" a viable option. Fakeit works well though. On Mon, Mar 4, 2019 at 6:10 PM Paul Kube wrote: > " perhaps there should be a note in the User Manual that, at least > for Icom rigs, the 'Fake It'

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Rebecca Milligan
volunteer to be in the group to take some of the burden off the developers. 73, N4EFS From: Rebecca Milligan [mailto:rebeccamilli...@comcast.net] Sent: Monday, March 4, 2019 6:47 PM To: 'WSJT software development' Subject: RE: [wsjt-devel] VFO-B behavior I think it would be dif

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Rebecca Milligan
. 73, Rebecca, N4EFS From: Paul Kube [mailto:paul.k...@gmail.com] Sent: Monday, March 4, 2019 6:07 PM To: marting0...@gmail.com; WSJT software development Subject: Re: [wsjt-devel] VFO-B behavior " perhaps there should be a note in the User Manual that, at least for

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Tag Loomis (Tag)
I have an IC-7300 and I can confirm that VFO-B does not change on band change until TX On Mon, Mar 4, 2019 at 3:10 PM Paul Kube wrote: > " perhaps there should be a note in the User Manual that, at least > for Icom rigs, the 'Fake It' split mode is preferred/recommended?" > > "Rig" mode works f

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Paul Kube
" perhaps there should be a note in the User Manual that, at least for Icom rigs, the 'Fake It' split mode is preferred/recommended?" "Rig" mode works fine with my IC-7200 and IC-7300. 73, Paul K6PO On Mon, Mar 4, 2019 at 1:45 PM Martin Davies G0HDB wrote: > On 4 Mar 2019 at 4:51, Black Micha

Re: [wsjt-devel] VFO-B behavior

2019-03-04 Thread Martin Davies G0HDB
On 4 Mar 2019 at 4:51, Black Michael via wsjt-devel wrote: > Both conditions need to fixed.  VFO-A needs to be set as selected VFO > and VFO-B set to the split freq at all times.  Otherwise a tune > instigated from an external source will be on the wrong frequency.And > yes...I know you can click

Re: [wsjt-devel] VFO-B behavior

2019-03-03 Thread Gary McDuffie
> On Mar 3, 2019, at 13:52, Black Michael via wsjt-devel > wrote: > > On ICOM rigs hamlib assumes split is always on VFOB to cover rigs without > status commands...as does FLRig (and perhaps others). Kenwood is the same way, and I’m not sure I would want to alter that. Gary - AG0N

Re: [wsjt-devel] VFO-B behavior

2019-03-03 Thread Black Michael via wsjt-devel
Both conditions need to fixed.  VFO-A needs to be set as selected VFO and VFO-B set to the split freq at all times.  Otherwise a tune instigated from an external source will be on the wrong frequency.And yes...I know you can click Tune in WSJT-X and then VFO-B gets set...but that leaves the ampl

Re: [wsjt-devel] VFO-B behavior

2019-03-03 Thread Black Michael via wsjt-devel
I'm not talking about altering the split on VFOB behavior. I'm referring to the fact that if VFOB is active on the rig that VFOA does not get set at all.  So having WSJT-X simply make VFOA the active VFO would fix the problem and split would still be on VFOB. Mike On Sunday, March 3, 2019

Re: [wsjt-devel] VFO-B behavior

2019-03-03 Thread Paul Kube
If VFO-B is the active VFO and you switch bands on WSJT-X only VFOB gets set...VFOA does not change.. The same is true if VFO-A is the active VFO; VFO-B does not get set with a band change until you transmit. I just hit WSJT-X's "Tune" button for a second when switching bands. Works fine on the

Re: [wsjt-devel] VFO-B behavior

2019-03-03 Thread Black Michael via wsjt-devel
Also when switching bands should set VFO-B too for split operation if appropriate. Mike On Sunday, March 3, 2019, 2:56:29 PM CST, Black Michael via wsjt-devel wrote: Found an undesirable behavior that I think can be easily fixed. On ICOM rigs hamlib assumes split is always on VFOB to

[wsjt-devel] VFO-B behavior

2019-03-03 Thread Black Michael via wsjt-devel
Found an undesirable behavior that I think can be easily fixed. On ICOM rigs hamlib assumes split is always on VFOB to cover rigs without status commands...as does FLRig (and perhaps others). If VFO-B is the active VFO and you switch bands on WSJT-X only VFOB gets set...VFOA does not change...so