Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work
Try: sudo apt install libgfortran3 On Mon, May 11, 2020 at 11:53 AM David Spoelstra wrote: > As a follow-on, I did install "gfortran": sudo apt install gfortran and > got this: > Reading package lists... Done > Building dependency tree > Reading state information... Done > gfortran is already the newest version (4:9.3.0-1ubuntu2). > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it is > not installable" when I try and install wsjt-x > > Thanks! > -David, N9KT > > > On Mon, May 11, 2020 at 2:16 PM David Spoelstra > wrote: > >> When I tried to install in the latest Ubuntu 20.04 LTS, I got: >> The following packages have unmet dependencies: >> wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable >> >> When I try "sudo apt install libgfortran3" I get: >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> E: Unable to locate package libgfortran3 >> >> I'm a little lost as to how to get libgfortran3. Any suggestions? >> >> Thanks! >> -David, N9KT >> >> ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] NetworkMessage request
Rgr that, sorry :) this thread has been dormant for exactly a year so confused, heh Hoping some one from dev team would get back to me one way or another on my request On Tue, Feb 25, 2020 at 3:11 PM Sam W2JDB via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Tag, > > Sorry, I was addressing this to Mike as he mentioned "some of us with > poorer eyesight". > > 73, > > Sam W2JDB > > > > -Original Message- > From: Tag Loomis (Tag) > To: WSJT software development > Sent: Tue, Feb 25, 2020 6:02 pm > Subject: Re: [wsjt-devel] NetworkMessage request > > I don’t see the relevance to my question :) > > In the wrong thread maybe? > > On Tue, Feb 25, 2020 at 2:54 PM Sam W2JDB via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > Hi Mike, > > If you are visually impaired, you may want to contact Rich K1HTV regarding > a companion program called QLog that I developed and enhanced for blind ops > to use with WSJT-X. It is Windows only. It has a local QSO database that > you can import all your previous QSOs You can export new QSOs. I will log > all WSJT-X QSOs and automatically uploads those QSOs to QRZ, Clublog and > EQSL if you are a member of those organization. It announces all > progression and it identifies the station and grid that you are > calling/working. It even has an optional built in internet time sync > function. You can call CQ, Call a station, filter replies and participate > in the special events in WSJT-X without the need to create new log files to > eliminate dupes. The program is free. > > Bill and Joe are aware of this program that I built for the blind ham > community. > > 73, > > > Sam W2JDB > > > > -Original Message- > From: Sam L Kloberdanz > To: WSJT software development > Sent: Tue, Feb 25, 2020 5:24 pm > Subject: Re: [wsjt-devel] NetworkMessage request > > I’ll have to call tomorrow, I’m hung for the rest of the day.. > > > Sam > N0GTO > > On Feb 25, 2020, at 2:11 PM, Tag Loomis (Tag) > wrote: > > Just over a year now and no reply.. > > Could we be notified at a bare minimum if Tx 6 is being transmitted and > its contents are in the existing status message or a new one? > > Author of GridTracker > - Stephen "Tag" Loomis / N0TTL > > On Mon, Feb 25, 2019 at 6:50 PM Mike Maynard wrote: > > Bill, > > From what I can tell, it looks like Stephen is just trying to get the > actual currently transmitting packet. This would be an operational aid - > for example: It would allow a developer the ability to create a status > screen that is much easier to see (maybe larger type? different > contrasting colors, etc). > > Obviously it would not allow for any change in QSO progression. That > would still require direct intervention with WSJT. > > In my setup... I have a keypad that I programmed to set the QSO > progression using hot-keys. the screen I run WSJT on is a little hard to > read at a glance. It takes time to focus on it where it is. Sure I could > adjust my resolution, but then I lose space on the screen for other things. > > A larger display of current WSJT status could be a welcome option to some > of us* with poorer eyesight.* Enabling such a UDP packet would allow > such development to happen. > > Thanks > Mike > > On Thu, Feb 21, 2019 at 4:39 PM Bill Somerville > wrote: > > On 21/02/2019 21:02, Tag Loomis wrote: > > First time message to the group. > > Would it be possible to have the current transmitting message be emitted > in either in the Status Out message after “Special operation mode (quint8)” > as utf8 *OR* a brand new message type? > > If it’s already present and I’m just not seeing it, any pointer would be > great! > > Thank you for your time! > > Stephen Loomis / N0TTL / GridTracker developer. > > Hi Stephen, > welcome to the group. > The WSJT-X UDP protocol is meant to aid the WSJT-X operator but with the > expectation that QSOs will be progressed from with WSJT-X by user > interaction with the software. Because of that a message that echoes the > current outgoing message doesn't seem to add any value. Can you please > explain in detail how such a message would be used? > 73 > Bill > G4WJS. > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > Mike > K2GC > www.k2gc.net > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___
Re: [wsjt-devel] NetworkMessage request
I don’t see the relevance to my question :) In the wrong thread maybe? On Tue, Feb 25, 2020 at 2:54 PM Sam W2JDB via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Mike, > > If you are visually impaired, you may want to contact Rich K1HTV regarding > a companion program called QLog that I developed and enhanced for blind ops > to use with WSJT-X. It is Windows only. It has a local QSO database that > you can import all your previous QSOs You can export new QSOs. I will log > all WSJT-X QSOs and automatically uploads those QSOs to QRZ, Clublog and > EQSL if you are a member of those organization. It announces all > progression and it identifies the station and grid that you are > calling/working. It even has an optional built in internet time sync > function. You can call CQ, Call a station, filter replies and participate > in the special events in WSJT-X without the need to create new log files to > eliminate dupes. The program is free. > > Bill and Joe are aware of this program that I built for the blind ham > community. > > 73, > > > Sam W2JDB > > > > -Original Message- > From: Sam L Kloberdanz > To: WSJT software development > Sent: Tue, Feb 25, 2020 5:24 pm > Subject: Re: [wsjt-devel] NetworkMessage request > > I’ll have to call tomorrow, I’m hung for the rest of the day.. > > > Sam > N0GTO > > On Feb 25, 2020, at 2:11 PM, Tag Loomis (Tag) > wrote: > > Just over a year now and no reply.. > > Could we be notified at a bare minimum if Tx 6 is being transmitted and > its contents are in the existing status message or a new one? > > Author of GridTracker > - Stephen "Tag" Loomis / N0TTL > > On Mon, Feb 25, 2019 at 6:50 PM Mike Maynard wrote: > > Bill, > > From what I can tell, it looks like Stephen is just trying to get the > actual currently transmitting packet. This would be an operational aid - > for example: It would allow a developer the ability to create a status > screen that is much easier to see (maybe larger type? different > contrasting colors, etc). > > Obviously it would not allow for any change in QSO progression. That > would still require direct intervention with WSJT. > > In my setup... I have a keypad that I programmed to set the QSO > progression using hot-keys. the screen I run WSJT on is a little hard to > read at a glance. It takes time to focus on it where it is. Sure I could > adjust my resolution, but then I lose space on the screen for other things. > > A larger display of current WSJT status could be a welcome option to some > of us with poorer eyesight. Enabling such a UDP packet would allow such > development to happen. > > Thanks > Mike > > On Thu, Feb 21, 2019 at 4:39 PM Bill Somerville > wrote: > > On 21/02/2019 21:02, Tag Loomis wrote: > > First time message to the group. > > Would it be possible to have the current transmitting message be emitted > in either in the Status Out message after “Special operation mode (quint8)” > as utf8 *OR* a brand new message type? > > If it’s already present and I’m just not seeing it, any pointer would be > great! > > Thank you for your time! > > Stephen Loomis / N0TTL / GridTracker developer. > > Hi Stephen, > welcome to the group. > The WSJT-X UDP protocol is meant to aid the WSJT-X operator but with the > expectation that QSOs will be progressed from with WSJT-X by user > interaction with the software. Because of that a message that echoes the > current outgoing message doesn't seem to add any value. Can you please > explain in detail how such a message would be used? > 73 > Bill > G4WJS. > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > Mike > K2GC > www.k2gc.net > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] NetworkMessage request
Just over a year now and no reply.. Could we be notified at a bare minimum if Tx 6 is being transmitted and its contents are in the existing status message or a new one? Author of GridTracker - Stephen "Tag" Loomis / N0TTL On Mon, Feb 25, 2019 at 6:50 PM Mike Maynard wrote: > Bill, > > From what I can tell, it looks like Stephen is just trying to get the > actual currently transmitting packet. This would be an operational aid - > for example: It would allow a developer the ability to create a status > screen that is much easier to see (maybe larger type? different > contrasting colors, etc). > > Obviously it would not allow for any change in QSO progression. That > would still require direct intervention with WSJT. > > In my setup... I have a keypad that I programmed to set the QSO > progression using hot-keys. the screen I run WSJT on is a little hard to > read at a glance. It takes time to focus on it where it is. Sure I could > adjust my resolution, but then I lose space on the screen for other things. > > A larger display of current WSJT status could be a welcome option to some > of us with poorer eyesight. Enabling such a UDP packet would allow such > development to happen. > > Thanks > Mike > > On Thu, Feb 21, 2019 at 4:39 PM Bill Somerville > wrote: > >> On 21/02/2019 21:02, Tag Loomis wrote: >> >> First time message to the group. >> >> Would it be possible to have the current transmitting message be emitted >> in either in the Status Out message after “Special operation mode (quint8)” >> as utf8 *OR* a brand new message type? >> >> If it’s already present and I’m just not seeing it, any pointer would be >> great! >> >> Thank you for your time! >> >> Stephen Loomis / N0TTL / GridTracker developer. >> >> Hi Stephen, >> >> welcome to the group. >> >> The WSJT-X UDP protocol is meant to aid the WSJT-X operator but with the >> expectation that QSOs will be progressed from with WSJT-X by user >> interaction with the software. Because of that a message that echoes the >> current outgoing message doesn't seem to add any value. Can you please >> explain in detail how such a message would be used? >> >> 73 >> Bill >> G4WJS. >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > > > -- > Mike > K2GC > www.k2gc.net > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Someone released an Auto CQ mod
The post has NOT been removed, just the links to the software On Sat, Mar 30, 2019 at 11:47 AM Tom Melvin wrote: > Hi All > > Don’t want to get into a protected discussion on this as I suspect the Dev > list is not suitable for some of it. > > Take the automatic QSO Mod (I thought JTDX did that already) out of the > equation, there are a couple of other features I saw in the posting that > could be incorporated into the mainstream release: > > Filter to exclude some prefixes - perhaps a local always on (JTDX Robot), > want to filter, great add the callsign to a filter list, supports (simple) > wildcard, want to ignore all Scotland, for example, add GM* - They won’t > appear. > > Noise issues - filter station above and below a certain Db reports. > > Can’t cope with the colour settings, can display new calls only - filter > out worked before to narrow down the ‘hit’ list. > > Those three I can see being helpful and useful. > > While I am against the Auto CQ option - would like to point out - the > station posting on QRZ is European, in the UK at least, extract from > Licence: > > 10(1) The Licensee may conduct Unattended Operation of Radio Equipment > provided that any such operation is consistent with the terms of this > Licence. Additional restrictions which apply to the Unattended Operation of > Beacons are specified in Schedule 2 to this Licence. > > > > So in some parts of the world it’s legal, In looking at schedule 2 - I > would watch calling WSPR a beacon. UK licence excludes any form of beacons > between 3.6Mhz and 28Mhz - even then the 80m and 10m bands it is only for > DF hunting. Basically 4m upwards with a pile of other restrictions is ok - > So any form of WSPR on HF is (as far as I can tell - would love to be > corrected) illegal if its called a beacon. > > Tom > > P.S. I don’t like censorship so if the QRZ post has been removed it is a > little worrying at what else are we not being told - It may be against FCC > regs but not all of us are governed by them. > > > -- > 73’s > > Tom > GM8MJV (IO85) > > > > > > On 30 Mar 2019, at 15:23, Topher Petty wrote: > > That's not only against the spirit of Amateur Radio, but it's also against > FCC rules regarding unattended operation. FT8 is NOT a beacon, and doesn't > fall under those rules. > > Anyone who uses this deserves to be flogged repeatedly with a wet noodle, > and, if they're in the States, fined to the fullest extent of the > regulations. > > WSPR is a beacon, FT8 is not. This pisses me off to no end. > > de AI8W, Chris > > On Fri, Mar 29, 2019 at 2:28 PM Tag Loomis wrote: > >> Sorry, but some [expletive deleted] released an Auto CQ and Auto >> Responder mod to WSJT-X >> >> https://forums.qrz.com/index.php?threads/wsjt-x-full-auto-mod.652050/ >> >> I know there’s not much to be done about it, but man this makes me mad! >> >> >> -Stephen ‘Tag’ Loomis / N0TTL >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
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 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 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 Tune in WSJT-X and then VFO-B gets >> > set...but that leaves the amplifier in-line with too much power to >> > tune and for some could fry the amplifier. >> > Mike >> >> Hi Mike (and all), for what it's worth I've found that using the 'Fake >> It' split mode, rather than >> the 'Rig' mode, works best with my Icom IC-7600. >> >> Some years ago, when I first tried using the 'Rig' mode with WSJT I found >> that the time taken >> to switch VFOs (from A to B in my case) and then to re-tune the >> newly-selected VFO with the >> desired offset (eg. +1kHz) was significantly longer than just re-tuning >> the active VFO, >> presumably because there was a longer command sequence to be received, >> processed and >> then actioned by the rig. The delay in the rig switching VFOs and then >> re-tuning was >> resulting in the transmission not starting until (IIRC) some 2-3secs into >> a Tx period. >> >> I would assume that using the 'Fake It' mode would work equally well >> irrespective of which >> VFO was the active one, so perhaps there should be a note in the User >> Manual that, at least >> for Icom rigs, the 'Fake It' split mode is preferred/recommended? >> >> -- >> 73, Martin G0HDB >> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unexpected Behavior
I've noticed that if I double-click on the callers "CQ" is the only way to jump to their TX frequency.. IfI click on anything thing else, such as a reply, my TX doesn't move. I wouldn't consider it a bug, more of a known action, but I could be wrong of course. On Sat, Mar 2, 2019 at 3:09 AM Claude Frantz wrote: > On 1/20/19 4:50 AM, Frank Kirschner wrote: > > Hi Frank & all, > > > First thing I noticed was that when I double-clicked on his call in the > > Band Activity window, it wasn't made the active call. The last call I > > worked stayed in the transmit messages list. So I manually entered his > > call. It seemed to transmit the first message OK. However, every few > > minutes, either the active call in the transmit messages window would > > switch back to the previous call, or the QRG would jump to 3.573 MHz. I > > switched back and transmitted some more, but this kept happening. > > I'm not sure if this is the subject pointed on previously. > > Please allow me to explain my observation, in order to verify. > > I'm on FT8 mode. A have performed and terminated a QSO with a first > station. Now, a second station is calling me on another frequency. The > entry appears with a red background colour. I double click on this entry > in order to respond to this second calling station. The green RX marker > jumps to the frequency of the calling station, but the red TX marker > remains in place although "Hold TX Freq" is OFF. Therefore I'm now > transmitting on the previous frequency where my first partner station is > still working. > > Bug or feature ? This behaviour was present in 2.0.0 and is still > present in 2.0.1. If I remember well, this behaviour has the reported > previously here. > > Best wishes, > Claude (DJ0OT) > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
