Power Setting

[David N7NTN]

Is there a recommended power setting for the V71A for the Nexus DRx digital modes- 5/10/50 watts?

[Chris Doutre]

For simplex, 50 watts.

For repeater, you may be able to dial it back, depending on the path to your chosen repeater. Try a lower setting and see what happens.

73.

Chris KC9AD

--
You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/ba11692b-09c7-4697-bf98-98effb7a2152n%40googlegroups.com.

[Gayland Gump]

David,    To the best of my knowledge it would be the same as for any radio.  As little as necessary to get the job done to your satisfaction.  I typically use the High setting when I am doing simplex.  Clearly if you are doing digital on a repeater all you should need is whatever it takes for you to reliably get into the repeater.  Anybody have any different recommendations please share your input.

Gayland

KG7GCF

On Thu, Jan 20, 2022 at 3:40 PM David N7NTN <dh....@gmail.com> wrote:

Is there a recommended power setting for the V71A for the Nexus DRx digital modes- 5/10/50 watts?

--

[Gayland Gump]

You just beat me to the reply.

Gayland

KG7GCF

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000501d80e59%24c158cc50%24440a64f0%24%40doutre.org.

[David N7NTN]

Thank you gentlemen, I will stay at 50W.

[Steve Stroh]

David:

If memory serves, the power levels on the TM-V71A are 5 watts, 25 watts, and 50 watts. 

To be heard in the majority of Whatcom County (on simplex) I recommend transmitting at 50 watts. 

This assumes, of course, that your antenna is up on a pole or tower where the primary radiation pattern won’t “spray RF” directly into people.

If your antenna is indoors, including an attic, I’d recommend using 25 watts. 

Working through the 146.740 repeater, 25 watts is plenty… 5 watts would probably work most of the time.

Steve N8GNJ

On Thu, Jan 20, 2022 at 15:40 David N7NTN <dh....@gmail.com> wrote:

Is there a recommended power setting for the V71A for the Nexus DRx digital modes- 5/10/50 watts?

--

You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/ba11692b-09c7-4697-bf98-98effb7a2152n%40googlegroups.com.

--

Steve Stroh N8GNJ

Editor

Zero Retries Newsletter - https://zeroretries.substack.com

Twitter - @zeroretries / https://twitter.com/zeroretries

[David N7NTN]

Steve, the available power settings on the V71A are 5/10/50W which leaves a big step between 10 & 50 unless there is a way to vary the gap. I've been running at 50W, but only doing digital applications so far. The reason I asked is because I'm setting up the direwolf aprs function in the Nexus DRx and there's a place to enter the watts. I'm not sure it matters, but it prompted the question about wattage in general.

David N7NTN

[Steve Stroh]

David:

The online manual:

https://manual.kenwood.com/files/B62-1926-40.pdf, page 97 states that the “Medium” power level of a…

TM-71A “K Type” is approx. 10W.

TM-V71A “M4 Type” is 25W. 

Searching for mentions of K Type and M4 Type, it seems to me that US versions are K Type (438 -450 MHz).

Thus I stand corrected on “Medium” TX power - it is 10W.

Between 10W and 50W, here in the near-sea-level lowlands, trying to work others via simplex with no terrain or repeater advantage, I choose to operate at 50W.

Steve N8GNJ

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/b79e54bc-9a33-400f-bd80-7807e5b38918n%40googlegroups.com.

[David N7NTN]

Steve, yes it is a K. So here's another question: I just set up the direwolf aprs and am tuned to 144.990, and I can hear the digital signal. My monitor is registering the signal as received audio. Am I supposed to receive more information or have I entered something incorrectly in the configuration?
David N7NTN

[Steve Magnuson]

David,

I’m not sure what you mean by “my monitor is registering the signal as received audio”.

In general, most hams use 144.390MHz to pass APRS traffic.

Stations operating as packet or Winlink P2P stations or gateways on other frequencies, 144.990MHz for example, typically announce themselves periodically (once every 30 minutes is common). If you are monitoring that frequency using the APRS GUI, that is likely what you are seeing.

Steve
AG7GN

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/5fc49320-0330-4027-9649-7fa44c6e77ffn%40googlegroups.com.

[David N7NTN]

Steve , I got the APRS up and running incorrectly as you point out on 144.990. The activity(?) window had a repeating message that said received audio and a little more...shortly after that a message started coming in from a Canadian ham (I didn't write down his callsign but I believe he is well known here) in red saying the audio levels were too high and the format of the frequency was incorrect. I believe that was directed at me. After that I did some more research that explained how to bring up alsamixer in a terminal and set my audio levels (~50) and unmute. I also realized the 144.390MH is the correct frequency. At that point it was late and I shut down for the night. I'm hoping this will set me on the right path, but I haven't started yet today. I also saw that YAAC may be an alternate program to use, but one step at a time. One of my problems is that I'm not sure what I should be seeing if I do have things set up correctly. Your comments and suggestions would be greatly appreciated.

David

N7NTN

[Steve Magnuson]

There’s a lot to unpack in your last post, David.

> in red saying the audio levels were too high

That’s not necessarily an issue on your end. It’s just as likely that his TX audio level is too high.

> and the format of the frequency was incorrect. I believe that was directed at me.

That is definitely an issue on his end. Direwolf is simply pointing out to you that the message you received did not have the frequency in the correct format. It was not directed at you. Those are automated messages they are sending. If your GUI APRS Mode in the Configure APRS tab is set to Monitor Only (the default), you aren’t even transmitting.

> YAAC may be an alternate program to use

YAAC is useful for composing and sending custom APRS messages in “real time” typically to a particular station (communicating with the ISS, for example). You can do many other APRS things with YAAC. The same for Xastir. Both of these programs need to have Direwolf running (via the Direwolf APRS GUI for example). They communicate with Direwolf via a TCP/IP connection using the AGWPE port.

> One of my problems is that I'm not sure what I should be seeing if I do have things set up correctly.

You should see traffic like this:

2022/01/21 12:49:35 CHURCH audio level = 65(12/14) [NONE] ___||____
2022/01/21 12:49:35 [0.3] CHURCH>APDW16:!4851.69NS12237.06W#PHG5260W7JIM
2022/01/21 12:49:35 Position, OVERLAY DIGI (green star) w/overlay S, DireWolf, WB2OSZ, 25 W height=40 6dBi omni
2022/01/21 12:49:35 N 48 51.6900, W 122 37.0600
2022/01/21 12:49:35 W7JIM
2022/01/21 12:52:13
2022/01/21 12:52:13 Digipeater CHURCH audio level = 56(15/15) [NONE] ___||____
2022/01/21 12:52:13 [0.3] VA7LLB>APWW11,CHURCH*,WIDE2-1:@205210h4909.07N/12202.30WlPHG2650Kenwood TS-2000
2022/01/21 12:52:13 Position with time, Laptop, APRSISCE win32 version, 4 W height=640 5dBi omni
2022/01/21 12:52:13 N 49 09.0700, W 122 02.3000
2022/01/21 12:52:13 Kenwood TS-2000
2022/01/21 12:54:34
2022/01/21 12:54:34 Digipeater CHURCH audio level = 60(13/16) [NONE] __|||____
2022/01/21 12:54:34 [0.3] VE7RAD-10>APRS,CHURCH*,WIDE2-1:!4909.30n/12201.05w#ve7rad-10 fill in digi#<0x0d><0x0a>
2022/01/21 12:54:34 Warning: Lower case n found for latitude hemisphere. Specification requires upper case N or S.
2022/01/21 12:54:34 Warning: Lower case w found for longitude hemisphere. Specification requires upper case E or W.
2022/01/21 12:54:34 Position, DIGI (white center), Generic, (obsolete. Digis should use APNxxx instead)
2022/01/21 12:54:34 N 49 09.3000, W 122 01.0500
2022/01/21 12:54:34 ve7rad-10 fill in digi#
2022/01/21 12:57:38
2022/01/21 12:57:38 Digipeater CHURCH audio level = 52(17/14) [NONE] ___||:___
2022/01/21 12:57:38 [0.4] TRAILR>APMI06,CHURCH*:@212045z4903.34NS12222.98W# W1,BCn VE7WTZ-10 Fill-In Digi
2022/01/21 12:57:38 Position with time, OVERLAY DIGI (green star) w/overlay S, SQ3PLX http://microsat.com.pl/
2022/01/21 12:57:38 N 49 03.3400, W 122 22.9800
2022/01/21 12:57:38 W1,BCn VE7WTZ-10 Fill-In Digi
2022/01/21 12:57:47
2022/01/21 12:57:47 Digipeater CHURCH audio level = 66(12/14) [SINGLE] ____:____
2022/01/21 12:57:47 [0.4] KF7VOL-5>APAT81-1,CHURCH*,WIDE2-1:!4839.09N/12222.01Wk347/009/A=000228A 146.520MHz 578 Mobile
2022/01/21 12:57:47 "146.520" in comment looks like a frequency in non-standard format.
2022/01/21 12:57:47 For most systems to recognize it, use exactly this form "146.520MHz" at beginning of comment.
2022/01/21 12:57:47 Position, truck, for Anytone. 81 for 878 HT
2022/01/21 12:57:47 N 48 39.0900, W 122 22.0100, 10 MPH, course 347, alt 228 ft, 146.520 MHz
2022/01/21 12:57:47 A 146.520MHz 578 Mobile
2022/01/21 12:59:35
2022/01/21 12:59:35 CHURCH audio level = 66(16/14) [SINGLE] ___::____
2022/01/21 12:59:35 [0.3] CHURCH>APDW16,WIDE2-2:!4851.69NS12237.06W#PHG5260W7JIM
2022/01/21 12:59:35 Position, OVERLAY DIGI (green star) w/overlay S, DireWolf, WB2OSZ, 25 W height=40 6dBi omni
2022/01/21 12:59:35 N 48 51.6900, W 122 37.0600
2022/01/21 12:59:35 W7JIM
2022/01/21 13:04:41
2022/01/21 13:04:41 Digipeater CHURCH audio level = 57(14/14) [NONE] __|:_____
2022/01/21 13:04:41 [0.2] VE7RAD-10>APRS,CHURCH*,WIDE2-1:!4909.30n/12201.05w#ve7rad-10 fill in digi#<0x0d><0x0a>
2022/01/21 13:04:41 Warning: Lower case n found for latitude hemisphere. Specification requires upper case N or S.
2022/01/21 13:04:41 Warning: Lower case w found for longitude hemisphere. Specification requires upper case E or W.
2022/01/21 13:04:41 Position, DIGI (white center), Generic, (obsolete. Digis should use APNxxx instead)
2022/01/21 13:04:41 N 49 09.3000, W 122 01.0500
2022/01/21 13:04:41 ve7rad-10 fill in digi#
2022/01/21 13:04:57
2022/01/21 13:04:57 CHURCH audio level = 53(16/14) [NONE] __|||____
2022/01/21 13:04:57 [0.3] CHURCH>APDW16,WIDE1-1,WIDE2-1:}N5XMT-1>APX219,TCPIP,CHURCH*::KF7VOL-5 :?VER
2022/01/21 13:04:57 Third Party Header, DireWolf, WB2OSZ

There are lots of APRS-related websites that explain APRS.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/0d115232-2c0f-4167-be61-fe157d11ad82n%40googlegroups.com.

[David N7NTN]

Steve,...'monitor only'...oh, right  that makes a few points irrelevant, duh not too hard to unpack from here (laughing)

I'm not sure what you mean by 'directed at you'. The message said the format 144.990 should be 144.990MH

and I see in the screen shot a message indicating a non-standard format...the frequency without the MH appended

you'll have to tell me what to do about that if anything

and now on 144.390 I'm seeing the APRS monitor screen in my chosen colors. The message in red is still there indicating that the digipeater V7VIC-15 input level is too high

and the continuous stream of information.

So it looks like I have it set up right so far. What item of the 'monitor only' drop down tab should I chose to become active or is monitor only the standard?

David

N7NTN

[Steve Magnuson]

David,

Responses below.

> I'm not sure what you mean by 'directed at you’.

I meant that the transmission was not sent specifically to you. You indicated in your first message that you thought it was sent specifically to you. It wasn’t.

> The message said the format 144.990 should be 144.990MH
>
> and I see in the screen shot a message indicating a non-standard format...the frequency without the MH appended
>
> you'll have to tell me what to do about that if anything

Nothing for you to do. Direwolf is simply telling you that the frequency text in that other ham’s APRS message is not in the correct APRS format. There is nothing you can do about that.

> So it looks like I have it set up right so far. What item of the 'monitor only' drop down tab should I chose to become active or is monitor only the standard?

Google “APRS Digipeat” and “APRS iGate” to see what those options do. Andy might chime in here too since he’s set up a number of igates/digipeaters.

I know that you earlier reduced your receive levels in alsamixer to get rid of that “level too high” message from that one station. If you see that message from just that one station it’s not your problem, it’s the transmitter’s. So, you might want to bump up your receive level again so that your FSQ and other modes will still work OK.

Steve
AG7GN

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/bd632aed-7405-4572-9f2f-350c187fcdb5n%40googlegroups.com.