>From my ROS log 2010-30-06 on 14.112: RX16: 16:41 @ -54,7 Hz: CQDX CQDX CQDX de DL3VDL DL3VDSd4taaKPa?M AMa®oeadÅ oeAsa(3esA.C'M <CANCEL> -9 dB RX16: 16:42 @ -54,7 Hz: CQDX CQDX CQDX de DL3VDL DL3VDL DL3VDL pse k <STOP> +0 dB RX16: 16:43 @ -54,7 Hz: CQDX CQDX CQDX de DL3VDL DL3VDL DL3VDL pse k <STOP> +7 dB RX16: 16:44 @ -15,6 Hz: CQDX CQDX CQDX de DL3VDL DL3VDL DL3VDL pse k <STOP> +11 dB
I moved 2Kc down at 2010-01-07 ;-) And as far as I know beaconing on HF is a "NO NO NO" among radio amateurs that run a packet BBS, or a /winmor RMS because it increases the chance of QRM, that's the whole point. If José was a radio amateur he should have known that, as a engineer with knowledge of his "target market" he could have known that. Marc, PD4U --- In [email protected], "Siegfried Jackstien" <siegfried.jackst...@...> wrote: > > * exactly every minute > > > > so the other stations must have made their beacontext with a stopwatch > > > > if you send the beacon in ros to 1 minute the soft DOES NOT transmit exactly > every minute for more than just one reason: > > first of all the duration of the beacontext is added to the timer cause > timer restarts AFTER sending . that is why I said the stopwatch thing > > okay say duration of text is 15 sec so you set beacon to 45 sec . does now > the soft send every minute? > > NO NO NO > > The second thing is that jose made another timer with 150 sec in the soft > THAT CAN NOT BE MADE SHORTER BY THE USER!!!! > > And that timer is resetted if there is traffic . so the beacon does only > work if there is NO TRAFFIC > > Beacon does not send if others use that qrg (in mode ros) >
