Re: [wsjt-devel] Possible feature request, time skew notification?

> 2. In outdoor setting (sounds like it is more applicable) you can get a > trusted time from a GPS receiver. I had some experience with this recently, using this USB GPS https://www.ebay.com/itm/284227196983 with GPS2time

Re: [wsjt-devel] Problems building on MacOS X 11.1 Intel

Hi Bill, Thanks for the quick response. I tried to roll back to pre-v8 gfortran, couldn’t find v7 pre-built and didn’t want to go down that rabbit hole of building it. I tried again with gfortran 6.3.0 and got the same error however- [ 17%] Building Fortran object

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

On 7/18/21 at 3:56 PM, wsjt-devel@lists.sourceforge.net (Tom via wsjt-devel) wrote: Of course this is solved by putting in Run as Administrator in the shortcut for WSJT. But the question is why all of a sudden? And, of course, running general normal applications as Administrator flies in

Re: [wsjt-devel] Possible bug between wsjtx and net Hamlib

HI Kari, That was a worthwhile experiment, but unfortunately, I also get the exact same behavior between 2 wsjtx 2.4 instances (compiled from source) with rgctld-wsjtx showing hamlib v4.2. I'm pretty sure this is not a hamlib problem, but rather wsjtx improperly assuming that the get

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

HiYes the other threads are in relation to log4om. Anyways, seems nothing can be done right now about this other than to run as admin.Thanks, TomSent from my Galaxy Original message From: Bill Somerville via wsjt-devel Date: 2021-07-18 4:16 p.m. (GMT-05:00) To:

Re: [wsjt-devel] Possible bug between wsjtx and net Hamlib

Could you please try the master repo to see if has already been fixed? https://github.com/Hamlib/Hamlib Mike W9MDB On Sunday, July 18, 2021, 12:10:29 PM CDT, alawler mudhawk.com via wsjt-devel wrote:  HI Folks,   I've encountered what seems to be a bug in how wsjtx uses the network

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Tom, OK, so there something else going on as well. You state below that old versions of WSJT-X have also started showing this issue, that would seem to rule out the WSJT-X code *and* any Qt libraries as we package them along with WSJT-X. I am surprised you state that this issue has been

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi I already did this. It made no difference in my case. I have also given all groups full control. Logging in with an account in the local administrators group will only work as well if WSJT is run in administrator mode. Something has been changed with a Windows update since this always

Re: [wsjt-devel] Possible bug between wsjtx and net Hamlib

Hi Al, Your WSJT-X version 2.2.0  is quite old. Also, your Hamlib must be even older as you are using the short model numbers. Hamlib shipped with WSJT-X 2.2.0 use new longer model numbers, for example  FT-736R is now model number 1010 and FT-890 is 1015. Suggest you upgrade to current

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Tom, I think I have reproduced the issue. I have an account on my Windows PC, I use for testing UAC matters, that is not a member of the local administrators group. If I use this account I cannot have WSJT-X use Omni-Rig, even though I can start the Omni-Rig server by running its

Re: [wsjt-devel] Possible feature request, time skew notification?

> On Jul 18, 2021, at 09:26, Carey Fisher via wsjt-devel > wrote: > > If you simply look at the waterfall, it's clearly obvious whether your clock > is off or not. You and George are correct. Simply looking at the waterfall will get you within the two seconds required. After that, the df

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Exactly the same for all users. Don’t know where to go from here…. 73 Tom From: Bill Somerville via wsjt-devel Sent: Sunday, July 18, 2021 2:22 PM To: wsjt-devel@lists.sourceforge.net Cc: Bill Somerville Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM

Re: [wsjt-devel] Problems building on MacOS X 11.1 Intel

Hi Alex, thanks for that. We currently do not recommend using a gfortran version >= 8 on macOS, this is due to some known issues with our code for which fixes are a WIP. With gfortran v7 that compiler diagnostic message is only a warning, which is how our build gets passed it. The passing of

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Tom, thanks for that. So it seems that something is blocking COM communications between WSJT-X and Omni-Rig that is resolved by running WSJT-X with elevated rights. The Windows security model, in general, blocks IPC between processes running at different security levels. If that is the

Re: [wsjt-devel] Problems building on MacOS X 11.1 Intel

Hi Bill, Thanks for getting back to me. This is what I get: grey>:/Users/alex$ which gfortran /usr/local/bin/gfortran grey>:/Users/alex$ gfortran -v Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/11.1.0_1/libexec/gcc/x86_64-apple-darwin20/11.1.0/lto-wrapper

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Ok. I did this. When you run WSJT without being admin, no log is made at all. You get Failed to start Omni Rig COM server in WSJT If you run it as admin, then a log appears. Here are the first few lines… 13:45:51.670 Omni-Rig started: Version 1.19 13:45:51.675 Loading commands

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Tom, I did have a minor typo in the first path I wrote below, other than that it most certainly is where the Omni-Rig configuration file is found: C:\Users\bill\build>dir "%AppData%\Afreet\Products\OmniRig\" Volume in drive C is Windows8_OS Volume Serial Number is 56CD-82B3 Directory of

[wsjt-devel] Possible bug between wsjtx and net Hamlib

HI Folks, I've encountered what seems to be a bug in how wsjtx uses the network hamlib functionality.I'm going to start with a simple symptom statement, then will include more supporting detail and the specific configuration etc. The problem: wsjtx does not work with a remotely

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi There is no such path. I am using omni-rig 1.19 just downloaded from the web at dxatlas. The use of administrator mode only works for the 64 bit WSJT. The 32 bit fails with both user and administrator mode. Always failed to start the omnirig com server. Tom From: Bill

Re: [wsjt-devel] Possible feature request, time skew notification?

If you simply look at the waterfall, it's clearly obvious whether your clock is off or not. 73, Carey, WB4HXE On Sat, Jul 17, 2021 at 10:17 PM Paul Bramscher via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I was at a monthly outdoor ham event in the greater St. Paul/Minneapolis >

Re: [wsjt-devel] wsjt-x v2.5.0-rc3

This seems to be fixed now. I had to set the CODEC to single channel 48kHz and select LEFT in the wsjt audio settings, it has been running for over 24hrs without problems. 73 Conrad PA5Y From: Conrad PA5Y via wsjt-devel Sent: 17 July 2021 13:59 To: WSJT software development Cc: Conrad PA5Y

Re: [wsjt-devel] Possible feature request, time skew notification?

Wouldn’t a simple glance at the Wide Graph provide clear evidence of timing errors? Even without WWV, GPS, or software changes, it seems trivial to identify the error and walk in a correction. George J Molnar College Park, Maryland KF2T | FM19ma

Re: [wsjt-devel] WSJT-X 2.5.0-rc3 RST_RCVD logging issue

Rather good way to get qso one period faster. Important with VHF ES DXing (mostly 6m). Conditions change so fast. There are not so many 4 character grids in Japan. And if callsign's QRZ or HamQTH entry is up to date external logger adds the locator, usually 6 characters, or even more precise.

Re: [wsjt-devel] My problems while compiling from the source

On 18/07/2021 08:31, Claude Frantz via wsjt-devel wrote: On 7/17/21 10:02 PM, Kari Sillanmäki via wsjt-devel wrote: Hi Kari, Bill, Adrian and all, This may not comfort you much, but just for fun and giggles I installed Debian Buster onto a virtual machine and then cloned Hamlib and WSJT-X

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

Hi Tom, thanks for the clarification. You didn't confirm which version of Omni-Rig you are using. It would be interesting to see the Omni-Rig debug log for a test where WSJT-X claims it is unable to start the Omni-Rig COM server. To enable Omni-Rig debug logging put the following into the

Re: [wsjt-devel] My problems while compiling from the source

On 7/17/21 10:02 PM, Kari Sillanmäki via wsjt-devel wrote: Hi Kari, Bill, Adrian and all, This may not comfort you much, but just for fun and giggles I installed Debian Buster onto a virtual machine and then cloned Hamlib and WSJT-X from git. Compiled, and got a working WSJT-X. So

Re: [wsjt-devel] Possible feature request, time skew notification?

I’m using a different approach, with a USB mouse GPS and the NMEATime2 from http://visualgps.net/index.html#nmeatime2-content I’m always on time. 73s Alex On 18/07/2021 07:58, Wolfgang K. Meister via wsjt-devel wrote: Yes, there is a

Re: [wsjt-devel] Problems building on MacOS X 11.1 Intel

On 18/07/2021 03:31, Alex Lelievre via wsjt-devel wrote: Hi there, I’m running into an error in the fortran portion of the WSJT-X project on MacOS X.   I’m reaching out to see if anyone has bumped into this: [ 17%] Built target record_time_signal [ 17%] *Automatic MOC for target fort_qt* [

Re: [wsjt-devel] My problems while compiling from the source

Thankyou, however I see, to be compatible with install instructions ; git clone git://git.code.sf.net/p/wsjt/wsjtx src ,however I adapted to suit, I note that linquist requires qttools5-dev installed. Also    ;   cmake --build . --target install should really show ;   sudo cmake --build .