Amateur (Ham) Radio BS and Callsign Thread!

The messages are being sent successfully, it just keeps trying to send multiple times.

 

So you or whoever you are sending them to actually get the message? I ask because when I was having the issues, it would show as sent, but the repeater didn't actually receive it. Then it would go to a similar process of trying like 6 more times.

 

Once you get the ack it should stop sending.

 

This is absolutely the most important information to be gleaned from his experience. Truly. I’m not trying to make a Friday-thread, but it is unacceptable if a drive through discriminates against hams.

 

OP, any chance you can rename “Ham” in title as “ham” lower case?

 

Need to mount an mobile antenna on 2016 DC, can people show some pics of thier tacos with Ham Radio Antenna mounts so I can get some ideas. Certainly would appreciate any thoughts on (dis)advantages to certain locations or types of mounts too!

 

It sends, gets digipeted, gets and ack returned from SMSGTE, and is delivered to the cell phone recipient. The re-sends are not acknowledged and not forwarded as a text message.

KJ7LVZ-9


Messages screen


SMS from my phone

 

Drill a hole in the roof. JUST DO IT.

 

AGREE.....!

 

It has to show the ack was... Acked.

 

Height is might. As up top as you can go. Either an nmo mount or mag mount.

 

How do I ack an ack? Message sent, the response was delivered to my messages inbox. Does SMSGTE not automatically ack a message?

 

You didn't get an ack, you sent one.

 

Got acked on a different message last night. I think if you don't get the original acknowledgement, it isn't present with later message transmissions. Maybe the path settings from the SMSGTE acknowledgement don't ask for digipeting.

So many fun things to learn.

 

The ack he's talking about is done automagically by the client receiving the message, at least if the protocol is fully implemented. Status and Posit packets are sent with no expectation of an ack packet but message packets are sent and will retry until either it receive an ack from the recipient or it times out.

Fun fact, the example message he's using shows my station sending the "ack2" and in that case the client is Xastir over the Internet directly (TCPIP, not RF).

Typically this is a finite number generally with decaying delay. IOW you hit send the message packet is transmitted immediately (or as soon as the TNC/client detects it's OK, they sometimes watch squelch to clear) and then some number of times following some delay algorithm.

For example my Argent Tracker3 is set to a 120 second delay with a limit of 7. So that means it sends at most 8 packets at intervals of 0 (first packet), then 2 minutes later, then 4 minutes after that one, then 6, 8, 10 and finally a 12 minute delay. If it has not heard an ack packet by the last one (which I think is 38 minutes later) that message is assumed to be undelivered. I've experimented making that 30, 60 and 90. None of them are really ideal compared to an actual operator sending a message. If the network hasn't transported an ack in the first few minutes it's not really worth letting it ping away indefinitely.

In that time the person you sent the message to may have actually composed a response message that implicitly acknowledged your original message in fact got through but to the network his station for whatever reason wasn't configured to send an ack or the network or your client never heard it.

In a local network of all RF stations this I find is not usually the case, ack packets usually work. It's when sending messages over a digipeater they are sometimes mistimed or experience collisions. Worse yet is when it has to traverse APRSIS and the Internet there's so many more opportunities for a packet to end up in the bit bucket that waiting

 

I was too chicken to drill a hole in my roof. I have reposted this a few times. Check here...

https://www.tacomaworld.com/threads/amateur-ham-radio-bs-and-callsign-thread.260643/page-235

 

TM-V71A, Larsen dual-band antenna, NMO roof mount, Factory mic cable.
Some people have indicated my signal drops out and gets very staticy while transmitting. I was having a conversation with a guy last night, truck was off, and he said part way through my transmission it would sound like frying bacon. It wasn't consistent, it would go in and out. Tried all three power settings (5w, 10w, 50w.) I figured maybe the transceiver was reacting to bad SWR but with transmitting only 5w, that doesn't seem to be the case.

Did some google-fu and others have identified the same issue as the mic cable RJ-45 connector being finicky. My cable is under tension when I am using it. Anyone have a source for a longer mic cable? I don't want an "extension"; I would like a longer coiled cable. It is a special cable with the voice wires shielded. Maybe I should just do a strain relief off the radio body and wedge the connector so it doesn't wiggle in the mic?

 

I believe the hack is to buy your own shielded cable and swap the pinout to the right order on the plug so you don't get the clocking issue

 

I have shielded CAT-5 (CAT-6E?) cable at home, RJ-45 connectors, and a crimp tool. Guess it wouldn't hurt to try. I thought the audio cables were shielded from the rest of the wires. Maybe just making the voice and voice ground a twisted pair will be sufficient.

 

The whole issue is the Mic and data line being put right next to each other. There's bibles worth of posts a out guys saying "oh mind works fine" and then a few months later you'll have reports of woody the wood pecker on tx.

Here's one suggestion to make an extension for the stock cable.


~~~~~~~~~~~
1- no connection
2- DC 8V, 100mA max
3- GND
4- PTT
5- GND (MIC)
6- Mic, 600 impedance
7- No Connection
8- Keypad serial data

Read on the Yahoo group for the 71A that a flat cable would put more separation between the serial line and the mic line and would help reduce/eliminate the motorboating. Seems to work on mine. Radio mounted in front of console in my ranger. Mic cord was obviously not gonna last long as much as it was getting stretched(also pulling on connector). An 18 inch piece of flat CAT5 secured midway to eliminate pulling on connector also provided just enough extra to make mic cord long enough. 3 fixes in one, not pulling on connector, added link and separated the critical wires. It seems to have worked on mine. Funny thing, I had the radio a year before it started motorboating.


~~~~~~~~
I forget which one it is, but folks also separate one of the lines completely and shield it externally to help the issue. It's not external rf or common mode down the line. It's an internal thing.

Frank KK4YTM