Kenwood: TM-D710G group scanning issue

[caylorman]

Wanting to see if anyone else with a Kenwood TM-D710G is having an issue with scanning within groups. I use the rig for both ham use as well as monitoring local railroad traffic. Typically, the A side is scanning railroad frequencies in the group 7 block while the B side is running APRS. I have no issues with group scanning these channels, but when I switch to a group that has 2m/70cm frequencies and try to group scan, it will randomly stop scanning. There isn't a specific channel it always stops on.

I've seen this occur when the 2m/70cm group is scanned on both A and B sides of the radio, with APRS on and off (both beacon and the APRS/TNC off). It occurs on other blocks with ham frequencies, but doesn't appear to affect the RR frequency blocks. I've checked to see if maybe the PTT is getting depressed, but the mic has been in the same spot for both group scans and only the ham groups appear to be affected.

Anyone have any ideas what may be going on?

 

[AB4BF]

Wanting to see if anyone else with a Kenwood TM-D710G is having an issue with scanning within groups. I use the rig for both ham use as well as monitoring local railroad traffic. Typically, the A side is scanning railroad frequencies in the group 7 block while the B side is running APRS. I have no issues with group scanning these channels, but when I switch to a group that has 2m/70cm frequencies and try to group scan, it will randomly stop scanning. There isn't a specific channel it always stops on.

I've seen this occur when the 2m/70cm group is scanned on both A and B sides of the radio, with APRS on and off (both beacon and the APRS/TNC off). It occurs on other blocks with ham frequencies, but doesn't appear to affect the RR frequency blocks. I've checked to see if maybe the PTT is getting depressed, but the mic has been in the same spot for both group scans and only the ham groups appear to be affected.

Anyone have any ideas what may be going on?

I think it might be sub-audible tones that may be transmitted from one or more repeaters. I don't have a D710G, so its just a guess on my part.

 

[n9mxq]

Its the rig.. Can't get mine to scan more than about a minute before it just stops scanning.. My 710 (non-g) will scan forever. Not sure what they tweaked between the two.. but there's something causing it..

 

[caylorman]

OK, I think at least narrowed it down some. From my experimentation, it looks like groups with channels that have CTCSS active will randomly stop scanning. I made a test group with channels using no tone, and with tone on the input active. No problems with scanning there. I next activated CTCSS on one of the channels and started the group scan. The scan stopped on its own after about 5 minutes.

Now, I have no clue why it happens the way it does, but it looks like I at least found some kind of fix.

 

[KE5MC]

Thinking back to my D710 there was something about APRS options that effected the other side. Blocking the sound of the data burst other than just turning APRS side volume down or the Voice option and 100 CTCSS tone. Might be related to the issue at hand, but I'm not sure.
Good Luck!
Mike

 

[n9mxq]

OK, I think at least narrowed it down some. From my experimentation, it looks like groups with channels that have CTCSS active will randomly stop scanning. I made a test group with channels using no tone, and with tone on the input active. No problems with scanning there. I next activated CTCSS on one of the channels and started the group scan. The scan stopped on its own after about 5 minutes.

Now, I have no clue why it happens the way it does, but it looks like I at least found some kind of fix.

Interesting... Never thought about tones being the issue

Thinking back to my D710 there was something about APRS options that effected the other side. Blocking the sound of the data burst other than just turning APRS side volume down or the Voice option and 100 CTCSS tone. Might be related to the issue at hand, but I'm not sure.
Good Luck!
Mike

APRS cuts VHF rx out on the other side every time in both my 710 and 710g.. nothing new there.. The 100hz tone was for voice alert so you'd know a nearby operator was monitoring 146.52.. Used to have that set up in my semi when I was OTR.. Thousands of miles, quite a few bursts with 100hz pl, never got a reply on 52...

 

[KB3KBR]

Interesting... Never thought about tones being the issue



APRS cuts VHF rx out on the other side every time in both my 710 and 710g.. nothing new there.. The 100hz tone was for voice alert so you'd know a nearby operator was monitoring 146.52.. Used to have that set up in my semi when I was OTR.. Thousands of miles, quite a few bursts with 100hz pl, never got a reply on 52...

That's not how voice alert works. The idea is if you hear a burst with the tone then reply back with voice on the APRS channel to make contact and move to a different channel. http://www.aprs.org/VoiceAlert3.html

 

[n9mxq]

That's not how voice alert works. The idea is if you hear a burst with the tone then reply back with voice on the APRS channel to make contact and move to a different channel. http://www.aprs.org/VoiceAlert3.html

I had my beacon set, and frequency broadcasting 146.52.. I listened to 144.39 for bursts, called a bunch of times, in several states.. and only ever had one convo..

 

[KE5MC]

I believe your "frequency broadcasting on 146.52" is part of the APRS data packet if enabled, but the receiving end has to be setup to decode and respond to the information. I'll admit I only read about it many years ago. Kind of like sleeping at a "Holiday Inn". Better luck to be had on APRS frequency with a brief voice exchange and move to a different frequency. If remembered wrong... well likely I will hear about it.

 

[R8000]

I think there was a firmware issue when they came out with the new style hand mic. If you used the new hand mic on a radio with old firmware (meant for the orig mic), the new mic would randomly think you are doing a push button command.

 

[zerMATT]

Reviving an old thread here, but I've recently wanted to make a D710A a primary-ish dual-band in my shack and in the car. I use scan *all the time* with my current primary radio, the FTM-400, but when I try scanning with the D710A, it scans for maybe 30 seconds and stops. When it stops, it's somewhat random - some 2m frequencies, some 1.25m, and some 70cm. When it stops, it's stopping on channels saved with and without CTCSS programmed. Are there any suggestions out there on how I might resolved this?

 

[AK9R]

when I try scanning with the D710A, it scans for maybe 30 seconds and stops

I've never had an issue like that with my TM-D710s. Are you sure it's not receiving a signal? Is a knob, button, or PTT being bumped? Is the radio loosing power briefly?