Date   

Re: What do you hope to achieve in 2016?

Kevin Lemon
 

Build something. Maybe a 15m beam. ImD meter, something.

Fix my vertical. Then guy it with something the squirrels won't chew through.

Work a couple hundred more of you fine people. 

Save the universe.

Then on February first... hi hi


On Sun, Dec 27, 2015 at 8:04 PM, n7we1980@... [070]
<070@...> wrote:
 

Hey Fellow 070-ers!

It's almost 2016.  Maybe I spent too many years in the business world, but this time of year I feel a little guilty if I don't do some planning and set some goals for the coming year.  Not New Years Resolutions - but goals about what I want to do and what I want to achieve during the next year.

So how about a discussion thread on what your goals are?  What contests do you want to be sure to work?  What new endorsements do want to complete?  Upgrade your station?  New antennas?  Operate portable?  Do an APE?  I'm thinking about mine, and will post them here soon.

Why post them?  Because it's true that the probability of achieving your goals is much higher if you tell others what they are!!  So I'm going to post mine!  How about you?

Rick - N7WE - #1602



Re: What do you hope to achieve in 2016?

Martin Tuip
 

Getting some LOTW WAS awards since I am close to many of them. Secondly fix the finals on my rig since one is blown and third install a vertical antenna for the heck of it.  


Martin
Kg7hax 


-------- Original message --------
From: "n7we1980@... [070]" <070@...>
Date: 12/27/2015 18:04 (GMT-08:00)
To: 070@...
Subject: [070] What do you hope to achieve in 2016?

 

Hey Fellow 070-ers!

It's almost 2016.  Maybe I spent too many years in the business world, but this time of year I feel a little guilty if I don't do some planning and set some goals for the coming year.  Not New Years Resolutions - but goals about what I want to do and what I want to achieve during the next year.

So how about a discussion thread on what your goals are?  What contests do you want to be sure to work?  What new endorsements do want to complete?  Upgrade your station?  New antennas?  Operate portable?  Do an APE?  I'm thinking about mine, and will post them here soon.

Why post them?  Because it's true that the probability of achieving your goals is much higher if you tell others what they are!!  So I'm going to post mine!  How about you?

Rick - N7WE - #1602



What do you hope to achieve in 2016?

Rick - N7WE
 

Hey Fellow 070-ers!

It's almost 2016.  Maybe I spent too many years in the business world, but this time of year I feel a little guilty if I don't do some planning and set some goals for the coming year.  Not New Years Resolutions - but goals about what I want to do and what I want to achieve during the next year.

So how about a discussion thread on what your goals are?  What contests do you want to be sure to work?  What new endorsements do want to complete?  Upgrade your station?  New antennas?  Operate portable?  Do an APE?  I'm thinking about mine, and will post them here soon.

Why post them?  Because it's true that the probability of achieving your goals is much higher if you tell others what they are!!  So I'm going to post mine!  How about you?

Rick - N7WE - #1602



Re: Online QSLing for Mobile/Portable

Kevin Lemon
 

That was somewhat mind blowing, but put well enough even though I can grasp the idea.

As far as mobilizing myself, which I am now prepared to do, I can say that it's good that there are only two locations other than home that I would likely operate from.

The Kansas City International Airport.
Yes it's only 85 miles from home, but like a fireman, I'm there three days a week.

And..

Columbus Ohio (Rickenbacker AFB). Same scenario.

I don't psk31 and drive.

I see how this can get rather confusing. 

I have a /M secondary on QRZ.com but it'd have to see if I can edit the locator on it.

After all of that, I think I'd have to choose if I'm going to go to eQsl or LoTW or both.

It seems almost that the time I spend doing correct logs will exceed operating time. Not sure how that will work, enjoyment wise.

I do send cards. Maybe six or seven a week. 

Thanks for putting this into perspective, it's a good start for proper planning.

Kevin K0MCI 
2141

On Sun, Dec 27, 2015 at 7:19 PM, Stephen Melachrinos w3hf@... [070]
<070@...> wrote:
 

Well it took me a while to collect my thoughts, but Jerry's caution is appropriate--there are complexities of mobile or portable operations that affect use of online QSLing systems like eQSL and LoTW. This question comes up often enough that I’ve decided to write up something and save it for future editing and use. There are enough differences between the two that it can be tricky to set things up so they work on both systems. And FWIW, I’ve never used other online systems (QRZlog, HRDlog, etc) so I don’t know how this will play with their system.

There are two ground rules that I consider essential to use of online QSLing systems:

1. The callsign I use on the air MUST be EXACTLY the callsign that is “sent” with my online QSL.
2. The QTH that is “sent” with my online QSL MUST be the QTH for the station I was using.

The reasons for these should be obvious, but let me elaborate a bit. If I operate with a portable identifier (e.g., /0 or /KH2), I would send a paper QSL that would use the same callsign exactly how I identified on the air. And that card would show my actual station location, not my home QTH. I wouldn’t send a “W3HF in Pennsylvania” QSL card if I really had been on Guam or in Colorado. The same has to be true for online QSLing. Too many people think of their online account as the totality of their log, and fail to realize that each uploaded entry in an online account is actually the equivalent of sending a paper card. Furthermore, the stations I contact will likely send their online QSL to the callsign they received during the QSO, and it's messy if that's not the way I uploaded the QSOs. It’s just cleaner if I make it easy on my side.

eQSL’s system is account-based. Every QSL you submit (or that is sent to you) is assigned to an account (actually, a sub-account that can be linked to a master account) that is defined by your callsign, your location, and a contiguous range of effective dates for that combination. One of the consequences of this is that if you use the same callsign from separate locations, you’ll need separate accounts (with non-overlapping dates) so that you can set up the different QTHs. This can get very messy if you visit the same site multiple times, but need separate accounts for each activation because you’ve used the same callsign from another location in between.

All of your callsign/location/date-based accounts can linked together into a single master account. You won’t be able to display a list of QSLs from multiple sub-accounts together, but some eQSL awards let you aggregate the QSLs from certain multiple sub-accounts (e.g., all accounts within a single country for DX100 purposes). 

One complexity in dealing with eQSL is that you need to separately upload the QSOs from each sub-account, and make sure that they are in the RIGHT sub-account. If you are logged into one sub-account, and accidentally upload QSOs that should be in another account, you’ll have to either manually delete them or ask the eQSL “help desk” to assist you with a bulk delete.

In contrast, LoTW is transaction-based. Yes there is a login account that accumulates QSLs, and within that one account you can see all incoming confirmations from all your callsigns. But QSLs you submit are identified based not on that login but on the certificate and station location you use to sign the transaction. ARRL will assign you a PKI certificate for each callsign you use; you need a different certificate for each callsign variant—W3HF is different from W3HF/0 and W3HF/m.

When you sign a QSO or set of QSOs (in preparation for uploading), you also have to define a station location. That’s a bit of a misnomer—a “station location” consists of a particular callsign (so it’s tied to one of your certificates) and some additional (optional) information like IOTA, grid square, state, and county.  Note that you can’t change the DXCC entity that was assigned when the PKI certificate is issued, even though the FCC allows you to use your callsign anywhere in US territory. You can associate any callsign certificate you have with multiple locations (within the same DXCC entity) to create multiple “station locations.” You then select the location/certificate combination you want for any given upload. So LoTW accommodates use of the same callsign from multiple locations a bit better than eQSL does.

LoTW also lets you combine QSLs from multiple callsigns for awards purposes, subject to the rules for each award.

So how do you implement all of this so it makes sense together? Here’s how I do it.

First of all, I virtually always use a portable identifier. I know the FCC doesn’t require it and LoTW doesn't care either, but it keeps the accounts segregated on eQSL. I tend to visit the same places multiple times over stretches of time, and almost always these are in separate call districts, so each of these is a unique callsign. This lets me keep the same eQSL accounts running separately but continuously. This wouldn’t be as effective if I had to use the same call to operate from different locations.

Second, I scrupulously segregate my log based on my operating location and callsign used. I am very careful to make sure that there’s no possibility of mixing up W3HF QSOs with W3HF/0 QSOs or VQ9HF QSOs. 

Third, I always upload QSOs to the online sites manually—exporting an ADIF from the logger and uploading using the TQSL utility or the eQSL web site. I know that many logging systems can automate that process, but IMO it’s too risky to embed an eQSL or LoTW login within my logger and let it do the upload without me double-checking it. Maybe I’d feel different if I had completely separate log files, but that’s not the way I’m set up (for other reasons).

So the net result is that I have 16 separate eQSL sub-accounts. There are only a few where I’ve had to re-use callsigns (operating as W3HF/0 from both a hotel parking lot and a club station in Denver, and three separate uses of W3HF/3). I have 9 separate PKI certificates from ARRL, and 8 station locations defined for LoTW use. (There are a few combinations I haven’t fully implemented yet.)

I'm sure there are other ways to do what I've done so please don't interpret this writeup as saying this is the ONLY way to make it work. But this DOES work well for my situation, and I've gotten used to the complexities.

If anyone has any questions feel free to ask away, either on the reflector or direct.

73
Steve
W3HF (including /3, /4, /6, /8, /0, /KH2, /KH6) and VQ9HF
 
 
 
On 12/23/15, Jerry n9avy@... [070]<070@...> wrote:
 


LoTW requires a separate log for /m operation or any unique identifier attached to your call sign.  If you operated in Canada as VE/K0MCI that would also be separate log.  It may require some people to get the call you send and enter it correctly as sent. 

As for Eqsl,  they may have their own set of rules; so, you'd have to check their FAQ. 
Steve, W3HF, would no doubt be the authority on this since he operates his station from different locations .

73,  Jerry ,  N9AVY




From: "Kevin Lemon k0mci@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Wednesday, December 23, 2015 8:10 PM
Subject: Re: [070] K0MCI

 
Thanks, good chat. I do need to figure out the basics regarding awards and then perhaps see how I can work in the mobile if possible.
Seems complex on some counts, but for others, not so bad.

HRD will allow some selective exporting, but I'm not sure how the /M is going to fly.

I'll officially ask later.

Thanks again Jerry, appreciation is all yours for the patience with my improv.

73 Kevin K0MCI 2141


 
Caught Kevin on 40 m.  Nice signal  from 349.5 miles (according to QRZ) away. One of the better signals on band.

We talked about logging since he wasn't sure how to log for /m operations.  Told him it might be better to have separate log for his K0MCI/m than to combine .  Hope my suggestion was okay.

Jerry  N9AVY


Re: Online QSLing for Mobile/Portable

Jerry N9AVY
 

Good write up Steve ! 

Those who folow/understand this will  stop the confusion on the grids when operating as Stan,W9SMR and W9SMR/9 when he's in Indiana; so people won't get a grid for FL when he's in Indiana.

A few years ago I was N9AVY/135  for Hiram Percy Maxim's 135th Birthday  (the original W1AW !).  I have separate LoTW log for that.

Jerry  N9AVY




From: "Stephen Melachrinos w3hf@... [070]" <070@...>
To: 070@...
Sent: Sunday, December 27, 2015 7:19 PM
Subject: [070] Online QSLing for Mobile/Portable

 
Well it took me a while to collect my thoughts, but Jerry's caution is appropriate--there are complexities of mobile or portable operations that affect use of online QSLing systems like eQSL and LoTW. This question comes up often enough that I’ve decided to write up something and save it for future editing and use. There are enough differences between the two that it can be tricky to set things up so they work on both systems. And FWIW, I’ve never used other online systems (QRZlog, HRDlog, etc) so I don’t know how this will play with their system.

There are two ground rules that I consider essential to use of online QSLing systems:

1. The callsign I use on the air MUST be EXACTLY the callsign that is “sent” with my online QSL.
2. The QTH that is “sent” with my online QSL MUST be the QTH for the station I was using.

The reasons for these should be obvious, but let me elaborate a bit. If I operate with a portable identifier (e.g., /0 or /KH2), I would send a paper QSL that would use the same callsign exactly how I identified on the air. And that card would show my actual station location, not my home QTH. I wouldn’t send a “W3HF in Pennsylvania” QSL card if I really had been on Guam or in Colorado. The same has to be true for online QSLing. Too many people think of their online account as the totality of their log, and fail to realize that each uploaded entry in an online account is actually the equivalent of sending a paper card. Furthermore, the stations I contact will likely send their online QSL to the callsign they received during the QSO, and it's messy if that's not the way I uploaded the QSOs. It’s just cleaner if I make it easy on my side.

eQSL’s system is account-based. Every QSL you submit (or that is sent to you) is assigned to an account (actually, a sub-account that can be linked to a master account) that is defined by your callsign, your location, and a contiguous range of effective dates for that combination. One of the consequences of this is that if you use the same callsign from separate locations, you’ll need separate accounts (with non-overlapping dates) so that you can set up the different QTHs. This can get very messy if you visit the same site multiple times, but need separate accounts for each activation because you’ve used the same callsign from another location in between.

All of your callsign/location/date-based accounts can linked together into a single master account. You won’t be able to display a list of QSLs from multiple sub-accounts together, but some eQSL awards let you aggregate the QSLs from certain multiple sub-accounts (e.g., all accounts within a single country for DX100 purposes). 

One complexity in dealing with eQSL is that you need to separately upload the QSOs from each sub-account, and make sure that they are in the RIGHT sub-account. If you are logged into one sub-account, and accidentally upload QSOs that should be in another account, you’ll have to either manually delete them or ask the eQSL “help desk” to assist you with a bulk delete.

In contrast, LoTW is transaction-based. Yes there is a login account that accumulates QSLs, and within that one account you can see all incoming confirmations from all your callsigns. But QSLs you submit are identified based not on that login but on the certificate and station location you use to sign the transaction. ARRL will assign you a PKI certificate for each callsign you use; you need a different certificate for each callsign variant—W3HF is different from W3HF/0 and W3HF/m.

When you sign a QSO or set of QSOs (in preparation for uploading), you also have to define a station location. That’s a bit of a misnomer—a “station location” consists of a particular callsign (so it’s tied to one of your certificates) and some additional (optional) information like IOTA, grid square, state, and county.  Note that you can’t change the DXCC entity that was assigned when the PKI certificate is issued, even though the FCC allows you to use your callsign anywhere in US territory. You can associate any callsign certificate you have with multiple locations (within the same DXCC entity) to create multiple “station locations.” You then select the location/certificate combination you want for any given upload. So LoTW accommodates use of the same callsign from multiple locations a bit better than eQSL does.

LoTW also lets you combine QSLs from multiple callsigns for awards purposes, subject to the rules for each award.

So how do you implement all of this so it makes sense together? Here’s how I do it.

First of all, I virtually always use a portable identifier. I know the FCC doesn’t require it and LoTW doesn't care either, but it keeps the accounts segregated on eQSL. I tend to visit the same places multiple times over stretches of time, and almost always these are in separate call districts, so each of these is a unique callsign. This lets me keep the same eQSL accounts running separately but continuously. This wouldn’t be as effective if I had to use the same call to operate from different locations.

Second, I scrupulously segregate my log based on my operating location and callsign used. I am very careful to make sure that there’s no possibility of mixing up W3HF QSOs with W3HF/0 QSOs or VQ9HF QSOs. 

Third, I always upload QSOs to the online sites manually—exporting an ADIF from the logger and uploading using the TQSL utility or the eQSL web site. I know that many logging systems can automate that process, but IMO it’s too risky to embed an eQSL or LoTW login within my logger and let it do the upload without me double-checking it. Maybe I’d feel different if I had completely separate log files, but that’s not the way I’m set up (for other reasons).

So the net result is that I have 16 separate eQSL sub-accounts. There are only a few where I’ve had to re-use callsigns (operating as W3HF/0 from both a hotel parking lot and a club station in Denver, and three separate uses of W3HF/3). I have 9 separate PKI certificates from ARRL, and 8 station locations defined for LoTW use. (There are a few combinations I haven’t fully implemented yet.)

I'm sure there are other ways to do what I've done so please don't interpret this writeup as saying this is the ONLY way to make it work. But this DOES work well for my situation, and I've gotten used to the complexities.

If anyone has any questions feel free to ask away, either on the reflector or direct.

73
Steve
W3HF (including /3, /4, /6, /8, /0, /KH2, /KH6) and VQ9HF
 
 
 
On 12/23/15, Jerry n9avy@... [070]<070@...> wrote:
 


LoTW requires a separate log for /m operation or any unique identifier attached to your call sign.  If you operated in Canada as VE/K0MCI that would also be separate log.  It may require some people to get the call you send and enter it correctly as sent. 

As for Eqsl,  they may have their own set of rules; so, you'd have to check their FAQ. 
Steve, W3HF, would no doubt be the authority on this since he operates his station from different locations .

73,  Jerry ,  N9AVY




From: "Kevin Lemon k0mci@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Wednesday, December 23, 2015 8:10 PM
Subject: Re: [070] K0MCI

 
Thanks, good chat. I do need to figure out the basics regarding awards and then perhaps see how I can work in the mobile if possible.
Seems complex on some counts, but for others, not so bad.

HRD will allow some selective exporting, but I'm not sure how the /M is going to fly.

I'll officially ask later.

Thanks again Jerry, appreciation is all yours for the patience with my improv.

73 Kevin K0MCI 2141


 
Caught Kevin on 40 m.  Nice signal  from 349.5 miles (according to QRZ) away. One of the better signals on band.

We talked about logging since he wasn't sure how to log for /m operations.  Told him it might be better to have separate log for his K0MCI/m than to combine .  Hope my suggestion was okay.

Jerry  N9AVY



Re: Online QSLing for Mobile/Portable

Rick - N7WE
 

Thanks Steve!  Great explanation.

I've heard (but not seen) there are some changes coming to LoTW to accommodate NPOTA activators.  Not sure what they have in mind, but it is supposed to make multiple locations for one call sign easier. Two weeks ago they told me it would be available by Jan 1.

Rick - N7WE - #1602


Online QSLing for Mobile/Portable

Steve W3HF
 

Well it took me a while to collect my thoughts, but Jerry's caution is appropriate--there are complexities of mobile or portable operations that affect use of online QSLing systems like eQSL and LoTW. This question comes up often enough that I’ve decided to write up something and save it for future editing and use. There are enough differences between the two that it can be tricky to set things up so they work on both systems. And FWIW, I’ve never used other online systems (QRZlog, HRDlog, etc) so I don’t know how this will play with their system.

There are two ground rules that I consider essential to use of online QSLing systems:

1. The callsign I use on the air MUST be EXACTLY the callsign that is “sent” with my online QSL.
2. The QTH that is “sent” with my online QSL MUST be the QTH for the station I was using.

The reasons for these should be obvious, but let me elaborate a bit. If I operate with a portable identifier (e.g., /0 or /KH2), I would send a paper QSL that would use the same callsign exactly how I identified on the air. And that card would show my actual station location, not my home QTH. I wouldn’t send a “W3HF in Pennsylvania” QSL card if I really had been on Guam or in Colorado. The same has to be true for online QSLing. Too many people think of their online account as the totality of their log, and fail to realize that each uploaded entry in an online account is actually the equivalent of sending a paper card. Furthermore, the stations I contact will likely send their online QSL to the callsign they received during the QSO, and it's messy if that's not the way I uploaded the QSOs. It’s just cleaner if I make it easy on my side.

eQSL’s system is account-based. Every QSL you submit (or that is sent to you) is assigned to an account (actually, a sub-account that can be linked to a master account) that is defined by your callsign, your location, and a contiguous range of effective dates for that combination. One of the consequences of this is that if you use the same callsign from separate locations, you’ll need separate accounts (with non-overlapping dates) so that you can set up the different QTHs. This can get very messy if you visit the same site multiple times, but need separate accounts for each activation because you’ve used the same callsign from another location in between.

All of your callsign/location/date-based accounts can linked together into a single master account. You won’t be able to display a list of QSLs from multiple sub-accounts together, but some eQSL awards let you aggregate the QSLs from certain multiple sub-accounts (e.g., all accounts within a single country for DX100 purposes). 

One complexity in dealing with eQSL is that you need to separately upload the QSOs from each sub-account, and make sure that they are in the RIGHT sub-account. If you are logged into one sub-account, and accidentally upload QSOs that should be in another account, you’ll have to either manually delete them or ask the eQSL “help desk” to assist you with a bulk delete.

In contrast, LoTW is transaction-based. Yes there is a login account that accumulates QSLs, and within that one account you can see all incoming confirmations from all your callsigns. But QSLs you submit are identified based not on that login but on the certificate and station location you use to sign the transaction. ARRL will assign you a PKI certificate for each callsign you use; you need a different certificate for each callsign variant—W3HF is different from W3HF/0 and W3HF/m.

When you sign a QSO or set of QSOs (in preparation for uploading), you also have to define a station location. That’s a bit of a misnomer—a “station location” consists of a particular callsign (so it’s tied to one of your certificates) and some additional (optional) information like IOTA, grid square, state, and county.  Note that you can’t change the DXCC entity that was assigned when the PKI certificate is issued, even though the FCC allows you to use your callsign anywhere in US territory. You can associate any callsign certificate you have with multiple locations (within the same DXCC entity) to create multiple “station locations.” You then select the location/certificate combination you want for any given upload. So LoTW accommodates use of the same callsign from multiple locations a bit better than eQSL does.

LoTW also lets you combine QSLs from multiple callsigns for awards purposes, subject to the rules for each award.

So how do you implement all of this so it makes sense together? Here’s how I do it.

First of all, I virtually always use a portable identifier. I know the FCC doesn’t require it and LoTW doesn't care either, but it keeps the accounts segregated on eQSL. I tend to visit the same places multiple times over stretches of time, and almost always these are in separate call districts, so each of these is a unique callsign. This lets me keep the same eQSL accounts running separately but continuously. This wouldn’t be as effective if I had to use the same call to operate from different locations.

Second, I scrupulously segregate my log based on my operating location and callsign used. I am very careful to make sure that there’s no possibility of mixing up W3HF QSOs with W3HF/0 QSOs or VQ9HF QSOs. 

Third, I always upload QSOs to the online sites manually—exporting an ADIF from the logger and uploading using the TQSL utility or the eQSL web site. I know that many logging systems can automate that process, but IMO it’s too risky to embed an eQSL or LoTW login within my logger and let it do the upload without me double-checking it. Maybe I’d feel different if I had completely separate log files, but that’s not the way I’m set up (for other reasons).

So the net result is that I have 16 separate eQSL sub-accounts. There are only a few where I’ve had to re-use callsigns (operating as W3HF/0 from both a hotel parking lot and a club station in Denver, and three separate uses of W3HF/3). I have 9 separate PKI certificates from ARRL, and 8 station locations defined for LoTW use. (There are a few combinations I haven’t fully implemented yet.)

I'm sure there are other ways to do what I've done so please don't interpret this writeup as saying this is the ONLY way to make it work. But this DOES work well for my situation, and I've gotten used to the complexities.

If anyone has any questions feel free to ask away, either on the reflector or direct.

73
Steve
W3HF (including /3, /4, /6, /8, /0, /KH2, /KH6) and VQ9HF
 
 
 

On 12/23/15, Jerry n9avy@... [070]<070@...> wrote:
 


LoTW requires a separate log for /m operation or any unique identifier attached to your call sign.  If you operated in Canada as VE/K0MCI that would also be separate log.  It may require some people to get the call you send and enter it correctly as sent. 

As for Eqsl,  they may have their own set of rules; so, you'd have to check their FAQ. 
Steve, W3HF, would no doubt be the authority on this since he operates his station from different locations .

73,  Jerry ,  N9AVY




From: "Kevin Lemon k0mci@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Wednesday, December 23, 2015 8:10 PM
Subject: Re: [070] K0MCI

 
Thanks, good chat. I do need to figure out the basics regarding awards and then perhaps see how I can work in the mobile if possible.
Seems complex on some counts, but for others, not so bad.

HRD will allow some selective exporting, but I'm not sure how the /M is going to fly.

I'll officially ask later.

Thanks again Jerry, appreciation is all yours for the patience with my improv.

73 Kevin K0MCI 2141


 
Caught Kevin on 40 m.  Nice signal  from 349.5 miles (according to QRZ) away. One of the better signals on band.

We talked about logging since he wasn't sure how to log for /m operations.  Told him it might be better to have separate log for his K0MCI/m than to combine .  Hope my suggestion was okay.

Jerry  N9AVY


Re: Getting active again

Dan Morris - KZ3T
 

Good idea Ted.  I think I’ll find a spot for something like that in my macros.

for those asking or wondering about macros here is what I do and how I have mine set up:
In my program there are 10 banks of macros with 10 macros in each bank.  For 15/20/40/80M i have the following 10 macros:
1. CQ
2. Ans CQ
3. Start QSO This is where I can start a macro with xxx de mycall (and then say what I want if ragchewing)  I do this while the other person is talking, this way I can answer any questions as he asks.  when he’s done I hit F4 to Xmt continue on to finish and then I click on Shift-F4 to finish and when this macro finishes, it turns over to him.
4. Full Info: RST, my name, my qt., my grid, my epc#, my 070#  BTU
5. Equip - Send this if they send me one - Stn info, my age and 1st licensed info BTU
6. Info No #’s — Same as #4 just without the digital numbers
7. DX Quick QSO - RST, my name, TU 734 de kz3t sk
8. QRZ -  Self explanatory
9. Short Signoff - Tnx for mode/speed , Qsl via equals/lotw, 73 God Bless sk
10. Sign Off - Tnx mode/speed, enjoyed the contact. All the best … have a good day, etc and then sk

I have a set of macros for 10 meters alone since in my INFO macro I also give my 10-10# and for 30 meters where I give my 30MDG # — Oh, one bank is Translations - that is where when I sign off I sometimes will use that bank if talking to a French or Spanish or Russian etc.  I got that idea from someone here on the list. . .
My other macros I use for contests for 10-10, 070, etc.

Sorry it got a little lengthy but figured I would share.   Now, I’m always tuned in to something anyone has that might be a little better or any changes.   Seems like the first 2 or 3 years I was constantly changing my macros as I watched others on the waterfall and then tweaking mine as I go.  Everyone has something similar but yet quite different in how they communicate.  

Maybe I’m naive or something since running digital. I feel like I’m still used to being on SSB for so long that when on digital it is the basic info and then tnx for QSO.  I feel like I’m cutting that person short and they might think I’m a butthead for not wanting to talk like we do on SSB.  It’s so easy to get carried away on SSB when talking and I feel like I need to say more on digital.

Just sayin'

Dan Morris   KZ3T   070-1065



On Dec 27, 2015, at 7:06 PM, Ted pegduck56@... [070] <070@...> wrote:


Hi Mike,
also, a suggestion to have a macro something like this when you get asked or maybe working a non-member:



"I am participating in a contest or event for the PODXS 070 Club (see http://podxs070.com)
PODXS 070 is a friendly on line club that promotes the use of psk31. Check out the website !"

73, Ted
K7TRK
#1028




On Sunday, December 27, 2015 2:46 PM, "Bob Brown cricklewood@... [070]" <070@...> wrote:


 
Thanks Mike - Perfect!

On Sun, Dec 27, 2015 at 4:07 PM, 'Mike Miller' lists@... [070] <070@...>wrote:
 
On 26 Dec 2015 at 17:23, cricklewood@... [070] wrote:

> Can someone tell
> me how to set up and "auto cq" using FLDIGI? .... I googled
> and couldn't
> find anything.

Hi Bob,

I looked a little more into the macro tag and the  
bottom of page 132 of the FLDigi manual gives a better 
description.

" The and macro tags should have the NN 
replaced with the time interval in seconds.
CQ CQ de k
• will enable the PTT
• cause 5 seconds of idle signal
• send the CQ CQ de W1HKJ W1HKJ k
• disable PTT
• and count down 20seconds before repeating the macro
• after sending the text the count down timer button (upper right hand corner of main dialog) will display the
current timer value in seconds. Press this button to disable the timer.
Generated on Thu Nov 19 2015 05:48:40 for FLDIGI Users Manual by Doxygen

4.1Macros 133
• the timer be disabled if the Escape key is pressed, the T/R is pressed, and macro key is pressed, or if a
callsign is copied from the Rx text area to the callsign logbook entry.
• the time will be disabled if any mouse activity occurs in the waterfall control."

73
Mike kc9doa #1040







Re: Getting active again

Ted <pegduck56@...>
 

Hi Mike,
also, a suggestion to have a macro something like this when you get asked or maybe working a non-member:



"I am participating in a contest or event for the PODXS 070 Club (see http://podxs070.com)
PODXS 070 is a friendly on line club that promotes the use of psk31. Check out the website !"

73, Ted
K7TRK
#1028




On Sunday, December 27, 2015 2:46 PM, "Bob Brown cricklewood@... [070]" <070@...> wrote:


 
Thanks Mike - Perfect!

On Sun, Dec 27, 2015 at 4:07 PM, 'Mike Miller' lists@... [070] <070@...> wrote:
 
On 26 Dec 2015 at 17:23, cricklewood@... [070] wrote:

> Can someone tell
> me how to set up and "auto cq" using FLDIGI? .... I googled
> and couldn't
> find anything.

Hi Bob,

I looked a little more into the macro tag and the
bottom of page 132 of the FLDigi manual gives a better
description.

" The and macro tags should have the NN
replaced with the time interval in seconds.
CQ CQ de k
• will enable the PTT
• cause 5 seconds of idle signal
• send the CQ CQ de W1HKJ W1HKJ k
• disable PTT
• and count down 20seconds before repeating the macro
• after sending the text the count down timer button (upper right hand corner of main dialog) will display the
current timer value in seconds. Press this button to disable the timer.
Generated on Thu Nov 19 2015 05:48:40 for FLDIGI Users Manual by Doxygen

4.1Macros 133
• the timer be disabled if the Escape key is pressed, the T/R is pressed, and macro key is pressed, or if a
callsign is copied from the Rx text area to the callsign logbook entry.
• the time will be disabled if any mouse activity occurs in the waterfall control."

73
Mike kc9doa #1040





Re: Getting active again

Bob Brown <cricklewood@...>
 

Thanks Mike - Perfect!

On Sun, Dec 27, 2015 at 4:07 PM, 'Mike Miller' lists@... [070] <070@...> wrote:
 

On 26 Dec 2015 at 17:23, cricklewood@... [070] wrote:

> Can someone tell
> me how to set up and "auto cq" using FLDIGI? .... I googled
> and couldn't
> find anything.

Hi Bob,

I looked a little more into the macro tag and the
bottom of page 132 of the FLDigi manual gives a better
description.

" The and macro tags should have the NN
replaced with the time interval in seconds.
CQ CQ de k
• will enable the PTT
• cause 5 seconds of idle signal
• send the CQ CQ de W1HKJ W1HKJ k
• disable PTT
• and count down 20seconds before repeating the macro
• after sending the text the count down timer button (upper right hand corner of main dialog) will display the
current timer value in seconds. Press this button to disable the timer.
Generated on Thu Nov 19 2015 05:48:40 for FLDIGI Users Manual by Doxygen

4.1Macros 133
• the timer be disabled if the Escape key is pressed, the T/R is pressed, and macro key is pressed, or if a
callsign is copied from the Rx text area to the callsign logbook entry.
• the time will be disabled if any mouse activity occurs in the waterfall control."

73
Mike kc9doa #1040



Re: Getting active again

Don Bolstad K9DEB
 

Good info. Thanks. Need to set up in my macros too. 

Don K9DEB #2007 

Sent from my iPhone6

On Dec 27, 2015, at 15:07, 'Mike Miller' lists@... [070] <070@...> wrote:

 

On 26 Dec 2015 at 17:23, cricklewood@... [070] wrote:

> Can someone tell
> me how to set up and "auto cq" using FLDIGI? .... I googled
> and couldn't
> find anything.

Hi Bob,

I looked a little more into the macro tag and the
bottom of page 132 of the FLDigi manual gives a better
description.

" The and macro tags should have the NN
replaced with the time interval in seconds.
CQ CQ de k
• will enable the PTT
• cause 5 seconds of idle signal
• send the CQ CQ de W1HKJ W1HKJ k
• disable PTT
• and count down 20seconds before repeating the macro
• after sending the text the count down timer button (upper right hand corner of main dialog) will display the
current timer value in seconds. Press this button to disable the timer.
Generated on Thu Nov 19 2015 05:48:40 for FLDIGI Users Manual by Doxygen

4.1Macros 133
• the timer be disabled if the Escape key is pressed, the T/R is pressed, and macro key is pressed, or if a
callsign is copied from the Rx text area to the callsign logbook entry.
• the time will be disabled if any mouse activity occurs in the waterfall control."

73
Mike kc9doa #1040


Re: 24/7

Dan Morris - KZ3T
 

Matt — I see that PJ2MI IOTA I get an error at the bottom of the progress checker page.  I went and looked at his QRZ page and he lists his IOTA as SA-099

I have another error on there but I figured that out with David’s help and I will add the ‘dash’ in there for the VK station

Dan Morris   KZ3T   070-1065



On Dec 27, 2015, at 12:23 PM, Matthew King - KK4CPS mrk.twg@... [070] <070@...> wrote:


Congrats, Dan - job well done!


73


Matt King

070 #1708 LONP #261

PODXS 070 Club Executive Director


This email has been sent from a virus-free computer protected by Avast. 
www.avast.com

On Sun, Dec 27, 2015 at 11:40 AM, Jerry n9avy@... [070] <070@...> wrote:
 

Tree must be an oak full of acorns because anyone who tackles the 24/7 is a candidate for the "acorn ranch" !   :-)


Jerry  N9AVY




From: "n7we1980@... [070]" <070@...>
To: 070@... 
Sent: Sunday, December 27, 2015 10:33 AM
Subject: [070] Re: 24/7

 
Congrats Dan!  You are now among the certified crazy!  Welcome to this branch of the tree!

Rick - N7WE - #1602







Re: Getting active again

Mike Miller <lists@...>
 

On 26 Dec 2015 at 17:23, cricklewood@gmail.com [070] wrote:

Can someone tell
me how to set up and "auto cq" using FLDIGI? .... I googled
and couldn't
find anything.
Hi Bob,

I looked a little more into the <TIMER:NN> macro tag and the
bottom of page 132 of the FLDigi manual gives a better
description.

" The <TIMER:NN> and <IDLE:NN> macro tags should have the NN
replaced with the time interval in seconds.
<TX><IDLE:5>CQ CQ de <MYCALL> <MYCALL> k <RX><TIMER:20>
• will enable the PTT
• cause 5 seconds of idle signal
• send the CQ CQ de W1HKJ W1HKJ k
• disable PTT
• and count down 20seconds before repeating the macro
• after sending the text the count down timer button (upper right hand corner of main dialog) will display the
current timer value in seconds. Press this button to disable the timer.
Generated on Thu Nov 19 2015 05:48:40 for FLDIGI Users Manual by Doxygen

4.1Macros 133
• the timer be disabled if the Escape key is pressed, the T/R is pressed, and macro key is pressed, or if a
callsign is copied from the Rx text area to the callsign logbook entry.
• the time will be disabled if any mouse activity occurs in the waterfall control."

73
Mike kc9doa #1040


Re: 24/7

Dan Morris - KZ3T
 

Hurry, Hurry the branch is getting weak!! hihi

Dan Morris




On Dec 27, 2015, at 11:38 AM, 'Hamette' hamette@... [070] <070@...> wrote:


Well Done! Save a place for me on the branch!

 

Paula K7PAX #1739

 

From: 070@... [mailto:070@...] 
Sent: Sunday, December 27, 2015 08:23
To: 070 List Service 070 List Service
Subject: [070] 24/7

 

  

Woo Hoo - Finally got my 24/7 finished, over, done with, fine avec, hecho con, etc.

Dan Morris KZ3T 070-1065
dbmorris315@...




Re: 24/7

Dan Morris - KZ3T
 

Hey Jerry — Actually I have been down with this crud/cough going around and did not want to pass it on so did not go to church.  figured I’d take advantage of that since our temp here is 77 degree F!!!  We are having some really crazy warm weather this time of year.

And thanks to all who helped.

Dan Morris   KZ3T   070-1065



On Dec 27, 2015, at 11:37 AM, Jerry n9avy@... [070] <070@...> wrote:


Congrats Dan !   Did you play hookie from church ?

Jerry  n9avy




From: "Dan Morris dbmorris315@... [070]" <070@...>
To: 070 List Service 070 List Service <070@...> 
Sent: Sunday, December 27, 2015 10:22 AM
Subject: [070] 24/7

 
Woo Hoo - Finally got my 24/7 finished, over, done with, fine avec, hecho con, etc.

Dan Morris KZ3T 070-1065
dbmorris315@...






Re: Getting active again

John Etling
 

I personally do not use a “brag” macro unless the other party throws theirs in. I really am not all that interested as a lot of “brag” files take more time to send than the rest of the QSO combined. BUT, to specifically answer the question: Radio, Antenna and power output. That’s it.

… I’m just sayin’

 

73 de K3JAE

John Etling

k3jae@...

070 #1820   LONP #321

PODXS 070 – Nobody Special – Just a Member

 

 

 

 

From: cricklewood@... [070] [mailto:070@...]
Sent: Saturday, December 26, 2015 19:24
To: 070@...
Subject: [070] Getting active again

 

 

Hello all...... it's been quite awhile since I was active on PSK.   In the past I would call it "dabbling" even though I am a PODXS member.  I plan to change all that and get active.

 

I wanna play in the 24x7 and currently at 42, so I have a ways to go.

 

Sooo... using FLDIGI and setting up macros again.   In the past I would have what I consider a "Brag" that was way too wordy.... just curious what active members have in their's?

 

Was just on 30m for awhile calling CQ and no replies.   Can someone tell me how to set up and "auto cq" using FLDIGI?  .... I googled and couldn't find anything.

 

Also, if anyone has suggestions on what freq on 30m they usually call on.  I think getting activity on the WARC bands is a good idea.

 

73, and hope to CU on the waterfall!

 

Bob KW3F

PODXS Member # 2061


Re: 24/7

Matthew King - KK4CPS <mrk.twg@...>
 

Congrats, Dan - job well done!


73


Matt King

070 #1708 LONP #261

PODXS 070 Club Executive Director


This email has been sent from a virus-free computer protected by Avast.
www.avast.com

On Sun, Dec 27, 2015 at 11:40 AM, Jerry n9avy@... [070] <070@...> wrote:
 

Tree must be an oak full of acorns because anyone who tackles the 24/7 is a candidate for the "acorn ranch" !   :-)


Jerry  N9AVY




From: "n7we1980@... [070]" <070@...>
To: 070@...
Sent: Sunday, December 27, 2015 10:33 AM
Subject: [070] Re: 24/7

 
Congrats Dan!  You are now among the certified crazy!  Welcome to this branch of the tree!

Rick - N7WE - #1602




Re: 24/7

Jerry N9AVY
 

Tree must be an oak full of acorns because anyone who tackles the 24/7 is a candidate for the "acorn ranch" !   :-)


Jerry  N9AVY




From: "n7we1980@... [070]" <070@...>
To: 070@...
Sent: Sunday, December 27, 2015 10:33 AM
Subject: [070] Re: 24/7

 
Congrats Dan!  You are now among the certified crazy!  Welcome to this branch of the tree!

Rick - N7WE - #1602



Re: 24/7

Paula K7PAX #1739
 

Well Done! Save a place for me on the branch!

 

Paula K7PAX #1739

 

From: 070@... [mailto:070@...]
Sent: Sunday, December 27, 2015 08:23
To: 070 List Service 070 List Service
Subject: [070] 24/7

 

 

Woo Hoo - Finally got my 24/7 finished, over, done with, fine avec, hecho con, etc.

Dan Morris KZ3T 070-1065
dbmorris315@...


Re: 24/7

Jerry N9AVY
 

Congrats Dan !   Did you play hookie from church ?

Jerry  n9avy




From: "Dan Morris dbmorris315@... [070]" <070@...>
To: 070 List Service 070 List Service <070@...>
Sent: Sunday, December 27, 2015 10:22 AM
Subject: [070] 24/7

 
Woo Hoo - Finally got my 24/7 finished, over, done with, fine avec, hecho con, etc.

Dan Morris KZ3T 070-1065
dbmorris315@...