Re: TNC-PI COMMANDS
Jerry Spillman <jzs@...>
Tadd and John,
Thank you for the prompt and courteous replies. As to John's reply, thank you, I will be very happy to try that once I can resolve a couple of other issues that seem primary here. One of them being the file www.tnc-x.com/params.zip, which will not unzip on the pi. It is difficult to use files that I am not able to access, and don't know where to get a viable copy. For Tadd, I have a jnos three frequency node (three radios, three tncs, one headless linux box)(Kate:W0HU-6) running in my home that I have connected with using the tnc-pi rig. I also have an x1j4 (SMTN:W0HU-5) node I have connected with, and my home terminal, W0HU. The home terminal and smtn know for sure what to do with mh. Kate knows what to do with j. However, whether I am instructing the tnc correctly as to the sending of either, I am not sure, as I only see a connect, then nothing, no matter what further information I send, and I can't figure out a successful disconnect from the Pi end... Again, I may not be sending the right information from my keyboard, I am not quite sure how to operate in the KISS mode. As I stated above, I can't tweek txDelay because the file won't unzip on the Pi (why isn't it a tar.gz?). I have tweeked transmit audio level as best I can using the received tone method specified in the TNC-PI manual. The transceiver I am working with is set to WIDE. More wild stabs at this will be much appreciated. 73, Jerry
|
|
Heardbleed bug affects OpenSSL
wb2ifs@...
if you haven't seen the news already click here: http://www.computerweekly.com/news/2240217841/EFF-calls-for-rapid-mitigation-of-Heartbleed-internet-bug
This affects all systems using OpenSSL--including the PI! 73 de WB2IFS
|
|
TNC-Pi setup
robjbrad@...
Hello, I'm new to the group and have recently started using my TNC-Pi. I'm using APRX as a receive i-gate and also attended digipeater. I wondered if anyone has configured ramdisk logging and/or webserver log access? I'm going to have a go, but I have limited Linux knowledge....
Also is there any way of setting the receive audio level optimally other than watching for the orange LED? Many thanks, Rob - M0TKT
|
|
Re: TNC-PI COMMANDS
Jerry, What kind of software is the connected station running? Are you sure it knows what to do with an MH? It might be better to connect from your new TNC to another TNC that you control or whose operator you can talk to on FM or on the phone. Then you can tweek things like transmit audio level, TxDelay and whatnot. Send many messages and make sure your success rate is very high. Make sure your TxDelay is not set too short. Set it to 90 to start. That should be audibly really obvious but will only make things slower. Now if it was too short, you'll see the thing suddenly work reliably. Also make sure your transceiver doesn't have a NARROW audio mode. If it does, set it to WIDE. This happens with the modern Chinese radios which are made for both Amateur and commercial markets. Wild stabs at the problem is all I have. Tadd
On Apr 09, 2014, at 04:18 PM, John Wiseman wrote:
|
|
Re: TNC-PI COMMANDS
John G8BPQ
Jerry, The TNC-PI is a KISS TNC, so doesn't have any commands in that sense. What you can send to a connected station depends on what software that station is running. A Node is likely to respond to MH, but another user terminal won't. There is a description of one way to use the TNC-PI as a simple Keyboard to Keyboard terminal at https://sites.google.com/site/bpq32wiki/home/installing-linbpq/simple-kiss-terminal 73, John
From:
Raspberry_Pi_4-Ham_RADIO@...
[mailto:Raspberry_Pi_4-Ham_RADIO@...]
On Behalf Of jzsszj@...
My TNC-Pi appears to be working, however, I get no response when trying to send mh to a connected station. I am able to successfully connect, however nothing is happening after that, including being able to disconnect. It was suggested that I check the parameter settings recommended in the manual, all are as specified. I am a bit weak on Linux, however, need to know a full list of checks that I can make to figure out how to make this unit work keyboard to keyboard. Thanks. Jerry
|
|
TNC-PI COMMANDS
jzsszj@...
My TNC-Pi appears to be working, however, I get no response when trying to send mh to a connected station. I am able to successfully connect, however nothing is happening after that, including being able to disconnect. It was suggested that I check the parameter settings recommended in the manual, all are as specified. I am a bit weak on Linux, however, need to know a full list of checks that I can make to figure out how to make this unit work keyboard to keyboard. Thanks. Jerry
|
|
Re: TNC-PI Help please
Ryan Stapleton
Hello Ray,
toggle quoted messageShow quoted text
Sadly that didn't seem to change anything. Thanks -Ryan
On Apr 8, 2014, at 3:58 AM, Ray Wells <vk2tv@...> wrote:
|
|
Re: TNC-PI Help please
Ray Wells
Ryan, Tabs are fine, probably my ageing eyes deceiving me. Ray vk2tv
On 08/04/14 21:19, Ryan Stapleton wrote:
|
|
Re: TNC-PI Help please
Ryan Stapleton
I have not hooked them both up together. I have tried one at a time. Thanks Ryan
On Apr 8, 2014, at 3:15 PM, "John Wiseman" <john.wiseman@...> wrote:
|
|
Re: New RPi Form factor
Bob Scan
Great News.........where do I send my money :) B
From: John Wiseman To: Raspberry_Pi_4-Ham_RADIO@... Sent: Tuesday, April 8, 2014 3:56:42 AM Subject: RE: [Raspberry_Pi_4-Ham_RADIO] New RPi Form factor Ronny,
I have a couple of prototype 9600 versions
of the TNC-PI running. Watch this space!
The same board can also be configured as a
D*Star Modem.
73, John G8BPQ
From:
Raspberry_Pi_4-Ham_RADIO@...
[mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of Ronny Julian Sent: 08 April 2014 02:22 To: Raspberry_Pi_4. Subject: [Raspberry_Pi_4-Ham_RADIO] New RPi Form factor I can see the computer snapping onto the next TNC-Pi now! 9600
bps also? Just tossing it out there.
Ronny
K4RJJ
|
|
Re: TNC-PI Help please
John G8BPQ
Ryan, It is probably a silly question, but are you trying to use both TNC's on the same PI. You can only connect one at a time, unless at least one is set to i2c mode. 73, John G8BPQ
From:
Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...]
On Behalf Of ryan@...
Hello All, I appreciate you all taking the time to read and respond. I have recently put together 2 TNC-PI's. These are my first real attempt at putting together a kit. (My last one was over 10 yrs ago and only a little LED Christmas Tree)
I finally hooked up a radio yesterday but don't have any joy. I am going to list what I have done here. I also only have a multi-meter for test equipment.
I picked up an OLD Yaesu CAT-2500 yesterday at a local hamfest. The radio works and I am able to transmit and receive on it no problem.
I wired up what I believe are the connectors from the 4 pins on the TNC PI. (1,3,5,6) to the radio.
When I key up the radio I do hear a tone on another radio I have with both TNC-Pi's.
TNC-PI 1: When I send a packet on one of my other setups (TH-72A or PK-88/Radio combo) I see the yellow light come on. I tried: sudo minicom -b 19200 -o -D /dev/ttyAMA0 and got some squiggles but no one ones appeared at all when packets came in. Minicom also showed offline.
TNC-PI 2: The yellow light does not always come on when a packet happens. I tried: sudo minicom -b 19200 -o -D /dev/ttyAMA0 I didn't see any data. minicom also showed off line.
All Cases:
I do the kiss attach /dev/ttyAMA0 1 10.1.1.1 and it says "AX.25 port 1 bound to device a x0"
sudo axlisten -a : nothing comes across.
axcall 1 KA3WUT-4 : No red light, no keying up.
Config Files: /boot/cmdline.txt: dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
/etc/ax25/axports: # /etc/ax25/axports # # The format of this file is: # # name callsign speed paclen window description # 1 KA3WUT-1 19200 236 2 TNC 1
Notes: KA3WUT-4 is my PK-88 KA3WUT-7 is my TH72
Questions: I have seen where some folks are saying listen to pin 6 of a chip? What chip is that and how does one do that? If a normal headset I assume I need to have one 1 of the headset set to pin 6 (I assume 1 is top left of a chip?) Does anything else need to be connected to the headset and if so what?
I can take photos of my boards front and back if that would be helpful? ; I am up for suggestions/ideas/help.
Thank you -Ryan (KA3WUT Chantilly, VA)
|
|
Re: TNC-PI Help please
Not sure about that I thought mine were tabs?
Tommy MM0KNE
From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of Ryan Stapleton
Sent: 08 April 2014 12:20 To: Raspberry_Pi_4-Ham_RADIO@... Subject: Re: [Raspberry_Pi_4-Ham_RADIO] TNC-PI Help please
Hello Ray, They are all TABs between the fields in the axports. I will change them to spaces tonight after work and see what happens.
Thanks -Ryan
On Apr 8, 2014, at 3:58 AM, Ray Wells <vk2tv@...> wrote:
Ryan,
|
|
Re: TNC-PI Help please
reference the pin6 question, it is pin 6 of the op amp. The audio goes in via pin 3 and out via pin 6. If you look at the build instructions you will see the circuit diagram, with help from some of the guys, I managed to trace the entire board out and track the audio through. I must admit that I never managed to hear the tone that apparently is always generated but I used Visual Analyser to get it to show as a trace in the laptop. I found Visual Analyser hard work, found SCOPE more user friendly. I should openly admit I am no guru on this just reflecting my experience of trying to get the TNC-Pi up and running Tommy MM0KNE
From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of Ray Wells
Sent: 08 April 2014 08:59 To: Raspberry_Pi_4-Ham_RADIO@... Subject: Re: [Raspberry_Pi_4-Ham_RADIO] TNC-PI Help please
Ryan,
|
|
Re: TNC-PI Help please
Ryan Stapleton
Hello Ray,
toggle quoted messageShow quoted text
They are all TABs between the fields in the axports. I will change them to spaces tonight after work and see what happens. Thanks -Ryan
On Apr 8, 2014, at 3:58 AM, Ray Wells <vk2tv@...> wrote:
|
|
Re: New RPi Form factor
Ronny Julian <k4rjjradio@...>
Sounds good! I thought you might. This smaller factor would be a neat "Blade" to build around later. Ronny K4RJJ
On Tue, Apr 8, 2014 at 3:56 AM, John Wiseman <john.wiseman@...> wrote:
|
|
Re: TNC-PI Help please
Ray Wells
Ryan, There appears to be no space between the callsign and the port speed in axports. Is that the case? A space is definitely needed. Ray vk2tv
On 06/04/14 21:05, ryan@... wrote:
|
|
Re: New RPi Form factor
John G8BPQ
Ronny, I have a couple of prototype 9600 versions of the TNC-PI running. Watch this space! The same board can also be configured as a D*Star Modem. 73, John G8BPQ
From:
Raspberry_Pi_4-Ham_RADIO@...
[mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of Ronny Julian
I can see the computer snapping onto the next TNC-Pi now! 9600 bps also? Just tossing it out there.
Ronny K4RJJ
|
|
New RPi Form factor
Ronny Julian <k4rjjradio@...>
I can see the computer snapping onto the next TNC-Pi now! 9600 bps also? Just tossing it out there. Ronny K4RJJ
|
|
TNC-PI Help please
Ryan Stapleton
Hello All,
I appreciate you all taking the time to read and respond. I have recently put together 2 TNC-PI's. These are my first real attempt at putting together a kit. (My last one was over 10 yrs ago and only a little LED Christmas Tree) I finally hooked up a radio yesterday but don't have any joy. I am going to list what I have done here. I also only have a multi-meter for test equipment. I picked up an OLD Yaesu CAT-2500 yesterday at a local hamfest. The radio works and I am able to transmit and receive on it no problem. I wired up what I believe are the connectors from the 4 pins on the TNC PI. (1,3,5,6) to the radio. When I key up the radio I do hear a tone on another radio I have with both TNC-Pi's. TNC-PI 1: When I send a packet on one of my other setups (TH-72A or PK-88/Radio combo) I see the yellow light come on. I tried: sudo minicom -b 19200 -o -D /dev/ttyAMA0 and got some squiggles but no one ones appeared at all when packets came in. Minicom also showed offline. TNC-PI 2: The yellow light does not always come on when a packet happens. I tried: sudo minicom -b 19200 -o -D /dev/ttyAMA0 I didn't see any data. minicom also showed off line. All Cases: I do the kiss attach /dev/ttyAMA0 1 10.1.1.1 and it says "AX.25 port 1 bound to device ax0" sudo axlisten -a : nothing comes across. axcall 1 KA3WUT-4 : No red light, no keying up. Config Files: /boot/cmdline.txt: dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait /etc/ax25/axports: # /etc/ax25/axports # # The format of this file is: # # name callsign speed paclen window description # 1 KA3WUT-1 19200 236 2 TNC 1 Notes: KA3WUT-4 is my PK-88 KA3WUT-7 is my TH72 Questions: I have seen where some folks are saying listen to pin 6 of a chip? What chip is that and how does one do that? If a normal headset I assume I need to have one 1 of the headset set to pin 6 (I assume 1 is top left of a chip?) Does anything else need to be connected to the headset and if so what? I can take photos of my boards front and back if that would be helpful? I am up for suggestions/ideas/help. Thank you -Ryan (KA3WUT Chantilly, VA)
|
|
Re: FW: TNC-Pi
Today I double checked and buzzed out the PCB all connections are showing OK. I had previously checked out the transmit by starting xastir and when "transmit now" was actioned the radio did indeed transmit however it did not sound like aprs to me but first I started on the RX. The radio has the ability to receive local FM broadcast stations so I tuned into one of them. APRS traffic in the area is rather sparse and the fm station gave me the ability to obtain a steady input and to confirm that the receive cable was correct. With the PI / TNC powered off, I was able to detect the audio on most of the points that the circuit diagram suggested. This included pins on the Op amp, PIC various resistors and capacitors eg C8. I also got clear audio going into R3 but as suggested not able to pick it up on the downside. On the Modem chip the following was found Clear audio on Pin 6 No audio on Pin 5 Audio heard on Pin 13 but badly distorted. I powered up the Pi and started to look at the TX side. Pulse detected on Pin8 of PIC I then opened Xastir and started the TNC, it came up and I pressed the Transmit Now option. The Radio did transmit and it was heard by another radio. Checked APRS.fi and found that the nearest digi had picked it up and had passed it onto APRS.fi.
As I mentioned earlier, APRS is a tad sparse around here and the nearest digi beacons every 30 minutes and I have managed to receive and decode the output 3 times. It seems to be working although I am not sure about the distortion across the modem chip, and I still have not heard the 450Hz tone that is supposed to be there all the time.
As to the fix, might have been a dry joint somewhere, I had to re-sweat a couple of contacts to get a meter reading. I will leave it running for 24 Hrs and see what it looks like. This TNC plus the Pi are destined for remote deployment in SAR work so need to be sure, we do have backup systems but this is ideal in terms of storage and power options. You can probably see the APRS.fi data for yourself. The additional bonus of all this effort is that I am getting a lot of use with the Oscilloscope software.
Many thanks for all the advice and offers of assistance, it really is appreciated.
Tommy MM0KNE
From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of John Hansen
Sent: 04 April 2014 15:11 To: Raspberry_Pi_4-Ham_RADIO@... Subject: Re: FW: [Raspberry_Pi_4-Ham_RADIO] TNC-Pi
I'm not clear as to whether you are working on receive audio or transmit audio here. If it's receive audio, I suggested looking on pin 6 of the MCP6023 because after it runs through resistor R3, I find it is somewhat difficult to detect. On receive, you should see audio at pin 6 (if you don't, take a close look at the connecting cable from your radio and the connections in the area of U4 and focus on this until you find where the audio gets lost). If you do find audio there, take a look at the pattern of data coming out of pin 13 of the MX614. You should always see a data pattern there, but when packets are being received, you should see a noticeable change in this pattern. If you working on transmit audio, the first thing to check is whether bits are actually getting to the PIC from the Pi. Look for data pulses on pin 8 of the PIC when you are attempting to send data from the Pi. If you don't see anything there, the problem is either with the Pi configuration or with the data path from the Pi to the TNC (make sure the jumpers are both on!). If you do see data there, then check the Red LED to make sure it lights up when transmitting. If you see data on pin 8, but don't get a a red LED, then contact me and I'll send you a replacement PIC (though there is possibility of a bad modem chip as well... this is unlikely if receive is working). John W2FS
On Fri, Apr 4, 2014 at 4:25 AM, John Wiseman <john.wiseman@...> wrote:
Tommy,
If you like I’ll take a look at it. I’m going to be away for most of April but could check it out when I get back.
73, John G8BPQ
From: Raspberry_Pi_4-Ham_RADIO@... [mailto:Raspberry_Pi_4-Ham_RADIO@...] On Behalf Of coolcamper55@...
Further update, have buzzed out all connections from Modem IC and PIC IC plus most of the board and all shown fine. I tried again with the Visual ANalyser software and have come to the conclusion that all I am getting from the probe points is mains hum. I get a very low throbbing but definitely not a clear audible tone.
Seriously running out of ideas, maybe time to dust off the tiny Track4 Tommy MM0KNE
|
|