PTT with IC-7100

675 views
Skip to first unread message

Robert Cheek

unread,
Nov 26, 2021, 8:01:43 PM11/26/21
to pat-users
I am sure that I am missing something, but I can't seem to get PTT to work with ARDOP.  I had quite a time getting the audio to work, but I am now seeing lots of trace activity from ardopc_64 now.  Also, the CAT control of the frequency of the rig is working, but not the PTT.

Here is my setup:
ARDOP  

./ardopc_64 8515 plughw:1,0 plughw:1,0 -c /dev/ttyUSB0 -p /dev/ttyUSB0
ARDOPC Version 1.0.4.1-BPQ
LinBPQ Port /dev/ttyUSB0 fd 4
CAT Control on port /dev/ttyUSB0
Using RTS on port /dev/ttyUSB0 for PTT
ARDOPC listening on port 8515

RIGCTLD
~$ rigctld -vv -m "370" -r /dev/ttyUSB0 -s 19200 -p /dev/ttyUSB0

and here excerpts from the config file for PAT
"mycall": "N4RFC",
  "secure_login_password": "*********"
  "auxiliary_addresses": [],
  "locator": "EM74td",
  "service_codes": [
    "PUBLIC"
  ],
  "http_addr": "localhost:8080",
  "motd": [
    "Open source Winlink client - getpat.io"
  ],
  "connect_aliases": {
    "telnet": "telnet://{mycall}:CMST...@cms.winlink.org:8772/wl2k"
  },
  "listen": [],
  "hamlib_rigs": {"370": {"address": "localhost:4532","network": "tcp"}},
  "ax25": {
    "port": "wl2k",
    "beacon": {
      "every": 3600,
      "message": "Winlink P2P",
      "destination": "IDENT"
    },
    "rig": ""
*******************************************************************
 "ardop": {
    "addr": "localhost:8515",
    "arq_bandwidth": {
      "Forced": false,
      "Max": 500
    },
    "rig": "370",
    "ptt_ctrl": true,
    "beacon_interval": 0
    "cwid_enabled": true

The IC-7100 work fine with JTDX and FLDIGI, both control the frequency and key the PTT just fine.  Makes me think all is well with HamLib. 

Anyone see anything I missed? I am really looking forward to getting PAT working with the IC-7100. 

Regards,
Bob - N4RFC



KB9MTD - Aaron Webb

unread,
Nov 26, 2021, 8:34:58 PM11/26/21
to Robert Cheek, pat-users
Robert,

I don't have an Icom but on my Yaesu there are two different ports used. One for CAT and the other for PTT. Check to see if the second port is ttyUSB1. Test out a second port for PTT.

Aaron


--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/bde530ca-715f-442b-9338-a9c91bc54331n%40googlegroups.com.

Stephen Kangas

unread,
Nov 26, 2021, 9:17:29 PM11/26/21
to KB9MTD - Aaron Webb, Robert Cheek, pat-users

I recall that both of my Icom xcvrs have a pull-up resistor to a positive rail on the PTT input and expects the external device control signal to perform a short to ground on that to activate PTT (usually via an open collector driver, or mechanical relay).  Some external devices do the opposite, ie applying a positive voltage for PTT, and sometimes depending upon the external device it is configurable.  SO, for example, your RTS line out of your control device may be toggling positive voltage AND may otherwise be floating.  If you have a DMM, or oscilloscope, to check this perhaps that will give you some clues.

 

Not saying this is your issue, just suggesting something to look at that may possibly be related.  You may wish to start with checking the schematic diagram for your Icom, and checking the PPT input with a DMM to see what voltage state it is currently in; if it’s a positive voltage that it may expect grounding and you can short it to ground to see if the radio goes into Xmt; if it’s floating, then it’s the opposite where it expects either a positive or negative voltage to activate its internal interface chip/xstr.  I have run into this several times in the past interfacing laptops to various brands of radios, esp when using a virtual serial port driver with various interface cables.

 

Best is if someone here with your Icom model and same external control device/cables responds.

 

Stephen W9SK

john.w...@ntlworld.com

unread,
Nov 27, 2021, 6:12:20 AM11/27/21
to pat-users
 You can't key a 7100 using RTS over the virtual port - you have to use cat commands. Have you looked at

https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html?

I suggest you try

./ardopc_64 8515 plughw:1,0 plughw:1,0 -c /dev/ttyUSB0 -k FEFE88E01C0001FD -u FEFE88E01C0000FD

Why are you running rigctld?

73,
John

Robert Cheek

unread,
Nov 27, 2021, 9:46:46 AM11/27/21
to pat-users
John,
See, I was right, I did miss something!  Yes, I have read the document on ARDOP but I didn't read and understand that particular section.  I struggled with the audio part for a while, and finally got that working, but missed the detail about the Icom PTT strings.  Also, I ran rigctld because I read somewhere else that needed to be run.   I assumed that the ARDOP modem used HamLib to do the CAT control.  Am I correct in assuming that like JTDX, the ARDOP modem starts the rigctld and I just need to supply the port with the -c option on the ARDOP ?

I'll give the strings a try here shortly!  Thanks for the input.

On another subject, I see you have terminal program for PI, is there one for Ubuntu or other Debian distros?

Regards and thanks for the help,
Bob - N4RFC

and Stephan and Arron, I am using a CAT PTT not a hardware PTT.   Thanks!

john.w...@ntlworld.com

unread,
Nov 27, 2021, 9:55:10 AM11/27/21
to pat-users
No, ARDOP does not use rigctld. It talks directly to the radio. That is why you have to specify the PTT on and off strings.

There is an Intel version of QtTermTCP that should work on most Linux distributions. 

73,
John


John,
See, I was right, I did miss something!  Yes, I have read the document on ARDOP but I didn't read and understand that particular section.  I struggled with the audio part for a while, and finally got that working, but missed the detail about the Icom PTT strings.  Also, I ran rigctld because I read somewhere else that needed to be run.   I assumed that the ARDOP modem used HamLib to do the CAT control.  Am I correct in assuming that like JTDX, the ARDOP modem starts the rigctld and I just need to supply the port with the -c option on the ARDOP ?

I'll give the strings a try here shortly!  Thanks for the input.

On another subject, I see you have terminal program for PI, is there one for Ubuntu or other Debian distros?

Regards and thanks for the help,
Bob - N4RFC

and Stephan and Arron, I am using a CAT PTT not a hardware PTT.   Thanks!

 You can't key a 7100 using RTS over the virtual port - you have to use cat commands. Have you looked at

https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html?

I suggest you try

./ardopc_64 8515 plughw:1,0 plughw:1,0 -c /dev/ttyUSB0 -k FEFE88E01C0001FD -u FEFE88E01C0000FD

Why are you running rigctld?

73,
John
=

Brian Silverstein

unread,
Nov 27, 2021, 2:41:19 PM11/27/21
to pat-users
Here is what I use for IC-7300 (HamLib 373)
I had to do some trial and error to get PTT to work but not lock up the radio in TX
Assuming your are using the USB connection to the radio CAT and PTT are both using the same USB
Good luck!

RIGCTL -
rigctld -m 373 -r /dev/ttyUSB0 -p /dev/ttyUSB0 -P RTS -s 19200


config.json -


},
  "listen": ["ax25"],
  "hamlib_rigs": {
  "IC-7300": {"address": "localhost:4532", "network": "tcp"}
  },


},
  "ardop": {
    "addr": "localhost:8515",
    "arq_bandwidth": {
      "Forced": false,
      "Max": 500
    },
    "rig": "IC-7300",
    "ptt_ctrl": false,
    "beacon_interval": 0,
    "cwid_enabled": true
  },


73
Brian K7BLS


Robert Cheek

unread,
Nov 27, 2021, 5:18:45 PM11/27/21
to pat-users
This is one of the things that get to me about Linux....Libraries.  I try to run the QtTermTCP app and I get this:
./QtTermTCP: error while loading shared libraries: libQt5Widgets.so.5: cannot open shared object file: No such file or directory
I have QT5 installed....I tried to install the libraries suggested in on the web page and they are already installed.  I searched for variations on libQt5Widgets and there is no install for libQt5Widgets.so.5!

Very frustrating!
DE N4RFC

Gmail

unread,
Nov 28, 2021, 2:45:12 AM11/28/21
to Robert Cheek, pat-users
Hello Robert 
In Hamlib for the icom 7100 you have to use 3070 instead of 370.
That has been changed after version hamlib 4.3
Do you use a raspberry pi? Than you have to look at build a pi (bap) by km4ack.
This software gives you a lot of ham applications and wherein also pat winlink with ardopc and packet winlink vhf/uhf.

Hope this helps

73 Ron
PD7RON
--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.

john.w...@ntlworld.com

unread,
Nov 28, 2021, 2:50:33 AM11/28/21
to pat-users
This works with a 7300 but not with a 7100. The 7300 supports keying via RTS. The 7100 doesn't

73,
John

john.w...@ntlworld.com

unread,
Nov 28, 2021, 2:52:14 AM11/28/21
to pat-users
QtTermTCP is a 32 bit program. If you are running on a 64 bit version of Linux you will have to install the 32 bit version of Qt.

73,
John

Robert Cheek

unread,
Nov 28, 2021, 9:13:26 AM11/28/21
to pat-users
John,
I downloaded the source and compiled it, the resulting executable works fine. 
Thanks,
Bob - N4RFC

MJ Inabnit

unread,
Nov 28, 2021, 9:44:36 PM11/28/21
to pat-...@googlegroups.com

Sounds very familiar:
https://groups.google.com/g/pat-users/c/-YE04t5eZ6A/m/xmDhx78dBAAJ

Got the error trying to run ARDOC_GUI .. Still doesn't run on the
latest Xubuntu :(

gl, 73
j
> --
> You received this message because you are subscribed to the Google
> Groups "pat-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pat-users+...@googlegroups.com
> <mailto:pat-users+...@googlegroups.com>.
> <https://groups.google.com/d/msgid/pat-users/690eb27e-6833-4d44-8718-ffdf8b9b56f4n%40googlegroups.com?utm_medium=email&utm_source=footer>.


--

wishing you well
Jaye, ke6sls--via the toshiba w/thunderchicken

Robert Cheek

unread,
Nov 29, 2021, 10:51:17 AM11/29/21
to pat-users
I was having that problem with the QtTermTCP program.  Apparently it was a 32 bit version on ad 64 bit OS.  I downloaded the source and complied it on my Ubuntu 20.04 LTS and it worked fine from there. 

Regards,
Bob - N4RFC
Reply all
Reply to author
Forward
0 new messages