headers
Leif Asbrink | 9 Jul 12:54

Linrad-02.15

Hi All,

Linrad-02.15 is now uploaded. Besides a few bug fixes
the main difference is that data files generated by
Linrad go into dedicated directories. These data
files are defined in a new header file: options.h

This file also contains other compile time options
(debug tools) that previously were defined in vernr.h.

The directories are
GIFDIR for screen dumps (cmd="G")
WAVDIR for standard sound files in pcm format (cmd="W")
RAWDIR for raw data in Linrads own format (cmd="S")

Raw data files now have the extension .raw

Currently the default for all three directories is 
the same: /home/linrad_data or C:\linrad_data depending 
on the operating system.

The "S" option did not work with SDR-14 on previous 
versions. Now .raw files up to a bandwidth of 230 kHz 
can be saved on the Debian Etch system with a Pentium 4.

The fatal error 1224 (Overrun error. Is Linrad 
swapped to disk??) is changed to a warning. This
error occurs under Windows when other programs 
do not allow Linrad to take care of the A/D raw
data fast enough.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 11 Jul 23:37

BUG: Coherent graph position

Hello all,

With Linrad-02.15, the coherent graph adjusts its 
size better for different font sizes. While doing
these changes I forgot to remove a provocation
to put the graph at its default position always.

To make Linrad-02.15 remember the position for
the coherent graph, change lines 428 and 429 of
coherent.c from this:
xsiz=3*cg_size+1;
ysiz=xsiz+16*text_height+2;

To this:
xsiz=3*cg_size+2;
ysiz=xsiz+6*text_height+2;

There is a new option in options.h. If you increase
COH_SIDE the coherent graph becomes bigger and the
S-meter will show RMS powers with more decimals.
(Useful on strong carriers and when averaging
noise over long times with the F2 key)

73

Leif

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 13 Jul 11:35

extra.c

If you want to add your own things into Linrad
using extra.c from version 02-15 you have to
correct the first line which reads:
#incluse <sys/time.h> 

The correct line should be:
#include <time.h>

73

Leif / SM5BSZ

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
Leif Asbrink | 15 Jul 00:23

Linrad-02.16

Hi all,

Linrad-02-15 had a fix to avoid segfaults under
Free BSD that were related to the timing between
how the different threads start executing. Now
the dsp threads wait for the screen thread to
enter its idel state before producing data and that
guarantees that memory is properly initiaded.
(at least for this particular problem)

As it turns out I forgot to make the waiting loops
conditional of the existence of a screen thread and
therefore the calibration routines of 02-15 do not
work. This is now fixed as well as the previously 
announced bugs. 

73

Leif

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
w3sz | 20 Jul 06:01
Picon

Linrad for Windows FT1000 addon

Hello, All!

I hope you are all having a good summer.  Below describes some slightly  
silly programming I did to slightly enhance my use of Linrad for Windows.   
Delete now if you tend to be bored or annoyed by my long and rambling  
emails.

Read on if you like to criticize / comment or have lots of free time ;)

When Linrad for Windows became available, I wanted to extend it so that it  
would work with my [Linrad for Linux] addon that allowed Linrad to control  
the frequency of my FT1000MP.  Not being a computer-literate person, I was  
not able to get a Windows XP COMport solution to work with the mingw32  
compiler that Leif uses to compile Linrad for Windows, and I was not able  
to rewrite the makefile so that Linrad could be compiled with one of the  
free C compilers that works with one of the various COMport solutions for  
Windows XP.

So I 'solved' the problem in a brute-force way by having my addon to  
Linrad for Windows write to a file the frequency that is to be sent to the  
FT1000MP whenever 'Q' is typed in Linrad, and then having a Visual Basic  
program read this file and send the frequency to the FT1000MP via the  
COMport.  This works well for controlling the FT1000MP frequency via a  
COMport from my main Linrad for Windows computer.

For the June ARRL VHF contest I set up 4 instances of Linrad running  
simultaneously on an auxiliary computer so that I could at all times  
monitor the 50, 144, 222 and 432 MHz bands with Linrad, so that if there  
was a band opening for example on 50 MHz while I was on 144 MHz, I could  
see it quickly and QSY to the appropriate band.
(Continue reading)

Permalink | Reply | 0 comments |
headers
w3sz | 21 Jul 01:14
Picon

wusers_hwaredriver.c uploaded

Hello, All,

This is just a followup to my email of late yesterday or early today,  
depending on your timezone.

I added the wusers_hwaredriver.c file to the zip file at:

http://www,nitehawk.com/w3sz/linft1000.zip

I checked the link and everything downloads OK.

Have a great weekend, and

73,

Roger Rehr
W3SZ

--

-- 
Roger Rehr
W3SZ
http://www.nitehawk.com/w3sz/

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 23 Jul 19:52

Windows bug workaround.

Hi All,

This bug report from Daniel, DL3IAE is of interest to
everyone trying Linrad on a Windows machine.

> in wlr2-16 (older versions too!) the usage of the 
> different filter options above the line "reserved 
> for blanker" are causing crashes of linrad or muting 
> of the sound output. (except for the lim,exp function)

The problem is that Linrad can not close the sound output
device and subsequently open it with different parameters
under Windows. (speed, channels or 8/16 bits)

The work-around is as follows. Start Linrad, but do not
click on any signal. Then you can use the boxes and
select various options. Look at the number at the right
hand side that indicates the current mode of operation.
Then press X followed by P and set the "Default output
mode" to the number you want (and perhaps change the output
speed if you wish). Then go to the main menu and exit.
Next time Linrad will start in the selected mode.

It is a good idea to select Default output mode = 3.

This is the meaniong of the two lowest bits:
00  8 bits one channel
01 16 bits one channel
10  8 bits two channels
11 16 bits two channels.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 30 Jul 13:04

Re: More Linrad Additions


Hi Roger,

I am sendin this via the mailing list since my mail bounces
reason: 550 [PERMFAIL] comcast.net requires valid sender domain

> I want to add a 'mute' control to Linrad so that one can 
> mute the audio output.  
> Then when one clicks on the next signal I want the audio output to be 
> re-enabled until the mute is hit again.
> 
> The mute could be done either by typing a key or clicking 
> on something on the screen.
The mute function is that you right-click on the selected signal.
You may left-click and then immediately right-click (without move)
to have the mouse on the correct place.

The signal continues for the time you have in buffers.

For an immediate mute, do the following from your user
routine:

  mix1_selfreq[0]=-1;
  lir_empty_da_device_buffer();
  clear_da();
  lir_sleep(10000);
  lir_empty_da_device_buffer();

You can make your own users_graph with any number of boxes to click
for this and other functions.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 31 Jul 01:23

Re: modified users_extra.c

Hi Roger and all,

I can still not send any E-mail to comcast.com so I reply
via the mailing list.

> It turned out that it was a bit of a problem having 4 instances of Linrad  
> running, with 3 of them muted, and trying to figure out which one was NOT  
> muted.
;-)

> Running with the standard users_extra.c was some help, as the users_extra  
> frequency and S meter indicate 'off' when the receiver is muted, but the  
> way I have the windows sized the S meter info is hidden, and the frequency  
> data doesn't exactly jump off the screen.  So I added [via the  
> users_extra.c file] a white "MUTE" indicator that appears on the  
> users_extra data line above the waterfall when the receiver is muted.   
> This is a lot more prominent than the other indicators, and makes it easy  
> to tell immediately which receiver is muted.
> 
> It only required adding a few lines to users_extra.c
> 
> //display mute if necessary
> if (mix1_selfreq[0]<0)
> {
>    sprintf (s,"MUTE");
>    settextcolor(15); //white
>    lir_text (18,0,s);
> }
> else
> {
(Continue reading)

Permalink | Reply | 0 comments |

Gmane