Date   
Re: Seeking insights -- trying to get IC7300 to transmit Ardop via PAT

John Wiseman
 

I assume you've replaced device in the command line with your device name (/dev/ttyUSB0).

Also make sure your 7300 is configured to allow PTT using the RTS signal on the control port.

I don't think it will work if you also have rigctld running.

The alternative, using --cat and k FEFE94E01C0001FD -u FEFE94E01C0000FD should also work.

73,
John G8BPQ


On 14/01/2020 23:35, Jonathan Scherch wrote:
On Wed, Jan 8, 2020 at 02:34 PM, Michael Dunn wrote:
piardopc 8515 IC7300 IC7300 --cat /dev/tty.IC7300:115200 -k FEFE94E01C0001FD -u FEFE94E01C0000FD
Thanks, Mike. Here is the script that I have been trying:

./piardopc 8515 plughw:1,0 plughw:1,0 -p device

The 7300 transmits, but does not alternate to RX (so that the target station reply could be heard). It simply stays in transmit and sends transmission every few seconds. I have to use Control-C to interrupt.

Any ideas how to make the TX alternate with RX?

BTW, here is my rigctld script:

rigctld -m 373 -r /dev/ttyUSB0 -s 9600

Thanks again.

Jonathan, KK7PW



Re: Seeking insights -- trying to get IC7300 to transmit Ardop via PAT

Ray Adkins
 

Check the unlinked from remote in the ci-v section. I think I had to change this to get it to work correctly.

Ray

Re: Seeking insights -- trying to get IC7300 to transmit Ardop via PAT

Jonathan Scherch
 

On Wed, Jan 8, 2020 at 02:34 PM, Michael Dunn wrote:
piardopc 8515 IC7300 IC7300 --cat /dev/tty.IC7300:115200 -k FEFE94E01C0001FD -u FEFE94E01C0000FD
Thanks, Mike. Here is the script that I have been trying:

./piardopc 8515 plughw:1,0 plughw:1,0 -p device

The 7300 transmits, but does not alternate to RX (so that the target station reply could be heard). It simply stays in transmit and sends transmission every few seconds. I have to use Control-C to interrupt.

Any ideas how to make the TX alternate with RX?

BTW, here is my rigctld script:

rigctld -m 373 -r /dev/ttyUSB0 -s 9600

Thanks again.

Jonathan, KK7PW


Re: IC-7300 for ARDOP / WinLink with Pi4

N3RDR
 

You are describing the same use I want to give to my Pi but I’m not as far along as you. I got wrapped around trying to make it compact for my go bag. 

To your question, it seems to me it is failing on a TCP connection before transmission occurs. Is that correct? How fast does the error comes? I’ll admit a a total newbie on this but the syntax makes me think it is trying to use IPv6 instead of IPv4 to connect (or to configure ARDOP?). Is that a possibility?

Sent from my 📲

On Jan 13, 2020, at 7:14 PM, Ken Crouse <k6kec@...> wrote:

Good afternoon, group - I recently picked up my first Pi (Raspberry Pi 4, Model B, 4GB) and have been working through several initial set-up videos.

One of my end goals is to be able to sit at my desk indoors and send e-mail on the HF bands using Pat and my Icom IC-7300 radio attached to my Pi 4 which are in the garage. Also would like to use Flrig, Fldigi to control the radio to move between ARDOP stations and frequencies.

I'm able to control the Pi using VNC server / connect and have Flrig / Fldigi installed and working somewhat well. I've been able to send messages using Telnet (essentially, just using WiFi). However, not able to get things working as I'd like and the error message that keeps coming back when I try to send via ARDOP reads as follows:

"2020/01/13 13:29:54 ARDOP TNC initialization failed: dial tcp [::1]:8515: connect: connection refused"

I've been using several of Jason Olham's KM4ACK videos (which have been quite helpful), but his video working through installation of ARDOP (  https://www.youtube.com/watch?v=BgqsTbxzR4E&t=238s  ) was made using a Yaesu model of radio and a Signalink sound card. The Icom IC-7300 has an internal sound card - there appears to be enough of a difference between Mr. Oleham's station and mine that I'm not able to get past the "  ./piardopc 8515 plughw;1,0 plughw:1,0 " command about 3:45 into the video.  I've gone back and made sure the 1 and 0 are correct.  I've also looked back through several other Settings recommendation for the radio and Fldigi but nothing that I do appears to be making any difference.

I posed this basic question to Mr. Oleham and he was kind enough to direct me to this group for possible assistance.

Thank you for your thoughts / recommendations.

P.S. I can get the Icom IC-7300 to communicate with my laptop computer and perform the tasks I'm trying to do with the Pi.

Re: IC-7300 for ARDOP / WinLink with Pi4

John Wiseman
 

I'm not clear form your description if you are running PAT on your local pc and trying to connect to ARDOP on the PI, or running both on the PI.

The message "2020/01/13 13:29:54 ARDOP TNC initialization failed: dial tcp [::1]:8515: connect: connection refused" shows that PAT is trying to connect to an IPv6 address ( ::1 is the IPv6 loopback address, same as  127.0.0.1 on IPv4). ARDOP doesn't support IPv6, so you need to use an IPv4 address wherever PAT is running, 127.0.0.1 for a local connection or the IP address of the PI for remote.

I suspect you have to configured  to connect to localhost. Normally on a PI localhost resolves to the IPv6 address ::1.

73,
John G8BPQ


shows that PAT is trying to connect to ARDOP on your local PC, not on the PI ( the [::1] is the IPv6 loopback address, similar to 127.0.0.1 on IPv4). You need to configure PAT to connect to the IP address of the PI.

On 14/01/2020 00:13, Ken Crouse wrote:
Good afternoon, group - I recently picked up my first Pi (Raspberry Pi 4, Model B, 4GB) and have been working through several initial set-up videos.

One of my end goals is to be able to sit at my desk indoors and send e-mail on the HF bands using Pat and my Icom IC-7300 radio attached to my Pi 4 which are in the garage. Also would like to use Flrig, Fldigi to control the radio to move between ARDOP stations and frequencies.

I'm able to control the Pi using VNC server / connect and have Flrig / Fldigi installed and working somewhat well. I've been able to send messages using Telnet (essentially, just using WiFi). However, not able to get things working as I'd like and the error message that keeps coming back when I try to send via ARDOP reads as follows:

"2020/01/13 13:29:54 ARDOP TNC initialization failed: dial tcp [::1]:8515: connect: connection refused"

I've been using several of Jason Olham's KM4ACK videos (which have been quite helpful), but his video working through installation of ARDOP (  https://www.youtube.com/watch?v=BgqsTbxzR4E&t=238s  ) was made using a Yaesu model of radio and a Signalink sound card. The Icom IC-7300 has an internal sound card - there appears to be enough of a difference between Mr. Oleham's station and mine that I'm not able to get past the "  ./piardopc 8515 plughw;1,0 plughw:1,0 " command about 3:45 into the video.  I've gone back and made sure the 1 and 0 are correct.  I've also looked back through several other Settings recommendation for the radio and Fldigi but nothing that I do appears to be making any difference.

I posed this basic question to Mr. Oleham and he was kind enough to direct me to this group for possible assistance.

Thank you for your thoughts / recommendations.

P.S. I can get the Icom IC-7300 to communicate with my laptop computer and perform the tasks I'm trying to do with the Pi.

IC-7300 for ARDOP / WinLink with Pi4

Ken Crouse
 

Good afternoon, group - I recently picked up my first Pi (Raspberry Pi 4, Model B, 4GB) and have been working through several initial set-up videos.

One of my end goals is to be able to sit at my desk indoors and send e-mail on the HF bands using Pat and my Icom IC-7300 radio attached to my Pi 4 which are in the garage. Also would like to use Flrig, Fldigi to control the radio to move between ARDOP stations and frequencies.

I'm able to control the Pi using VNC server / connect and have Flrig / Fldigi installed and working somewhat well. I've been able to send messages using Telnet (essentially, just using WiFi). However, not able to get things working as I'd like and the error message that keeps coming back when I try to send via ARDOP reads as follows:

"2020/01/13 13:29:54 ARDOP TNC initialization failed: dial tcp [::1]:8515: connect: connection refused"

I've been using several of Jason Olham's KM4ACK videos (which have been quite helpful), but his video working through installation of ARDOP (  https://www.youtube.com/watch?v=BgqsTbxzR4E&t=238s  ) was made using a Yaesu model of radio and a Signalink sound card. The Icom IC-7300 has an internal sound card - there appears to be enough of a difference between Mr. Oleham's station and mine that I'm not able to get past the "  ./piardopc 8515 plughw;1,0 plughw:1,0 " command about 3:45 into the video.  I've gone back and made sure the 1 and 0 are correct.  I've also looked back through several other Settings recommendation for the radio and Fldigi but nothing that I do appears to be making any difference.

I posed this basic question to Mr. Oleham and he was kind enough to direct me to this group for possible assistance.

Thank you for your thoughts / recommendations.

P.S. I can get the Icom IC-7300 to communicate with my laptop computer and perform the tasks I'm trying to do with the Pi.

Re: Dire Wolf Telemetry on RPi3

bobolink
 

On Sun, Jan 12, 2020 at 07:36 AM, Jon Adams wrote:
constructed a set of directories to match what it seemed they were expecting
Jon,

Sorry. I don’t have the device and am a beginner myself. Not going to be much help.

Bob

Re: RPi 3B+ w/ Buster, Alsa, Signalink USB, FLDIGI

David
 

The sound card is in the signalink. it generates the ptt signal going to the radio. make sure you have the jumper in the signalink correct for your radio.
David
ka4kkf

On 1/12/2020 18:01, Harry Bloomberg wrote:
The lack of audio coming out of the Pi to the Signalink sounds like the root cause.  You need audio going into the Signalink to trigger it's PTT.  Are you using Port Audio or PulseAudio?  Check your output device settings in Fldigi configuration.

73,
Harry Bloomberg W3YJ

On Sun, Jan 12, 2020 at 5:52 PM Grover Cleveland via Groups.Io <k7tp=yahoo.com@groups.io> wrote:
I am using a Signalink with Buster and the Pi sees the incoming audio just fine - good waterfall on FlDig. But nothing happens on Transmit. I have a radio without PTT on the CIV set so I have to rely on the Signalink to do the PTT. There seems to be no level at all coming out of the pi going to the Signalink

K7TP.

Re: RPi 3B+ w/ Buster, Alsa, Signalink USB, FLDIGI

Harry Bloomberg <hbloomb@...>
 

The lack of audio coming out of the Pi to the Signalink sounds like the root cause.  You need audio going into the Signalink to trigger it's PTT.  Are you using Port Audio or PulseAudio?  Check your output device settings in Fldigi configuration.

73,
Harry Bloomberg W3YJ


On Sun, Jan 12, 2020 at 5:52 PM Grover Cleveland via Groups.Io <k7tp=yahoo.com@groups.io> wrote:
I am using a Signalink with Buster and the Pi sees the incoming audio just fine - good waterfall on FlDig. But nothing happens on Transmit. I have a radio without PTT on the CIV set so I have to rely on the Signalink to do the PTT. There seems to be no level at all coming out of the pi going to the Signalink

K7TP.

Re: RPi 3B+ w/ Buster, Alsa, Signalink USB, FLDIGI

Grover Cleveland
 

I am using a Signalink with Buster and the Pi sees the incoming audio just fine - good waterfall on FlDig. But nothing happens on Transmit. I have a radio without PTT on the CIV set so I have to rely on the Signalink to do the PTT. There seems to be no level at all coming out of the pi going to the Signalink

K7TP.

Re: FS - DVMEGA dual bander

Tim Carroll
 

I have one I will sell you a lot  cheaper then that,got out of DMR,never use it.

Tim

KE4HGP

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of James Hertel
Sent: Sunday, January 12, 2020 1:00 PM
To: 3959@...; arm-allstar@...; Pi@irlp.groups.io; RaspberryPi-4-HamRadio@groups.io; Marshall Oldham <ke6pcv@...>; n5bmu <chadatn5bmu@...>; D.W. Smitha <dwsmitha@...>; Jim Linden <jimlinden@...>
Subject: Re: [RaspberryPi-4-HamRadio] FS - DVMEGA dual bander

 

I just found this !!! gads !!!

https://www.ebay.com/itm/BlueStack-Micro-Plus-DVMEGA-Dual-Band-VHF-UHF-Pre-Assembled-Digital-Hot-Spot/293041627612?hash=item443aa461dc:g:AEgAAOSww4BcrFnK

Wow ! those things are expensive! Mine is such a deal !

JIm N6KMR

On 1/12/2020 9:48 AM, Jim Hertel wrote:

  I have a DVMEGA that's and extra, Dual Band, I don't have wall wart for it but I am sure you have an extra in the drawer.  It works with "BlueDV" for windows program which is downloadable. (via www.pa7lim.nl)  prices range from 196 to 216 on Ebay for the single banders. I will sell this extra one for $110 shipped. I am open for offers too.

Re: FS - DVMEGA dual bander

James Hertel
 

On 1/12/2020 9:48 AM, Jim Hertel wrote:

  I have a DVMEGA that's and extra, Dual Band, I don't have wall wart for it but I am sure you have an extra in the drawer.  It works with "BlueDV" for windows program which is downloadable. (via www.pa7lim.nl)  prices range from 196 to 216 on Ebay for the single banders. I will sell this extra one for $110 shipped. I am open for offers too.

FS - DVMEGA dual bander

James Hertel
 

  I have a DVMEGA that's and extra, Dual Band, I don't have wall wart for it but I am sure you have an extra in the drawer.  It works with "BlueDV" for windows program which is downloadable. (via www.pa7lim.nl)  prices range from 196 to 216 on Ebay for the single banders. I will sell this extra one for $110 shipped. I am open for offers too.

Re: Dire Wolf Telemetry on RPi3

Jon Adams
 

Hi Bob -

I got back to this project yesterday after receiving the package from Adafruit. I wired in the Adafruit ADS1015 breakout board according to WB2OSZ's instructions in section 5.2 of his telemetry tool kit pdf.

I installed the kernel support from his section 5.3:

sudo apt-get install python-smbus
sudo apt-get install i2c-tools
sudo raspi-config
(Select Advanced Options then I2C. Answer yes and yes.)

and did all the other things he required in section 5.3.

So far, so good. So on to section 5.4:

After it finishes rebooting, see if we can communicate with the I2C device.
sudo i2cdetect -y 1
You should see something like this:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

and indeed!!! I saw this. So, the i2c bus is working and it found the ADC. Holy moly.

Next, I attempted to set up on my direwolf RPi the archived Adafruit ADS1x15 routines. From WB2OSZ's telemetry-toolkit manual, he says to perform the following commands:

cd ~
git clone https://github.com/adafruit/Adafruit-Raspberry-Pi-Python-Code
cd Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15
chmod +x *.py

The only thing that showed up in the Pi home directory was the Python-Code subdirectory and a readme file, which stated that this is no longer supported. This I knew. While I'm really not sure what I'm doing, I then looked inside the python files and constructed a set of directories to match what it seemed they were expecting. So, at home/pi, I have

pi@RPi3Bplus-server:~ $ ls
Adafruit-Raspberry-Pi-Python-Code  direwolf       Downloads      MagPi        Pictures          testscript
bcm2835-1.60                       direwolf.conf  dw-start.sh    Music        PiPyADC   sdr.conf   Videos
Desktop                            Documents      hp_adda_board  ntp-4.2.8p6  Public    Templates  YAAC
 
where Adafruit-Raspberry-Pi-Python-Code is the main directory it appears the code expects. Inside Adafruit-Raspberry-Pi-Python-Code, I have

pi@RPi3Bplus-server:~/Adafruit-Raspberry-Pi-Python-Code $ ls
Adafruit_ADS1x15  Adafruit_I2C
 
which I believe should be the two directories there.

The contents of the directory Adafruit_ADS1x15 are:

pi@RPi3Bplus-server:~/Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15 $ ls
Adafruit_ADS1x15.py  Adafruit_I2C.py  ads1x15_ex_comparator.py  ads1x15_ex_differential.py  ads1x15_ex_singleended.py
 
Each of these files I constructed by using nano to copy across the python code from the files of the same name, archived on the Adafruit git site.

Then, according to the Telemetry Toolkit data, I ran the chmod +x *.py command to make all these files executable. So, now I ran his next two commands:

cd ~/Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15
./ads1x15_ex_singleended.py

and got the unhappy result

pi@RPi3Bplus-server:~/Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15 $ ./ads1x15_ex_singleended.py
Traceback (most recent call last):
  File "./ads1x15_ex_singleended.py", line 4, in <module>
    from Adafruit_ADS1x15 import ADS1x15
  File "/home/pi/Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15/Adafruit_ADS1x15.py", line 5, in <module>
    from Adafruit_I2C import Adafruit_I2C
  File "/home/pi/Adafruit-Raspberry-Pi-Python-Code/Adafruit_ADS1x15/Adafruit_I2C.py", line 1
    ../Adafruit_I2C/Adafruit_I2C.py
    ^
SyntaxError: invalid syntax

so, this is where I'm stuck. I don't see an issue with a command ".../Adafruit_I2C/Adafruit_I2C.py", but the python interpreter does seem to.

Anyway, that's where I am right now.

Cheers and 73 - Jon N7UV

Re: Can't upgrade buster

Marty Hartwell
 

Hi Jason

Yes I ran into it also, the error message was something on the order of the date was wrong or

or something like that. I also got it to upgrade using the full command so I moved on. I am

seeing some other issues too but haven't had a chance to investigate further.

My plan is to try to use the Pi 4 with 4 GB of RAM as my main PC although I may have to
run another SSD as a Home disk like my laptop currently has. I may run into other issues
too, so it is differently a work in progress.

I still have my Pi 2 that I plan to try to use as my Ham PC strictly as digital mode. I have it

running Buster also, I just need to finish installing all of the digital software I am going to

want, and I may want to get some additional hardware so I may investigate some of your

videos to refresh my memory on that issue.

I hope to talk to you soon too.


Marty kd8bj


On 1/10/20 10:55 AM, km4ack wrote:
Ran into something unique to me this morning. Downloaded fresh copy of Buster and flashed to card. Booted pi and ran the usual sudo apt-get update. Then ran sudo apt-get upgrade which failed. (See screenshot.) Ran sudo apt-get full-upgrade which seems to have overcome this issue. Anyone else run into this on a fresh install?


73, de KM4ACK

Re: Can't upgrade buster

William Kimber
 

Nothing wrong at all.  You had just installed VLC and it put on the latest versions.  Then when you did update/upgrade as those were the correct, most up to date it did not need to update them.


You should have done the update/upgrade before doing the VLC install.


Cheers,

Will

On 11/01/20 7:43 am, Andrew Harmon wrote:
I just did a fresh install of vlc on raspbian buster and it installed successfully. Immediately afterwards did an update & upgrade and got 
The following packages have been kept back:
 libvlc-bin libvlc5 vlc vlc-bin vlc-data vlc-plugin-base vlc-plugin-qt vlc-plugin-skins2 vlc-plugin-video-output
Then I did sudo apt-get install libvlc-bin libvlc5 vlc vlc-bin vlc-data vlc-plugin-base vlc-plugin-qt vlc-plugin-skins2 vlc-plugin-video-output
And it worked.
Some weird circular dependencies going on here I think. 



Re: Can't upgrade buster

Matthew Allinson
 

I encountered it about 3 days ago on my RPi4B. Wasn’t in a new image install situation, just in the process of adding some new packages and ran those commands prior to starting. 

73, Matt, KG8TRS 

On Fri, Jan 10, 2020 at 11:55 km4ack <jason.oleham@...> wrote:
Ran into something unique to me this morning. Downloaded fresh copy of Buster and flashed to card. Booted pi and ran the usual sudo apt-get update. Then ran sudo apt-get upgrade which failed. (See screenshot.) Ran sudo apt-get full-upgrade which seems to have overcome this issue. Anyone else run into this on a fresh install?


73, de KM4ACK

--
73,

Matt Allinson, KG8TRS

Re: Can't upgrade buster

Andrew Harmon
 

I just did a fresh install of vlc on raspbian buster and it installed successfully. Immediately afterwards did an update & upgrade and got 
The following packages have been kept back:
 libvlc-bin libvlc5 vlc vlc-bin vlc-data vlc-plugin-base vlc-plugin-qt vlc-plugin-skins2 vlc-plugin-video-output
Then I did sudo apt-get install libvlc-bin libvlc5 vlc vlc-bin vlc-data vlc-plugin-base vlc-plugin-qt vlc-plugin-skins2 vlc-plugin-video-output
And it worked.
Some weird circular dependencies going on here I think. 



Re: Can't upgrade buster

Teton Amateur Radio Repeater Association (TARRA)
 

I wasn't trying to be harsh, just a couple things to keep in mind. If the subject was about what you were talking about, you may get some others jumping in. Also, if later on someone tries doing a search, they may not find what you were talking about because of it being under a different subject. Thank you for understanding and good luck with your project.

Related to your subject, I recently rebuilt my IRLP node to the latest with Debian 10. At the beginning of the process was to update/upgrade and it worked okay.

Mick - W7CAT

----- Original Message -----
From: Bill Lamm
To: RaspberryPi-4-HamRadio@groups.io
Sent: Friday, January 10, 2020 09:58:26 AM
Subject: Re: [RaspberryPi-4-HamRadio] Can't upgrade buster

> [Edited Message Follows]
>
> Sorry
>
> 73
> KD9MDL
> Bill Lamm
>
> On Fri, Jan 10, 2020, 10:55 AM km4ack < jason.oleham@... > wrote:
>
> >
> > Ran into something unique to me this morning. Downloaded fresh copy of
> > Buster and flashed to card. Booted pi and ran the usual *sudo apt-get
> > update*. Then ran *sudo apt-get upgrade* which failed. (See screenshot.)
> > Ran *sudo apt-get full-upgrade* which seems to have overcome this issue.
> > Anyone else run into this on a fresh install?
> >
> >
> > 73, de KM4ACK
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
--

Re: Can't upgrade buster

Teton Amateur Radio Repeater Association (TARRA)
 

Please change your subject since you hijacked the original post and are now talking about something different.

Mick - W7CAT

----- Original Message -----
From: Bill Lamm
To: RaspberryPi-4-HamRadio@groups.io
Sent: Friday, January 10, 2020 10:12:17 AM
Subject: Re: [RaspberryPi-4-HamRadio] Can't upgrade buster

> If I recall correctly the script stopped because a sub directory had not
> been built.. If I create that directory and run again will the script skip
> all the previous work and finish or do I need to start over and build
> directory before running script?
>
> Or wait a few for you to polish ?
>
> 73
> KD9MDL
> Bill Lamm
>
> On Fri, Jan 10, 2020, 11:05 AM km4ack wrote:
>
> > Yes. Work in progress but it is 99% complete for the moment. I was
> > actually working on the video when I ran into this issue.
> >
> > 73, de KM4ACK
> >
> >
>
>
>
>
--