[pskmail] Re: Aw: Re: Re: fldigi

  • From: Remi Chateauneu <remi.chateauneu@xxxxxxxxx>
  • To: pskmail@xxxxxxxxxxxxx
  • Date: Thu, 7 Mar 2013 16:48:25 +0000

"we need to control this as fldigi is a constant source of trouble."

If someone can gain control on how new fldigi releases are issued, how they
are tested etc... this can probably enhance things.

Maybe, for example,  we could have several builds available:
* Stable (Tested by everyone).
* Development (With recent commits, usable but with bugs).
* Last night build.

This would probably allow developers or courageous users, to use and test a
development version, while the others would simply download the stable one.


On Thu, Mar 7, 2013 at 1:04 PM, Pär Crusefalk <per@xxxxxxxxxxxx> wrote:

>  I agree that we need to control this as fldigi is a constant source of
> trouble.
> But, people will get the latest fldigi from distro repositories anyway so
> devoting test capacity to fldigi will unfortunately bring nothing.
> Fldigi will continue to evolve and break things. Don't get me wrong,
> fldigi is great but it's main use case is not as a remote controlled modem.
> Best path ahead should be to remove fldigi entirely.
>
> 73, Per
> sm0rwo
>
> Remi Chateauneu skrev 2013-03-07 13:37:
>
> It would probably be safer to deliver fldigi and its client, at the same
> time from the same code repository and the same language.
> At least you could control exactly what is delivered. This remark because
> it's not the first time fldigi is blocking pskmail:
>
>
> //www.freelists.org/post/pskmail/Fldigi-for-windows-bug-fixed-pse-upgrade,2
>
> "*Date*: Sat, 02 Jan 2010 13:44:25 +0100
>  the problem was in fldigi. the new 3.13BK version can be downloaded from
> hermes.esrac.ele.tue.nl/pskmail/fldigi or "
>
> //www.freelists.org/post/pskmail/fldigi,22
>
> "This is very strange! Before changing to 3.21.41 I had un uptime for 24h
> at the most, well some times it could run for a longer time. After updating
> it has been up for 48h now!!"
>
> //www.freelists.org/post/pskmail/Aw-Re-Fldigi-crash,2
>
> "Mon, 23 Apr 2012 07:34:33 -0500
>
> I had several crashes in FLDigi over the weekend testing the new JD3 modes
> using only FLDigi."
>
> What do you think ?
>
>
>
>
> On Thu, Mar 7, 2013 at 11:22 AM, Rein Couperus <rein@xxxxxxxxxxxx> wrote:
>
>>  The V2 modem is top priority on my todo list for @home :)
>>
>>  I have been happily using the V2 client during my stay here in Spain...
>> Version 2.0.31 is extremely stable now. Next will be to put the V2 modem
>> on the PI4TUE server
>> for testing...
>>
>>  Rein (still) EA/PA0R/M
>>
>>
>>  Hi,
>>
>> So, fldigi is killing the project. New users will get the latest, have a
>> terrible experience and move on...
>> Moving everybody to the version two client is a step in the right
>> direction but then we have to take care of the server side also.
>> Actually, I just fired up the stand alone modem and got it working
>> nicely. I changed a few things to make it more stable (submitted in
>> subversion) and now it's actually working.
>> I'm not saying we should use that as is but if we could make it work as
>> well as the v2 client then I would use it on my server also.
>>
>>
>> [image: V2modem]
>>
>> 73, Per
>> sm0rwo
>>
>>
>>
>> Rein Couperus skrev 2013-03-07 09:28:
>>
>>  A lot of Linux users have also updated to 3.21.6x for various reasons...
>>  The effect is indeed that data exchange is almost impossible.
>>  There is no reason to use fldigi versions higher than 3.21.40 for
>> pskmail, because
>> the ARQ interface had been stable since it was implemented the first time
>> in 2006.
>>
>>  @remi:
>> The ARQ interface was introduced into fldigi especially for pskmail,
>> which initially used the file system to communicate between the programs.
>> The xmlrpc interface came a lot later, and as the ARQ interface has
>> worked
>> perfectly from the start there is not any reason to chane to xmlrpc...
>> It went wrong when fldigi started to use the ARQ interface for AMP-2
>> (http://www.w1hkj.com/downloads/Amp.2.0.Specification.html).
>>
>>  Rein EA/PA0R/M
>>
>>   Am I right, that this causes following effect:
>>
>> 1) linux-clients: are able to establish connections and exchanging data
>> because fldigi package-versions in most linux-distributions are not
>> higher then 3.21.4x
>> 2) windows-users, running clients 1.5.x with actual fldigi-versions: are
>> also able to establish connections but ARE NOT ABLE TO EXCHANGE DATA?
>>
>> This would explain a lot of broken connections on my server...
>>
>> 73 de Franz, oe5rtl
>>
>>
>>
>> Am Mittwoch, den 06.03.2013, 15:42 +0100 schrieb Klaus Lohmann:
>> > Linux Mint 13 (Maya)
>> >
>> > This line appears on fldigi protocol panel (correct):
>> > <SOH>00uDL4OAH:26 !5227.76N/00944.50E-060/000/W7-64 1.5.11
>> > NoHF9E8B<EOT>�<s2n: 66, 100.0, 0.0>
>> >
>> > This is what the pskmail server gets from the socket:
>> > <SOH>00uDL4OAH:26 !5227.76N/00944.50E-060/000/W7-64 1.5.11
>> NoHF9E8�<s2n:
>> > 66, 100.0, 0.0>B<EOT>
>> > <SOH>00uDL4OAH:26 !5227.76N/00944.50E-060/000/W7-64 1.5.11
>> > NoHF9E8B�<s2n: 66, 100.0, 0.0><EOT>
>> > <SOH>00uDL4OAH:26 !5227.76N/00944.50E-060/000/W7-64 1.5.11
>> > NoHF9E8B�<s2n: 66, 100.0, 0.0><EOT>
>> > <SOH>00uDL4OAH:26 !5227.76N/00944.50E-060/000/W7-64 1.5.11 N�<s2n: 66,
>> > 100.0, 0.0>oHF9E8B<EOT>
>> >
>> > Somehow the character sequence of the last part of the line is mangled.
>> >
>> > Am 06.03.2013 14:51, schrieb Remi Chateauneu:
>> > > Which platform is it please ?
>> > >
>> > >
>> > > On Wed, Mar 6, 2013 at 1:17 PM, Klaus Lohmann 
>> > > <dl4oah@xxxxxxxxxx><http://dl4oah@xxxxxxxxxx>wrote:
>> > >> FYI:
>> > >>
>> > >> I moved to fldigi 3.21.68 and found, that there is no reliable
>> communication
>> > >> between fldigi and the server.
>> > >>
>> > >> Changed back to 3.21.40, which freezes sometimes but at least is
>> usable
>> > >> between the freezes.
>> > >>
>> > >> 73
>> > >> Klaus DL4OAH
>> > >>
>> > >
>> >
>> >
>>
>>
>>
>>
>>
>>
>>
>
>

PNG image

Other related posts: