Picon

Possible bug on signal/channel browsers, fldigi 3.22.02



Compiled on Debian Wheezy a few weeks ago.  Whether I use the docked channel panel, or the free-floating signal browser window, I can click on a conversation and have the cursor focus change on the waterfall (as it's always worked).  However, if I click on a promising waterfall signal, it no longer updates the focus/highlight on either the signal or channel browser views.  Am I missing a config option or is it a potential bug?

73, KD0KZE / Paul




__._,_.___
Posted by: pfbram-Wuw85uim5zDR7s880joybQ@public.gmane.org



__,_._,___
Picon

How to update your OS X fldigi LoTW Users Listing

This posting is for Mac OS X/fldigi users but may be useful for other platforms.

One of the cool items in fldigi is when you mouse hover over a call sign, a popup tooltip displays information
about the call sign, including if the call is an active LoTW user.  Your fldigi obtains the LoTW information
from the lotw1.txt file that is located in your .fldigi folder.

Open your .fldigi folder (File/Folders/Fldigi config...) and check the date on your lotw1.txt file. If
old or you cannot find the file, get an updated listing by going to following web page:

http://www.hb9bza.net/lotw/lotw1.txt

Give the page a few seconds to load into Safari and will see a LONG list of calls

1A0C
1A0KM
1A3A
1A4A
2A/DJ6AU
2A0APF
2A0APF/P
2A0BQI
2A0BQI/P
2A0BSM
<snip>

Now for the good stuff.  Once the current list is fully populated in Safari, right-click on the screen and
select the option to Save As and it should give you a standard OS X Save As dialog box. Be sure you select the
Page Source format option at the bottom and save the file with the lotw1.txt filename.  I usually save the
file to my desktop to check the file with a text editor before drag copying the updated file to my .fldigi folder.

I hope this tip is useful and will be used to update you fldigiā€™s lotw1.txt file

73 Dick AA5VU

------------------------------------
Posted by: Dick Kriss <aa5vu@...>
------------------------------------

Picon

Re: Success! Native Linux ax.25 + FLDIGI/KISS




Hello Remi,


<!-- /* start of attachment style */ .ygrp-photo-title{ clear: both; font-size: smaller; height: 15px; overflow: hidden; text-align: center; width: 75px; } div.ygrp-photo{ background-position: center; background-repeat: no-repeat; background-color: white; border: 1px solid black; height: 62px; width: 62px; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited { text-decoration: none; } div.attach-table div.attach-row { clear: both; } div.attach-table div.attach-row div { float: left; /* margin: 2px;*/ } p { clear: both; padding: 15px 0 3px 0; overflow: hidden; } div.ygrp-file { width: 30px; valign: middle; } div.attach-table div.attach-row div div a { text-decoration: none; } div.attach-table div.attach-row div div span { font-weight: normal; } div.ygrp-file-title { font-weight: bold; } /* end of attachment style */ --> Does it mean this it possible to run ftp, telnet etc... on AX25 with fldigi ? I used to do that with soundmodem and it was absolutely fantastic to ftp a file with 1200 bauds. Did someone try to use FBB ?

Yes.. you can assign an IP address to the AX interface and it should start working!  I don't know if I would recommend it though... TELNET even over 1200baud can be pretty tough. 



PS: Moved one year ago, could not have an antenna, but it should be ready in one or two months.

Good luck and it will be good to have you back on the air!

--David
KI6ZHD


__._,_.___
Posted by: David Ranch <linuxham-fld-U76wwbNhhF3R7s880joybQ@public.gmane.org>



__,_._,___
Picon

fldigi 3.22.02



With fldigi 3.22.02 I am getting very little power out
with the MT63 protocols.

With a system setting where I show about 50 Watts out on
the radio power meter function, I show NO power out at
all with MT63.  Even my system monitor scope shows
very little power.

I cannot push my sound card setting hight enough to get
the required power out with MT63.

I'm going to have to go back to an earlier version for my
operations.

Thanks and 73,

Mike, K0TER/NNN0SBK




__._,_.___
Posted by: stansberrymj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org



__,_._,___
Picon

Re: Digest Number 3290



p{margin: 0;padding: 0;}

David, G0WBX wrote

"My understanding is that many commercial (and most military) types, quote a
working (or channel) frequency, as being in the middle of the occupied channel,
be it voice, data or ??? (Sort of makes sense I think.)

"Us good old boys on the other hand, qoute the suppresed carrier frequency,
hence the offset needed."

I think all licensed services except ham radio do it that way. I, for one, would support a move in amateur radio to do the same- refer to frequencies by the center of the transmitted signal, not the suppressed carrier.  Why post that a net meets on "3582 kHz +1500" when you can just list it as "3583.5 kHz"?  Individual operators can determine what audio frequency works best for their equipment. 

And, while we're at it, let's get rid of LSB. It offers nothing USB doesn't; it is redundant and superfluous, in my opinion.

 

Ken, W1KRT

 



__._,_.___
Posted by: "=?utf-8?b?S2VuIERvd25z?=" <krtdowns <at> myfairpoint.net>



__,_._,___
Picon

Re: Decoding HF WEFAX transmissions

> Decoding HF WEFAX transmissions
>     Posted by: "D.J.J. Ring, Jr." n1ea@... djringjr
>     Date: Thu Dec 11, 2014 10:26 am ((PST))
> 
> Decoding HF WEFAX transmissions
> http://www.newearth.demon.co.uk/radio/hfwefax1.htm
> 
> Fldigi is excellent for FAX.
> 
> All maritime radio is USB as we had no LSB.
> 
> I remember a little memory device I used to get to the radio dial
> settings from the published frequencies which were 1900 Hz higher.
> 
> I used to say to myself: "Down two, plus one!" when tuning.  We used
> decade switches, the unit number's switch was pushed down 2 kHz and
> the decimal switch 100 Hz was pushed up.
> 
> So FAX from Norfolk, VA on 8080.0 kHz went down two to 8078.0 then
> plus one to be 8078.1 kHz.
> 
> Odd memory device but it was easier than subtracting 1.9 kHz.
> 
> 73
> 
> David N1EA

Hi.

My understanding is that many commercial (and most military) types, quote a 
working (or channel) frequency, as being in the middle of the occupied channel, 
be it voice, data or ???   (Sort of makes sense I think.)

Us good old boys on the other hand, qoute the suppresed carrier frequency, 
hence the offset needed.

Not helped any, by the "convention" caused by the early commercial Ham SSB 
radios, using LSB below 10MHz (due to the 9MHz IF commonly used, and only 
one carrier generation crystal, to keep complexity & costs down.)

I can't off-hand think of any commercial/military system that uses LSB, though 
there is probably some obscure setup somewhere.

What fun eh?..

73.

Dave G0WBX.

------------------------------------
Posted by: "Dave B" <g8kbvdave@...>
------------------------------------

Picon

Re: Re: Native ax.25 + FLDIGI/KISS testing program


More Improvement...

With the socat command:    socat 
PTY,link=/root/fldigi-dev,raw,echo=0,wait-slave UDP4:127.0.0.1:7342

outgoing AX25 connections with:    call fld ab4mw-1

would key up the radio and send out the request via Fldigi. 
Unfortunately, all heard signals (really received or using the File --> 
Audio --> Playback feature) wouldn't do anything.  Why wasn't RX working?

When using "nc -u -l 127.0.0.1 7342" to connect to fldigi, it **would** 
show output coming to STDOUT where as socat wouldn't show anything.  
Notice the SOURCE port:
    # netstat -an | grep 7342
    udp        0      0 127.0.0.1:7342 127.0.0.1:7342              
ESTABLISHED

but I could NOT get this netcat behavior to be duplicated as socat would 
always complain:

socat UDP:127.0.0.1:7342,sourceport=7342 -,raw,echo=1
socat[20482] E bind(3, {AF=2 0.0.0.0:7342}, 16): Address already in use

until I tried:

socat UDP:127.0.0.1:7342,sourceport=7342,reuseaddr -,raw,echo=1

That works just like netcat!  I then kissattached to the PTY interface 
and via Fldigi's nifty "File --> Audio --> playback" feature, I can see 
in my Linux AX.25 stack:

fld: fm AB4MW-5 to KI6ZHD-8 ctl SABM+ 21:31:25
fld: fm KI6ZHD-8 to AB4MW-5 ctl UA- 21:31:25
fld: fm KI6ZHD-8 to AB4MW-5 ctl UA- 21:31:25
fld: fm AB4MW-5 to KI6ZHD-8 ctl DISC+ 21:31:33
fld: fm KI6ZHD-8 to AB4MW-5 ctl UA- 21:31:33
fld: fm KI6ZHD-8 to AB4MW-5 ctl UA- 21:31:33

As you can see, I'm both hearing the packets AND the stack is replying 
to them!  Unfortunately, TX was broken and I couldn't TX anything via 
Fldigi anymore.  Putting the two together worked but it doesn't seem to 
be reliable:

# Do NOT use Fldigi's KISS "dual-port" feature or RX breaks
#
#    I also don't understand how this dual-port feature works as port 
7343 never shows up in "netstat -an | grep -e 7342 -e 7343"

So as a compromise, I run BOTH:

#For TX
$SOCAT PTY,link=$FLDIGIPTYFILE,raw,echo=0,wait-slave UDP4:127.0.0.1:7343 &
#For RX
$SOCAT PTY,link=$FLDIGIPTYFILE,raw,echo=0,wait-slave 
UDP4:127.0.0.1:7342,sourceport=7342,reuseaddr &

It seemed to have worked ONCE but I'm guessing here that socat is 
getting conflicts on the PTY interface.  I think this is closer but I'm 
still scratching my head.

Btw, it seems that Wireshark can't dissect AX.25 over KISS over UDP - 
https://www.wireshark.org/lists/wireshark-bugs/201208/msg00064.html .   
I've emailed the author to see if there is a way to fix this!

--David
KI6ZHD

------------------------------------
Posted by: David Ranch <linuxham-fld@...>
------------------------------------

Picon

Re: BFB297



Hello Group and Bill Weibel -

I used N5R-213(140906N)(factory).img
for the one that said N5R-219 and it worked.

The instructions seem to be confusing to me and I thought the N5R numbers would be the firmware image needed.

The units take the frequencies, write them, can transmit on the correct frequencies and the problem of having to use the MONI key to hear is gone.

Thanks

David N1EA

On Thu, Dec 11, 2014 at 8:08 PM, Bill Weibel  wrote:
Try this img file it should take you back to factory spec.


Bill



__._,_.___
Posted by: "D.J.J. Ring, Jr." <n1ea-WYrOkVUspZo@public.gmane.org>



__,_._,___
ab4mw | 11 Dec 21:05 2014
Picon

PORT and/or PULSE



I have both installed.  Port/ALSA yells errors and neither gives me waterfall yet.  I am afraid one is causing issues with the other.

SHould I pick one or can I safely have both?


I: Open: Port Audio open mode = Read, device type = paALSA
I: src_data_reset: rbsize = 16384
ALSA lib pcm_hw.c:1667:(_snd_pcm_hw_open) Invalid value for card
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1736
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir, &self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1904
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi, inParams, StreamDirection_In, NULL != callback )' f ailed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2171
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi, inputParameters, outputParameters, sampleRate, framesPerBuffer, callback, streamFlags, userData )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2840
E: pa_perror: Portaudio open stream error: Illegal combination of I/O devices
E: trx_trx_receive_loop: PortAudio error: Illegal combination of I/O devices. line: 223

Xubuntu 14 latest kernel  fldigi 3.22_02 freshly compiled today, but I had the same issue with the kamal version 3.22_01



__._,_.___


__,_._,___
Picon

flex xml definition files for fldigi

Tim Ellison, W4TME, the Customer Experience Manager for FlexRadio 
Systems has  updated the xml definition files for the Flex radios. They 
have been uploaded to

http://www.w1hkj.com/xmls/sdr/

73, Dave, W1HKJ

------------------------------------
Posted by: w1hkj <w1hkj@...>
------------------------------------

Picon

Decoding HF WEFAX transmissions



Decoding HF WEFAX transmissions
http://www.newearth.demon.co.uk/radio/hfwefax1.htm

Fldigi is excellent for FAX.

All maritime radio is USB as we had no LSB.

I remember a little memory device I used to get to the radio dial settings from the published frequencies which were 1900 Hz higher.

I used to say to myself: "Down two, plus one!" when tuning.  We used decade switches, the unit number's switch was pushed down 2 kHz and the decimal switch 100 Hz was pushed up.

So FAX from Norfolk, VA on 8080.0 kHz went down two to 8078.0 then plus one to be 8078.1 kHz.

Odd memory device but it was easier than subtracting 1.9 kHz.

73

David N1EA



__._,_.___
Posted by: "D.J.J. Ring, Jr." <n1ea-WYrOkVUspZo@public.gmane.org>



__,_._,___

Gmane