Loading ...
Sorry, an error occurred while loading the content.

2138Re: [dxatlas] skimmer/k3 bandwidth

Expand Messages
  • Steve Ellington
    Sep 17, 2010
      Well it's an interesting answer however if 30 hours work would open up skimmer for 192khz bandwidth it would certainly not be a "marginal improvement" in my opinion. It would be a HUGE improvement and greatly increase the demand for the product.

      "This would take 30-50 hours of work and produce only a marginal
      improvement of the functionality"

      ----- Original Message -----
      From: ve7tk
      To: dxatlas_group@yahoogroups.com
      Sent: Friday, September 17, 2010 2:40 PM
      Subject: Re: [dxatlas] skimmer/k3 bandwidth

      I think the best answer is in Message # 1134 on this list from the author.



      --- In dxatlas_group@yahoogroups.com, "Steve Ellington" <n4lq@...> wrote:
      > Mike
      > It's true and such a shame but from what I've been told, there's nothing you can do about it. So far, no one has offered a technical reason for this limitation other than "it's the programmers choice".
      > Steve
      > ----- Original Message -----
      > From: Mike
      > To: dxatlas_group@yahoogroups.com
      > Sent: Thursday, September 16, 2010 12:06 PM
      > Subject: [dxatlas] skimmer/k3 bandwidth
      > Hi,
      > I've been using cw skimmer with my k3. As I understand it, no matter what the sound card's sampling rate, skimmer is only capable of analyzing a 24 KHz-wide band centered on the k3's currently tuned cw transmit frequency, i.e. 12 Khz below and 12 Khz above the current xmit frequency. Is this correct? Or is there some other way of setting things up that would allow cw skimmer to analyze the entire received bandwidth (e.g. 96 Khz at a 96 K sampling rate)?
      > Thanks and 73,
      > Mike - ke5akl
      > [Non-text portions of this message have been removed]

      [Non-text portions of this message have been removed]
    • Show all 5 messages in this topic