Yes Irad... I like Greg Tillman's method of creating folders that can be accessed by both VarAC and Flmsg. This would allow using Flmsg to create a file using the standard template (ics-213, etc) and the resultant file could be sent using VarAC. This is the way Flmsg is used along with Flamp and Fldigi or just with Fldigi. The main idea is enabling use of Flmsg and the forms library that is already in existance and is maintained. 73... Rick KJ7ROX

Enter the callsign right where my crude arrow is pointing. You can then either 'ping' or 'connect'.

I also do this all the time. PSK is very useful in identifying stations that can hear YOUR station's beacon even if you could not hear theirs (or maybe they forgot to turn beacons on). Such 'blind' contacts I have made have often turned into coaching sessions for new VarAC users If you turn off PSK reporting in your settings you can prevent blind contacts to your station, but why would you want to? My $.02 73... KJ7ROX

That is a great idea, Bill! I just tested with a friend and it works, although with a bit of fishing around to find the transferred file. Maybe Flmsg could be integrated with VarAC and thereby make it unnecessary to add and maintain forms in VarAC?

I am interested. An EmComm group that I am a member of has been watching VarAC development for some time.

APRS would be another useful EmComm feature!

This could be a way to send ICS Forms.

I can appreciate that this is a big request, not only to add the function, but to maintain the set of forms, which change from time to time. Why not do it in the way that Fldigi/Flmsg works - maybe even use Flmsg which already has a process for updating form templates?

I will 'second' that feature request. In the parts of the EmComm world I am familiar with, forms in Winlink and NBEMS (via Flmsg) are important. 73...Rick KJ7ROX Payson, Arizona

Very interesting idea. However, isn't there a band plan/ frequency coordination problem with using a repeater designated for analog voice use for digital transmissions?

Try this - what I do: If there are no CQs logged, try connecting with someone who's beacon is recent and shows a decent SNR to your station (say, greater than -15) If you don't have any suitable beacons to use, try PSK RPT and see who is seeing YOUR beacon and try a Ping or Connect with a station with a reasonable SNR. When I do the above I ALWAYS have someone to connect with. 73...de KJ7ROX

I will be - KJ7ROX in Payson, Arizona. Tonto Amateur Radio Assoc. (TARA) - see n7tar.org

Here are my VARA FM PTT and VARA SETTINGS as used with VarAC-FM. COM4 is my 'Enhanced Port'.

Hmmmm.... Yes - same radio (991A), but I use CAT for PTT and manually change the freq. I was wondering why, on both Winlink via VaraFM and VarAC via VaraFM that I did not have the ability to control frequency. No biggie for me, I just avoid VOX if I can avoid it and it is not a problem to manually tune the freq. I have attached my markup of your cheat sheet as my $.02 worth. I wonder why it is a tradeoff between CAT and PTT only on VaraFM, not VaraHF?

Why use VOX for PTT? My setup works with CAT (only one USB cable also).

I think that this is an interesting idea, but I agree with Irad's comment about user frustration when a posted 'L' callsign is not actually live. I do not think you need to create an 'L' category though. Why not just send the away status with the beacon? It can be inaccurate if you are (as I am frequently) really nearby reading a book or otherwise occupied, but it is a currently managed state via the checkbox and timer. I think that would be useful to know when reviewing the beacons list for purposes of picking a potential qso partner. 73... Rick KJ7ROX

I 'second' that motion.

What I believe would be useful would be to have the ability to broadcast to a group of callsigns (less than 'ALL'). I am thinking of an EMComm situation or some similar team effort like supporting a 50k trail run, etc. In this situation, a broadcast could be asking for check-ins or condition reports, etc.