jt65.f90 has the wrong# of arguments to jt65a
It's missing mycall, hiscall, hisgrid
So I think the attached patch fixes it.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 5:58 PM, Scott Hernalsteen wrote:
> Hi all,
>
> I’m getting the attached error on the first successful decode cycle after
> starting
Barry --
Did you read my WSPRnet message posted here ?
http://wsprnet.org/drupal/node/5786
If not, please refer to it now.
We in the WSJT Development Group have nothing to do with running
WSPRnet. I hope the problem will be sorted out some time soon...
Of course, you don't need a WSPRnet acco
Hi all,
I’m getting the attached error on the first successful decode cycle after
starting the program. Dismissing the error dialog leaves the “DECODE” button
illuminated, however, no decoding is ever done.
I have a wave file from one of the time periods, however, the wav file
processes succe
Hi all,
I’m getting the attached error on the first successful decode cycle after
starting the program. Dismissing the error dialog leaves the “DECODE” button
illuminated, however, no decoding is ever done.
I have a wave file from one of the time periods, however, the wav file
processes succe
Bary, look in junk folder. I got the confirmation there :)
73 Tom
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/
Hi All,
Sorry this is off topic, but I am a bit stumped.
About a month ago I registered with WSPRnet using my callsign as
username and sat back to await a reply. Nothing has happened.
Yesterday I tried to log in using my callsign but it was apparently not
recognized.
I decided to re-register b
Hi Bill,
On 12/16/2015 03:19 PM, Bill Somerville wrote:
> On 16/12/2015 22:08, KI7MT wrote:
>> I did make progress on the Dynamic menu's this morning. I have both the
>> tagged and branch locations presenting properly, I just need to update
>> the wsjtx-sb bash script to work with the new menu's.
On 16/12/2015 22:08, KI7MT wrote:
> I did make progress on the Dynamic menu's this morning. I have both the
> tagged and branch locations presenting properly, I just need to update
> the wsjtx-sb bash script to work with the new menu's.
That sounds good Greg. Also it would help to be able to build
On 16/12/2015 22:08, Michael Black wrote:
> Why no line number in the run-time error? There was somebody else
> that had that problem a few weeks ago too.
> Does it need the debug version?
Hi Mike,
Yes, the Release configuration has minimal debug information.
It is always wise to use the Debug
> On 16 Dec 2015, at 18:59, Joe Taylor wrote:
>
> I think power settings by band is NOT a good idea, however. Indeed, in
> most setups power should not be set using our "Pwr" slider. The proper
> audio level should be set with the OS volume control, and power output
> then set with a contr
Hi Bill,
OK, I'll just back that stuff back out then, as it's not needed.
I did make progress on the Dynamic menu's this morning. I have both the
tagged and branch locations presenting properly, I just need to update
the wsjtx-sb bash script to work with the new menu's.
73's
Greg, KI7MT
On 12/
Why no line number in the run-time error? There was somebody else that had
that problem a few weeks ago too.
Does it need the debug version?
73
Mike W9MDB
On Wed, Dec 16, 2015 at 4:04 PM, Joe Taylor wrote:
> Mike --
>
> OK. Please remember that bug reports are most useful if they include a
> s
And I did send an earlier email which perhaps you missed. I got this error
on both hiscall and mycall numerous times.
Fortran runtime error: Actual string length is shorter than the declared
one for dummy argument "hiscall" (2/12)
On Wed, Dec 16, 2015 at 3:45 PM, Joe Taylor wrote:
> Mike --
Mike --
OK. Please remember that bug reports are most useful if they include a
set of steps that will reproduce the undesired behavior. As far as I
could see, opening and decoding your dropbox file does not produce any
error.
You know your way around the WSJT-X code well enough that you shou
> On 16 Dec 2015, at 15:09, Michael Black wrote:
>
> This patch (attached) remembers where you set the Pwr slider during tuning
> and restores it for subsequent tunes. Also restores it back after tuning
> to wherever it was before tuning.
> It saves the result in the settings file so the level
I had several of these errors (about 10 times) and now they aren't
occurring again.
I restarted WSJT-X several times and the error repeated on the next decode.
But now it's not doing it.
Phase of the moon?
I will, naturally, let you know if this repeats again.
73
Mike W9MDB
On Wed, Dec 16, 2015
Mike --
Your cryptic message is not meaningful to me.
Opening your file 151216_2114.wav in my WSJT-X-v1.7.0-devel-r6285
produces this output (and no errors):
2114 -19 1.0 769 # WA8AXF PU2KKE GG66
2114 -7 0.1 1032 # CQ KI6CYT CM87
2114 -4 -0.4 1073 # CQ WA7YOK CN88
2114 -16 1.1 1329 # CQ P
On 16/12/2015 21:37, Bill Somerville wrote:
It comes into play when you have a
pre-configured package and want to install it in some place other than
the prefix specified at install time.
Oops, I should have written:
want to install it in some place other than
the prefix specified atinstall *c
On 16/12/2015 21:27, KI7MT wrote:
> the use of DESTDIR, and I may have
> misunderstood what the need was.
Hi Greg,
DESTDIR is a bit confusing. It comes into play when you have a
pre-configured package and want to install it in some place other than
the prefix specified at install time. I believe
Hi Joe,
OK, I'll back this out on the next update and have a re-think on it. It
came up on the devel-list, the use of DESTDIR, and I may have
misunderstood what the need was.
73's
Greg, KI7MT
On 12/16/2015 02:20 PM, Joe Taylor wrote:
> Hi Greg,
>
> Not sure why you would ever want to put the ex
Hi Greg,
Not sure why you would ever want to put the executables in a place like
/home/joe/jtsdk/wsjtx/1.7.0/6283/install/Release/usr/bin/wsjtx ???
Anyway, all is OK after putting CM_PREFIX="".
-- Joe
On 12/16/2015 4:05 PM, KI7MT wrote:
> Hi Joe,
>
> I should have noted this in the Chan
Repeated error on r6284
Appears to be any JT9 decode.
This WAV file causes the same error but "for dummy argument "mycall" (1/12)
https://www.dropbox.com/s/7dx3sy5k1gjjlrt/151216_2114.wav?dl=0
73
Mike W9MDB
--
__
Fortran runtime error: Actual string length is shorter than the declared
one for dummy argument "hiscall" (2/12)
I think perhaps it burped on this decoded line:
RR 10W VRT 73
I wasn't saving wav files so don't have it.
Mike W9MDB
-
Hi Joe,
I should have noted this in the ChangeLog. The intention, though not
fully implemented, is to use that DESTDIR or --prefix options that are
available.
In this case, I hard-coded the CM_PREFIX at the top of the jtsdk-wsjtx
script to ( /usr ) so the local installation mirrors what would be
On 16/12/2015 18:36, Michael Black wrote:
> Did you commit the shift change?
Hi Mike,
it's in now. I'll hold off on the User Guide patch until this settles down.
73
Bill
G4WJS.
--
___
Just FYI,
I've disabled both the wsjtx_exp and wsjtx (currently at v.1.7.0) PPA's
on Launchpad. When v1.7.0-RCx is released, I'll re-enable it for Public
Installation / Testing.
The v1.6.0 GA Release is still available and will keep pace with any
updated releases from Joe.
73's
Greg, KI7MT
On
Hi Greg,
Unless I've done something wrong, jtsdk-nix-2.0.18 seems to be
installing to the wrong place:
-- Installing:
/home/joe/jtsdk/wsjtx/1.7.0/6283/install/Release/usr/bin/wsjtx
Should be .../install/Release/bin/wsjtx
NOT: .../install/Release/usr/bin/wsjtx
-- Joe
To: WSJT-X Developers and Testers of Experimental Code
With v1.7.0 r6283 I have made a first cut toward eliminating false
decodes when the new JT65 decoder is used on a crowded HF band. I can
now relax the embargo imposed yesterday (see messages copied below).
If you are helping us with tests
On 12/16/2015 12:59, Joe Taylor wrote:
> Mike and all,
>
> On 12/16/2015 12:00 PM, Michael Black wrote:
>> This brings up the idea that perhaps we should remember power level for
>> each mode/band.
>
> Let's not get carried away implementing special-purpose features. Lower
> power for Tune is prob
On 16/12/2015 19:16, KI7MT wrote:
> - Removed make clean steps to increase rebuild speed
Hi Greg,
this is excellent!
Hopefully developers will use the CMake build now either via JTSDK or
directly. Many billions of electrons will be left undisturbed instead of
having to push all those unnecessar
Hello All,
For those using JTSDK-Nix, an updated version is available. This update
fixes the WSJT-X build script issues reported earlier this week and a
few other minor issues.
*CHANGE-LOG*
- Removed wsprd_exp build via developer Makefile
- Fixed User Guide builds
- Removed make clean steps to
On 16/12/2015 18:36, Michael Black wrote:
> Did you commit the shift change? I don't see it.
Hi Mike,
just sorting out the tool tip, that turns out to be the complicated part.
73
Bill
G4WJS.
--
_
Did you commit the shift change? I don't see it.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 12:22 PM, Bill Somerville
wrote:
> On 16/12/2015 18:17, Michael Black wrote:
> > How about the opposite approach?
> > The shift key on the Tune click prevents it? That fits right in the
> > event chain then.
On 16/12/2015 18:17, Michael Black wrote:
> How about the opposite approach?
> The shift key on the Tune click prevents it? That fits right in the
> event chain then.
Hi Mike,
my suggestion was based on not changing the existing functionality so no
surprises for those used to the "Pwr" slider s
How about the opposite approach?
The shift key on the Tune click prevents it? That fits right in the event
chain then.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 12:08 PM, Bill Somerville
wrote:
> On 16/12/2015 17:59, Joe Taylor wrote:
> > I think power settings by band is NOT a good idea, however.
On 16/12/2015 17:59, Joe Taylor wrote:
> I think power settings by band is NOT a good idea, however. Indeed, in
> most setups power should not be set using our "Pwr" slider. The proper
> audio level should be set with the OS volume control, and power output
> then set with a control in the radio.
Mike and all,
On 12/16/2015 12:00 PM, Michael Black wrote:
> This brings up the idea that perhaps we should remember power level for
> each mode/band.
Let's not get carried away implementing special-purpose features. Lower
power for Tune is probably useful for some, and OK.
I think power setti
This brings up the idea that perhaps we should remember power level for
each mode/band. So, for example, you're in 20M/JT65 and you switch to 30M
you get the last 30M/JT65 power level you used, then switch to JT9 and get
the last 30M/JT9 level you used.
I could work on thatit's not much diffe
Goodmorning everyone.I thank the whole team for their hard work.Thanks for
checking power in tune with memory.It would help control power with memory tx
JT9 different for JT65.This seen in my use of power in two ways.Merry Christmas
73 Franco iz0mit
Messaggio originale
Da: mdblac...@
I think the idea of remembering power levels by band too is a good idea.
Question is, should that be an option one can turn on/off?
Again...is there any case where you would NOT want that?
Personally I'm in the same boat as you but just adjust power when I start
transmitting.
73
Mike W9MDB
On Wed
On 12/16/2015 09:09, Michael Black wrote:
> This patch (attached) remembers where you set the Pwr slider during tuning
> and restores it for subsequent tunes. Also restores it back after tuning
> to wherever it was before tuning.
> It saves the result in the settings file so the level will be reme
I added a sentence to each section talking about tuning. I tend to be
terse
Not sure it needs much more than this, does it?
Mike W9MDB
On Wed, Dec 16, 2015 at 9:34 AM, Bill Somerville
wrote:
> On 16/12/2015 14:46, Michael Black wrote:
>
> Oops...I though I had a clean branch...some leftove
On 16/12/2015 14:46, Michael Black wrote:
Oops...I though I had a clean branch...some leftovers in there from a
prior debug. Shoulda' reviewed that patch myself before sending.
It does have the m_settings->Setvalue in it.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 8:25 AM, Bill Somerville
mailto:
Oops...I though I had a clean branch...some leftovers in there from a prior
debug. Shoulda' reviewed that patch myself before sending.
It does have the m_settings->Setvalue in it.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 8:25 AM, Bill Somerville
wrote:
> On 16/12/2015 14:09, Michael Black wrote:
On 16/12/2015 14:09, Michael Black wrote:
> This patch (attached) remembers where you set the Pwr slider during tuning
> and restores it for subsequent tunes. Also restores it back after tuning
> to wherever it was before tuning.
> It saves the result in the settings file so the level will be
> r
This patch (attached) remembers where you set the Pwr slider during tuning
and restores it for subsequent tunes. Also restores it back after tuning
to wherever it was before tuning.
It saves the result in the settings file so the level will be remembered
across
restarts too.
Do we need to make th
Bill, this is good information and clarification. Thanks for taking the time to
put this together.
73,
Jim S.
N2ADV
> On Dec 16, 2015, at 6:47 AM, Bill Somerville wrote:
>
>> On 16/12/2015 11:15, Guy G4DWV/4X1LT wrote:
>> Hi,
> Hi Guy,
>>
>> Does this mean that Joe does not want users to go
Hi Guy,
note that the information in that document is quite old and things have
moved on a bit. I believe the basic encoding is still the same but some
of the implementation details have changed during incremental
improvements. Most notably the longer T/R periods are no longer
supported in WSJ
On 16/12/2015 11:34, Guy G4DWV/4X1LT wrote:
> could you supply a link for the JT9 protocol?
https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/jt9.txt
73
Bill
G4WJS.
--
__
On 16/12/2015 11:15, Guy G4DWV/4X1LT wrote:
> Hi,
Hi Guy,
>
> Does this mean that Joe does not want users to go on the air with the latest
> builds compiled with JDSDK?
At present that is the recommendation for the development branch. The
intent is that during periods of disruptive development we
Sri to butt in Joe, but could you supply a link for the JT9 protocol? I
found the article on JT65 interesting even though much of it went way above
my current understanding of the subject.
TIA
--
Hi,
Does this mean that Joe does not want users to go on the air with the latest
builds compiled with JDSDK?
Does this mean that I can only use the official release in future?
Sorry for the questions, but I do not know what 'head of the branch' means,
but I think that my guess could be close to
On 16/12/2015 00:48, Joe Taylor wrote:
> Important note to those who have been compiling and using code at the
> head of the WSJT-X Development branch, also known as "Version 1.7":
>
> REVISION 6278 IS TEST CODE, NOT INTENDED FOR ON-THE-AIR USE. PLEASE
> RESPECT THIS REQUEST AND DO NOT USE IT FOR
53 matches
Mail list logo
