Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Sergio Yes UT9LI
All comments are true. The accumulation of errors when entering the average value of dT is also true. But "auto dT" it must be for operator use. Then there will be no significant difference in dT in callLog. 25 июня 2019, 05:33:43, от "Reino Talarmo" < reino.tala...@kolumbus.fi >: >Why

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Sergio Yes UT9LI
All comments are true. The accumulation of errors when entering the average value of dT is also true. But "auto dT" it must be for operator use. Then there will be no significant difference in dT in callLog. 25 июня 2019, 05:51:21, от "Sergio Yes UT9LI" < ut...@ukr.net >: Yes!  Adjustment

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Sergio Yes UT9LI
Yes!  Adjustment dT can be organized in the program itself. Discarding values, for example, dT greater than 0.7, calculate the average value of dT over all accepted values ​​in the "callLog" list and automatically enter this value by analogy with the "+/- dT" button. In this case, the operator

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Sergio Yes UT9LI
Adjustment dT can be organized in the program itself. Discarding values, for example, dT greater than 0.7, calculate the average value of dT over all accepted values ​​in the "callLog" list and automatically enter this value by analogy with the "+/- dT" button. In this case, the operator will

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Reino Talarmo
>Why actually set the computer clock? Just compute an offset for the local >clock based on the mean (or median) of the DT of the decoded messages. Then >use this offset within WSJT-X to adjust the time used in the software from the >actual computer clock. Hi Jim Consider what would happen,

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Jim Record
Why actually set the computer clock? Just compute an offset for the local clock based on the mean (or median) of the DT of the decoded messages. Then use this offset within WSJT-X to adjust the time used in the software from the actual computer clock. Jim Record On Mon, Jun 24, 2019 at 2:11 AM

Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

2019-06-24 Thread Dave Slotter, W3DJS
Bill, Thank you for the detailed explanation... I'm an engineer myself, and I understand when compatibility issues arise. You didn't need to take all that time to respond, but I certainly do appreciate it! I can share this positive news for you, however... I provided the FT8 digital station for

[wsjt-devel] Wav error patch

2019-06-24 Thread Black Michael via wsjt-devel
This patch allows a dialog box if opening the WAV file has an error.To test just rename the "save" directory and you'll see the dialog pop up.One user was having problems saving wav files which prompted me to do this. https://www.dropbox.com/s/8lraugrv2ysq7xe/waverr.patch?dl=1 de Mike

Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

2019-06-24 Thread Bill Somerville
On 24/06/2019 18:46, Dave Slotter wrote: I was wondering, if WSJT-X uses HamLib, and at least some rigs are capable of setting and getting the transmit power, why do users have to fill in the Log QSO Field, "Tx power", manually? Is there a reason for not implementing this feature? Hi Dave,

Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

2019-06-24 Thread Dave Slotter
Mike, That's terribly disappointing to hear. However, thank you for the quick response! 73, -Dave W3DJS On Mon, Jun 24, 2019 at 2:06 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > We've found TX Power to be terribly unreliable and

Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

2019-06-24 Thread Black Michael via wsjt-devel
We've found TX Power to be terribly unreliable and that's why it's not implemented. Mike On Monday, June 24, 2019, 12:51:34 PM CDT, Dave Slotter wrote: Hi all, I was wondering, if WSJT-X uses HamLib, and at least some rigs are capable of setting and getting the transmit power, why

[wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

2019-06-24 Thread Dave Slotter
Hi all, I was wondering, if WSJT-X uses HamLib, and at least some rigs are capable of setting and getting the transmit power, why do users have to fill in the Log QSO Field, "Tx power", manually? Is there a reason for not implementing this feature? [image: image.png] Thank you in advance. 73,

[wsjt-devel] Icom IC-746 Pro CAT control logic failure? (WSJT-X v2.0.1)

2019-06-24 Thread Phil Erickson
Hi all, Our club (N1NC; Nashoba Valley Amateur Radio Club) had a VHF station for FT8 this past weekend for Field Day and ran into an insurmountable WSJT-X control problem. I tried searching the list but did not come up with a hit so seeking collective wisdom. Rig: Icom IC-746 Pro Interface:

Re: [wsjt-devel] Time sync and other FT8 comments after FD 2019

2019-06-24 Thread Sterling Mann
JS8call implemented an DT synchronizer that automatically synchronizes the DT of a station of interest based on user input of the start and end times of a single transmission. I think it might be trivial to implement a similar feature in WSJT-x that allows for time synchronization, but based on

[wsjt-devel] Time sync and other FT8 comments after FD 2019

2019-06-24 Thread WB5JJJ
First off, I much prefer SSB phone to FT8, but with the current band conditions, I find FT8 a great stop gap measure and certainly glad it's available, otherwise my rigs would be collecting dust and cat fur. FT8 will probably be a cyclic operational mode as band conditions improve, but it's big

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Reino Talarmo
Thanks for comments. I totally agree the GPS solution, just everybody needs to do so! I have one. Actually I did not proposed, at least not before testing, any addition or change into WSJTX. I just proposed a method more useful here, the other side of pond, were WWV etc. are not so strong and

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread VE3FBZ
Do not understand all the ragging about other people’s incorrect computer time. It’s their problem, not ours (mine). I simply avoid them and they miss out on a contact. Now that out of adjustment time is flagged, it’s a non issue. BTW if all returns are flagged as out of sync it’s your

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Hasan al-Basri
I also agree with Fred, why do we constantly focus on reinventing the wheel? WWV or other world time services and a mouse click will even work. A Cheap CASIO watch has NIST time in it for $30. (works well Stateside). The GPS dongles are dirt cheap and some even come with time setting software.

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Tom Melvin
All This posting by Fred gets my vote - easy, fool proof and does not distract the dev team. -- 73’s Tom GM8MJV (IO85) On 24 Jun 2019, at 09:27, Fred Price wrote: > You are all overthinking the problem. There are programs to set your computer > clock by a GPS dongle. A good plug in

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Fred Price
You are all overthinking the problem. There are programs to set your computer clock by a GPS dongle. A good plug in dongle from Amazon is $12USD and the program I use BktTimeSync is a free download. Also if the dev group keeps adding more n more WSJT will become bloatware. I'd rather see

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread DG2YCB, Uwe
A very good idea to set up time beacons, Reino! I like this approach! However, as a short-term solution IMO dev team should find a way to use the EXISTING data set of DT values for a pop-up saying that very likely time is not synced correctly, plus an option to correct time by one click. Look

Re: [wsjt-devel] Field Day time problem

2019-06-24 Thread Reino Talarmo
Hi, We are amateurs and could provide another time distribution experiment especially during Field Day events. I mean setting up time beacon or beacons that send e.g. every 15 s a short pulse, say 100 ms, on the base carrier frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute mark