Re: [wsjt-devel] WSJT-X: v1.7.0-devel WSPR defect

[Bill Somerville]

On 21/11/2015 19:37, Bill Somerville wrote:
> Hi All,
>
> *WARNING TO builders of the development branch*
>
> It seems that a recent change, probably merged from the wsjtx_exp branch
> is causing WSPR mode to put the rig in split mode if
> "Settings->Radio->Split Operating" is not set to "None". This is a
> defect that *will make your Tx frequency incorrect*. If you want to use
> the development code for WSPR then I suggest you set
> "Settings->Radio->Split Operating" to "None" when using WSPR mode. You
> may have to manually take your rig out of split mode as well.
>
> I will start looking into this straight away and update when it is fixed.
>
This issue is resolved as at r6150.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] JTAlert double click problem

[Michael Black]

I sent this to the wsjt-x group also but this may be more development
oriented...

JTAlert 2.6.22 and WSJT-X 1.7.0-devel r6147 on Windows 10 latest (was
happening on prior versions of everything too).
Numerous times in the last several weeks the JTAlert double-click has
stopped working.  Double-click and WSJT-X does nothing.  Both on localhost
and multicast.
I went through one debug iteration with Laurie and he said the debug shows
WSTJ-X responding to the request but WSJT-X does not start the QSO.
No rhyme or reason I can figure out as to when it starts.  Happens after a
while.

I've been running the debug version and attached to it just now to try and
figure out what may be wrong.   Not sure where I should set the
breakpoints.  I tried MainWindow::replyToCQ but that breakpoint doesn't get
hit.

I put another in pending_datagrams and that doesn't get hit.

Put one in heartbeat and that is working.

Suggestions on where to look/breakpoints would be helpful since this is
happening regularly.

73
Mike W9MDB

This
email has been sent from a virus-free computer protected by Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSPR message "--- Receiving on xxx m ---"

[Joe Taylor]

Hi Bill and all,

FYI, related to minor thread "Redundant Information in the WSPR Receive 
Window" a few minutes ago: with r6149 I have made the necessary change 
in the v1.6.0 branch to correct this unwanted behavior.

-- Joe, K1JT

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 27 Decodes in one period with v1.7.0

[Greg Beam]

I think this is a record for me, 27 decodes, 1 bad one at df 978. No 
matter how you look at it, that is pretty impressive.



73's
Greg, KI7MT
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] display problem with screenshot sorry

[f5jmh]

Hello all,

I have a small display problem on setting advanced, please see screenshot.
73's friendships and goodbye
F5JMH
Alain

Linux Ubuntu 14.04 64bits--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X: *Important* - please read if you build WSJT-X from source

[Bill Somerville]

On 22/11/2015 17:22, Alessandro Gorobey wrote:
> Can provide me a working configuration of FT-857 ?
> I use CAT PTT can be this the cause ? 
Hi Sandro,

sorry you and other FT-817/857/897 users are having to suffer this 
regression.

I have an FT-857 here and when I get time  I will try and improve the 
support as much as I can with the limited CAT capability.

For now all I can suggest is to try "Fale it" split mode.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] display problem with screenshot sorry

[Steven Franke]

Hi Alain, Bill, and all,

I’ve committed a change that fixes the Advanced tab display issue on my Linux 
box. I’ve also tested it on my OSX machine. I don’t have a windows box here, so 
I need to ask others to check that.

Steve k9an

> On Nov 22, 2015, at 11:01 AM, f5...@free.fr wrote:
> 
> Hello all,
> 
> I have a small display problem on setting advanced, please see screenshot.
> 73's friendships and goodbye
> F5JMH
> Alain
> 
> Linux Ubuntu 14.04 
> 64bits--
> ___
> 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] display problem with screenshot sorry

[Bill Somerville]

On 22/11/2015 17:01, f5...@free.fr wrote:
> Hello all,
>
> I have a small display problem on setting advanced, please see screenshot.
> 73's friendships and goodbye
> F5JMH
> Alain
>
> Linux Ubuntu 14.04 64bits
Bonsoir Alain,

thanks for reporting that, the layout need some adjustments. I will look 
at it shortly.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] display problem with screenshot sorry

[Steven Franke]

Alain,
I probably caused this by adding the new checkbox. It looked ok on OSX. I’ll 
take a look.
73 Steve k9an

> On Nov 22, 2015, at 11:01 AM, f5...@free.fr wrote:
> 
> Hello all,
> 
> I have a small display problem on setting advanced, please see screenshot.
> 73's friendships and goodbye
> F5JMH
> Alain
> 
> Linux Ubuntu 14.04 
> 64bits--
> ___
> 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] WSJT-X: *Important* - please read if you build WSJT-X from source

[Alessandro Gorobey]

Hi Bill,

perfectly understand the problem with end of life components.

http://rohmfs.rohm.com/en/products/databook/applinote/ic/memory/eeprom/eeprom_replacement_guide_3_appli-e.pdf

The new components increase from 10E5 to 10E6 the number of write but 
are NOT plugin replacement.


I try a lot of combinations, but none work. Or go in error in transmit 
phase (eg. CQ IW3RAB JN65) or pressing Tune button.


The parameters on FT-857 involve the poor split functionality, and the 
only parameter on radio is SPL from VFOA e VFOB


Can provide me a working configuration of FT-857 ?
I use CAT PTT can be this the cause ?

Desperate I returned temporarily to the previous hamlib version

Thank in advance

73's
Sandro
IW3RAB

Il 20/11/2015 18:08, Bill Somerville ha scritto:

On 20/11/2015 16:50, Alessandro Gorobey wrote:

I do that from QT55 and compiling wsjtx rc2 and develop.
I obtain the errors that Bill have solved in September 2014 with tune
button, split etc.
ERR--> Rig split mode setting not consistent with WSJT-X settings.

With with qt55-disable return to QT5.
This hamlib3 are compiled in august 2015
Compile the some programs and all work well.

Rig is Yaesu 857.

Hi Sandro,

for the FT-817/857/897 I have removed the "advanced" Hamlib rig driver
we have been using for these rigs. This is unfortunate but is forced on
us by circumstances out of our control. The background is that these
rigs have quite limited CAT control command sets but also have an
extensive undocumented CAT capability, the "advanced" driver makes use
of these undocumented capabilities. Recently Yaesu contacted the HRD
developers asking them to remove similar capabilities from HRD which
they complied with. The concern from Yaesu is that these capabilities
use an undocumented CAT command that writes directly to rig's EEPROM
memory and the memory device used by Yaesu is passed end of life and is
no longer obtainable. The "advanced" Hamlib driver I wrote has never
been submitted upstream to the Hamlib team, it takes extreme measures to
minimize writes to EEPROM so as to reduce wear on the memory device
which I believe limits writes to no more than would be made by the rig
itself in normal operation and we have had no reports of device failures
due to WSJT-X. Nevertheless it seems prudent to pre-empt any issues by
withdrawing the "advanced" driver from WSJT-X.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 _ _     _  __  ___ _
| |_   _/ ___||  _ \| |/ / / _ \_   _|
 _  | | | | \___ \| | | | ' /_| | | || |
| |_| | | |  ___) | |_| | . \_| |_| || |
 \___/  |_| |/|/|_|\_\ \__\_\|_| 2.0.3-491


BUILD APPLICATIONS: ( WSJT-X WSJTX-RC WSPR-X MAP65 )
-

USAGE:  build-(app_name) (type)

 App Names : wsjtx wsjtxrc wsjtxexp wsprx map65
 Release Types : rconfig rinstall package
 Debug Types ..: dconfig dinstall

HELP SCREENS
-
 JTSDK-QT Help, Type ..: help-qtenv
 Checkout Help, Type ..: help-checkout
 Build Help, Type .: help-(app_name)

COMPILER INFO ( Mingw 49_32 )
-
 C++ : 4.9.2
 GFortran ...: 4.9.2
 GNU Make ...: 4.1

CRITICAL APP INFO
-
 Cmake ..: 3.0.2
 Cpack ..: 3.0.2
 QT5 : 5.5.0
 QMake ..: 3.0
 NSIS ...: v3.0b1
 InnoSetup ..: 5.5.5a
 Pkg-Cfg : 0.28

(JTSDK-QT 5.5 ) C:\JTSDK\zz\build\Debug)c:\jtsdk\zz\install\debug\bin\wsjtx
Hamlib: dummy: _init called
Hamlib: rig_register (1)
Hamlib: rig_register (2)
Hamlib: yaesu: initrigs3_yaesu called
Hamlib: rig_register (121)
Hamlib: rig_register (127)
Hamlib: rig_register (110)
Hamlib: rig_register (105)
Hamlib: rig_register (106)
Hamlib: rig_register (107)
Hamlib: rig_register (109)
Hamlib: rig_register (120)
Hamlib: rig_register (101)
Hamlib: rig_register (122)
Hamlib: rig_register (123)
Hamlib: rig_register (111)
Hamlib: rig_register (115)
Hamlib: rig_register (113)
Hamlib: rig_register (114)
Hamlib: rig_register (128)
Hamlib: rig_register (131)
Hamlib: rig_register (116)
Hamlib: rig_register (103)
Hamlib: rig_register (124)
Hamlib: rig_register (104)
Hamlib: rig_register (125)
Hamlib: rig_register (129)
Hamlib: rig_register (132)
Hamlib: rig_register (130)
Hamlib: rig_register (117)
Hamlib: rig_register (119)
Hamlib: rig_register (118)
Hamlib: rig_register (126)
Hamlib: rig_register (133)
Hamlib: rig_register (134)
Hamlib: rig_register (135)
Hamlib: initrigs3_kenwood called
Hamlib: rig_register (213)
Hamlib: rig_register (201)
Hamlib: rig_register (225)
Hamlib: rig_register (203)
Hamlib: rig_register (204)
Hamlib: rig_register (216)
Hamlib: 

Re: [wsjt-devel] display problem with screenshot sorry

[Alessandro Gorobey]

Hi Alain and All,

as using same OS can verify in addition if the time markers are cutted 
on widegraph as in my example ?


This happens to me after changing monitor. The dpi setting whose wrong 
calculated and cause a zoom effect on characters.

try this please
xdpyinfo | grep -B2 resolution

73's
Sandro
IW3RAB


Il 22/11/2015 18:08, Steven Franke ha scritto:

Alain,
I probably caused this by adding the new checkbox. It looked ok on OSX. I’ll 
take a look.
73 Steve k9an


On Nov 22, 2015, at 11:01 AM, f5...@free.fr wrote:

Hello all,

I have a small display problem on setting advanced, please see screenshot.
73's friendships and goodbye
F5JMH
Alain

Linux Ubuntu 14.04 
64bits--
___
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

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel