[wsjt-devel] DXpedition/UDP logging bug?

[Saku]

HI !

Sorry if this is "known bug", but today I managed first time make a test 
with DXpedition mode (TY7C / 17m)
and I have been lazy to read all messages through as there were them so 
many after first official test.


As working DX  is "a single event" I can not repeat this. Unless I hear 
him some day on another band.


Qso went ok. At RR73 log window opened as usual and I pressed OK to log 
the qso. Logging is then done via UDP to Cqrlog.


I watched a while the traffic and noticed that few minutes  later I got 
again RR73 for 2 times.
Afterwards checking Cqrlog's list of worked stations I noticed that the 
qso was there 3 times with bit different minutes.


Same with wsjt-x's log:
2018-03-13,14:30:45,2018-03-13,14:32:44,TY7C,,18.096864,FT8,+03,-09,50,,
2018-03-13,14:33:14,2018-03-13,14:33:14,TY7C,,18.096864,FT8,+03,-09,50,,
2018-03-13,14:34:14,2018-03-13,14:34:14,TY7C,,18.096864,FT8,+03,-09,50,,

I use 1.9.0rc2 from official download, not the latest compiled from svn. 
So this bug may be fixed there.


In that case sorry for wasting  byte space.

--
Saku
OH1KH

--
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] Hamlib defaults

[jarmo]

Tue, 13 Mar 2018 13:30:39 + (UTC)
Black Michael via wsjt-devel 
kirjoitti:

> I believe perhaps we should have "Default" as an option on Data Bits,
> Stop Bits, Hand Shake, and Force Control Lines.  That would prevent a
> lot of operator errors since hamlib already has defaults for all rigs
> that generally work other than COM port and Baud rate which most
> everybody understands.
> 
> Is there any reason this won't work?

This works with CQRLOG, WSJT-X combination. I have set only baudrate
in CQRLOG, which calls rigctld up and the firing WSJT-X.

Jarmo

--
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] Guantanemo Bay callsigns

[Rich - K1HTV]

Yes Bill, I saw that but only the single suffix KG4 call was mentioned. Just 
wanted to make sure that the KG4xxx triple suffixes were also included.

Thanks for all you continue to do to improve the already great WSJT-X FT8 
software. Worked 3D2EU on Routma and H40YM on 60M at this morning's sunrise for 
my FT8 DXCC countries #207 & 208 with 75W or less..

FT8 is GREAT!

73,
Rich - K1HTV


> On March 13, 2018 at 11:23 AM Bill Somerville  wrote:
> 
> On 13/03/2018 15:19, Rich - K1HTV wrote:
> 
> > > 
> > Bill,
> > 
> >   Not only KG4x but also KG4xxx calls need to identified as USA and 
> > NOT Guantanamo Bay call signs. Only KG4 callsigns with a 2 letter suffix 
> > should be identified as the Guantanamo Bay DXCC entity. Presently KG4x or 
> > KG4xxx callsign show up as USA as they should, but are highlighted in 
> > purple.
> > 
> > 
> > 73,
> > 
> > Rich - K1HTV
> > 
> > > 
> Hi Rich,
> 
> this has been fixed for the next release as mentioned as recently as 
> yesterday:
> 
> https://sourceforge.net/p/wsjt/mailman/message/36259588/
> 
> 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

Re: [wsjt-devel] Hamlib defaults

[Black Michael via wsjt-devel]

This change would be made such that it won't affect current settings at all.The 
idea is simple enoughhamlib already has good defaults for most rigs...so 
rather than force users to figure out what to do the 1st time they select their 
rig with data bits, stop bits, and handshake it will use the defaults which 
will probably work.  Once you change it from defaults it will, of course, 
remember what you selected.  This may end up pointing out some bugs in hamlib 
too which is good.

de Mike W9MDB


   On Tuesday, March 13, 2018, 10:11:28 AM CDT, Claude Frantz 
 wrote:  
 
 On 03/13/2018 03:30 PM, Bill Somerville wrote:

Hi Bill & All,

> very few rigs allow changes to stop bits or data bits so nobody should
> care as the defaults will just work.

While using the Yaesu FT2000, I could only get stable working conditions
when setting timeout=500,retry=2,write_delay=5,post_write_delay=50.
There are probably further rigs which require settings different from
the default ones. As long as the values are appropriate, there is
probably no drawback setting such parameters, even if they are superfluous.

Best wishes,
Claude (DJ0OT)

--
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] Guantanemo Bay callsigns

[Bill Somerville]

On 13/03/2018 15:19, Rich - K1HTV wrote:


Bill,

  Not only KG4x but also KG4xxx calls need to identified as USA and 
NOT Guantanamo Bay call signs. Only KG4 callsigns with a 2 letter 
suffix should be identified as the Guantanamo Bay DXCC entity. 
Presently KG4x or KG4xxx callsign show up as USA as they should, but 
are highlighted in purple.



73,

Rich - K1HTV


Hi Rich,

this has been fixed for the next release as mentioned as recently as 
yesterday:


https://sourceforge.net/p/wsjt/mailman/message/36259588/

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

[wsjt-devel] Guantanemo Bay callsigns

[Rich - K1HTV]

Bill,  Not only KG4x but also KG4xxx calls need to identified as USA and NOT Guantanamo Bay call signs. Only KG4 callsigns with a 2 letter suffix should be identified as the Guantanamo Bay DXCC entity. Presently KG4x or KG4xxx callsign show up as USA as they should, but are highlighted in purple.73,Rich - K1HTV
 

--
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

[wsjt-devel] Monitoring Mode stops

[db...@gmx.de]

Hello,

To be useful, bug reports should include at least the following information:

Program version
1.9rc2 or 1.80
Operating system
raspbian on RaspberryPi2
Concise description of the problem
Monitoring Mode stops without notice.
Frequently monitoring Mode (green Button is on ) stops without notice. 
Sometimes it can be reactivated by pressing the button twice. But in most cases 
I can not reactivate the Monitoring Mode.
Waterfall display stops, BUT the progessbar is running (15sec.)
After closing the Programm wether with kill or normal exit, zombi processes are 
left in top or ps command. WSJTX can not be started any more. I have to reboot 
the machine.
Exact sequence of steps required to reproduce the problem
not applicable 


Best regards

Frank
DB5FP / KM6JBU--
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] Hamlib defaults

[Claude Frantz]

On 03/13/2018 03:30 PM, Bill Somerville wrote:

Hi Bill & All,

> very few rigs allow changes to stop bits or data bits so nobody should
> care as the defaults will just work.

While using the Yaesu FT2000, I could only get stable working conditions
when setting timeout=500,retry=2,write_delay=5,post_write_delay=50.
There are probably further rigs which require settings different from
the default ones. As long as the values are appropriate, there is
probably no drawback setting such parameters, even if they are superfluous.

Best wishes,
Claude (DJ0OT)

--
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] Hamlib defaults

[Bill Somerville]

On 13/03/2018 14:51, John wrote:

I should have been specific:  I was thinking about handshake..Default for 
TS870s is None but mine doesn’t like that…

Not everyone is conversant with rigctl nor which -m number is required for 
their rig…


Hi John,

RTS/CTS handshaking cannot be disabled on the rig for a TS870s, that is 
unusual for a Kenwood rig, most can be disabled though the default is 
enabled. You are right that the default is no handshaking, that is a 
Hamlib defect. In this case it is harmless apart from potential 
confusion as there is no option to use the RTS line as a PTT signal.


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

Re: [wsjt-devel] Hamlib defaults

[John]

Hi Bill,

I should have been specific:  I was thinking about handshake..Default for 
TS870s is None but mine doesn’t like that…

Not everyone is conversant with rigctl nor which -m number is required for 
their rig…

— John G4KLA
--
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] Hamlib defaults

[Bill Somerville]

On 13/03/2018 14:27, John wrote:

Hi BIll and Mike,

As long as the Default settings are known - somewhere…

— John G4KLA


Hi John,

very few rigs allow changes to stop bits or data bits so nobody should 
care as the defaults will just work.


Defaults can be listed using rigctl -L -m .

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

Re: [wsjt-devel] Hamlib defaults

[John]

Hi BIll and Mike,

As long as the Default settings are known - somewhere…

— John G4KLA
--
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] Hamlib defaults

[Bill Somerville]

On 13/03/2018 13:30, Black Michael via wsjt-devel wrote:
I believe perhaps we should have "Default" as an option on Data Bits, 
Stop Bits, Hand Shake, and Force Control Lines.  That would prevent a 
lot of operator errors since hamlib already has defaults for all rigs 
that generally work other than COM port and Baud rate which most 
everybody understands.


Is there any reason this won't work?


Hi Mike,

yes that is a good idea. I would omit the "Force Control Lines" part as 
that already has a default and Hamlib doesn't really have a default for 
those since it is interface hardware dependent.


The Handshake one is a bit tricky as many rigs that use RTS/CTS 
handshaking depend on a rig menu setting. Their factory default is 
usually with handshaking enabled because the other option is often PTT 
via RTS and that could cause damage if the user plugs in a standard 
RS-232 connection (could key the transmitter).


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

[wsjt-devel] Hamlib defaults

[Black Michael via wsjt-devel]

I believe perhaps we should have "Default" as an option on Data Bits, Stop 
Bits, Hand Shake, and Force Control Lines.  That would prevent a lot of 
operator errors since hamlib already has defaults for all rigs that generally 
work other than COM port and Baud rate which most everybody understands.

Is there any reason this won't work?
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

Re: [wsjt-devel] Ft -8 in normal mode

[Saku]

I have seen request to DXpedition-mode happen also two times.

Happened with "guess-decode" result (having "a2" at the end of decoded 
line).
I assume that signal  was so weak that decode was not clean, not that 
someone was actually using DXpedition on conventional FT8 freq.


Perhaps DXpedition-mode suggest should not pop up by decoded line that 
has "a2" I.E. is "guess-decoded".


--
Saku
OH1KH

Joe Taylor kirjoitti 12.03.2018 klo 15:25:

On 3/12/2018 8:35 AM, Ray Jacobs wrote:
It says you should be in expedition mode. What is the reason for 
this? It happened twice. Ray KA3PCX.


No, it *asks* you whether you should be in DXpedition mode.  As you 
must have noticed when you clicked "OK", the program does this

because it decoded a "Fox-mode" message.  See
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
for details.

Several people have been using Fox mode in the conventional FT8 
subbands.  As described in the instructions, this is considered very 
poor operating practice.


-- Joe, K1JT

-- 


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