Date   

Re: Firenet feed down

Lynn Deffenbaugh
 

Maybe just one of the servers is down.  Try disabling and re-enabling the port which causes APRSIS32 to (possibly) select a different translation.

Turns out that firenet.us and firenet.aprs2.net are the same set of 3 servers:

P:\>host firenet.us
firenet.us = 44.155.254.6
firenet.us = 45.79.131.203
firenet.us = 129.15.108.120

P:\>host firenet.aprs2.net
firenet.aprs2.net = 129.15.108.120
firenet.aprs2.net = 45.79.131.203
firenet.aprs2.net = 44.155.254.6
Alias:firenet.aprs2.net

Or change to specify one of these IP address specifically and see if you can determine which is working and which may be failed.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/20/2020 12:25 PM, Glenn O'Connor wrote:
It appears that Firenet.aprs2.net isn't functioning today, at least so far. I've switched my feed to
noam.aprs2.net.

Anyone have feedback if this is a temporary situation?

73,
Glenn-KF0ED


Firenet feed down

Glenn O'Connor
 

It appears that Firenet.aprs2.net isn't functioning today, at least so far. I've switched my feed to
noam.aprs2.net.

Anyone have feedback if this is a temporary situation?

73,
Glenn-KF0ED


Re: iGATE Functioning?

James Ewen
 

Don,

Probably the most important part of this is to learn the various parts of an AX.25 packet.

There's basically the source, destination, path, and payload sections of a packet. Once you can find those parts, then you can start to decode all the information in the payload based on the APRS specifications.

KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

Source    :  KD4APP-5

Destination : APWW11

Path     :  TCPIP*,qAC,T2KA

Payload : <IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

So, it's easy to see that the packet came from your station, aimed at APWW11, and it travelled via TCPIP*,qAC,T2KA

Perhaps Lynn can offer more information about the payload. 

I'm not sure what the msg_cnt is counting... can't find a reference to it in the wiki.

 If you send yourself a ?IGATE you'll see the count of local, direct, and total unique stations received "recently" (30 minutes) on an RF port. I just did that, and here's what your station told me.

14:17:50> ?igate
14:17:51< IGate[1/2] MSG_CNT=20 LOC_CNT=3 RF_CNT=3
        < IGate[2/2] TT4-NEW[KISS] Bi-Directional DX=10*N4NE-2(45mi@196°)

If you send a ?APRSL you'll see the stations that APRSISCE/32 considers "recently" "local" for the purposes of gating messages from the -IS to RF if addressed to one of those.

14:18:07> ?aprsl
14:18:07< Locals:AB4CZ-1(1) KD4UYP-10(1) W4DKZ-9(1)

  ?APRSD shows a list of the direct (no hops used) stations.

14:18:21> ?aprsd
14:18:22< Nothing Heard Direct

 ?APRSH * shows the list of all stations along with their used hop counts in ().  

14:18:37> ?aprsh *
14:18:37< Heard:AB4CZ-1(1) KD4UYP-10(1) W4DKZ-9(1)

RF Ports now track the most distant, directly heard (no path components used), position beacon per clock hour and report it as DX in <IGATE updates as well as in ?IGATE and ?APRSS query responses. You'll also see the DX along with timestamp for the past 8 hours per port if you double-click the "APRS OK" pane.

In all cases, the format of the information is DX=n*station(Dmi@B° (e.g. "DX=1*WX4MLB-3(8mi@2°)") where n=# of direct packets, Dmi=distance in miles, B°=bearing from receiver (aprs.fi's raw packets doesn't show the ° properly).

I also haven't been able to figure out where one might be able to enable/disable this i-gate activity report yet either.


James
VE6SRV


On Wed, Aug 19, 2020 at 12:49 PM Don Woodward <dbwoodw@...> wrote:
Thanks for the info - I'll study the packet info in the link you sent.

73's

Don W.
KD4APP


From: APRSISCE@groups.io <APRSISCE@groups.io> on behalf of James Ewen via groups.io <ve6srv=gmail.com@groups.io>
Sent: Tuesday, August 18, 2020 6:41 PM
To: APRSISCE@groups.io <APRSISCE@groups.io>
Subject: Re: [APRSISCE] iGATE Functioning?
 
Oops, sent too soon.

Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.

  T2KA: 

Actual packet contents finally! This is determined by Lynn's software. I'm going way out on a limb here expanding the term...

 <IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

IGATE is reporting information.

  <IGATE, 

Message Count

MSG_CNT=10, 

Location Count

  LOC_CNT=0 

Heard Direct Count 

  DIR_CNT=0 

Heard via RF Count 

RF_CNT=0  

Furthest station heard

  DX=7*N4NE-2(45mi@196<0xb0>) 

DX = shortened term for distance commonly used by amateur radio operators.
7* (number of time heard?)
N4NE-2 (callsign of the station heard, including SSID.
45mi distance to station in miles.
196° bearing to station.

The <0xb0> is the degree symbol that is being shown as a non-printable ascii hex code.

So no, your station is not sending packets to N4NEQ-2 via RF (at least not as indicated by this packet.)


James
VE6SRV


On Tue, Aug 18, 2020 at 4:31 PM James Ewen <ve6srv@...> wrote:
Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.


James
VE6SRV


On Tue, Aug 18, 2020 at 3:57 PM Don Woodward <dbwoodw@...> wrote:
Does this mean my iGATE has sent packets via RF to N4NEQ-2 ?

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

TIA and 73's

Don W.
KD4APP


Re: iGATE Functioning?

Don Woodward
 

Thanks for the info - I'll study the packet info in the link you sent.

73's

Don W.
KD4APP


From: APRSISCE@groups.io <APRSISCE@groups.io> on behalf of James Ewen via groups.io <ve6srv@...>
Sent: Tuesday, August 18, 2020 6:41 PM
To: APRSISCE@groups.io <APRSISCE@groups.io>
Subject: Re: [APRSISCE] iGATE Functioning?
 
Oops, sent too soon.

Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.

  T2KA: 

Actual packet contents finally! This is determined by Lynn's software. I'm going way out on a limb here expanding the term...

 <IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

IGATE is reporting information.

  <IGATE, 

Message Count

MSG_CNT=10, 

Location Count

  LOC_CNT=0 

Heard Direct Count 

  DIR_CNT=0 

Heard via RF Count 

RF_CNT=0  

Furthest station heard

  DX=7*N4NE-2(45mi@196<0xb0>) 

DX = shortened term for distance commonly used by amateur radio operators.
7* (number of time heard?)
N4NE-2 (callsign of the station heard, including SSID.
45mi distance to station in miles.
196° bearing to station.

The <0xb0> is the degree symbol that is being shown as a non-printable ascii hex code.

So no, your station is not sending packets to N4NEQ-2 via RF (at least not as indicated by this packet.)


James
VE6SRV


On Tue, Aug 18, 2020 at 4:31 PM James Ewen <ve6srv@...> wrote:
Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.


James
VE6SRV


On Tue, Aug 18, 2020 at 3:57 PM Don Woodward <dbwoodw@...> wrote:
Does this mean my iGATE has sent packets via RF to N4NEQ-2 ?

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

TIA and 73's

Don W.
KD4APP


Re: HF iGate Verification

Brad Ko6kL
 

I run a 30m receive aprs from time to time, 
park on 40m after 30m go's dead...
7.109.5 L I think....   there is a little 300bps at times...

switching out pc's in the shack right now and it's not up.

regards
brad
ko6kL



Re: XML Configuration

Lynn Deffenbaugh
 

The XML is purposely not documented as it is subject to change without notice.

But the elements you are inquiring about are what drive the symbols under the covers of the View / Symbols / Flight/Hurricane/Marine/Mobile menu options.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/18/2020 7:28 PM, T W via groups.io wrote:
Does anyone know where I can find a list and or explanation of the options used in the xml config file? Most specifically the Flight, Hurricane, Marine, and Mobile entries in the view config?

Thanks in advance

kf6kyd


XML Configuration

T W
 

Does anyone know where I can find a list and or explanation of the options used in the xml config file? Most specifically the Flight, Hurricane, Marine, and Mobile entries in the view config?

Thanks in advance

kf6kyd


Re: iGATE Functioning?

James Ewen
 

Oops, sent too soon.

Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.

  T2KA: 

Actual packet contents finally! This is determined by Lynn's software. I'm going way out on a limb here expanding the term...

 <IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

IGATE is reporting information.

  <IGATE, 

Message Count

MSG_CNT=10, 

Location Count

  LOC_CNT=0 

Heard Direct Count 

  DIR_CNT=0 

Heard via RF Count 

RF_CNT=0  

Furthest station heard

  DX=7*N4NE-2(45mi@196<0xb0>) 

DX = shortened term for distance commonly used by amateur radio operators.
7* (number of time heard?)
N4NE-2 (callsign of the station heard, including SSID.
45mi distance to station in miles.
196° bearing to station.

The <0xb0> is the degree symbol that is being shown as a non-printable ascii hex code.

So no, your station is not sending packets to N4NEQ-2 via RF (at least not as indicated by this packet.)


James
VE6SRV


On Tue, Aug 18, 2020 at 4:31 PM James Ewen <ve6srv@...> wrote:
Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.


James
VE6SRV


On Tue, Aug 18, 2020 at 3:57 PM Don Woodward <dbwoodw@...> wrote:
Does this mean my iGATE has sent packets via RF to N4NEQ-2 ?

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

TIA and 73's

Don W.
KD4APP


Re: iGATE Functioning?

James Ewen
 

Basic understanding of the construction of APRS packets is useful...

The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)  

Timestamp the APRS-IS heard the packet

2020-08-18 17:17:00 EDT:   

Source callsign (station sending the packet) 


Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 

  APWW11, 

Handled by a network connection

  TCPIP*,  
 
q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection

  qAC,  

APRS-IS server that handled the packet.


James
VE6SRV


On Tue, Aug 18, 2020 at 3:57 PM Don Woodward <dbwoodw@...> wrote:
Does this mean my iGATE has sent packets via RF to N4NEQ-2 ?

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

TIA and 73's

Don W.
KD4APP


iGATE Functioning?

Don Woodward
 

Does this mean my iGATE has sent packets via RF to N4NEQ-2 ?

2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>)

TIA and 73's

Don W.
KD4APP


Re: HF iGate Verification

John Brent - VA7WPN
 

Thank you,

Our intent is NOT to "SPAM the air waves" with relentless beacons, arbetrary weather, and "Smart beaconing". We are targeting the areas of Vancouver Island, and the interior of BC where there is NO cellular service, let alone any kind of repeater / igate coverage. We have looked into a LOT of other options, such as satellite communications / APRS, and portable repeaters / crossbanding. The testing we did was only helpful when we were witin 50km of "Scociety" after that, the hills mountains and 150' trees killed all performance. 

Our support is for the hunters, hikers, campers, and other exploring hams. The swaths of remote unserviced areas in BC alone are amazing, and huge. We all want to experiance that, with some kind of safety net / communications capability. We belive this is one of the better options. Its not nefarious.

John Brent
 VA7WPN


Re: HF iGate Verification

James Ewen
 

One should probably define what gating from IS-RF consists of before condemning  the activity.

I-gates by definition should be a two way communications gateway. They should take the activity heard on RF and gate it to the APRS-IS network. They also are supposed to gate APRS message packets (note, APRS message packets, not any other packets) heard locally on the APRS-is stream to RF, and also a single courtesy position packet. This allows an APRS station sending APRS message packet to a station beyond local RF range, and to be able to get a response back, along with a single location packet from the destination station.

What some software authors have done is provided a capability to arbitrarily move traffic from the APRS-IS to the RF network based on the gate operator desires. This is where we can end up with problems because the APRS-IS traffic levels far exceed the capacity of the 1200 baud, VHF system, let alone the 300 baud HF system.

An i-gate set up to gate packets from RF to IS, and to support IS-RF messaging shouldn't flood the RF network and cause detrimental degradation of the RF network. The RF users are the ones in control of the requests for packets to be gated back to RF, as well as stations looking to send APRS messages to stations on HF only.

Yes, there are those who will disregard the system health as a whole... obviously the world needs to know the weather conditions in my backyard every 5 minutes, and to ensure they do, I will transmit at 50 watts through a high gain antenna using WIDE1-1,WIDE2-2 so that I can ensure that my packets make it onto the APRS-IS network...

If one wants to get after people abusing the APRS network, how about going after all the people using WIDE1-1 as a path element who are operating at 5 watts or higher? They are going to be much more of a detriment to the APRS network than an HF i-gate that will send an APRS message and courtesy position packet to the 300 baud RF network only upon request of a station operating on HF.

Just a caution that one needs to ensure they know what the issue at hand truly is before spending too much time arguing their side.

I would ask John Brent VA7WPN what they intend with their RF-IS gateway.

James
VE6SRV


On Tue, Aug 18, 2020 at 7:51 AM Justin Cherington <huntjlc@...> wrote:

“We know it’s bad form but it does something we want (Insert reason here), so we are gonna do it anyway.”

- 50% of APRS users

Lol. 


Re: HF iGate Verification

Justin Cherington
 

“We know it’s bad form but it does something we want (Insert reason here), so we are gonna do it anyway.”

- 50% of APRS users

Lol. 


Re: HF iGate Verification

John Brent - VA7WPN
 

Lynn

I understand that its bad form and we ARE looking for alternatives for this, such as JS8Call (But it has NOT way for an APRS message to be replied too), CCW Messenger is dead in the water, and not everyone has $1200 for a PACTOR modem to do Robust Packet from a mobile or backpack. I own a PTC-IIex, and its showing its age. Its started failing, and I have taken the precautions with new caps to fix the issues that I am having, but the techs over at SCS have indicated to me on a few occasions that it may very well be the DSP Chip that is failing, and that there ARE NO replacements, and I am not the only one who is having these issues with these ageing devices.

I have been looking high and low for a few years with the help of a number of members in the club for alternatives, we have had little to no luck. As APRS its self, does exactly what we need it for, its really the only way we can perform the tasks we need to perform without designing a whole new mode and system.

John Brent
 VA7WPN


Re: HF iGate Verification

Lynn Deffenbaugh
 

It is considered bad form to gate from the APRS-IS to HF.  Gating IS to 1200 baud VHF is bad enough, but gating to 300 baud HF can really get you into trouble.

There is some support group that discusses such topics, but the actual name escapes me at the moment.  You might want to task on the aprssig mailing list.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/17/2020 5:10 PM, John Brent - VA7WPN wrote:
Good afternoon,

Our local club has been working on getting our HF iGate setup. So far we have some success, and were very happy with that, but we want to continue to improve and expand the capability. We have been able to track a number of other HF APRS stations on 10.147.60Mhz @ 300 baud, across Canada and the US. So we KNOW there is activity on the band, and that were not th only ones using it.

We are gating to and from IS. We can see that on our APRS.FI page, so there is a level of success. But, we want to make sure that were setup appropriatly, and being responcible at the same time. We want to provide this support to everyone on 30m, We know there is activity, but we need to spread the word.

Are there any others who are running 30m APRS stations or iGates here? Can we build some mutual support?

Thank you,

John Brent
 VA7WPN


Re: HF iGate Verification

David Musselwhite
 

Check with VE6AB.  He should point you in the right direction.


On Mon, Aug 17, 2020 at 2:10 PM John Brent - VA7WPN <john.brent@...> wrote:
Good afternoon,

Our local club has been working on getting our HF iGate setup. So far we have some success, and were very happy with that, but we want to continue to improve and expand the capability. We have been able to track a number of other HF APRS stations on 10.147.60Mhz @ 300 baud, across Canada and the US. So we KNOW there is activity on the band, and that were not th only ones using it.

We are gating to and from IS. We can see that on our APRS.FI page, so there is a level of success. But, we want to make sure that were setup appropriatly, and being responcible at the same time. We want to provide this support to everyone on 30m, We know there is activity, but we need to spread the word.

Are there any others who are running 30m APRS stations or iGates here? Can we build some mutual support?

Thank you,

John Brent
 VA7WPN


Re: soundmodem and aprsi32

John Brent - VA7WPN
 

We have an HF APRS iGate setup on the following :

  Freq : 10.147.60 Mhz USB
   Mod : 300 baud
 Tones : 200 hz spacing centered on 1700kz

Were not using PSK, but it is possible and we may be implimenting it if testing at our location proves to be a success.

http://wa8lmf.net/APRS_PSK63/DualMode.htm

I hope this helps, I belive you have been using our setup, and I recognize your callsign as one we have gated.

John Brent
 VA7WPN


HF iGate Verification

John Brent - VA7WPN
 

Good afternoon,

Our local club has been working on getting our HF iGate setup. So far we have some success, and were very happy with that, but we want to continue to improve and expand the capability. We have been able to track a number of other HF APRS stations on 10.147.60Mhz @ 300 baud, across Canada and the US. So we KNOW there is activity on the band, and that were not th only ones using it.

We are gating to and from IS. We can see that on our APRS.FI page, so there is a level of success. But, we want to make sure that were setup appropriatly, and being responcible at the same time. We want to provide this support to everyone on 30m, We know there is activity, but we need to spread the word.

Are there any others who are running 30m APRS stations or iGates here? Can we build some mutual support?

Thank you,

John Brent
 VA7WPN


Re: Dark Mode

Don Woodward
 

Thanks - that worked - I have it on a large TV and I leave it on at night and it's very bright when sleeping so this is perfect now.

73's

Don W.
KD4APP


From: APRSISCE@groups.io <APRSISCE@groups.io> on behalf of Lynn Deffenbaugh via groups.io <kj4erj@...>
Sent: Sunday, August 16, 2020 3:07 PM
To: APRSISCE@groups.io <APRSISCE@groups.io>
Subject: Re: [APRSISCE] Dark Mode
 

Screen / Brightness / Dim and then turn down your opacity with the left arrow.

vs

But as you can see, it only affects the map itself.


Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/16/2020 10:19 AM, Don Woodward wrote:
Any way to set dark mode is APRSISCE on Windows 7?

TIA,

Don Woodward
KD4APP


Re: Dark Mode

Lynn Deffenbaugh
 

Screen / Brightness / Dim and then turn down your opacity with the left arrow.

vs

But as you can see, it only affects the map itself.


Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 8/16/2020 10:19 AM, Don Woodward wrote:
Any way to set dark mode is APRSISCE on Windows 7?

TIA,

Don Woodward
KD4APP

821 - 840 of 35507