Date   

Re: TNC PI 9k6 RX problem at 9600

César Regalado León <ea8cxn@...>
 

I autoreplay, I test with wireshark and I can see all the traffic at 1200.

At 9600 I can see the outgoing traffic but not the ingoing traffic, so by the moment I think I can not do anything else to find where is the problem


Best Regards


Re: TNC PI 9k6 RX problem at 9600

César Regalado León <ea8cxn@...>
 

Hello !

I'm continnue testing my TNC-PI 9k6!

Today I made and experiment. I reset the TNC and then I get the following values:

pi@raspberrypi:~ $ sudo ./pitnc_setparams /dev/serial0 0 15 2
pitnc_setparams Version 0.0.0.5
pi@raspberrypi:~ $ sudo ./pitnc_getparams /dev/serial0 0
pitnc_getparams Version 0.0.0.5

Using Serial port /dev/serial0
retrying...

   TNC Software Version           8
01 TXDelay - Zero means use ADC  40
02 Persistance                   63
03 Slottime (in 10 mS)           20
04 TXTail                        30
05 Full Duplex - Not used         0
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  9600
09 RX Level (Config)              0
10 TX Level                      96
11 RX Level (Actual)              0
13 Centre Freq                 2550
8 8 28 3f 14 1e 0 ff ff 60 0 60 0 ff e2 c0 sum 0

Pay attention to the Item 11, wich is 0 because I just resset it!.

After that, I turn on Xastir and start listening. I transmit a beacon and the beacon is received perfectly in my FT1D HT, and then I transmit a beacon from the FT1D HT and check if there is any change. I get the following results:

pi@raspberrypi:~ $ sudo ./pitnc_getparams /dev/serial0 0
pitnc_getparams Version 0.0.0.5

Using Serial port /dev/serial0
retrying...

   TNC Software Version           8
01 TXDelay - Zero means use ADC  40
02 Persistance                   63
03 Slottime (in 10 mS)           20
04 TXTail                        30
05 Full Duplex - Not used         0
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  9600
09 RX Level (Config)              0
10 TX Level                      96
11 RX Level (Actual)             98
13 Centre Freq                 2550
8 8 28 3f 14 1e 0 ff ff 60 0 60 62 ff 80 c0 sum 0

So its mean that the TNC is received something and automatically adjusted the RX Level. 

Anybody knowns  any command or software under linux to continous listening the TNC? Like a sniffer?

 

Thank you !

 


Re: apt-get install libncursesw5-dev not found

Mark J Culross
 

Bernard (F6BVP):

If you're adventurous & there's not something else keeping you from updating, you could get yours fully updated in place with the following commands:

   sudo apt-get update && sudo apt-get -y dist-upgrade [ENTER]

Good luck & have fun !!

Mark J Culross
KD5RXT


On Wed, Aug 29, 2018 at 5:54 AM, f6bvp
<f6bvp@...> wrote:
Hi All,

In tried to install new ve7fet/linuxax25] ax25apps-2.0.0 on raspbian.
Lee VE7FET wrote on https://github.com/ve7fet/linuxax25/releases/tag/ax25apps-2.0.0

------
This release patches our source with nearly all the changes in the upstream official source from 2015-2017, inclusive.

NOTE: As of this version, ncursesw libraries (ie libncursesw5-dev) are required to compile the call binary. This is due to the addition of UTF-8 support.

Also, a reminder, this version of ax25ipd is NOT the same as the upstream official source. This version supports dynamic hosts/DNS and the ability to route packets over axip links that are not from the gateway callsign. That said, we've incorporated all the upstream patches from the official source, where possible.

With all the significant changes, we'll release this as version 2.0.0, as it may break compatibility with previous versions.
-----------------
My distro is two years old and not the last stretch raspbian (wheezy probably ???).
Does anyone know if package libncursesw5-dev is available for stretch raspbian distro ?

Bernard, f6bvp



Re: apt-get install libncursesw5-dev not found

Ross Bennett <therossbennett@...>
 

Bernard wrote:
My distro is two years old and not the last stretch raspbian (wheezy probably ???).Does anyone know if package libncursesw5-dev is available for stretch raspbian distro ?
Yes it is! I've just looked it up in the aptitude package manager.

Raspbian stretch release 9.4 this morning offers libncursesw5dev-dev version 6.0+20161126-1

Good luck!

Ross


apt-get install libncursesw5-dev not found

Bernard f6bvp / ai7bg
 

Hi All,

In tried to install new ve7fet/linuxax25] ax25apps-2.0.0 on raspbian.
Lee VE7FET wrote on https://github.com/ve7fet/linuxax25/releases/tag/ax25apps-2.0.0

------
This release patches our source with nearly all the changes in the upstream official source from 2015-2017, inclusive.

NOTE: As of this version, ncursesw libraries (ie libncursesw5-dev) are required to compile the call binary. This is due to the addition of UTF-8 support.

Also, a reminder, this version of ax25ipd is NOT the same as the upstream official source. This version supports dynamic hosts/DNS and the ability to route packets over axip links that are not from the gateway callsign. That said, we've incorporated all the upstream patches from the official source, where possible.

With all the significant changes, we'll release this as version 2.0.0, as it may break compatibility with previous versions.
-----------------
My distro is two years old and not the last stretch raspbian (wheezy probably ???).
Does anyone know if package libncursesw5-dev is available for stretch raspbian distro ?

Bernard, f6bvp



Re: TNC PI 9k6 RX problem at 9600

Bill P.
 

When using raspi-config for the Pi-3 / Pi-3b+ a message responds that these models cannot be overclocked. Going into /boot/config.txt for a Pi-1 or 2 the line for overclocking is uncommented but when going into the same line for the Pi-3 the line has the speed commented out allowing the model 3 to run at its native speed.

Yes extra cooling is needed, there are $5 cooling fan and copper heat sink kits on ebay, I bought 2 of each style and installed them and also put risers under the Pi case to allow air to circulate around the bottom. I use Pi-3b+ for astro cameras which are running all night and others for WSJT-X. I am not sure how true it is but somewhere it is said the Pi will slow if it gets too hot.
Bill k6acj.


Re: RPi Cases

Larry Macionski
 

Can they hold the raspberry pi with a shield / daughter board?
I bought a Bud plastic box that holds a RPi and my TNC-pi Packet shield. Had them for 2-3 years. Red plastic.

I still would prefer a metal enclosure. They abound on the internet but none that I have seen are "double Depth" that would allow a "second story"

I did last year buy a  dozen or so of these pencil boxes, which I use. See the picture.  I have a Brother QL-700 label maker on my PC that is invaluable for jogging the memory.
I also use the "plastic shoe boxes" labeled the same.. Then there is my inventory spreadsheet... So when I need to find a 1K ohm resistor or 2N2222,  I search the spread sheet first...

My spread sheet lists the item, quantity, the box it is in  (Pencil Box X, Shoe Box X, Beer case X) and the location of the box. (Attic, hall closet, workshop)   I also have these plastic AMMO boxes -because of weight.. Mostly for AMMO though but I have 1-2 with wall warts and transformers.

So either I'm OCD or anal... but my kids will be able to provide an inventory of each box they sell at my  Estate sale for 25 cents a box..

Laugh if you want but I no longer spend hours looking for that 2N3904 that's somewhere in a box. I saw it last month.

My spread sheet is over 1800 lines long. Can you remember where 1800 items are in your house?


Re: TNC PI 9k6 RX problem at 9600

Max
 

The speed of a 3B should be 1200 and a 3B+ should be 1400. Unless someone is trying to reduce the power requirement there is no point in slowing down the CPU.

On Monday, August 27, 2018, 11:08:28 PM CDT, Simon Rosenberg via Groups.Io <SimonR4@...> wrote:
.
I beleive I saw someplace that you have to overclock the  Raspberry Pi 3B from 700 to 900 and be sure that you add two heat sinks to the small and larger computer chips on the board. Avoid a closed case or provide for a fan to cool the Pi
73
Simon

KD2DOE


Re: TNC PI 9k6 RX problem at 9600

Simon Rosenberg
 

I beleive I saw someplace that you have to overclock the  Raspberry Pi 3B from 700 to 900 and be sure that you add two heat sinks to the small and larger computer chips on the board. Avoid a closed case or provide for a fan to cool the Pi
73
Simon
KD2DOE


Re: RPi Cases

Jim Higgins
 

It will be far easier to find them by their appearance as a small low priced plastic box than by looking at the product code, but the UPC is 91141 38200. "Item #38200 Super Stacker, Crayon Box." They're on the end cap at my local Super Walmart. Might be the same at yours.

Jim H



Received from Al Massaro at 8/27/2018 06:56 PM UTC:

Somebody have an item SKU? Our Back to School stuff is back on the shelf.
KF5SMH


Re: RPi Cases

Al Massaro KF5SMH
 

Somebody have an item SKU?  Our Back to School stuff is back on the shelf.
KF5SMH


Re: RPi Cases

 

Remember thermals.


On Mon, Aug 27, 2018 at 9:09 AM Jim Higgins <HigginsJ@...> wrote:

They stack really nicely with covers on and I just noticed that they stack
very nicely with covers off.

So you could easily cut most of the bottom out of one and stack it onto
another with hot melt or even use long screws in the corners to fasten them
together and have a case that would hold an RPi plus several add-on boards.

Jim H



Received from Roy Crosier at 8/27/2018 01:20 PM UTC:

>They are on clearance here in SE St. Louis Walmarts for $1, marked down from
>$2.49, but still a bargain. My nearest store still has hundreds of them.
>
>Roy
>AC9DN






--


John D. Hays
Edmonds, WA
K7VE

   


Re: RPi Cases

Jim Higgins
 

They stack really nicely with covers on and I just noticed that they stack very nicely with covers off.

So you could easily cut most of the bottom out of one and stack it onto another with hot melt or even use long screws in the corners to fasten them together and have a case that would hold an RPi plus several add-on boards.

Jim H



Received from Roy Crosier at 8/27/2018 01:20 PM UTC:

They are on clearance here in SE St. Louis Walmarts for $1, marked down from $2.49, but still a bargain. My nearest store still has hundreds of them.

Roy
AC9DN


Re: RPi Cases

Roy Crosier <valvetimer@...>
 

They are on clearance here in SE St. Louis Walmarts for $1, marked
down from $2.49, but still a bargain. My nearest store still has hundreds
of them.

Roy
AC9DN


RPi Cases

Jim Higgins
 

Walmart is selling back to school crayon cases, with latching lids, that are the perfect size to hold an RPi. Clear, orange, blue, yellow cases. The lids are all clear.

$0.55 each.

Jim H


Re: TNC PI 9k6 RX problem at 9600

César Regalado León <ea8cxn@...>
 

Thank you for the answer, I was very confussed trying to find the problem.

Also I try to change the values of the 9600Pkt gain from  the radio but no answer as well...

 

I have another yaesu radio, the FT991 but it is on the Sat at this moment, when they return to me the equipment I will test it and maybe the problem is only with the 8X7 yaesu radio.

 

Best regards!


Re: TNC PI 9k6 RX problem at 9600

John
 

Those values are ok.  The setting of 0 on receive merely means that the TNC itself will automatically determine the value.  That works quite well on 9600 generally.  The I2C value simply means it hasn't been set and so the default that the TNC uses (0) will be used.  So this is set up for serial operation.  

I think the problem may be with the radio.  We did not know this when we were getting this going but it seems that those Yaesu VHF/HF/UHF radios may not handle 9600 baud very well.  This is the third report I've had that someone was having issues with one of them.  It does not seem to be an issue with all Yaesu's, because for one person switching to an FT-1500 solved the problem and for another switching to an FT-8900 (if I am remembering correctly) took care of the problem.  Further experimentation might be required to determine whether there is a work around to get this radio working properly, but in the meantime I've changed the web page for this series of radios (FT-817, FT-857, FT-890) indicating that they don't seem to handle 9600 very well.

John Hansen W2FS
Coastal ChipWorks

On Sun, Aug 26, 2018 at 1:53 PM, Tadd KA2DEW in NC via Groups.Io <tadd@...> wrote:
what does the RX Level (Config) register need to be set to?   0 does’t look correct. 

09 RX Level (Config)              0
10 TX Level                      96
11 RX Level (Actual)              0
13 Centre Freq                 2550

07 I2C Address (0 = async) Hex   ff

The I2C address doesn’t appear to be rational either. 

is there an example of the registers from a working 9600 link? 
   Tadd


Tadd / KA2DEW
Raleigh NC  FM05pv

“Packet networking over ham radio": http://tarpn.net/t/packet_radio_networking.html

“Raleigh-centric ham radio resources page": http://torborg.com/a






Re: TNC PI 9k6 RX problem at 9600

 

what does the RX Level (Config) register need to be set to?   0 does’t look correct. 

09 RX Level (Config)              0
10 TX Level                      96
11 RX Level (Actual)              0
13 Centre Freq                 2550

07 I2C Address (0 = async) Hex   ff

The I2C address doesn’t appear to be rational either. 

is there an example of the registers from a working 9600 link? 
   Tadd


Tadd / KA2DEW
Raleigh NC  FM05pv

“Packet networking over ham radio": http://tarpn.net/t/packet_radio_networking.html

“Raleigh-centric ham radio resources page": http://torborg.com/a





TNC PI 9k6 RX problem at 9600

César Regalado León <ea8cxn@...>
 

Hello to everyone.

I'm very happy with my TNC-PI 9k6 at 1200bps, it is a real good TNC, very impressive of it performance.

I have experience a problem at 9600bps. My set up is :

- TNC-PI 9K6
- Raspberry Pi 3B

- Yaesu FT-857D.

When I set up at 9600, I can TX a beacon and received it on my Yaesu FT1D, perfectly decoded. I adjust the TX values to 98 wich looks like very well, but I can not receive anything.

With the ./pitnc_setparams I try plenty of values for the RX, but nothing happen, even if I put it to 0, no message is decoded.

This is my set up:

pitnc_setparams Version 0.0.0.5

   PIC Software Version           8
01 TXDelay - Zero means use ADC  40
02 Persistance                   63
03 Slottime (in 10 mS)           20
04 TXTail                        30
05 Full Duplex - Not used         0
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   ff
08 Mode Speed                  9600
09 RX Level (Config)              0
10 TX Level                      96
11 RX Level (Actual)              0
13 Centre Freq                 2550
8 8 28 3f 14 1e 0 ff ff 60 0 60 0 ff e2 c0 sum 0
Any one experience something similar? I repeat that the TX is perfect at 9600, and at 1200 all is working good, but my RX at 9600 is cero...

 

Best Regards!!


Re: I2C issue

 

Jon, 
  hmm… I2CDetect should work regardless of the radios being on. 
Also, you can fix the TNC-PI by sending a write to register 15 with a parameter of 2.   That will clear out any trash in the TNC-PI so you can read registers.   register 15, value 2 will cause the TNC-PI to reboot and you should be able to see the LEDs do their startup flash.  G8BPQ’s PILINBPQ program does that to the TNC-PI every time it starts, one at a time.

You might consider laying the TNC-PIs out side by side and running a 10 pin ribbon between them.  It’s a lot easier to see them and adjust them if the are side by side.  Only the first 10 pins of the 40-pin connector are actually used by the TNC-PI.  

Check out this web page:  http://tarpn.net/t/tncpi/tncpi.html


Tadd / KA2DEW
Raleigh NC  FM05pv

“Packet networking over ham radio": http://tarpn.net/t/packet_radio_networking.html

“Raleigh-centric ham radio resources page": http://torborg.com/a




On Aug 16, 2018, at 6:51 PM, Jon Greene via Groups.Io <jonarmy1@...> wrote:

Thanks Tadd for that information,

So today I went up the mountain and shut off all 4 of the radio's, then even though I didn't have to do it but, did a factory reset of the PiTNC's, then one by one redid the I2C settings from setting the I2C address then the TXDelay setting.

So after got all 4 of the PiTNC set, and then restacked.  I then still had the radio's off and rebooted, then checked the I2C and they had kept there settings, so then I turned the radio's back on and everything started to work.

Then I restarted to pi to see if when we remotely reboot the pi that everything would still work.  So after rebooting the pi with the radio's turned on, I then used the i2cdetect -y 1 and non of the 4 PiTNC were on the list, and the radio program wasn't even running. Yet I still did a pitnc_getparams 1 6 (for one of the PiTNC) and it was showing address of 0 and TXDelay of like 40.  

So after I saw that I shut the pi off, turned the radio's off, rebooted the pi and then did a i2cdetect -y 1 and it had all 4 of the PiTNC address.  So does anyone know of a way to either have the radio's stay on and not cause issues, or should I try to get relays that can turn the radio's off when the pi shuts down, and when it reboots waits a certain amount of time like 1 minute before it turns the radio's on.

Jon KK4ZIZ


On Friday, July 20, 2018 10:35 AM, Tadd KA2DEW in NC via Groups.Io <tadd@...> wrote:


Jon,
  The TNC-PI has the ability to return trash from PITNC-get if it is receiving data from a radio.  I don’t know if this is what is happening for you but it seems to have better dialogs with the PITNC programs if the radio receiver is disconnected. 
  One way to know that PITNC-get is showing you garbage, is to look at the returned I2C address register, register #7.  If it doesn’t match what you know the I2C address is, then you are getting garbage.  
  Sending a reset to the TNC, PITNC-set 0 0 register 15, data 2, will clear out all that, but if you are hooked to an active receiver, it’ll get garbage again, sometimes.  I’m not clear on what the mechanism there, just that’s what it looks like to me. 
  The TXdelay can be written in the registers, like you are doing, but setting it via the Potentiometer seems to be more reliable.  I don’t know why.  You can program G8BPQ via the config to write a TXDELAY of 0 to the KIS parameters, I think.  Then the potentiometer on the TNC-PI will have control of the TXDELAY.  
  
  This is what I use for a point to point dedicated link on our network.  
Notice the TXDELAY=0 and the KISSOPTIONS.  

PORT
PORTNUM=1        ; Optional but sets port number if stated
ID=p2p link to W1AW-4     ; Displayed by PORTS command
TYPE=I2C         ; Port is RS232 Com or I2C Com
PROTOCOL=KISS    ; TNC is used in KISS (or JKISS) mode
;;;;;;KISSOPTIONS=PITNC,NOPARAMS  ;; don’t set NOPARAMS.  we want params.  
I2CBUS=1         ; 0 for Version 1 board, 1 for Version 2 board. Don't include this for RS232/USB TNCs
I2CDEVICE=6      ; Decimal I2C device-ID --  Don't include for RS232/USB TNCs
;                ; See ..\RelatedFiles\KissRoms\KissRoms.zip.
FULLDUP=0        ; Only meaningful for KISS (or JKISS) devices
; IOADDR=1       ; 1 = SERIAL PORT COM1 ETC.  << do not use if TYPE=I2C
SPEED=19200      ; RS232 COM PORT SPEED
CHANNEL=A        ; A for single channel TNC, A or B for multichannel
PERSIST=225      ; PERSIST=256/(# of transmitters-1)  — don’t set this to 255 else the two nodes can sync on failure
SLOTTIME=100    ; CMSA interval timer in milliseconds
TXDELAY=0        ; Transmit keyup delay in milliseconds   0 means leave it up to the TNC-PI
TXTAIL=1         ; TX key down, in milliseconds, at packet end
QUALITY=1        ; Quality factor applied to node broadcasts heard on
;                ; this port, unless overridden by a locked route
;                ; entry. Setting to 0 stops node broadcasts
MINQUAL=50       ; Entries in the nodes table with qualities greater or
;                ; equal to MINQUAL will be sent on this port. A value
;                ; of 0 sends everything.
MAXFRAME=1       ; # of frames that can be sent in a single transmission (1 thru 7)
FRACK=4000       ; Level 2 timout in milliseconds -- how long before we retry transmitting to neighbor
RESPTIME=30      ; Level 2 delayed ack timer in milliseconds -- how long after we receive from neighbor before we key up and acknowledge the transmission
RETRIES=20       ; Level 2 maximum retry value
PACLEN=236       ; Default max packet length for this port
UNPROTO=ID       ; BT=EXT broadcast addrs format: DEST[,digi1[,digi2]]
;                ; BCALL=KK4CFN-8 ; BTEXT call. unstated defaults to APPL1CALL
L3ONLY=0         ; 1=No user downlink connects on this port
DIGIFLAG=0       ; Digipeat: 0=OFF, 1=ALL, 255=UI Only
DIGIPORT=0       ; Port on which to send digi'd frames (0 = same port)
USERS=0          ; Maximum number of L2 sessions, 0 = no limit
ENDPORT




Tadd / KA2DEW
Raleigh NC  FM05pv

“Packet networking over ham radio": http://tarpn.net/t/packet_radio_networking.html

“Raleigh-centric ham radio resources page": http://torborg.com/a




On Jul 19, 2018, at 7:26 PM, Jon Greene via Groups.Io <jonarmy1@...> wrote:

Currently our club has a stack of 4 Pi TNC, all 4 Pi TNC are hooked to there specific radio via the DB9 connector and using I2C protical

Were currently running LinBPQ on the Raspberry Pi.

So today took a trip up to the mountain were the setup is located at, so I took all 4 of the stack off and checking each I2C config.

So I would reset the Pi TNC to factory, then after pi has booted up, shut it down, then turned the petitioner so it would not be in the factory reset setting.  So after the Pi would start up I'd do the I2Cdetect -y 1 and of course get the blank response with nothing showing like it should. So then I'd do the pitnc_getparams 0 0 and get the reading of the Pi TNC.  So I'd change the address using pitnc_setparams 0 0 7 6 (of course I have 4 total so I spread the I2C address out)

So then I shutdown, unplug wait a moment then boot back up, and then see the Pi TNC at address 6.  Then I would change the TXDelay from the default to some where around 75, this is were it got a little confusing.

After I would change the TXDelay sometimes it would change right away, sometimes it would show TXDelay at like 150 or somewhere in that nature, at some times I would get the bottom were there would be around 14 items at the bottom ex: 8 1 4b 40 a 0 0 0 6 1d 13 c0 sum 0 

Sometimes I would have a total of 3 lines and at the end would be sum 0

Then also with changing the TXDelay, at times I had to do the pitnc_setparams command like 3 times before it responded back with the value I told it.

What could be causing the change in parameters not adjusting right away or the total of 3 lines ending with sum 0

I know when I've restarted sometimes even after knowing the TXDelay was set to around 75 or so, and then when I rebooted the value changed.  Right now I don't have the pi reboot cause I don't want to loose these values, and I've told my other sysop for our packet group not to reboot the pi.

Jon KK4ZIZ 




5221 - 5240 of 13409