Re: [digitalradio] Caller ID in Multipsk

2008-12-20 Thread Patrick Lindecker
Hello Andy,

> assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
> WSPR , but I am wondering just how much less ?
If WSPR is able to detect of -25 dB, the Call ID is only able to detect -13 
dB signals (it begins to decode from -18 dB but not below).
However, as WSPR it is a free-error transmission.

As it is short (3.3 s), it's much more to introduce oneself (Call sign + 
Locator).

It could be used for beacons alone or to test a mode (Throbx, Olivia) inside 
a sequence... in this way:
 
CQ CQ CQ CQ CQ CQ DE F6CTE F6CTE +K

The program switches to TX, sends the Call ID then the RS ID  (to make 
switch the other Ham to the desired mode ) and a message. Afterwards, the 
program switches to RX.
The other Ham must leave RS ID and Call ID buttons pushed.

Note: the Call ID structure is fix now, but there are still some small bugs.

73
Patrick

- Original Message - 
From: "Andrew O'Brien" 
To: 
Sent: Saturday, December 20, 2008 3:49 PM
Subject: [digitalradio] Caller ID in Multipsk


> The caller ID function in the latest test version of Multipsk works
> very well.  I wonder if anyone has tested it for how well it does for
> weak signals ?  I am wondering if Patrick has invented something that
> could be used in a manner similar to WSPR in beacon mode (not QSO WSPR).
>
> The data captured via Multipsk is displayed as follows
>
> 14:39:23 EA2AFR-IN83MH  -13  990 Hz
>
> Not unliked WSPR.  It certainly is a lot quicker than a WSPR
> transmission , just 3 seconds as opposed to two minutes in WSPR.  I
> assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
> WSPR , but I am wondering just how much less ?
>
>
>
> It would be interesting to see if the caller Id function within
> Multipsk could be developed in to some auto-spotting database much
> like the WSPR.org database with automatic uploads of calls received to
> a central webpage
>
> Andy K3UK
>
>
>
> 
>
> Announce your digital presence via our Interactive Sked Page at
> http://www.obriensweb.com/sked
>
>
>
> Yahoo! Groups Links
>
>
>
>
> 



Re: [digitalradio] Caller ID in Multipsk

2008-12-20 Thread Siegfried Jackstien
dear patrick
is it possible to put the dial frequence in the log???
would be a way to auto upload the spotted callsigns to a cluster or something 
like that
greetz
dg9bfc
sigi

  - Original Message - 
  From: Patrick Lindecker 
  To: digitalradio@yahoogroups.com 
  Sent: Saturday, December 20, 2008 4:41 PM
  Subject: Re: [digitalradio] Caller ID in Multipsk


  Hello Andy,

  > assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
  > WSPR , but I am wondering just how much less ?
  If WSPR is able to detect of -25 dB, the Call ID is only able to detect -13 
  dB signals (it begins to decode from -18 dB but not below).
  However, as WSPR it is a free-error transmission.

  As it is short (3.3 s), it's much more to introduce oneself (Call sign + 
  Locator).

  It could be used for beacons alone or to test a mode (Throbx, Olivia) inside 
  a sequence... in this way:
  
  CQ CQ CQ CQ CQ CQ DE F6CTE F6CTE +K
  
  The program switches to TX, sends the Call ID then the RS ID (to make 
  switch the other Ham to the desired mode ) and a message. Afterwards, the 
  program switches to RX.
  The other Ham must leave RS ID and Call ID buttons pushed.

  Note: the Call ID structure is fix now, but there are still some small bugs.

  73
  Patrick

  - Original Message - 
  From: "Andrew O'Brien" 
  To: 
  Sent: Saturday, December 20, 2008 3:49 PM
  Subject: [digitalradio] Caller ID in Multipsk

  > The caller ID function in the latest test version of Multipsk works
  > very well. I wonder if anyone has tested it for how well it does for
  > weak signals ? I am wondering if Patrick has invented something that
  > could be used in a manner similar to WSPR in beacon mode (not QSO WSPR).
  >
  > The data captured via Multipsk is displayed as follows
  >
  > 14:39:23 EA2AFR-IN83MH -13 990 Hz
  >
  > Not unliked WSPR. It certainly is a lot quicker than a WSPR
  > transmission , just 3 seconds as opposed to two minutes in WSPR. I
  > assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
  > WSPR , but I am wondering just how much less ?
  >
  >
  >
  > It would be interesting to see if the caller Id function within
  > Multipsk could be developed in to some auto-spotting database much
  > like the WSPR.org database with automatic uploads of calls received to
  > a central webpage
  >
  > Andy K3UK
  >
  >
  >
  > 
  >
  > Announce your digital presence via our Interactive Sked Page at
  > http://www.obriensweb.com/sked
  >
  >
  >
  > Yahoo! Groups Links
  >
  >
  >
  >
  > 



   

Re: [digitalradio] Caller ID in Multipsk

2008-12-21 Thread Patrick Lindecker
Hello Sigi,

The dial frequency is not automatically available except if you use a CAT 
system. The "Freq MHz" QSO field is filled by the user.

What I can do is:
* fill the Call sign and Locator in the QSO fields with the Call ID information 
so to give the possibility to export the information through SpotCollector 
(DXLab),
* add this dial frequency information to the CALL_ID.TXT file (if the field is 
filled), for memorization

Better to speak of this on the Multipsk group.

73
Patrick


  - Original Message - 
  From: Siegfried Jackstien 
  To: digitalradio@yahoogroups.com 
  Sent: Saturday, December 20, 2008 7:41 PM
  Subject: Re: [digitalradio] Caller ID in Multipsk


  dear patrick
  is it possible to put the dial frequence in the log???
  would be a way to auto upload the spotted callsigns to a cluster or something 
like that
  greetz
  dg9bfc
  sigi

- Original Message - 
From: Patrick Lindecker 
To: digitalradio@yahoogroups.com 
Sent: Saturday, December 20, 2008 4:41 PM
    Subject: Re: [digitalradio] Caller ID in Multipsk


Hello Andy,

> assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
> WSPR , but I am wondering just how much less ?
If WSPR is able to detect of -25 dB, the Call ID is only able to detect -13 
dB signals (it begins to decode from -18 dB but not below).
However, as WSPR it is a free-error transmission.

As it is short (3.3 s), it's much more to introduce oneself (Call sign + 
Locator).

It could be used for beacons alone or to test a mode (Throbx, Olivia) 
inside 
a sequence... in this way:

CQ CQ CQ CQ CQ CQ DE F6CTE F6CTE +K

The program switches to TX, sends the Call ID then the RS ID (to make 
switch the other Ham to the desired mode ) and a message. Afterwards, the 
program switches to RX.
The other Ham must leave RS ID and Call ID buttons pushed.

Note: the Call ID structure is fix now, but there are still some small bugs.

73
Patrick

- Original Message - 
From: "Andrew O'Brien" 
To: 
Sent: Saturday, December 20, 2008 3:49 PM
Subject: [digitalradio] Caller ID in Multipsk

> The caller ID function in the latest test version of Multipsk works
> very well. I wonder if anyone has tested it for how well it does for
> weak signals ? I am wondering if Patrick has invented something that
> could be used in a manner similar to WSPR in beacon mode (not QSO WSPR).
>
> The data captured via Multipsk is displayed as follows
>
> 14:39:23 EA2AFR-IN83MH -13 990 Hz
>
> Not unliked WSPR. It certainly is a lot quicker than a WSPR
> transmission , just 3 seconds as opposed to two minutes in WSPR. I
> assume that CALL ID in MULTIPSK using Reed Solomon ID is robust than
> WSPR , but I am wondering just how much less ?
>
>
>
> It would be interesting to see if the caller Id function within
> Multipsk could be developed in to some auto-spotting database much
> like the WSPR.org database with automatic uploads of calls received to
> a central webpage
>
> Andy K3UK
>
>
>
> 
>
> Announce your digital presence via our Interactive Sked Page at
> http://www.obriensweb.com/sked
>
>
>
> Yahoo! Groups Links
>
>
>
>
>