Date   

2400 baud with Yeasu/Vertex FTL-1011

 

The Yeasu/Vertex FTL-1011 vhf-lo (6m) (and probably the 2011, 7011 radios for 2m, 70cm) seem to work with 2400 baud.  They aren’t quite as noise immune on 2400 as on 1200 but the 6m version is really cheap!   https://www.ebay.com/itm/Vertex-FTL-1011-VHF-FM-Transceiver-FREE-SHIPPING/282346444832.  They do 35watts @51mhz and easily tune to the 1.5mhz of the 6m band.  Some of them work higher in 6m band.  


   Tadd — KA2DEW





On Jun 23, 2020, at 7:26 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

The TNC-Pi9k6 has a voltage range that is software select able from 24mv to 3000mv (3 volts).  This range works with most radios, but I've personally only tried a small set.

There is also a 2400 baud mode, but I have yet to find a radio that will work with it.  It's nice to have all those speeds, but then finding a radio that it can work with is another matter entirely.

I have a couple NinoTNC boards (ver2) that I need to start more earnest testing.  Too many other spring time things are in the way, planting the garden, keeping up on the grass cutting, smoking meat, eating it, etc etc etc.  Oh, and naps.  Naps are important.  *Sign*, retirement is such a tough life.

Mark
KD0QYN


On Tuesday, June 23, 2020, 6:07:13 PM CDT, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:


Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.




Re: TV HDMI #pi

Chuck M
 

If my senioritis isn't acting up, remember making the changes in the config file re HDMI setup.  Will check again and also check the other item mentioned re TV setup.  Tried several different cables, TVs, and monitors before buying the booster.

having no problems with my Pi 4B or an older Pi 2 that controls my 3D printer.  Just the Pi 3B.

Chuck
KD9DVB


On Tuesday, June 23, 2020, 6:33:24 PM EDT, N5XMT <dacooley@...> wrote:


Shouldn't need it.  You can boost the HDMI signal out with a single command in the /boot/config.txt file

On Tue, Jun 23, 2020 at 1:34 PM Chuck M via groups.io <cam51mail=yahoo.com@groups.io> wrote:
Had a similar problem with a Pi 3B.  Ended up buying one of these to boost its signal.  Works okay with this.


Bit of a pain for portable use as it's another device to tote, plus extra HDMI cable, etc.  Does fine at home.

GL
Chuck
KD9DVB


On Tuesday, June 23, 2020, 2:33:57 PM EDT, w9ran <w9ran@...> wrote:


Hopefully this isn't your issue, but I recently found one of my Pi 3Bs
would no longer display hdmi output even though it has for months.   A
different Pi worked fine on the same monitor and cable.   Since ssh was
enabled I was able to communicate with it and tried all the stuff you
find in the FAQs, knowing it wasn't just a config.txt setting because
there was no video at startup which comes from the bootloader not from
Linux.   Google searching confirmed that random hdmi hardware failure on
the Pi is not unheard of.   Since the composite video works and the
published documentation doesn't show anything beyond the hdmi connector
I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN





Re: TNCPi WITH YAESU FT 7900R

Mark Griffith
 

The TNC-Pi9k6 has a voltage range that is software select able from 24mv to 3000mv (3 volts).  This range works with most radios, but I've personally only tried a small set.

There is also a 2400 baud mode, but I have yet to find a radio that will work with it.  It's nice to have all those speeds, but then finding a radio that it can work with is another matter entirely.

I have a couple NinoTNC boards (ver2) that I need to start more earnest testing.  Too many other spring time things are in the way, planting the garden, keeping up on the grass cutting, smoking meat, eating it, etc etc etc.  Oh, and naps.  Naps are important.  *Sign*, retirement is such a tough life.

Mark
KD0QYN


On Tuesday, June 23, 2020, 6:07:13 PM CDT, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:


Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.



Re: TNCPi WITH YAESU FT 7900R

Mark Griffith
 

Al,

I use a FT-7900 with my TNC-Pi9k6.  You need to use the 6 pin mini-DIN connector and not the DB-9.  That way, you don't need to change anything when switching between 1200 and 9600 baud except the settings on the TNC and on the radio.  No switching jumpers or cables.

The pin-out you mention on the PiGate site is just for radios that don't have the built-in packet port.  You *could* set it up through the mic and headset ports, but then you are limited to 1200 baud only.

Please let me know if you have any more questions.

Mark
KD0QYN


On Tuesday, June 23, 2020, 12:13:35 PM CDT, Al Massaro <almassaro1@...> wrote:


OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.


Re: TNCPi WITH YAESU FT 7900R

 

Another issue which may be important is some radios require more audio voltage/level going into the data port.  The NinoTNC has two selectable output ranges, high, for data radios, and low, for microphone audio, for this very reason.  NinoTNC has 1200, 2400, 4800, 9600 baud DSP modems built in so it needs to support a wide range of radios.  
   Tadd - KA2DEW

On Jun 23, 2020, at 6:29 PM, Ray Wells <vk2tv@...> wrote:

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.



Re: Tnc-x PI

Mark Griffith
 

Don,

If your RED LED power light is flashing, your power supply is very weak.  It needs to be steady on all the time.  If adding an external USB device like a TNC-X causes it to start flashing, then again, the power supply is too weak.

Mark
KD0QYN


On Tuesday, June 23, 2020, 5:21:32 PM CDT, Don Poaps <va7dgp@...> wrote:


Tad 

that's one of the first syntaxes I used. The yellow light is flashing on the Pi Hat. All of the lights blink when power is applied.

Putting it to bed for a while. If I plugged my USB tnc-x I get it to start in not type.

later

Don va7dgp/va7qu

On Tue., Jun. 23, 2020, 1:00 p.m. Tadd KA2DEW in NC via groups.io <tadd=mac.com@groups.io> wrote:
Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Re: TV HDMI #pi

N5XMT
 

Shouldn't need it.  You can boost the HDMI signal out with a single command in the /boot/config.txt file


On Tue, Jun 23, 2020 at 1:34 PM Chuck M via groups.io <cam51mail=yahoo.com@groups.io> wrote:
Had a similar problem with a Pi 3B.  Ended up buying one of these to boost its signal.  Works okay with this.


Bit of a pain for portable use as it's another device to tote, plus extra HDMI cable, etc.  Does fine at home.

GL
Chuck
KD9DVB


On Tuesday, June 23, 2020, 2:33:57 PM EDT, w9ran <w9ran@...> wrote:


Hopefully this isn't your issue, but I recently found one of my Pi 3Bs
would no longer display hdmi output even though it has for months.   A
different Pi worked fine on the same monitor and cable.   Since ssh was
enabled I was able to communicate with it and tried all the stuff you
find in the FAQs, knowing it wasn't just a config.txt setting because
there was no video at startup which comes from the bootloader not from
Linux.   Google searching confirmed that random hdmi hardware failure on
the Pi is not unheard of.   Since the composite video works and the
published documentation doesn't show anything beyond the hdmi connector
I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN





Re: TNCPi WITH YAESU FT 7900R

Ray Wells
 

That's not quite correct. For receive, the difference between the 1200 and 9600 ports on the rear socket is that the former has de-emphasised audio while the latter has "flat" audio from the discriminator. There are reasons why using the discriminator output for 1200 packet is often superior for many hardware TNC/modems that aren't smart enough to compensate for relative tone levels (1200/2200Hz) when they are wrong. Soundcard style modems like Direwolf are far more capable and less particular in this regard. If you want to know why the correct audio is important, take a look at this site with pictures and a very simple explanation.   https://www.febo.com/packet/layer-one/transmit.html

I know I flog that site and will continue to do so because if everybody using packet read that article and implemented correct audio practices there would be a lot more stations having much greater reliability with packet radio/APRS communications. If I sound like a grumpy old man, I am. I've been involved with packet since about 1985 and the biggest single factor for people's
woes and failures with the mode remains wrong audio setup.

For transmit when using the rear socket, the radio will probably select the right option depending on whether you choose 1200 or 9600 for the speed in the radio setup, like my Kenwood TM-V71A does.

Ray vk2tv

On 24/6/20 3:17 am, Jim Lange wrote:
You need to use the 1200 port on the radio. The other is for high speed packet and won’t work with a TNC that isn’t made for it. Otherwise all is good. 

Sent by me


On Jun 23, 2020, at 13:13, Al Massaro <almassaro1@...> wrote:

OK I am thinking of trying a TNCPi with a ft 7900r, the pigate site shows the pinout for a FT 2800/2900 using the mic port. My question is my 7900 has a rear data port why can't I use it? Her is a comparison of the 28/2900 mic pinout and my plan for my 7900. Do I need to figure out and use the pinout for the 7900 (MH48A6J) MIC PORT instead? Below left mic pinout from website, Below right my plan for 7900.


Re: TV HDMI #pi

N5XMT
 

Try uncommenting the the following.  Try the first one and see if that works, if not uncomment the 2nd one as well.



# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

On Tue, Jun 23, 2020 at 9:54 AM Rob <n3ljs@...> wrote:
Running the pi with a 20 inch vizio tv out in the shop all is good. Decided to use a 32 inch vizio tv. No signal on the 32 in. When the 20 inch is on I unplug the hdmi cable Then plug into the 32 inch it works.....I did a reboot... then no display on the 32 inch......TNX

Newbie

ROB N3LJS


Re: Tnc-x PI

Don Poaps
 

Sorry, my big screen TV died. Trying to read this with bad eyes and a very small screen https://tnc-x.com/TNCPi.pdf this is what I'm going by. So far have seen any notes.
73
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Tue, Jun 23, 2020 at 1:47 PM Tim via groups.io <the_fro_god=yahoo.com@groups.io> wrote:
Did you try the Note added 12/4/2018 stuff?


Re: Tnc-x PI

Don Poaps
 

Tad 

that's one of the first syntaxes I used. The yellow light is flashing on the Pi Hat. All of the lights blink when power is applied.

Putting it to bed for a while. If I plugged my USB tnc-x I get it to start in not type.

later

Don va7dgp/va7qu


On Tue., Jun. 23, 2020, 1:00 p.m. Tadd KA2DEW in NC via groups.io <tadd=mac.com@groups.io> wrote:
Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Re: Tnc-x PI

nfg
 

Did you try the Note added 12/4/2018 stuff?


Re: TV HDMI #pi

Chuck M
 

Had a similar problem with a Pi 3B.  Ended up buying one of these to boost its signal.  Works okay with this.


Bit of a pain for portable use as it's another device to tote, plus extra HDMI cable, etc.  Does fine at home.

GL
Chuck
KD9DVB


On Tuesday, June 23, 2020, 2:33:57 PM EDT, w9ran <w9ran@...> wrote:


Hopefully this isn't your issue, but I recently found one of my Pi 3Bs
would no longer display hdmi output even though it has for months.   A
different Pi worked fine on the same monitor and cable.   Since ssh was
enabled I was able to communicate with it and tried all the stuff you
find in the FAQs, knowing it wasn't just a config.txt setting because
there was no video at startup which comes from the bootloader not from
Linux.   Google searching confirmed that random hdmi hardware failure on
the Pi is not unheard of.   Since the composite video works and the
published documentation doesn't show anything beyond the hdmi connector
I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN





Re: Tnc-x PI

Siegfried Jackstien
 

hmm could we get such a thingy run on a pluto??

yes i know not a raspi but it is a linux box (kind of) ... and a wideband transceiver

here in germany a few guys planning to make the pluto a user access point for hamnet ... THAT could be really a nice idea for replacing the packet net (or the rest of that we still have) all to hamnet ...

dg9bfc sigi

Am 23.06.2020 um 19:59 schrieb Tadd KA2DEW in NC via groups.io:

Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Re: Tnc-x PI

 

Try doing sudo before the command.   


On Jun 23, 2020, at 3:58 PM, Don Poaps <va7dgp@...> wrote:

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don




Tnc-x PI

Don Poaps
 

I've been reading the setup from tncpi pdf from off the tnc-x website.

I've downloaded the zipped files,  there are now in the folder pitnc.
Both files permission are for Owner 

I keep getting retrying.

If I do ls /dev/serial*
It shows /dev/serial0 and /dev/serial1



So sort of lost as to where to go next

73 

Don



Re: TNCPi WITH YAESU FT 7900R

Al Massaro
 

Ed, ok good to go, I just got back to this to work on the pinout for them and found your post, it is now on order.
Thanks
AL M
KF5SMh


Re: TNCPi WITH YAESU FT 7900R

Ed Bloom, KD9FRQ
 

Al,

Get the 6 Pin Min Din 1200 Baud to DB9 Kantronic Type cable from HamMadeParts.

Ed, KD9FRQ

On 6/23/2020 1:01 PM, Al Massaro wrote:
Thanks Ed, now to figure out if it is the Kantronics or 9800 style they have listed, nothing specific stated for 7900.
AL M
KF5SMH



Re: TV HDMI #pi

w9ran <w9ran@...>
 

Hopefully this isn't your issue, but I recently found one of my Pi 3Bs would no longer display hdmi output even though it has for months.   A different Pi worked fine on the same monitor and cable.   Since ssh was enabled I was able to communicate with it and tried all the stuff you find in the FAQs, knowing it wasn't just a config.txt setting because there was no video at startup which comes from the bootloader not from Linux.   Google searching confirmed that random hdmi hardware failure on the Pi is not unheard of.   Since the composite video works and the published documentation doesn't show anything beyond the hdmi connector I'm not optimistic about being able to fix it, but am open to suggestions.

73, Bob W9RAN


Re: HamPi 1.0 Released!

Bob
 

Dave, the Soapy/SDRPlay drivers worked with RSP2-GQRX for you?  I couldn’t get it to work; perhaps I missed something.

73 Bob
K4RCG

On Tue, Jun 23, 2020 at 09:51 Dave Slotter, W3DJS <slotter@...> wrote:
On Sun, Jun 21, 2020 at 05:13 AM, Ranjith Unnikrishnan wrote:
Thanks Dave
Downloaded It.
Now wanting to run it as a WSPR node, with SDR Play RSP1 .

Will it be plug and play  ?

Will i need any API to be installed for SDR Play ?

Also any pointers as to how to route the audio from SDRPlay to WSJT X for input to run the WPSR Node

You're welcome.

There are two ways to run WSPR on the HamPi image "out of the box". One is to run the "wspr-pi" application in /usr/local/bin . The second is to run WSJT-X.

The SDRPlay is receive-only. You can not use it to send WSPR.

The SoapySDRPlay drivers have been installed on HamPi. This allows you to use the SDRPlay with GQRX and CubicSDR, for example.
 
--
- Dave
  W3DJS

1501 - 1520 of 13014