Date
1 - 10 of 10
My Bluetooth Mobilink TNC 2 issue
|
I have a Mobilink TNC which has been working for a while. Lately, the
TX part is not being picked. I can see tracers showing what appears to be RF reaching out to a digipeater. I see the scroller with * by the stations sending off there data. I see the Mic e and SMSGTE messages etc. For some reason my data is not picked up. 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k ALLSTAR 530780 HH# 5971 HH# 11384 Alberta Mesh# 5404 
|
|
|
|
Lynn Deffenbaugh
You didn't mention exactly what you expect to be picking up your transmissions, nor how you know they are not being picked up.
toggle quoted message
Show quoted text
We would also need to know what radio you have connected to the Mobilink and whether you believe that radio and antenna combination will actually reach whatever you expect to be receiving your packets. But a more basic question is: When you tell APRSISCE/32 to transmit, does the Mobilink TNC actually key up the radio? Have you listened to the packet bursts on another radio to confirm that some audible signal is actually going out over the air? And what is the callsign-SSID configured in your APRSIS32 instance? Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 6/8/2021 2:00 PM, Don Poaps wrote:
I have a Mobilink TNC which has been working for a while. Lately, the |
|
|
|
Sorry, Duh!
toggle quoted message
Show quoted text
Alinco DR 605 using Ham Made cable with RF 45 to Mic and speaker. I can pick up local stations. I can use the Mobilink Bluetooth config program and key the radio. I see the Bluetooth TX radio. I then switched the radio and went to use my Woxum HT with the Bluetooth tnc. I get the same issue. The weird thing is that this HT work for quite a while. I switch to the Alinco and it worked great. I started getting messages via email that my station was seen. This morning I switched back to the HT. I'm having the same issues as Alinco. I have another Bluetooth TNC I'll bring and replace. It's really weird that lately TX side doesn't work. I did do a reset on the TNC. I'll remove the 12 v 110 Power and run directly from the 12 v battery to see if they're some sort of RFI interfering with the TX. back to the drawing board. 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k ALLSTAR 530780 HH# 5971 HH# 11384 Alberta Mesh# 5404 On Tue, Jun 8, 2021 at 11:08 AM Lynn Deffenbaugh <kj4erj@...> wrote:
|
|
|
|
Rob Giuliano
What do you mean by "not being picked up"? It could mean any or all of these: You are unable to see the data on places like aprs.fi? You are not seeing the DIGI'ed signal com back from a local DIGI? You can't hear any tones on another radio receiver? Are you sure the tracers are not RX? For TX issues, the first question would be: Does the radio PTT work when the APRSIS32 timer hits zero? If YES, Can you hear packets from your radio on another receiver? Robert Giuliano
On Tuesday, June 8, 2021, 2:01:09 PM EDT, Don Poaps <va7dgp@...> wrote:
I have a Mobilink TNC which has been working for a while. Lately, the TX part is not being picked. I can see tracers showing what appears to be RF reaching out to a digipeater. I see the scroller with * by the stations sending off there data. I see the Mic e and SMSGTE messages etc. For some reason my data is not picked up. 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k ALLSTAR 530780 HH# 5971 HH# 11384 Alberta Mesh# 5404 |
|
|
|
Lynn Deffenbaugh
How about the rest of the answers?
toggle quoted message
Show quoted text
You didn't mention exactly what you expect to be picking up your transmissions, nor how you know they are not being picked up. Do you believe that radio and antenna combination will actually reach whatever you expect to be receiving your packets. When you tell APRSISCE/32 to transmit, does the Mobilink TNC actually key up the radio? Have you listened to the packet bursts on another radio to confirm that some audible signal is actually going out over the air? - This is different than the Mobilink config program just keying the radio. And what is the callsign-SSID configured in your APRSIS32 instance? - At least this one appears to be VA7DGP which was last heard via the APRS-IS yesterday. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 6/8/2021 2:23 PM, Don Poaps wrote:
Sorry, Duh! |
|
|
|
todd.dugdale@...
If you configure the Mobilinkd TNC for one radio, and then use it on another, the audio settings will be different. The TX audio might be too low or too high, or there's too much difference between the levels of the two tones. It sounds like you set up the audio on the Alinco, and then plugged the TNC into a Woxoun. This might explain why the Alinco "works" and the other radio doesn't. If you set up the TX audio on the Woxoun, you would know it transmits because you need to listen to the transmitted audio level on a different radio.
Further, if you did a "reset" of the Mobilinkd TNC (as you said), then you wiped out the audio settings for the Alinco and you're using the defaults. The problem is probably not that the Mobilinkd isn't "transmitting"; the transmitted signal probably can't be read because of bad audio levels. |
|
|
|
Hi Todd.
toggle quoted message
Show quoted text
I did use the Mobilink Audio Config program on my Android phone. I've put the Bluetooth on the back burner for now. Thank You 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k ALLSTAR 530780 HH# 5971 HH# 11384 Alberta Mesh# 5404 On Mon, Jun 14, 2021 at 1:53 PM <todd.dugdale@...> wrote:
|
|
|
|
todd.dugdale@...
Well, your screenshot shows a Windows install of APRSIS32. If you're using the Mobilinkd TNC with a PC, you need to configure the audio with the Windows version of the config app, and save that config. Your Android config will only be using the audio settings for the particular Android device that you're using.
I've 'fixed' two local operators' TNC2 simply by setting the audio levels. in both cases, the Moblinkd was declared "broken". If the Mobilinkd doesn't "work" with that Android device, you should day so. Then it's likely an app setting. Good luck. -KD0TLS |
|
|
|
http://www.mobilinkd.com/downloads/
toggle quoted message
Show quoted text
I have a TNC3. Mobilinkd TNC configuration utility for Microsoft Windows. Use these programs to set output volume, monitor input volume and set all KISS parameters on computers running Microsoft Windows. The computer must have a Bluetooth interface in order to use this program. This is only for the TNC2 -- it will not work with the TNC3. I'll be working on this later. 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k ALLSTAR 530780 HH# 5971 HH# 11384 Alberta Mesh# 5404 On Mon, Jun 14, 2021 at 5:27 PM <todd.dugdale@...> wrote:
|
|
|
|
Speaking as someone who has written a Mobilinkd config app for macOS and built a NucleoTNC, I don’t think this is correct. With the Mobilinkd, there is no relationship to the audio card on the device where you are running the config app, regardless of whether it is a PC, Mac, Android or iOS device. The TNC2/3 uses its onboard circuitry to capture audio; no audio data is sent to the computer for processing. It should work perfectly well to configure the TNC2 with Android and use it on a Windows machine. You do, however, need remember to save the settings to the NVRAM on the TNC, so that, if it is power cycles at any point when changing from one device to another, it retains the settings you just configured.
- Wes, W8WJB |
|
|