• When did this WEBSDR started ?
    • This websdr went live on Wednesday may 13, 2020


  • Which bands do we support  ?
    • 80m, 60m, 40m, 30m 20m. All bands complete with CW segment.


  • Do we have a chatbox ?
    • No, this WebSDR has no chat box. Our hobby is radio.
      Internet is only the channel to receive the signals by from the remote location.


  • Latency ?
    • Different browsers have different overall latency in the audio.
      Firefox has the lowest latency contribution of the browsers we measured.
      The latency of Chrome (and CATSync) is 80msec higher and that of Microsoft Edge 65msec higher.
      Also external sound cards will have short but different latency contributions.
      Even with CADSync the overall latency should be <=500msec.


  • CATSync and the RIT (Receiver Incremental Tuning) on the transceiver.
    In CATSync we see (in some rigs) RIT which is double the value as set in your rig. The reason is that OmniRig adds the RIT offset to the main frequency, which was also done in your rig, ending up in two times the RIT added to the frequency in CATSync.

      A work around is modifying the corresponding OmniRig .ini file for the transceiver.
      (These files are in: Program Files(x86)/Alfreet/OmniRig/Rigs)
      For the FTDX5000 and FT-950 the line starting with Value1 in [STATUS1] is modified:

            Value1=13|5|vfText|0.00005|0|pmRitOffset         <========== here is the change

      The RIT offset is now multiplied by 0.00005 instead of a 1 ("0" didn't work).
      See also: http://dxatlas.com/OmniRig/IniStru.txt


  • Increasing noise level at sun set.
    This is not local man-made noise, but received sky wave noise.
    A good reference is the thesis of Ben Witvliet PE5B:


     On page 67 the noise level on 60m is plotted vs. time. It is measured with a low dipole and calibrated equipment.
     The radiation pattern of a low dipole is practically the same as that of the small receiving loop.


Create a Free Website With JouwWeb