I updated the server wiki page with a new column: Traffic. It shows the qsy frequency. It may also be an idea to put a small 'serverinfo' file into the pskdownload directory so the client can download it and read the info. Rein > -----Ursprüngliche Nachricht----- > Von: pskmail@xxxxxxxxxxxxx > Gesendet: 21.03.08 15:01:17 > An: <pskmail@xxxxxxxxxxxxx> > Betreff: [pskmail] Re: Server configuration for scanning > Hi Rein, many thanks. > > I will interface my radio with pc later. > > There is a way from a new client version to know if the server connected is > able to switch really the TRX to a new frequency? > > > > 73 > > > > Roberto IS0GRB > > > > > > ----- Original Message ----- > > From: Rein Couperus > > To: pskmail@xxxxxxxxxxxxx > > Sent: Friday, March 21, 2008 2:25 PM > > Subject: [pskmail] Server configuration for scanning > > > >Hi Rein, many thanks for the update. > >I think we need to remind to the servers sysop that are using the "Low > >Frequency Cutoff" at value of 500, to cut some of disturbs not interested, > >in the menu W-Fall of fldigi, to set this value to default "0", because > >leaving the value to 500 and switching the frequency will create problems > >because fldigi can not decode the traffic. > >As soon as possible will upgrade is0grb-3. > > Just to be sure we all talk about the same thing.... > > The qsy facility of server version 0.6 does not work on the audio channel, > it qsy's the TRX VFO. So all fldigi config data remain the same, including > the > "Low frequency cutoff" and the sweet spot. > > To configure a server for scanning the following must be done: > * The server TRX must have a remote control facility. Pskmail uses hamlib, > to be more precise it issues a rigctl command to qsy the TRX. > * Scanning must be enabled in pskmailrc.pl > * The ./qrg/freqs.txt file must be present and have relevant values for > frequency and mode. > * For the qsy facility to work a variable $traffic_qrg = xxxxxxx; must be > present in pskmailrc.pl. > > Here is the pskmailrc.pl example running at PI4TUE: > > ################################################# > # rig control (scheduler, scanner) > $scheduler = 0; > $rigtype = 326; > $rigrate = 9600; > $rigdevice = "/dev/ttyS0"; > ########################## > $scanner = "F"; > $qrgfile = "$ENV{HOME}/qrg/freqs.txt"; > $freq_offset = 0; # minutes after '0' > @freq_corrections = qw (-500 -500 -500 -500 -500); # trx frequency correction > @Beaconarray = qw (1 0 0 0 1); > $traffic_qrg = 10146250; > ################################################# > > The freqs.txt file has: > 10147250,10147250,10147250,10147250,10147250 > PSK125,PSK250,PSK250,PSK250,PSK250, > > Some comments: > PI4TUE uses a IC756, which has a sweet spot of 1500 Hz. > The @freq_corrections array contains the -500 Hz shift from the default 1000 > Hz. > PI4TUE uses PSK125 in minute 0, and PSK250 in minutes 1,2,3 and 4. > $rigtype=326 means IC756 > $freq_offset=0 is for time shifting all frequencies by a number of minutes > (leave default 0). > @Beaconarray shows beacons to be sent in minutes 0 and 4 after every full > hour. > $traffic_qrg is the VFO QSY frequency in Hz (in this case center freq - 1500 > Hz). > > Hope this helps clarify some things... > > 73, > > Rein PA0R > > > > > > -- > http://pa0r.blogspirit.com > > > -- > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.519 / Virus Database: 269.21.8/1337 - Release Date: 20/03/2008 > 20.10 > > -- http://pa0r.blogspirit.com