Skip to main content

Tracker2 + LCD and poor decoding

I do sometime clear up the Favourite from my Nuvi350 but it left me wondering why it took so many packets before a single callsign pop-up in the Favourite list. Wonder no more .. after I added an LCD module to my setup I found out that most of the incoming packets were not recognised by Tracker2 eventhough they came with a very strong signal. I have no idea if this has to do with configuration or purely hardware problem. I've a TT4 which could decode most if not all packets it received but surely I need to tweak the configuration. In Tracker2 firmware, I could not find a way to do this. BTW, TT4 is connected to a Yaesu HT through an audio cable while the Tracker2 is connected to a Kenwood TMV71A through a data cable. I've played around with the audio level going through the PR1 pin on the Kenwood but it doesn't help much.

Anyway, since it is hard to get a suitable enclosure for the LCD display, I just epoxy-ed the exposed parts & traces on the LCD and 3M-ed it to my car's dashboard..

Update 1: It seems lowering the audio setting on PR1 pin/Kenwood data port does increase the number of packets decoded by Tracker2. The default setting was at 9, I reduced it to 6 before and now to 4. Probably it was over-deviation that causes the problem? I've no idea really but will monitor if this is the case.


m0kxq said…
you do have the radio set to NARROW deviation and NOT wide
9W2TPT said…
Hi Phil,

Thanks for the suggestion. I've now upgraded to TMD710 in my car and have the TMV71 in my shack connected to TT4. It doesn't seem to have a problem with TT4.. so I didn't pursue this anymore. The OT2m is happily sitting at mountain top connected right now and works great with a HT as digipeater.

Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.