Re: [wsjt-devel] Reading SWR from rig
On 3/7/19 6:37 PM, Deisher, Michael wrote: Thanks for the quick reply, Bill. Do you (or any others on the list) have any recommendations for implementing this "below" wsjtx? In my current setup, wsjtx seems to "lock" the serial device so that other apps (e.g., flrig) cannot access it. It makes sense, but I remember reading about people experimenting with virtual serial devices and such that allow multiple applications to share the rig. This seems a bit fraught with potential issues (e.g., two masters with conflicting commands) but could allow simple things like reading/displaying status information. Hi Mike, I cannot understand how such a setting can work well without any control conflicts. There is no serialization, no arbitration. Perhaps I'm thinking to much in the computer science logic. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] "a1" in printing decode locations?
On 08/03/2019 00:12, Bill Frantz wrote: When printing decodes, I have frequently seen the "a1" on the right side of the window. (The name of the location is forced beyond the right margin of the Receive window.) I think having the "a1" appear may be a bug, particularly since it forces the name of the location out of the default-sized window. Below are two successive examples, the first with the "a1" and the second without. I didn't do anything between the decodes to attempt to remove it. ... 231630 -17 0.2 1295 ~ CQ XP3A GP44 a1 Greenland 17m ... 231700 -16 0.1 1294 ~ CQ XP3A GP44 Greenland 17m ... 73 Bill AE6JV Hi Bill, the WSJT-X User Guide has this information: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0.html#_ap_decoding 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] "a1" in printing decode locations?
When printing decodes, I have frequently seen the "a1" on the right side of the window. (The name of the location is forced beyond the right margin of the Receive window.) I think having the "a1" appear may be a bug, particularly since it forces the name of the location out of the default-sized window. Below are two successive examples, the first with the "a1" and the second without. I didn't do anything between the decodes to attempt to remove it. ... 231630 -17 0.2 1295 ~ CQ XP3A GP44 a1 Greenland 17m ... 231700 -16 0.1 1294 ~ CQ XP3A GP44 Greenland 17m ... 73 Bill AE6JV --- Bill Frantz| "I wish there was a knob on the TV to turn up the 408-356-8506 | intelligence. There's a knob called "brightness", but www.pwpconsult.com | it doesn't work. -- Gallagher ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X: macOS users - Important - please read
Bill, do you know if this was the case with the posted 2.0.0 version as well? My problems with audio over USB sound devices seem to have completely gone away with this updated version - I thought they had with 2.0.1 but within an hour or so things were slow again, and I finally found that if I used the Mini's built-in headphone output things worked perfectly. Now with this updated 2.0.1 release, it's a tad slower than the headphone output to use a USB sound card, but it starts the transmission within about .5s of the transmit period and finishes around 13s, *before* the Monitor button lights up green again (previously it would still be transmitting, some times right up until the 15s mark).= On Wed, Mar 6, 2019 at 12:07 PM Bill Somerville wrote: > > Hi to all WSJT-X users on macOS, > > there was a problem with the build of WSJT-X recently shipped as v2.0.1. > It is both slow and liable to unexpected crashes. This was due to a slip > up when making the release kit that included diagnostic options which > should not be enabled for release builds. > > A new DMG installer has been posted to the WSJT-X project web site > (https://physics.princeton.edu/pulsar/k1jt/wsjtx.html) and to the > project Source Forge files area > (https://sourceforge.net/projects/wsjt/files/wsjtx-2.0.1/). I urge you > to download the replacement DMG and replace your current WSJT-X v2.0.1 > application bundle using it. > > One side effect of the incorrect build is that a trace file > "$TMPDIR/WSJT-X_trace.log" will have been accumulating, you may wish to > delete this file although the normal macOS background file cleanup tasks > will do that itself after three days. > > You may see a subtle performance improvement with the replacement v2.0.1 > since it will not be writing copious trace information to disk, also > even if you have not experienced the crash issue that is not proof that > it will not happen during your next QSO, so please update your application. > > Sorry for the inconvenience and 73 > Bill > G4WJS. > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci Princeton University |ICBM Address: 40.346344 -74.652242 345 Lewis Library |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1' ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Double click not working
Double-clicking on GW0TSM here does not work. Nothing happens. de Mike W9MDB___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Reading SWR from rig
Mike (KK7ER)L Select Hamlib NET rigctl from the rig menu, then launch rigctld (from the WSJT-X package) in the background. WSJT-X listens on 4532 to anyone who wants to send commands (R/W) to it. — John G4KLA smime.p7s Description: S/MIME cryptographic signature ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Reading SWR from rig
Mike, I've been using the free LP-Bridge software with my Windows 7 system for many years with my Elecraft K3. The K3 is connected to LP-bridge which creates multiple virtual ports. The K3 can simultaneously connect to WSJT-X, N1MM, MMTTY, DX Lab suite's Launcher and Commander applications. For non-K3 radios, you can use LPB2. I understand that both LP Bridge and LPB2 also works with Windows 8. I read that they can be used with Windows 10 but not with Ham radio Deluxe (HRD) software, which uses Unicode. You can read more about LP Bridge and LPB2 at: http://www.telepostinc.com/LPB.html 73, Rich - K1HTV = = = From: "Deisher, Michael" To: WSJT software development Cc: Bcc: Date: Thu, 7 Mar 2019 17:37:01 + Subject: Re: [wsjt-devel] Reading SWR from rig Thanks for the quick reply, Bill. Do you (or any others on the list) have any recommendations for implementing this "below" wsjtx? In my current setup, wsjtx seems to "lock" the serial device so that other apps (e.g., flrig) cannot access it. It makes sense, but I remember reading about people experimenting with virtual serial devices and such that allow multiple applications to share the rig. This seems a bit fraught with potential issues (e.g., two masters with conflicting commands) but could allow simple things like reading/displaying status information. 73, Mike KK7ER ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Reading SWR from rig
Thanks for the quick reply, Bill. Do you (or any others on the list) have any recommendations for implementing this "below" wsjtx? In my current setup, wsjtx seems to "lock" the serial device so that other apps (e.g., flrig) cannot access it. It makes sense, but I remember reading about people experimenting with virtual serial devices and such that allow multiple applications to share the rig. This seems a bit fraught with potential issues (e.g., two masters with conflicting commands) but could allow simple things like reading/displaying status information. 73, Mike KK7ER -Original Message- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Thursday, March 7, 2019 9:23 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Reading SWR from rig On 07/03/2019 17:01, Deisher, Michael wrote: > Hi. I hope this is not beyond the scope of WSJT-X but since you have > built-in rig control features, here goes. In the interests of having all > important information on one screen is it possible to read the SWR during > transmission and have an alert if the SWR is high. I think this would be > nice to catch sudden antenna issues (due to wind, etc) quickly. If this is > not currently supported, is there a way to send/receive custom messages > to/from a rig while wsjtx is transmitting? > > Thanks! > > 73, Mike KK7ER Hi Mike, this is out of scope, the CAT control in WSJT-X works at a level of a basic virtual rig, reading the SWR is not available for many rigs and even where it is, it is not available via every CAT mechanism WSJT-X supports. Basically if it can't be done for all we are not going to support it unless it is a must-have feature for WSJT-X operation. 73 Bill G4WJS. ___ 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] Reading SWR from rig
On 07/03/2019 17:01, Deisher, Michael wrote: Hi. I hope this is not beyond the scope of WSJT-X but since you have built-in rig control features, here goes. In the interests of having all important information on one screen is it possible to read the SWR during transmission and have an alert if the SWR is high. I think this would be nice to catch sudden antenna issues (due to wind, etc) quickly. If this is not currently supported, is there a way to send/receive custom messages to/from a rig while wsjtx is transmitting? Thanks! 73, Mike KK7ER Hi Mike, this is out of scope, the CAT control in WSJT-X works at a level of a basic virtual rig, reading the SWR is not available for many rigs and even where it is, it is not available via every CAT mechanism WSJT-X supports. Basically if it can't be done for all we are not going to support it unless it is a must-have feature for WSJT-X operation. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Linux (Ubuntu) not picking up on /dev/ttyXXX symlinks in config
On 07/03/2019 17:01, Topher Petty wrote: I'm not certain whether this is an OS limitation or a limitation in the way WSJTX parses the /dev files, and, as I stated, I am able to manually enter the symlink alias and get it working. I'm just bringing this limitation to your attention in case there is something that can be done to make the dropdowns see the symlinks in WSJTX. Thank you for your time. 73 de AI8W, Chris Hi Chris, you are expecting arbitrary symlinks to be discovered as serial port devices, that isn't going to happen. If you really want mnemonic device file names for your serial devices then use you udev rules to do that. WSJT-X uses the Qt QSerialPortInfo::availablePorts() function to enumerate serial devices and on a udev system that will return all devices with a 'tty' sub-system type. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Linux (Ubuntu) not picking up on /dev/ttyXXX symlinks in config
I've been trying to find a way around this issue for quite some time, but to no avail. I've got several USB->Serial port devices on my machine, including a RIGblaster Advantage, and an Edgeport/8. I've got UDEV rules set up so that it doesn't matter which order the devices come up; they're all assigned fixed aliases that are always attached to their individual ports. For example, whether my RIGblaster comes up as /dev/ttyUSB0 or /dev/ttyUSB9, it's assigned an alias at /dev/ttyUSB-RB that is always linked to that device. Likewise, my Edgeport ports can come up as /dev/ttyUSB0 to USB7 or 1 to 8 or 2 to 9, etc... but the ports are always assigned a symlink by the system as /dev/ttyUSB-EP0 through EP7. WSJTX doesn't see the symlink ports in the dropdown. I have been able to manually enter the alias for the RIGblaster, and WSJTX does save the setting... I'm not certain whether this is an OS limitation or a limitation in the way WSJTX parses the /dev files, and, as I stated, I am able to manually enter the symlink alias and get it working. I'm just bringing this limitation to your attention in case there is something that can be done to make the dropdowns see the symlinks in WSJTX. Thank you for your time. 73 de AI8W, Chris ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
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: > >> 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 groups do we need? > > On groups.io, there is > > FT8-Digital > WSJTX > > And here we have the devel list. I try to follow all three, because the > questions encountered may or may not seem to be actually on-topic for the > stated purpose of the list where they are posted. > > I agree, it’s a real problem to sort it out. > > 73, > > > John K8AJS > jbast...@me.com Well for me we can keep using the "devel" list as far as any of the owners/maintainers/moderators could complain about "off-topic" or similar arguments. I don't use to subscribe to Yahoo groups and I'd prefer to have just one "information-source" in this case, till it will be allowed. Take it easy :-) -- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
