Re: [wsjt-devel] DXpedition mode

[Libor Holouš]

Hello Pino..

First, AIF should not use DXmode in normal frequency.
I thing this guy haven't read documentation carefuly, because this is the 
basic thing?


Adding some button is, by my opinion, just source of another mistakes and 
misunderstanding of users, so better thing is just make copy of profile and 
rename the copy to something like DX-hound and configure for split, 
announced frequencies and hound mode.
In case of dxpedition operation, just switch profile without neccessary of 
closing program..


If people like AIF try DXmode in normal frq. just ignore him and keep 
calling in normal mode..
But it has happened me once too, that it was probably some decoding issue, 
the station worked in normal mode, so probably magic bit was decoded 
accidentaly.


This is my opinion. Maybe other can have another..

Regards,
Libor OK2ZO

- Original Message - 
From: "Pino Zollo" 

To: 
Sent: Saturday, March 10, 2018 10:37 AM
Subject: [wsjt-devel] DXpedition mode


Hi, yesterday night on 160m I did answer to the CQ of 5B4AIF.

He replied in DXpedition mode to me and to a G4 station.

On my screen appeared a small window saying: "You should be in
DXpedition mode".


I quickly changed to DXpedition mode, but an other small window said me
that I should be in Split Mode...

By the time that I did it the propagation went down


So... it should be nice to have an evidence of a station calling in
DXpedition Fox modemaybe with the call of a nice brown color

Also should be nice to have a button to switch quickly to a predefined
setup of DXpedition mode...

 it could be also automatic when you doubleclick on a brown call.


Best 73

Pino ZP4KFX



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 1.9.0 rc2 Waterfall

[Libor Holouš]

Hi Gary..

Not for decoding but find and fit into most free space.
BTW, I have it smooth too now, no changes, just upgraded.. I liked it more 
like before it was..

Now I feel like glasses needed..

But somebody maybe like it or don't want to wear glasses and that way it is 
more comfortable? :-)


My WF settings: N Avg 1, Palete Green1

73 Libor OK2ZO

- Original Message - 
From: "Gary McDuffie" 

To: "WSJT software development" 
Sent: Wednesday, March 07, 2018 8:28 PM
Subject: Re: [wsjt-devel] WSJT-X 1.9.0 rc2 Waterfall






On Mar 7, 2018, at 9:59 AM, Lawrence Lopez  wrote:

I found the really liked the new format of the waterfall.
It was much less critical to adjust in order to get data.


The waterfall has no bearing on the ability to decode.  It isn’t even 
needed.


Gary - AG0N
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] tx audio equalisation, just a thought.

[Libor Holouš]

Sorry Mike.. This was directed to Peter of course.. :-)
  - Original Message - 
  From: Libor Holouš 
  To: WSJT software development 
  Sent: Friday, January 26, 2018 12:31 PM
  Subject: Re: [wsjt-devel] tx audio equalisation, just a thought.


  Hello Mike, --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] tx audio equalisation, just a thought.

[Libor Holouš]

Hello Mike, 
just for sure, have you checked, that your sound card doesn't use equalising 
settings?
Some soundcards do have this possibility and in my PC serviceman career I have 
seen many times, that people complained for audio quality in Skype and finaly 
they had switched some DSP effects, like "bathroom" on. Typicaly it was Realtek 
HD audio.. But some other have this functionality too. (If not using USB 
dongle. :-)
If not and you have this possibility, it could solve your issue a bit, because 
you could create some own profile and use equaliser and W-mtr to calibrate all 
subaudioband to one power level (using tune button and clicking by watterfall). 
Of course not as great as you suggest, but can help a bit.

See my IDT audio panel:



73 Libor
  
- Original Message - 
From: "Bill Somerville" 
To: 
Sent: Friday, January 26, 2018 11:49 AM
Subject: Re: [wsjt-devel] tx audio equalisation, just a thought.


> On 26/01/2018 10:28, Peter Sumner wrote:
>> Hello Mike,
>> can you offer some URL's as I have exhausted my google searches for 
>> both of those suggestions... all I get is topic about fishing for rig 
>> split and fake it gives me pages of topics about the US president and 
>> his fake news. have tried various other combinations but as I do not 
>> know what they are meant to do it is hard to refine the searches.
>>
>> Peter.
> 
> Hi Peter,
> 
> I think Mike may have missed that you are using EME on the microwave 
> bands. The facility he suggests is only appropriate and available for 
> the narrower modes used commonly on HF.
> 
> With respect to your original request, I do see some merits but 
> profiling your Tx pass band characteristics for a mode like QRA64 
> although it is quite tricky given the number of frequencies that need 
> calibration. The implementation would not be too hard as a simple table 
> of factors would be mapped to each tone frequency within the digital 
> audio synthesizer, OTOH the work to implement a maintenance facility for 
> the correction factors would be considerable and I doubt considered 
> worth the payback. Also modern rigs are dealing with this more 
> fundamentally by providing SSB-DATA modes tailored for AFSK operation 
> which have very flat pass band characteristics.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] PSK Reporter ANTENNA

[Libor Holouš]

Hello Dennis.

This is available in WSJT-X. Hope the picture helps you..

73 Libor
  - Original Message - 
  From: Dennis Drakopoulos via wsjt-devel 
  To: wsjt-devel@lists.sourceforge.net 
  Cc: Dennis Drakopoulos 
  Sent: Thursday, January 25, 2018 9:03 AM
  Subject: [wsjt-devel] PSK Reporter ANTENNA




  Hello from Athens!
  I believe it would be beneficial for all if WSJT software development team 
could add as a feature, to allow the user to provision antenna information 
field on the spots being uploaded to PSK REPORTER project.




  73 de SV1CDN, Dennis!


--


  --
  Check out the vibrant tech community on one of the world's most
  engaging tech sites, Slashdot.org! http://sdm.link/slashdot


--


  ___
  wsjt-devel mailing list
  wsjt-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] for_us patch

[Libor Holouš]

Same experience, but only if you log the qso before decoding it. If keep opened 
logging dialog, it is showed on right. Else on left.. 
But not big fault, if send RR73, I don't need exactly recieve 73 then. It's 
just for check and ussualy I can see it on left rolling. 
For QSO finnishing it's minnor.. If the station not get my RR73, sends again 
R-xx and when TX is enabled, it replies by RR73 again, while showed on right.

What happen's to me, when I decide to call some station and somebody else calls 
me same time, it's showed only on band activity window and when clicked on it, 
it's unable to change called callsign until F4 pressed. Not sure, if this 
behavior was in betas..

73 Libor
  - Original Message - 
  From: Neil Zampella 
  To: wsjt-devel@lists.sourceforge.net 
  Sent: Friday, January 12, 2018 5:48 PM
  Subject: Re: [wsjt-devel] for_us patch


  This happened to me this morning.  I noticed that if I sent a RR73, then 
enabled the Enable Tx for the next Tx period, the 73 did not show up in the Rx 
tab either.

  Neil, KN3ILZ  


  




  On 1/11/2018 1:14 PM, Black Michael wrote:

If you have to repeat a 73...so you click Tx 5...the resulting 73 from your 
QSO partner does not get displayed on the Rx Frequency tab.


It's because it follows the if clause right about that does not have the 
bDisplayRight logic.
So...it appears that simply removing the braces from the else clause fixes 
this since the logic is always executed.


Eric, WA1SXK helped figure this out.



de Mike W9MDB





--


  --
  Check out the vibrant tech community on one of the world's most
  engaging tech sites, Slashdot.org! http://sdm.link/slashdot


--


  ___
  wsjt-devel mailing list
  wsjt-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Another Compound Callsign Problem

[Libor Holouš]

Hello Scott..

Excuse me, must say, you was true.. I haven't tried it yesterday, because PC 
was off that time and I didn't want disturb family..
Now heard you and called you on 20m and if set to DX Call - TI3/W7RI and 
generate standard messages, it generates W7RI OK2ZO JN89.
If manualy set TI3/W7RI OK2ZO - it transmits only TI3/W7RI OK2Z
That's the issue.. The only full call is shown in TX5 - TI3/W7RI 73
If you had just TI/W7RI, it would be like I have written lower..
Therefore it realy can have an effect, you have mentioned..

Tried profile from your side, setting type 2 call in TX1 or TX3 is not good to 
the pile, so only TX5 is usable. 
Tx6 as of standard CQ TI3/W7RI EJ79.

So, the only solution is use more often Tx6 and Tx5.. 

73 Libor

P.S. Heard you only very short time, then the band started closing.. right as 
written lower..
  On Monday, December 4, 2017, 5:36:00 PM CST, Libor Holous OK2ZO 
 wrote: 




  Dear Scott..


  Look.. As I said, experienced smart operator will get the call correctly..
  The others can repair it in their logs anytime later. It's not your problem. 
The system is setup this way, so if you can't get standard call, you must use 
compound and count with it.
  Lets see the example, not only for you or Gary...


  On your side, I'd not use automatic reply 1st. Sit to some QRG, best lower 
one 300-500Hz, switch fixed QRG on.
  Tx6 CQ UP TI5/W7RI
  Tx5 DE TI7/W7RI EJ79 - to include square for square hunters.
  Tx4 switch to RR73


  In Settings - set Doubleclick enable TX.. Open logging dialog automaticaly.


  And lets go for QSO as automat works..
  CQ UP... 


  Who replies with Tx1:
  TI7/W7RI OK2ZO
  OK2ZO W7RI -01
  W7RI OK2ZO R-02
  OK2ZO W7RI RR73 ... opens logging dialog - logging QSO
  W7RI OK2ZO 73 ... during receiving this, double clicking to another station 
of your choice, or you can let continue the automat with DE TI5/W7RI EJ79 


  One minute or 1.5 minute on ideal state..


  Who replies with Tx2:
  W7RI OK2ZO -10
  OK2ZO W7RI R-03
  W7RI OK2ZO RR73
  DE TI5/W7RI EJ79 ... logging dialog, clicking save, quickly double clicking 
next in list or wait until Tx5 is complete and waiting for new callers.


  45s or 1.25 min for QSO. 


  You miss Grid here, but if it's not important for you? (BTW, you get it from 
LotW when confirmed).
  If sb. calls you with Tx1 like:
  W7RI OK2ZO JN89
  you can bet, he's got wrong call. Then you can click on Tx5 or Tx6 or just 
reply to another caller and let Tx5 go during that period. If is not an idiot? 
- return to first paragraph of this mail..


  --
  According my previous "question", my experience with lots of stations from 
NA/SA is bad. They prefer US wide open window against Central EU, especialy on 
upper bands. If they work EU, than here is band closed already and they work 
West EU or BigGuns only. And it's not only on FT8 of course.. In US? - EU is 
not interesting - rather ragchewing within US, right when opening to us..
  Thats from my experience... I can't have some beams and towers in the town. 
Vertical on the roof is a miracle for me and luxury, the others can't have. 


  I'm not a big gun, but also with just a little bullet you can hit, if you 
know howto...
  I thank so much to all authors of such wonderful mode, which helps me aiming 
much better..


  73s.


  Libor


  PS.. I do apologise for probable errors in my English.. 






  Odesláno ze zařízení Samsung


   Původní zpráva 
  Od: Scott Bidstrup  
  Datum: 04.12.17 21:52 (GMT+01:00) 
  Komu: wsjt-devel@lists.sourceforge.net 
  Předmět: Re: [wsjt-devel] Another Compound Callsign Problem 

  On 04/12/2017 12:57 p.m., Libor Holous OK2ZO wrote:
  > Experienced users will quickly know, you are from Costa Rica.. Just send
  > time to time CQ and standard 73 message with full call..

  Libor, I understand what you are saying, but the reality is that a lot 
  of fellows in the States, when they sit down for a session, will simply 
  glance at the band activity window and not connect up my abbreviated 
  call and my full callsign, because it may not appear on their list of 
  decodes.  If my full callsign, from a CQ or 73 message doesn't appear in 
  the band activity window, they will not appreciate that I am a DX station.

  I do, in fact, call CQ frequently - mostly so my full callsign gets out 
  there, and also because it makes starting an autosequence more sure. 
  But when I'm working a pileup, as I am most of the time, I can go for 
  quite a few QSOs - ten or fifteen minutes - with the software never 
  sending a CQ, but simply replying to the first decode that pops up after 
  my last 73 message, and Call 1st then sends to the standard messages. 
  When that happens, I do not send a complete callsign at all until the 
  next 73 message, (and technically, that's not legal under the rules here 
  - we are supposed to transmit the full, unabbreviated call signs of ours 
  and 

Re: [wsjt-devel] Feature Request of FT8 TX Frequency limitation less than 2kHz

[Libor Holouš]

Hello guys..

According this theme I'd like to ask about expanding the band possibility. FT8 
seems to be very popular these days and there are some DXpeditions operating 
there, so 2 kHz is not enough space for all that traffic. The extreme is 40 and 
20m, but when propagation allows, the other bands too (on higher bandsis not 
possible to see most of EU traffic, from DX side it must be crazy :-)

I'd suggest add another kHz lower. Lots of newer radios got 3kHz filter, so it 
is possible to hear whole band easily. Beginning of band should be used by DX 
stations (expeditons) using fixed freq. while using split operation (for 
transmit are freq. bellow 200Hz and above 2.4kHz practicaly unusable). For JT65 
users then should be less possibility of intrusion and there will be more space 
for non-dx operations too.

Example:
Expedition tunes in VFO B 14072kHz, audio sets between approx. 1100-1300. VFO-A 
for RX tunes 1kHz higher 14073 and sets 3kHz filter. Sets Hold TX freq.
CQ message "CQ UP DX1DX square".
RR73 should be a standard in this case.

User, normaly set on 14073 should see expedion calling betwen 100-300Hz, what 
is readable, but difficult to transmit there directly, but can use 300-2400Hz 
for call easily, if sets split on the radio, can easily use up to approx. 
2930Hz, still readible by expedition. And voila: 14073000+2930+60Hz = 
14075990Hz. So intrusion to JT65 band is solved. 

The only expedition was using radio split was 5T5OK - used UP2 - but it was 
unfortunately in JT65 band. Extending band by 1000Hz lower could help a bit.

I don't know the details of earlier mentioned developed DX mode in this 
discussion, so for today's conditions it is possible solution without some SW 
development (except overwrite freq. list in future)

It's theme for discussion. FT8 started revolution in digital modes, and is much 
more popular now, than PSK31 was. 
The JT65 was not popular for me, due looong time procedure of the QSO, if it 
was DX there, it was for several coffies, until got QSO. It's still not as fast 
as RTTY or PSK, but there is no space for macros, most users use on PSK 
(Everybody seen the QSO, while complete PC and SW setup, WX, age and lots of 
rubbish was send on PSK), so waiting for the qso was also sometimes boring.

So, lets discuss.. :-)

73 Libor OK2ZO
  - Original Message - 
  From: Black Michael via wsjt-devel 
  To: WSJT software development 
  Cc: Black Michael 
  Sent: Tuesday, November 21, 2017 3:05 PM
  Subject: Re: [wsjt-devel] Feature Request of FT8 TX Frequency limitation less 
than 2kHz


  Although FT8 has "intruded" on the lower part of the normal JT65 spot I don't 
see it as a problem.
  There aren't that many JT65's out there...and, in the past, I've seen plenty 
of JT65's "intruding" on the JT9 area.
  It's quite natural to bump up the 2kHz limit when the band is crowded.  ALl 
has to do with the average bandwidth of a receiver typically being 2400 and 
higher.  So far don't think I've seen any FT8's above 2500.



  The only reason WSPR is excluded is because the same people that wrote WSPR 
also wrote WSJT-X...otherwise it probably would not be excluded (e.g. there are 
other JT65 programs that don't excluded the WSPR area ).


  de Mike W9MDB





  On Monday, November 20, 2017, 11:10:15 PM CST, Tsutsumi Takehiko 
 wrote: 




  Hi all,



  It is great to observe the popularity of FT8 format among non-wsjt-x 
experience in the past and I have a proposal to add the following feature for 
these.



  If I miss any consideration to my proposal, I welcome your comments.



  Regards,



  take



  de JA5AEA

  
-



  Please add the feature to limit FT8 TX frequency less than 2kHz. 



  Reasons are stated as follow.



  1. The working frequency table was and is designed and planned that the width 
of FT8 is 2kHz. However, the limitation feature of 2kHz to the operator has not 
implemented to wsjt-x software.



  2. Recently we observe above 2kHz communication practice by operators who 
does not know above design concept and the interference to adjacent wsjt-x 
channel such as JT65 is created.



  3. Such TX frequency limitation practice is  implemented to JT65 operation at 
30m to protect WSPR channel  in wsjt-x software.



  Some may object the implementation by the recent FT8 traffic expansion. But 
my position is that these traffic un-balanced problem should be separately 
solved by the optimization work of the working frequency table in near future.



  Sent from Mail for Windows 10



  --
  Check out the vibrant tech community on one of the world's most
  engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
  wsjt-devel mailing list