While using Screen through Terminal on my Mac to connect to my TM-D710G, I haven't found a way to delete mistakes without using CTRL-X, which removes the entire entry without transmitting.  The TNC2 has a DELETE option that allows you to remove mistakes using backspace or delete on your keyboard.  There's also an option to use a forward slash to cancel out typed characters.  Is there any corresponding option for our TNCs?

Hello Joshua,

The issue you're describing is a classic "terminal backspace" issue.  Have you done some internet searches for this issue?

   https://www.google.com/search?q="screen"+backspace+doesn't+work

   This looks good:  https://discussions.apple.com/thread/792594


Beyond that, is there a reason you're using screen vs. some other serial terminal program?  There has to be a lot of other programs that will do better:

   https://www.google.com/search?q=serial+terminal+program+for+mac

--David
KI6ZHD

I did not do some internet searches.  Since I found the answer to the TNC2 issue in its manual, I figured this was a TNC issue, not a terminal issue.  

I am using screen simply because it is what I am familiar with.  I'll try some other things if there's no other evidence this is a TNC specific issue.  

In Terminal I checked "Delete sends Command-H" and that seemed to fix my issue.  I'm 1500 miles from home in Fort Wayne, IN.  While my wife was getting her hair done, I looked for some packet stations on 145.010 to 145.090.  I did not receive any beacons in 45 minutes.  I'm surprised this part of the midwest isn't terribly active in packet (or voice repeaters for that matter.)  Maybe I should check Indiana's band plan...

Traveling from Utah to Indiana I didn't get a single reply on a 2m repeater.  I found a couple BBS stations though and left messages while the wife was driving.  Anywho, got the backspace problem fixed.  

Hello Joshua,

In Terminal I checked "Delete sends Command-H" and that seemed to fix my issue. 

Ok.. that's good and considering they have a checkbox for this in the terminal program, that shows how common of a need there is for this.

I'm 1500 miles from home in Fort Wayne, IN.  While my wife was getting her hair done, I looked for some packet stations on 145.010 to 145.090.  I did not receive any beacons in 45 minutes.  I'm surprised this part of the midwest isn't terribly active in packet (or voice repeaters for that matter.)  Maybe I should check Indiana's band plan.

Ha.. I can't say I've ever tried "mobile packet" before (APRS doesn't count).  Anyway, yes.. I would start with understanding the local bandplan (there sometimes can be multiple per state) and then use an SDR to monitor the band first.  At minimum, use an SDR program / plugin that offers persistent peaks and broadly monitor the packet section of the band for like 20-30min.  Any resulting peaks is where you want to start focusing on.

Traveling from Utah to Indiana I didn't get a single reply on a 2m repeater

How many repeaters did you try?  I've found very similar behaviors in other geos and it comes down to a few things:

   1. People don't know you so why would they reply to your call?
   2. Why would people reply to your call?

I've always found that your APPROACH to announcing your call for a QSO can really improve your chances.  For example:

   - BAD:  You transmit a "KJ7LVZ listening" once, get no response, and leave the repeater

   - GOOD: You transmit a "This is Joshua KJ7LVZ traveling from Utah to Indiana.  I was curious if anyone can give me a signal report and possibly tell me where a good place to eat might be".

The key here is to give people a reason to pick up the microphone and even if you're not hungry, every HAM has an opinion on food so they might come out of the woodwork to express it.  :-)  Try other "opinion topics" be it technical ones, non-technical ones.. etc.

.  I found a couple BBS stations though and left messages while the wife was driving.  Anywho, got the backspace problem fixed.  

I'm impressed that packet would deal with the Doppler shift so well.  Were these proper BBSes with white pages and other BBS relaying functions to get the reply sent back to your home BBS?  If not, if the sysop replies to your message, it's going to be stranded on that BBS until you travel back that way and retrieve it. 

--David
KI6ZHD

@David Ranch

The doppler effect is so small it doesn't count; I calculated a shift of 16hz at 70mph using an online calculator. 
I don't have a local BBS so I didn't bother with forwarding, I just checked to see what was available on the node, left a message for the Sysop saying "hi" and that was it.  I wanted to check them again on the way home but I drove the entire time so I missed my opportunity.  

I tried 15 or so different repeaters.  I tried a variety of things including mention of my destination, "Good morning", "Merry Christmas", and others.  I am sure I could have tried more but didn't.  I make sure to speak clearly and slowly enough I am easy to understand.  Anytime someone checks into my local repeater system and I can hear enough to understand them, I give them a reply.  If they key up while talking 100 mph which causes the first two letters of their call to not make it and then the other can't be understood, I don't bother. 

Next time I'm anywhere near a food place, I'll give the eatery question a try.  

Looks like it's about time to hike up the mountain to install a digipeater so I can actually have a home BBS.

73 KJ7LVZ

Joshua,

Here in NE Indiana we use 145.53 for 1200 bps packet. 145.05 is most of the rest of the state. And a mix of 145.01 near of Evansville and 145.09 near Noblesville. 

73,
Dan N9WNH