Date   

Re: My hf rig

Brian - KN6NXD
 

Awesome! I'm a new Tech and I have been working 10m for a few weeks. If you are patient and work the band, there is sporadic openings. In the past two weeks I have logged Canada, Arizona, Utah, Oregon, So-Cal, Alabama, and Hawaii on 40 watts and a simple dipole that is oriented N-S (about 3 degrees (+/-)). Be patient as 10m is more miss than hit right now. Keep at it, it is a blast!
73,
Brian - KN6NXD


Re: Pryme PR-222 1.25m HT #forsale

Erik - W6EMR
 
Edited

Sold - Thanks Jim, N6MED.

73,
Erik, W6EMR 


FOR SALE: Kenwood TS-520 w/remote VFO-520 #forsale

Dennis - WU6X
 

From Erik: W6EMR
Kenwood TS-520 w/remote VFO-520
Vintage hybrid HF rig. All controls deoxed, both units. Factory AC and DC power cords. Unit has 12v inverter installed. NO WARC Bands. 80-10m. Included in sale is a Shure base station microphone, a straight CW key and custom embroidered dust covers. The remote VFO has the hard to find cord.
I am willing to have the output tested independently before sale. Unit should be good up to 100 watts. Hard copy manual included. $250
Pictures on request. My email is good on QRZ or the club roster.

Call or txt 530.888.6278

 

Sorry Erik ... I accidentally deleted your first post; now good to go! This is a nice looking rig at a good price!
Dennis - WU6X
Groups Admin


Re: How To: Using N3FJP Logging Software at the SFARC Field Day at Georgetown, CA

Brian - AI6US
 

Here is a original longer version on YouTube without our club information.

https://youtu.be/DJEIXuoKWqc
--
Brian- AI6US


Re: Looking to carpool to field day

Jeff - KM6RGO
 

Hi Joshua,

I am heading up Fri after work and staying until Sun after teardown.  I live in Auburn, but work in Roseville and will be leaving directly after work (approx 4:30 - 5 (ish).  If that works for you, let me know.  There is room in the Sequoia for stuff, and more stuff, we will figure it out.  So, if you find a different scenario that works better for you, all good.

Lookin' forward to Field Day!

Jeff - KM6RGO


On Sat, Jun 19, 2021 at 11:49 AM Joshua - KN6NUF <me@...> wrote:
Hi,

I’m looking to carpool up to field day from Roseville. If you have an open seat for a ride up for me and a my camping stuff I would really appreciate it. Happy to share gas money and some laughter. 
--
73,

Joshua, KN6NUF


Re: How To: Using N3FJP Logging Software at the SFARC Field Day at Georgetown, CA

Joshua - KN6NUF
 

Is there another place to watch this or a guide that’s not locked in Facebook? I would like to learn but I’m not a bookface. 

73,
Joshua - KN6NUF

On Jun 18, 2021, at 7:38 PM, Brian - AI6US <ai6us@...> wrote:


First time using the N3FJP Logging Software or want a refresher for the upcoming SFARC Field Day at the Georgetown, CA airport? Here is an edited video overview for using the N3FJP logging software with the Sierra Hills ARC Field Day site information.

Our exchange is: W6EK 4A SV - That means we are operating with callsign W6EK, with 4 hf stations, operating Class "A" from the ARRL Section SV - Sacramento Valley.

https://www.facebook.com/700669501/videos/10161207082994502/
--
Brian- AI6US

--
73,

Joshua, KN6NUF


Looking to carpool to field day

Joshua - KN6NUF
 

Hi,

I’m looking to carpool up to field day from Roseville. If you have an open seat for a ride up for me and a my camping stuff I would really appreciate it. Happy to share gas money and some laughter. 
--
73,

Joshua, KN6NUF


How To: Using N3FJP Logging Software at the SFARC Field Day at Georgetown, CA

Brian - AI6US
 

First time using the N3FJP Logging Software or want a refresher for the upcoming SFARC Field Day at the Georgetown, CA airport? Here is an edited video overview for using the N3FJP logging software with the Sierra Hills ARC Field Day site information.

Our exchange is: W6EK 4A SV - That means we are operating with callsign W6EK, with 4 hf stations, operating Class "A" from the ARRL Section SV - Sacramento Valley.

https://www.facebook.com/700669501/videos/10161207082994502/
--
Brian- AI6US


Re: FIELD DAY 2021 RSVP #fieldday #QST

Stuart - W1SLC
 

Looking forward to it!!

Stuart Clark, AF6SC

.
Monitored by the NSA. 
 III      🇺🇸

On Jun 18, 2021, at 11:22, Dennis - WU6X <wu6x@...> wrote:



Field Day 2021 is approaching fast! 

 

If you haven't done so already and you are planning on participating in a meal or overnight stay, please RSVP through the W6EK.org web site or below

 

Field Day 2021 RSVP

Georgetown, CA Airport Campground
June 25th, 26th & 27th

Click here to fill out the RSVP!

WE NEED A HEADCOUNT! OUR DEADLINE IS MIDNIGHT TONIGHT!  

That's Friday, June 18th 2021 at 11:59 PM.

 

Just a short hop from Auburn, CA, our Field Day event will be at the Georgetown Airport Campground at 6245 Aerodrome Way, Georgetown 95634. 38.920748, -120.865619 (E36 at 2625 foot elevation).

 

Fly-In, Drive-In (on Aerodrome Way) or Talk-In on 146.430Mhz simplex (no tone).

 

The event begins with set-up at 11am on Friday June 25th and wraps up at 11am on Sunday. 

Contact scoring begins on Saturday the 26th at 11:00am and ends Sunday the 27th at 10:59am followed by take down, pack up and site clean-up.

 

The Georgetown Airport Campground is a beautiful location. Plenty of room / shade for stations, antennas, and socializing. Yes, we are taking COVID precautions with lots of handy wipes, cleaner, et. al, etc.

 

For more info on Field Day at the Georgetown Airport, please contact info@... with “Field Day 2021” in the subject header.

 

Please plan to come join the rest of us.  You can participate in any part of the event from set-up to operations to tear down or even operate from home as a club member (see below).  If you just want to get out of COVID confinement, come join us to watch, visit, and eat.  Bring your own chair as provided seating is limited.  If you are going to eat please let us know which meals and preference via the RSVP link, so we can get an idea of how much food to purchase. Did I mention we need a headcount?

 

About scoring and the 'see below' above:  You can participate in Field Day from home, your car, your RV or portable location and still help the Club!! Although we would still like to see you in Georgetown. In a “normal year” when Field Day is over, we count up all our points and report them to the ARRL.  Then we anxiously wait for the national statistics to be reported so we know how we did compared to other stations.  Last year, because of Covid, the ARRL amended their rules to allow individuals to operate from home using their own call signs and add their points to the Club’s points as if they were at the Field Day site.  The ARRL rules will allow the same point scoring option for this year.  So even if you can’t come up to the site you can participate from home.  After Field Day we will tell you how to report so your points are credited to the Club. Our Club name designation is “Sierra Foothills ARC”.

  

If you have questions, please feel free to ask.  More importantly, please plan on joining us for all or some part of this event.  It is always a lot of fun!

 

73's and hope to see you there.

--
Scott M Vogelsang - wa6yne   


Re: COVID Vax QR code & card

Gary - KB7QWC
 

Mine came back in just a few minutes.

   …Gary, KB7QWC

 

From: sfarc@w6ek.groups.io <sfarc@w6ek.groups.io> On Behalf Of Carl - WF6J
Sent: Friday, June 18, 2021 1:43 PM
To: SFARC Group <sfarc@w6ek.groups.io>
Subject: [from W6EK Groups.io] COVID Vax QR code & card

 

State site is:

 

Fill it out with the info when you got vaccinated, they will “get back to you”

 

73,

Carl, WF6J


COVID Vax QR code & card

Carl - WF6J
 

State site is:

Fill it out with the info when you got vaccinated, they will “get back to you”

73,
Carl, WF6J


FIELD DAY 2021 RSVP #fieldday #QST

Dennis - WU6X
 

Field Day 2021 is approaching fast! 

 

If you haven't done so already and you are planning on participating in a meal or overnight stay, please RSVP through the W6EK.org web site or below

 

Field Day 2021 RSVP

Georgetown, CA Airport Campground
June 25th, 26th & 27th

Click here to fill out the RSVP!

WE NEED A HEADCOUNT! OUR DEADLINE IS MIDNIGHT TONIGHT!  

That's Friday, June 18th 2021 at 11:59 PM.

 

Just a short hop from Auburn, CA, our Field Day event will be at the Georgetown Airport Campground at 6245 Aerodrome Way, Georgetown 95634. 38.920748, -120.865619 (E36 at 2625 foot elevation).

 

Fly-In, Drive-In (on Aerodrome Way) or Talk-In on 146.430Mhz simplex (no tone).

 

The event begins with set-up at 11am on Friday June 25th and wraps up at 11am on Sunday. 

Contact scoring begins on Saturday the 26th at 11:00am and ends Sunday the 27th at 10:59am followed by take down, pack up and site clean-up.

 

The Georgetown Airport Campground is a beautiful location. Plenty of room / shade for stations, antennas, and socializing. Yes, we are taking COVID precautions with lots of handy wipes, cleaner, et. al, etc.

 

For more info on Field Day at the Georgetown Airport, please contact info@... with “Field Day 2021” in the subject header.

 

Please plan to come join the rest of us.  You can participate in any part of the event from set-up to operations to tear down or even operate from home as a club member (see below).  If you just want to get out of COVID confinement, come join us to watch, visit, and eat.  Bring your own chair as provided seating is limited.  If you are going to eat please let us know which meals and preference via the RSVP link, so we can get an idea of how much food to purchase. Did I mention we need a headcount?

 

About scoring and the 'see below' above:  You can participate in Field Day from home, your car, your RV or portable location and still help the Club!! Although we would still like to see you in Georgetown. In a “normal year” when Field Day is over, we count up all our points and report them to the ARRL.  Then we anxiously wait for the national statistics to be reported so we know how we did compared to other stations.  Last year, because of Covid, the ARRL amended their rules to allow individuals to operate from home using their own call signs and add their points to the Club’s points as if they were at the Field Day site.  The ARRL rules will allow the same point scoring option for this year.  So even if you can’t come up to the site you can participate from home.  After Field Day we will tell you how to report so your points are credited to the Club. Our Club name designation is “Sierra Foothills ARC”.

  

If you have questions, please feel free to ask.  More importantly, please plan on joining us for all or some part of this event.  It is always a lot of fun!

 

73's and hope to see you there.

--
Scott M Vogelsang - wa6yne   


My hf rig

KM6ZRN Mark
 

I finally got my hf rig set up today with a 10 meter di pole. Pretty excited!  It was hot outside, but I got it done.
--
KM6ZRN  Mark  in  Lincoln, Ca


Happening Now: SFARC Net - 06/17/2021 #cal-notice

sfarc@w6ek.groups.io Calendar <noreply@...>
 

SFARC Net

When:
06/17/2021
7:30pm to 8:30pm
(UTC-07:00) America/Los Angeles

Where:
W6EK Repeater - 145.430 -600, PL162.2

View Event

Description:
Check-in for Club updates from Officers and members, QSTs and more. Everyone is welcome!


Canceled: [from W6EK Groups.io] SFARC Event - Ice Cream Floats & Watermelon at Recreation Park - Sept. 21, 6pm #cal-invite

Orion - AI6JB
 


SFARC Event - Ice Cream Floats & Watermelon at Recreation Park - Sept. 21, 6pm #cal-invite

Orion - AI6JB
 


Re: Coffee Net / Cycling

Aaron K6ABJ
 

I am happy to hear Greydon's issue was an isolated incident. I am also happy to report the cycling issue I was having has been resolved. By reducing the hangtime setting down to 1000ms my node works well, and the muting on my ID-5100 was the result of desensing.

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Wed, Jun 16, 2021, at 8:38 PM, Greydon Hicks wrote:
I agree with Brian that the issue I experienced is not related.

I have used EchoLink from many locations across the west in the past week and a half. I only experienced the problem I described when connecting in Palisades Colorado this past Monday afternoon and Tuesday morning.  I suspect it was a local connection issue between my cell phone and nearest cell site as signal strength was low.

Last two days I have connected through the cell service in Moab Utah with full signal strength and experienced no drop outs.

Hope this helps.







On Jun 16, 2021, at 8:23 PM, Aaron K6ABJ <ajones@...> wrote:

Insightful analysis. One consideration I hadn't realized until you pointed it out, my radio listening to W6EK directly on 145.430 is an ID-5100 and does have dual monitor. Although unlikely, the radio must have been decensing from the repeater transmission.

Okay, so another question, why HamVoip? There seems to be a strong rivalry between the makers of HamVoip and AllStarLink that began after the initial creator died. I went with AllStarLink because it was the one you initially told me about. Now that I am diving into AllStar more and discovering and comparing the two, my initial impressions are that HamVoip seems to be better written and updated more recently, while AllStarLink claims to have the rights to the copyright and be an easier application to setup for a noob. This may have been asked before, but does anyone else in the club have opinions regarding the two implementations?

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Wed, Jun 16, 2021, at 6:54 PM, Brian - AI6US wrote:
Here is a guess... this has to do with transmit time and hang time. If your node hangtime was longer that our repeater hang time, it would not drop and reset when the repeater carrier dropped. It would only reset if an excessively long gap between transmissions and the carrier was still off when your node hang time expired and it dropped. Due to the timing overlap, your node likely did not drop and reset the transmit timer.

Our repeater and HamVoip node are both set to time out at 5 minutes. The Wires-X is set to time out at 3 minutes. I did not observe any transmissions exceeding a 3 minute time out yesterday during the net. This means that during yesterday's net, the carrier was dropped in less than 3 minutes and reset both of the the outbound AllStarLink and Wires-X nodes.

Maybe the 8800 radio decenses the radio from the repeater transmission? When the 8800 carrier drops, the decense ends and the radio can then receive the repeater. 

Or, more likely...

The radio can only listen to one band and it is not dual monitor.

As far as Greydon's comment, it sounds unrelated to your issue and may have to do with his transmit timer reset setting.

Best Regards! 
Brian Gohl - AI6US 
(916) 770-7751 cell


-------- Original message --------
From: Aaron K6ABJ <ajones@...>
Date: 6/16/21 6:18 PM (GMT-08:00)
To: SFARC Members <sfarc@w6ek.groups.io>
Subject: Re: [from W6EK Groups.io] Coffee Net / Cycling

Brian,

Thank you for looking into the W6EK repeater's log of time outs. Your findings suggest the problem is on my end, which in a way isn't a surprise as my node is new and I am still trying to figure out how to configure it so everything works properly.

My node is a radio node running AllStarLink and using an Ft-8800 tranceiver. The hangtime was the default 5000 ms, althangtime was the default 4000 ms, and the totime (transmit time out) is the default 180000 (3 minutes).

I am not sure what the althangtime setting controls exactly, the documentation states its a longer squelch tail, but that is all. Whether its value simply gets added to the hangtime value, or as the name implies is an alternate time value that gets triggered by some other action, is a mystery to me. Any ideas? In either event 5 seconds and 4 seconds seem like incredibly long hangtimes, and in indeed my node transmitter continues to transmit long after the received signal stops, suggesting to me a need to reduce one or both these times. This afternoon, switching both hangtime values to 1000 ms, I get a very short hangtime. I am suspecting it may be a bit too short though, so for the time being I have settled on both values being set to 1750ms.

Continuing with my diagnostic reasoning, I am guessing that the cycling phenomenon I experienced may be the result of a long hangtime, and that as a result of the long hangtime my AllStar node is timing out. This would account for my node periodically going silent, but how do I explain the cycling behavior, the audio going back and forth between my ID-5100 which was listening to the W6EK repeater on 145.430, and my FT-60R which was listening to the output frequency of my AllStarNode?

If the transmitter of my node (a FT-8800) was over-powering the receiver in my other radio (an ID-5100 which was directly listening to the W6EK repeater on 145.430) to mute through some sort of safety feature, this could account for my ID-5100 going silent whenever I was receiving audio through my node (which I was listening to using the receiver of my Yaesu FT-60r). I don't believe my Icom ID-5100 has a safety feature that would however cause such, so here is my other guess as to what may have been happening... Perhaps when my node (a FT-8800) was transmitting and I was hearing the audio on my receiving radio (a FT-60r), the A side of my ID-5100 (tuned to 145.430) would go silent because the B side of my ID-5100 was listening on the output frequency of my node and the volume of the B side was turned down? Like I said, I am guessing at straws to explain the strange phenomenon. Anyone who has read all this and can follow the logic has earned themselves Two Gold Stars, because even though I wrote it I am not sure I understand it! 

The explanation of what may have happened to me would not however account for what Greydon, KC6SLE experienced yesterday morning while listening to the net using Echolink. He reported to me that he experienced EchoLink going silent for five seconds about every 60 seconds.

With my hangtime and althangtime settings in my node now changed away from their default settings, I will listen to the net tomorrow morning and report my findings.  I am crossing my fingers and all my toes! Yes, I can do that I am after-all a very talented man!

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Tue, Jun 15, 2021, at 4:33 PM, Brian - AI6US wrote:
Aaron,

I looked at the logs for this morning and the internet feeds did not record a time outs. I also reviewed the last hour of the Broadcastify recording (9:30-10:30) and did not hear any drops. What is the AllStarLink node timeout setting on your side? Is your setup a radio node or direct?

There have been 3 timeouts logged on the repeater today. 
1. 10:46
2. 14:52
3. 15:09

Hope this helps.
--
Brian- AI6US


--
Brian- AI6US



Re: Coffee Net / Cycling

Lisa - KC6SLE
 

I agree with Brian that the issue I experienced is not related.

I have used EchoLink from many locations across the west in the past week and a half. I only experienced the problem I described when connecting in Palisades Colorado this past Monday afternoon and Tuesday morning.  I suspect it was a local connection issue between my cell phone and nearest cell site as signal strength was low.

Last two days I have connected through the cell service in Moab Utah with full signal strength and experienced no drop outs.

Hope this helps.






On Jun 16, 2021, at 8:23 PM, Aaron K6ABJ <ajones@...> wrote:


Insightful analysis. One consideration I hadn't realized until you pointed it out, my radio listening to W6EK directly on 145.430 is an ID-5100 and does have dual monitor. Although unlikely, the radio must have been decensing from the repeater transmission.

Okay, so another question, why HamVoip? There seems to be a strong rivalry between the makers of HamVoip and AllStarLink that began after the initial creator died. I went with AllStarLink because it was the one you initially told me about. Now that I am diving into AllStar more and discovering and comparing the two, my initial impressions are that HamVoip seems to be better written and updated more recently, while AllStarLink claims to have the rights to the copyright and be an easier application to setup for a noob. This may have been asked before, but does anyone else in the club have opinions regarding the two implementations?

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Wed, Jun 16, 2021, at 6:54 PM, Brian - AI6US wrote:
Here is a guess... this has to do with transmit time and hang time. If your node hangtime was longer that our repeater hang time, it would not drop and reset when the repeater carrier dropped. It would only reset if an excessively long gap between transmissions and the carrier was still off when your node hang time expired and it dropped. Due to the timing overlap, your node likely did not drop and reset the transmit timer.

Our repeater and HamVoip node are both set to time out at 5 minutes. The Wires-X is set to time out at 3 minutes. I did not observe any transmissions exceeding a 3 minute time out yesterday during the net. This means that during yesterday's net, the carrier was dropped in less than 3 minutes and reset both of the the outbound AllStarLink and Wires-X nodes.

Maybe the 8800 radio decenses the radio from the repeater transmission? When the 8800 carrier drops, the decense ends and the radio can then receive the repeater. 

Or, more likely...

The radio can only listen to one band and it is not dual monitor.

As far as Greydon's comment, it sounds unrelated to your issue and may have to do with his transmit timer reset setting.

Best Regards! 
Brian Gohl - AI6US 
(916) 770-7751 cell


-------- Original message --------
From: Aaron K6ABJ <ajones@...>
Date: 6/16/21 6:18 PM (GMT-08:00)
To: SFARC Members <sfarc@w6ek.groups.io>
Subject: Re: [from W6EK Groups.io] Coffee Net / Cycling

Brian,

Thank you for looking into the W6EK repeater's log of time outs. Your findings suggest the problem is on my end, which in a way isn't a surprise as my node is new and I am still trying to figure out how to configure it so everything works properly.

My node is a radio node running AllStarLink and using an Ft-8800 tranceiver. The hangtime was the default 5000 ms, althangtime was the default 4000 ms, and the totime (transmit time out) is the default 180000 (3 minutes).

I am not sure what the althangtime setting controls exactly, the documentation states its a longer squelch tail, but that is all. Whether its value simply gets added to the hangtime value, or as the name implies is an alternate time value that gets triggered by some other action, is a mystery to me. Any ideas? In either event 5 seconds and 4 seconds seem like incredibly long hangtimes, and in indeed my node transmitter continues to transmit long after the received signal stops, suggesting to me a need to reduce one or both these times. This afternoon, switching both hangtime values to 1000 ms, I get a very short hangtime. I am suspecting it may be a bit too short though, so for the time being I have settled on both values being set to 1750ms.

Continuing with my diagnostic reasoning, I am guessing that the cycling phenomenon I experienced may be the result of a long hangtime, and that as a result of the long hangtime my AllStar node is timing out. This would account for my node periodically going silent, but how do I explain the cycling behavior, the audio going back and forth between my ID-5100 which was listening to the W6EK repeater on 145.430, and my FT-60R which was listening to the output frequency of my AllStarNode?

If the transmitter of my node (a FT-8800) was over-powering the receiver in my other radio (an ID-5100 which was directly listening to the W6EK repeater on 145.430) to mute through some sort of safety feature, this could account for my ID-5100 going silent whenever I was receiving audio through my node (which I was listening to using the receiver of my Yaesu FT-60r). I don't believe my Icom ID-5100 has a safety feature that would however cause such, so here is my other guess as to what may have been happening... Perhaps when my node (a FT-8800) was transmitting and I was hearing the audio on my receiving radio (a FT-60r), the A side of my ID-5100 (tuned to 145.430) would go silent because the B side of my ID-5100 was listening on the output frequency of my node and the volume of the B side was turned down? Like I said, I am guessing at straws to explain the strange phenomenon. Anyone who has read all this and can follow the logic has earned themselves Two Gold Stars, because even though I wrote it I am not sure I understand it! 

The explanation of what may have happened to me would not however account for what Greydon, KC6SLE experienced yesterday morning while listening to the net using Echolink. He reported to me that he experienced EchoLink going silent for five seconds about every 60 seconds.

With my hangtime and althangtime settings in my node now changed away from their default settings, I will listen to the net tomorrow morning and report my findings.  I am crossing my fingers and all my toes! Yes, I can do that I am after-all a very talented man!

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Tue, Jun 15, 2021, at 4:33 PM, Brian - AI6US wrote:
Aaron,

I looked at the logs for this morning and the internet feeds did not record a time outs. I also reviewed the last hour of the Broadcastify recording (9:30-10:30) and did not hear any drops. What is the AllStarLink node timeout setting on your side? Is your setup a radio node or direct?

There have been 3 timeouts logged on the repeater today. 
1. 10:46
2. 14:52
3. 15:09

Hope this helps.
--
Brian- AI6US


--
Brian- AI6US


Re: Coffee Net / Cycling

Aaron K6ABJ
 

Insightful analysis. One consideration I hadn't realized until you pointed it out, my radio listening to W6EK directly on 145.430 is an ID-5100 and does have dual monitor. Although unlikely, the radio must have been decensing from the repeater transmission.

Okay, so another question, why HamVoip? There seems to be a strong rivalry between the makers of HamVoip and AllStarLink that began after the initial creator died. I went with AllStarLink because it was the one you initially told me about. Now that I am diving into AllStar more and discovering and comparing the two, my initial impressions are that HamVoip seems to be better written and updated more recently, while AllStarLink claims to have the rights to the copyright and be an easier application to setup for a noob. This may have been asked before, but does anyone else in the club have opinions regarding the two implementations?

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Wed, Jun 16, 2021, at 6:54 PM, Brian - AI6US wrote:
Here is a guess... this has to do with transmit time and hang time. If your node hangtime was longer that our repeater hang time, it would not drop and reset when the repeater carrier dropped. It would only reset if an excessively long gap between transmissions and the carrier was still off when your node hang time expired and it dropped. Due to the timing overlap, your node likely did not drop and reset the transmit timer.

Our repeater and HamVoip node are both set to time out at 5 minutes. The Wires-X is set to time out at 3 minutes. I did not observe any transmissions exceeding a 3 minute time out yesterday during the net. This means that during yesterday's net, the carrier was dropped in less than 3 minutes and reset both of the the outbound AllStarLink and Wires-X nodes.

Maybe the 8800 radio decenses the radio from the repeater transmission? When the 8800 carrier drops, the decense ends and the radio can then receive the repeater. 

Or, more likely...

The radio can only listen to one band and it is not dual monitor.

As far as Greydon's comment, it sounds unrelated to your issue and may have to do with his transmit timer reset setting.

Best Regards! 
Brian Gohl - AI6US 
(916) 770-7751 cell


-------- Original message --------
From: Aaron K6ABJ <ajones@...>
Date: 6/16/21 6:18 PM (GMT-08:00)
To: SFARC Members <sfarc@w6ek.groups.io>
Subject: Re: [from W6EK Groups.io] Coffee Net / Cycling

Brian,

Thank you for looking into the W6EK repeater's log of time outs. Your findings suggest the problem is on my end, which in a way isn't a surprise as my node is new and I am still trying to figure out how to configure it so everything works properly.

My node is a radio node running AllStarLink and using an Ft-8800 tranceiver. The hangtime was the default 5000 ms, althangtime was the default 4000 ms, and the totime (transmit time out) is the default 180000 (3 minutes).

I am not sure what the althangtime setting controls exactly, the documentation states its a longer squelch tail, but that is all. Whether its value simply gets added to the hangtime value, or as the name implies is an alternate time value that gets triggered by some other action, is a mystery to me. Any ideas? In either event 5 seconds and 4 seconds seem like incredibly long hangtimes, and in indeed my node transmitter continues to transmit long after the received signal stops, suggesting to me a need to reduce one or both these times. This afternoon, switching both hangtime values to 1000 ms, I get a very short hangtime. I am suspecting it may be a bit too short though, so for the time being I have settled on both values being set to 1750ms.

Continuing with my diagnostic reasoning, I am guessing that the cycling phenomenon I experienced may be the result of a long hangtime, and that as a result of the long hangtime my AllStar node is timing out. This would account for my node periodically going silent, but how do I explain the cycling behavior, the audio going back and forth between my ID-5100 which was listening to the W6EK repeater on 145.430, and my FT-60R which was listening to the output frequency of my AllStarNode?

If the transmitter of my node (a FT-8800) was over-powering the receiver in my other radio (an ID-5100 which was directly listening to the W6EK repeater on 145.430) to mute through some sort of safety feature, this could account for my ID-5100 going silent whenever I was receiving audio through my node (which I was listening to using the receiver of my Yaesu FT-60r). I don't believe my Icom ID-5100 has a safety feature that would however cause such, so here is my other guess as to what may have been happening... Perhaps when my node (a FT-8800) was transmitting and I was hearing the audio on my receiving radio (a FT-60r), the A side of my ID-5100 (tuned to 145.430) would go silent because the B side of my ID-5100 was listening on the output frequency of my node and the volume of the B side was turned down? Like I said, I am guessing at straws to explain the strange phenomenon. Anyone who has read all this and can follow the logic has earned themselves Two Gold Stars, because even though I wrote it I am not sure I understand it! 

The explanation of what may have happened to me would not however account for what Greydon, KC6SLE experienced yesterday morning while listening to the net using Echolink. He reported to me that he experienced EchoLink going silent for five seconds about every 60 seconds.

With my hangtime and althangtime settings in my node now changed away from their default settings, I will listen to the net tomorrow morning and report my findings.  I am crossing my fingers and all my toes! Yes, I can do that I am after-all a very talented man!

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Tue, Jun 15, 2021, at 4:33 PM, Brian - AI6US wrote:
Aaron,

I looked at the logs for this morning and the internet feeds did not record a time outs. I also reviewed the last hour of the Broadcastify recording (9:30-10:30) and did not hear any drops. What is the AllStarLink node timeout setting on your side? Is your setup a radio node or direct?

There have been 3 timeouts logged on the repeater today. 
1. 10:46
2. 14:52
3. 15:09

Hope this helps.
--
Brian- AI6US


--
Brian- AI6US


Re: Coffee Net / Cycling

Brian - AI6US
 

Here is a guess... this has to do with transmit time and hang time. If your node hangtime was longer that our repeater hang time, it would not drop and reset when the repeater carrier dropped. It would only reset if an excessively long gap between transmissions and the carrier was still off when your node hang time expired and it dropped. Due to the timing overlap, your node likely did not drop and reset the transmit timer.

Our repeater and HamVoip node are both set to time out at 5 minutes. The Wires-X is set to time out at 3 minutes. I did not observe any transmissions exceeding a 3 minute time out yesterday during the net. This means that during yesterday's net, the carrier was dropped in less than 3 minutes and reset both of the the outbound AllStarLink and Wires-X nodes.

Maybe the 8800 radio decenses the radio from the repeater transmission? When the 8800 carrier drops, the decense ends and the radio can then receive the repeater. 

Or, more likely...

The radio can only listen to one band and it is not dual monitor.

As far as Greydon's comment, it sounds unrelated to your issue and may have to do with his transmit timer reset setting.

Best Regards! 
Brian Gohl - AI6US 
(916) 770-7751 cell


-------- Original message --------
From: Aaron K6ABJ <ajones@...>
Date: 6/16/21 6:18 PM (GMT-08:00)
To: SFARC Members <sfarc@w6ek.groups.io>
Subject: Re: [from W6EK Groups.io] Coffee Net / Cycling

Brian,

Thank you for looking into the W6EK repeater's log of time outs. Your findings suggest the problem is on my end, which in a way isn't a surprise as my node is new and I am still trying to figure out how to configure it so everything works properly.

My node is a radio node running AllStarLink and using an Ft-8800 tranceiver. The hangtime was the default 5000 ms, althangtime was the default 4000 ms, and the totime (transmit time out) is the default 180000 (3 minutes).

I am not sure what the althangtime setting controls exactly, the documentation states its a longer squelch tail, but that is all. Whether its value simply gets added to the hangtime value, or as the name implies is an alternate time value that gets triggered by some other action, is a mystery to me. Any ideas? In either event 5 seconds and 4 seconds seem like incredibly long hangtimes, and in indeed my node transmitter continues to transmit long after the received signal stops, suggesting to me a need to reduce one or both these times. This afternoon, switching both hangtime values to 1000 ms, I get a very short hangtime. I am suspecting it may be a bit too short though, so for the time being I have settled on both values being set to 1750ms.

Continuing with my diagnostic reasoning, I am guessing that the cycling phenomenon I experienced may be the result of a long hangtime, and that as a result of the long hangtime my AllStar node is timing out. This would account for my node periodically going silent, but how do I explain the cycling behavior, the audio going back and forth between my ID-5100 which was listening to the W6EK repeater on 145.430, and my FT-60R which was listening to the output frequency of my AllStarNode?

If the transmitter of my node (a FT-8800) was over-powering the receiver in my other radio (an ID-5100 which was directly listening to the W6EK repeater on 145.430) to mute through some sort of safety feature, this could account for my ID-5100 going silent whenever I was receiving audio through my node (which I was listening to using the receiver of my Yaesu FT-60r). I don't believe my Icom ID-5100 has a safety feature that would however cause such, so here is my other guess as to what may have been happening... Perhaps when my node (a FT-8800) was transmitting and I was hearing the audio on my receiving radio (a FT-60r), the A side of my ID-5100 (tuned to 145.430) would go silent because the B side of my ID-5100 was listening on the output frequency of my node and the volume of the B side was turned down? Like I said, I am guessing at straws to explain the strange phenomenon. Anyone who has read all this and can follow the logic has earned themselves Two Gold Stars, because even though I wrote it I am not sure I understand it! 

The explanation of what may have happened to me would not however account for what Greydon, KC6SLE experienced yesterday morning while listening to the net using Echolink. He reported to me that he experienced EchoLink going silent for five seconds about every 60 seconds.

With my hangtime and althangtime settings in my node now changed away from their default settings, I will listen to the net tomorrow morning and report my findings.  I am crossing my fingers and all my toes! Yes, I can do that I am after-all a very talented man!

Aaron Jones, K6ABJ 
   
    ajones@... | Mobile: 916-715-7328


On Tue, Jun 15, 2021, at 4:33 PM, Brian - AI6US wrote:
Aaron,

I looked at the logs for this morning and the internet feeds did not record a time outs. I also reviewed the last hour of the Broadcastify recording (9:30-10:30) and did not hear any drops. What is the AllStarLink node timeout setting on your side? Is your setup a radio node or direct?

There have been 3 timeouts logged on the repeater today. 
1. 10:46
2. 14:52
3. 15:09

Hope this helps.
--
Brian- AI6US


--
Brian- AI6US

161 - 180 of 7158