On my very expensive scoop (hi) you see a packet frame @ 1200 Baud received from a station about 50 kilometers away. Looks fine to me.
After updating the Firmware from version V2.35 to V2.81 I see a good increase in the decoded frames.
How to update the Firmware
chmod +x tarpnflashinstaller.sh
* My Ninotnc is connected to ttyACM0.
tarpnflash version ttyACM0
* Is there a newer version available in the dir "ninotnc" you can run.
tarpnflash flash ttyACM0 (version number)
* Now the Firmware is being updated.
* Check if the flash of the firmware went well.
tarpflash version ttyACM0
* Great now running Version v2.81
/dev/ttyACM0 NinoTNC v2.81
I immediately built my second NinoTNC. I am very curious how that works with IL2P mode, Improved Layer 2 Protocol. In the picture below, the two NinoTnc`s are running at 2400 Baud with IL2P mode. Functions perfectly. Now I have some problems with adjusting to 4800 and 9600 Baud. I have to look into this.
Boy, I can hit my head against the wall. I made a very rookie mistake. I had soldered a number of Leds the wrong way round. Tsss before I finally invented that. Very stupid. But when I finally found out (it’s even in the description on the tarpn website) it now works the way it should.
Let’s test how the reception is. (aprs on 144.800Mhz @ 1200 Baud)
I feel like he is a little deaf. Looks like he’s missing some frames. Maybe it’s the setup I’m using. I am using a Yaesu ft7800 with the NinoTnc directly on the Mini Din of the radio. I have to figure this out, I will read the Tarpn website one more time.
Today I have been playing around with a KPC3 Non +. I bought this KPC3 in America and the upgrade Firmware in England. So you can imagine that it was not cheap.
So now we are going to insert the new Firmware.
I am very happy that it works perfectly. Now I want to do a comparison test with direwolf. Both with the 6.0 Firmware version and the 8.2 Firmware version. First, let’s find some time to get involved (again) with the hobby
I ordered two, I am very curious. Just wait for the B.O.M (Bill Of Materials)file and then I can order the components.
PRE ORDER LISTING–PLEASE READ: This is a revision of the N9600A that eliminates the need for a USB-serial daughter board, which is now in short supply in the US. This PCB, N9600A3, provides pads to use an MCP2221A-I/P USB bridge on-board, along with a USB-B connector. I expect to have stock ready to ship in May 2020, but that date may extend due to current global events interrupting supply chains.
This kit contains the printed circuit board and programmed dsPIC CPU required to build one TARPN N9600A3 packet radio terminal node controller (TNC). This kit does not include any other parts from the bill of materials, you will have to obtain more parts from a supplier to build a complete working TNC. Basic electronics tools and skills will be required to assemble a working TNC. You’ll need to be competent with a soldering iron, and have a supply of small-gauge solder. Side cutters will be necessary, as well as tweezers or needle-nose pliers.
The PCB is a high-quality 4-layer board with blue finish and white silkscreen for part locations and identifiers. It requires only thru-hole parts for assembly.
Once assembled, the N9600A3 TNC acts as a multi-mode data modem you can use to create narrow-band datalinks with VHF and UHF communication radios. The N9600A3 TNC sends and receives data using several user-selectable modulation methods and link protocols: traditional AX.25 modes at 1200 bps AFSK (like APRS) and 9600 bps using GMSK (compatible with the G3RUH standard).
N9600A3 differs from previous revision with the incorporation of an on-board USB bridge and USB-B connector, as well as 2 more DIP switch options that will enable several future firmware features that are under development now. All these future firmware upgrades will be supported in N9600A2 as well, through KISS options (N9600A2 does not have as many switches).
The TNC also supports an experimental layer 2 protocol called IL2P which incorporates several improvements, including Forward Error Correction. IL2P can be used as an alternative to AX.25 on both 1200 AFSK and 9600 GMSK modes. You can read more about IL2P here:
9600 bps GMSK will not work with all voice-band radios. It requires a radio with a data port (direct modulator/discriminator connection) or other wide-bandwidth connection. It should be possible to use 1200 bps AFSK mode with most voice-band radios, once you have obtained (or made) suitable connection cables.
You can find more information about this TNC, build instructions, bill of materials, configuration tips, and a community of users at the following links:
Some disclaimers: We are selling this kit at very close to our cost, in the hopes of growing the Terrestrial Amateur Radio Packet Network (TARPN) and the entire packet radio community. You must assemble and use this device at your own risk. Operation of any radio device on the Amateur Radio bands requires applicable licensing by the government of the country where the device is used. If you damage the PCB or CPU beyond repair during assembly or use, you’ll need to pony up another $7.57 plus shipping to order a replacement. We do not guarantee suitability for use for commercial purposes. Do not use this device as part of a life-saving system.
I hope that you enjoy assembling and using this device, and grow a packet radio network where you live!
144.800Mhz @ 1200Baud (Test on 03-29-20 11:00 (rx only))
Today I did a reception test with the AEA PK88 and Direwolf.I must say that I am impressed with the PK88.This is the best test I have done so far.Now the conditions were not optimal, there is very little traffic at the time.So I will probably test it again at a busier time.Even now I let the reception run for half an hour.
So we missed 19 packets out of a total of 211 packtes from Direwolf.This compared to the tnc3s that missed 73 out of 219 packets from Direwolf. Below again the TNC3s comparison with Direwolf.
It is nice to see that this AEA PK-88 performs so well after all these years and different owners.
The last week I save all the Aprs traffic I receive and post it on a blog.You might like to take a look there.https://pd9q.blogspot.com
I received a nice email from Tadd KA2DEW, there is a lot of development in the NinoTNC.Read the great news below.
We fixed the FTDI USB problem with the NinoTNC board by putting a USB-B socket on the PCB and a Microchip USB IC. This actually cut the parts cost by a few $. We’ll have the boards for sale on ETSY in April. Go to Etsy.com and search for TARPN. If the search doesn’t come up, then it isn’t listed yet. Our plan is to take orders in advance of shipping, and prime the pump with 200 boards ordering in early April with 3 weeks to get the boards into stock. At a time closer to ship time we’ll order programmed PIC CPUs with the latest firmware. When we get down to 50 or so in stock, we’ll order more. Because we’re running on out-of-pocket funding for the boards and CPUs, there may be some out-of-stock issues, but the price is right so hopefully people will smile and deal with it.
The new board is called the N9600A3. The last version was the A2, a black PCB with a 2-bit dip switch and the FTDI module on headers. The new board is the A3 blue PCB with USB B connector and a 4 bit dip switch. The new switches will be used to select more bit-rates. We’re not ready with anything new yet, but hopefully by the time the board ships? We’re likely to have 1200, 2400, 4800 and 9600 for FM and maybe some support for HF via SSB. Just like the A2 board, this one will come with IL2P Forward Error Correction mode which is a very efficient packet encoding providing Forward Error Correct in the same length packet as an AX.25 packet. (Full disclosure, as I understand it, packets with > 64 payload bytes will grow larger than AX.25 but small payloads result in shorter than AX.25 packets).
The NinoTNC A3 will come with a over-the-USB bootloader to update the firmware over USB, and we’ll be shipping a free Raspberry PI Raspbian application to boatload the TNC from a hex file. The hex file will be shipped for free one way or another. TARPN node ops will just do an UPDATEAPPS command on the TARPN scripts.
There is much software support to write for this which is not yet done. Our crack firmware and software teams are busy busy busy. Even though we’re not going to be ready with updated software in time we wanted to rush the A3 out there to solve the availability problem with the FTDIs. In addition we discovered that the tolerances for the Micro USB plugs and sockets are so bad that many people are breaking the FTDI modules plugging and unplugging. That’s not good. It’s easy to work-around but ugly. The A3’s USB-B connector is a much better deal.
Like before, we won’t be taking profit from this, and we’ll be selling the PCB + CPU for well under $10 on ETSY. Search on ETSY for TARPN. If it isn’t coming up, then we’re not ready to take pre-orders yet. It should be ready in early April. The news and info page will be updated when we get the store back up and when we have a clue about shipping this. We’ll also be posting a new A3 assembly link with access to the new bill of materials.
144.800Mhz @ 1200Baud (Two tests one on 03-23 and one on 03-24 (rx only))
The first test I did was of course not entirely fair, different antennas were used and different transmitters/receivers. Now I made a setup with the same antenna and the same receiver, so with the same audio input. First the setup, as a computer(if I haven’t lost it.some where) I use a Raspberry PI 2B+, as a sound card I use an Fe-Pi Audio Z V2. As a receiver I use a Realistic pro 2006. It is an old receiver but still works 100%. The antenna is a x50 from Diamond. Of course the Tnc3s from Symek, and Direwolf from John WB2OSZ. I use Kissutil from WB2OSZ, this allows me to connect to Direwolf and the Tnc3s as well as save the received Frames. This makes comparing easy/easier.
Now I have made two start files, one for Direwolf and one for the Tnc3s. I start these in different terminals. I do this manually, so there is a slight delay in starting up.
# Start kissutil on Direwolf kiss port 8001
# Let it run for 30 minutes and kill the process
# Start options "timeout -s 9 1800 ./direwolf.sh"
# Kissutil for Direwolf save to /home/aprs/rec-direwolf
/usr/local/bin/kissutil-direwolf -o /home/aprs/rec-direwolf
# Start kissutil on the /dev/ttyUSB0 for the Symek Tnc3s
# Let it run for 30 minutes and kill the process
# Start options "timeout -s 9 1800 ./tnc3s.sh"
# Kissutil for the Tnc3s save to /home/aprs/rc-tnc3s
/usr/local/bin/kissutil-tnc3s -p /dev/ttyUSB0 -s 38400 -o /home/aprs/rec-tnc3s
I start the scripts with the option “timeout” now I can specify the time how long the script runs. Example. “timeout -s 9 1800 ./tnc3s.sh” In this comparison, both scripts run for 30 minutes. 1800 Second. Now it is time for the comparison.
With the command “ls -A | wc -l” the number of files in the directory are counted. (Frames received.)
Here you can see the difference between the received frames of the Tnc3s and Direwolf. There is a difference of 73 and 125 missed frames from the Tnc3s. I tried something with the reception levels of the Tnc3s. It is To soft – Ok – To hard, there is little difference between To soft and Ok and To hard.
I did some tests with the amount of calls received. Just for fun.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.