non standard Serial port bug

2 posts / 0 new
Last post
NX1P
non standard Serial port bug

Non standard serial port locations do not seem to work.

Hi Petr, I'm building a rig bridge for
linux using python (like lp-bridge for windows). I have quite a bit of success and have run CQRLOG from a remote computer using a serial line to a second computer running the bridge program and talking to my K3.

I have used socat to build several virtual serial ports and have tested
them with my bridge using a terminal program and using hamlib through
rigctl

However, I can't seem to get CQRLOG to run. The problem may be related
to serial port selection. As my virtual serial ports are located
in /dev/pts/1 through 8, they do no show up in the drop down box
selector for serial port in CQRLOG. When I attempt to enter it directly
I get no response and I cannot see any traffic in my bridge monitoring window.

Now I know the bridge works with hamlib because I used rigctl. I know
the bridge is working with CQRLOG because I can do it remotely
through /dev/ttyS0 on the remote machine.

I have had success with Quisk and xlog using both remote and local virtual serial ports. Quisk uses its own rig interface and xlog using hamlib.

All I can think of is that CQRLOG won't allow any non probed serial
ports or non standard serial port paths. Is there a way around this?

Thanks,

Paula, NX1P

NX1P
non standard serial port bug: more info

running cqrlog from a terminal with Debug=2 gets the following results on initialization

<<<<<<<<<>>>>>>>>>>>

SELECT * FROM version

SELECT * FROM cqrlog_main ORDER BY qsodate,time_on
Loaded 36535 LoTW users
In inicializerig
Model:229
Port:/dev/pts/5
Baudrate:38400
Databits:8
StopBits:0
Handshake:None
Parity:None
DTR:OFF
RTS:OFF
Poll:200
rig_open: error =
rig_open: error = 254
Removing Rig control thread from memory
Loading window size a position (height|width|top|left):666|818|110|102

<<<<<<<<<<<<<<>>>>>>>>>>>>>

The first return error is an empty string, the second return error is 254 which I assume is a -2 (signed char)

I built a python test script for hamlib and that works along with quisk, fldigi (CAT control), xlog and rigctl so I'm pretty sure it is not Hamlib.

Any help would be great!

Next stop, the sources.

Paula NX1P

73, NX1P