Icom ID-4100 With DigiRig Using Pat on macOS 15.5

[Joel Black]

I have tried unsuccessfully to get Pat to key my ID-4100 with the following command:

rigctld -m 1 -p /dev/tty.usbserial-833210 -P RTS -s 9600 -vvvv

My understanding is that "m 1" is used for the dummy port in Hamlib but either my syntax is incorrect or I'm not holding my mouth right.

I am looking for pointers. I would love to completely abandon Windows.

Thanks,

Joel

[Justin Overfelt]

Hi Joel,

3082 is the model number for the ID-4100, so I think that's more likely to work than the dummy model.

But beyond that, what are you trying to do and what hardware are you using? Something like "I'm trying to connect using AX.25 packet using my ID-4100 through a Digirig on MacOS" or something like that. If you have a working setup on Windows, what does your config look like there?

-Justin AB3E 

[Robert Cheek]

To make sure the serial port passes all characters we will set it to the RAW mode, no filtering. Add this line to the “/usr/share/pat/bin/axup” file. Put this line before the Kissattach line in the 1200 baud section:

stty -F /dev/YOURSERIALDEVICE raw

In most cases it will be:

stty -F /dev/ttyUSB2 raw

This my help, fixed my problems with AX25 tools.

Bob - N4RFC

On Friday, June 20, 2025 at 4:19:10 PM UTC-4 joel.b...@gmail.com wrote:

[Justin Overfelt]

Hi All,

I just realized that Joel and I weren't discussing this on the main thread. Here's his original reply below:

Thanks for the correct model number for the ID-4100. I thought I looked through the list and never saw 4100. That was an oversight on my part.

I’m trying to use my ID-4100 with VARA-FM utilizing Pat. I have a DigiRig as the sound card interface between the ID-4100 and my Mac. The ID-4100 and DigiRig work on the Windows machine I’m trying to move away from where the ID-4100 is configured in VARA-FM to key using COM3 using RTS (I don’t remember where I got the RTS setting from but I think it was the DigiRig site).

I am using CrossOver to run VARA-FM and I have modified the Registry to map /dev/tty.usbserial-833210 to Com3.

If it matters, I start all this using a script that copies my VARA-FM Pat config file to config.json, runs rigctld as shown previously having now changed the radio model to 3082. It then starts VARA-FM and the http service for Pat.

Here are the relevant (I think) sections from my config.json file:

"listen": [],

  "hamlib_rigs": {

      "id-4100": {"address": "localhost:4532", "network": "tcp"}

  },

"varafm": {

    "addr": "localhost:8300",

    "bandwidth": 0,

    "rig": "id-4100",

    "ptt_ctrl": true

  },

I do seem to get the briefest of what sounds like an attempt to key the radio on the first Auto Tune transmit but the remaining 9 I get nothing and I get a No Signal message at the end. Ping yields the same. I do have the correct sound card selected in VARA FM.

I suggested he try Pat on Windows to remove the variable of VARA running in CrossOver. 

-Justin AB3E

[Martin Hebnes Pedersen]

Thanks for sharing Justin :)

By adding a fifth v ( -vvvvv ) to the rigctld command, it will enable TRACE logging. That should make rigctld log all commands sent to the radio. If we can see the PTT on/off commands there, it would indicate that VARA+Pat is configured correctly and working as intended.

You could also run pat with the env var VARA_DEBUG=1 to make it log the PTT ON/OFF commands sent from VARA FM to Pat.

That could hopefully provide some useful information to debug further.

-- 

Martin

--
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, visit https://groups.google.com/d/msgid/pat-users/9d59fbfc-a913-4c4c-a14c-15ac4b271114n%40googlegroups.com.

[Joel Black]

I appreciate all the tips.

It will be the weekend before I get another chance to take some time with this but I'll keep you posted.

Joel - W4JBB

[Joel Black]

As it turns out, I woke up about 1230 this morning and couldn’t go back to sleep - it’s gonna be a very long day…

I added the fifth “v” as recommended. One thing I noticed (in all honesty, I saw a lot of this before but didn't read through it - I had just copied the "-vvvv" knowing it was the verbose flag but didn't pay attention to what was being spit out). From what I'm seeing, hamlib is trying open a port on my Mac that doesn't even exist:

serial_open: /dev/ttyS0
serial_open(231): open failed#1 No such file or directory
serial_open: Unable to open /dev/ttyS0 - No such file or directory
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
rig_open: rs->comm_state==0?=0
rig.c(1176):rig_open returning2(-6) IO error

/dev/ttyS0 doesn't even exist on my system. If my understanding of rigctld is correct, "-p /dev/cu.usbserial-833310"  should be forcing PTT to on that particular port but something is constantly overriding my parameter.

I'm still looking.

Joel - W4JBB

[Joel Black]

...and just for grins, I rebooted and still get the same error.

Joel - W4JBB

[Justin Overfelt]

Joel,

Looking at rigctld, the docs on this point are somewhat confusing but I think you should be using -r for the serial port rather than -p. I think -p might be for if the PTT is controlled over a separate serial port and you've used -r elsewhere. 

-Justin

You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/XHAKlp70z7o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/pat-users/8ce9576d-bbdb-4cb1-af39-27be9e4eab85n%40googlegroups.com.