To see this working, head to your live site.

After beacon NO LUCK

in Bugs - Fixed

VarAC V12.0.0, VARA-FM, Windows 10, after every few beacons I get this:

<SENDING ADVANCED BEACON ON 2m - 146.475.000> DE N4UZZ

NO LUCK. Maybe next time ...

How can I have no luck beaconing? What does this mean?

Otto 73 de N4UZZ

13 comments

13 Comments

irad d

Sep 06

This bug is fixed in the next version 12.2. stay tuned.

Meir 4Z5PE | QO100<->HF VarAC Cluster

Aug 26

Example

PSKreporter screen of VarAC claiming I heard my own beacon.

And surprisingly, it is being reported on the wrong band!

Note: There is no beacon entry in the log at that time!

In this example, I am beaconing on 20m only and I am NOT beaconing on 40m!

Note: My cluster is monitoring multiple bands, and it is possible my 40m instance responded to a spurious INCOMING CONNECTION REQUEST, since PTT is not disabled. Note: It is the middle of the day and there are NO incoming signals on 40m.

Log

26/08/2025 08:51:41 - (CN:20) Sending beacon

26/08/2025 08:51:41 - (CN:20) KISS BEACON sent

26/08/2025 08:53:21 - (CN:20) KISS BEACON received from HB9AVK

26/08/2025 08:53:21 - (CN:20) PSKReporter: Logged successfully (HB9AVK)

26/08/2025 08:53:21 - (CN:20) PSKReporter: Sending accumulated records

26/08/2025 08:53:21 - (CN:20) Logging Contact to DB: HB9AVK

26/08/2025 08:58:32 - (CN:20) PSKReporter: Logged successfully (HB9BFM)

26/08/2025 08:58:32 - (CN:20) PSKReporter: Sending accumulated records

26/08/2025 09:00:25 - (CN:1) PSKReporter self report: Logged successfully

26/08/2025 09:00:25 - (CN:1) PSKReporter: Sending accumulated records

26/08/2025 09:01:35 - (CN:20) KISS BEACON received from SV1UY

26/08/2025 09:01:35 - (CN:20) PSKReporter: Logged successfully (SV1UY)

26/08/2025 09:01:35 - (CN:20) PSKReporter: Sending accumulated records

26/08/2025 09:01:35 - (CN:20) Logging Contact to DB: SV1UY

Edited

Meir 4Z5PE | QO100<->HF VarAC Cluster

Aug 26

Replying to

Happened again on 15m at 10:12!

The last beacon was at 10:07:

Happened again - 20m beacon, reported on 17m!

Edited

Meir 4Z5PE | QO100<->HF VarAC Cluster

Aug 26

Replying to

OK I see what is happening:

VarAC cluster hears itself beacon. Maybe picked up on a different band!
VarAC reports it to PSKreporter on the wrong band!
PSKreporter's timestamp is apparently 5 minutes behind!
Note that there are no self-beacons listed in any instance, nor do they appear in the logs!

Solution: This should definitely be filtered out:

VarAC should NOT be reporting its own beacons if heard on the wrong band.
It should NOT respond to its own beacons!
Filter out any self-heard beacons from the same cluster!
I don't know if it is really hearing itself through the radio or if this is some phantom effect bug!

Edited

irad d

Sep 06

Replying to

VarAC only source of beacons is the VARA modem. no database / phantom data transfer. if there is a leak of RF / Audio between the modems, VarAC will hear itself. It has no way to know if it is indeed other node or someone pretending to be you or another station you run remotly. Therefore I will not filter it. on the contrary - it allowed you to notice you have an leak issue. 73s.

Meir 4Z5PE | QO100<->HF VarAC Cluster

Aug 26

Still happening in VarAC 12.0.4.

wd4kav

Jul 31

In my case, I'm operating using VARA-HF when I have observed the error

KJ7ROX - Rick

Jul 31

I have observed the same intermittent "No Luck..." message. When it happens it is always immediately following my beacon. It appears that my own beacon is triggering the message in my VarAC.

It does not happen every time, but often enough for me to see the pattern.

73! Rick KJ7ROX

Payson, Arizona

Meir 4Z5PE | QO100<->HF VarAC Cluster

Jul 19

I experience this as well. Happened just now - in v12.0.0.

It somehow hears my own beacon - but only sometimes.

I did check, and there is only one VarAC instance on the band.

Datastream

00:10:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

00:25:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

00:40:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

00:45:20 > INCOMING CONNECTION REQUEST. Still don't know who that is.

00:45:50 > NO LUCK. Maybe next time...

00:46:14 > INCOMING CONNECTION REQUEST. Still don't know who that is.

00:46:44 > NO LUCK. Maybe next time...

00:55:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

01:10:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

01:25:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

01:40:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

01:55:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

02:10:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

02:25:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

02:40:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

02:55:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

03:10:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

03:25:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

03:40:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

03:55:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

03:59:16 > INCOMING CONNECTION REQUEST. Still don't know who that is.

03:59:46 > NO LUCK. Maybe next time...

04:10:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

04:25:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

04:40:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

04:55:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

05:10:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

05:25:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

05:40:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

05:55:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

06:10:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

06:25:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

06:40:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

06:55:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

06:56:05 > NO LUCK. Maybe next time...

07:10:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

07:25:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

07:33:31 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

07:41:00 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

07:51:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

08:06:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

08:21:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

08:36:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

08:51:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

08:51:59 > NO LUCK. Maybe next time...

09:06:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

09:21:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

09:36:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

09:52:04 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

10:07:04 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

10:22:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

10:37:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

10:52:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

11:07:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

11:20:17 > INCOMING CONNECTION REQUEST. Still don't know who that is.

11:20:47 > NO LUCK. Maybe next time...

11:22:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

11:37:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

11:52:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

12:07:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

12:22:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

12:37:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

12:52:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

13:07:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

13:22:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

13:37:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

13:52:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

14:07:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

14:22:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

14:37:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

14:52:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

15:07:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

15:22:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

15:37:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

15:43:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

15:58:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

16:13:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

16:22:40 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

19:40:12 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

20:18:34 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

20:18:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

20:19:14 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

20:34:15 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

20:34:21 > NO LUCK. Maybe next time...

20:49:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE

Log

...

19/07/2025 20:34:15 - (CN:1) Sending beacon

19/07/2025 20:34:15 - (CN:1) KISS BEACON sent

Note 1. I am operating VARA SAT with SDR Console in full duplex on QO-100. 2. It seems to occur also with VARA HF.

Edited

irad d

Jul 12

Did you set your modem type to "VARA-FM" in the VarAC Settings ?

It is most likely someone is trying to connect.

if you want to disable this incoming message alerts by editing the VarAC ini file parameter:

IncomingConnectionRequestAlert=OFF

KJ7ROX - Rick

Jul 13

Replying to

In my case I was operating hf with VaraHF.

I like to get the alerts and do not want to turn the alert message off.

Meir 4Z5PE | QO100<->HF VarAC Cluster

Jul 31

Replying to

I observe this in VarAC v12.0.4, with VARA SAT on QO-100, and with VARA HF.

May I suggest to move this discussion, out of the VarAC FM forum, and into VarAC Bug reports?

I too, do not wish to disable incoming connection alerts, just to eliminate the spurious ones.

Edited

KJ7ROX - Rick

Jul 09

I have experienced the same behavior. It appears that the message is in response to my own beacon transmission, not from anything received. It does not happen every time I beacon.