What debug level are you running? They are at the TRACE level now which should
be 5 v's.
Mike W9MDBfind . -name "*.c" -exec grep "PTT RTS" {} \; -print
rig_debug(RIG_DEBUG_TRACE, "%s: PTT RTS debug#1\n",
__func__);./src/rig.c
find . -name "*.c" -exec grep "debug#" {} \; -print
rig_debug(RIG_DEBUG_TRACE, "%s: PTT RTS debug#1\n", __func__);./src/rig.c
rig_debug(RIG_DEBUG_TRACE, "%s: debug#1\n", __func__);
rig_debug(RIG_DEBUG_TRACE, "%s: debug#2\n", __func__);
rig_debug(RIG_DEBUG_TRACE, "%s: debug#3\n", __func__);
rig_debug(RIG_DEBUG_TRACE, "%s: debug#4\n", __func__);
rig_debug(RIG_DEBUG_TRACE, "%s: debug#5 curr_vfo=%s\n",
__func__,./rigs/icom/icom.c
On Saturday, September 5, 2020, 05:54:12 PM CDT, Marco Calistri
<[email protected]> wrote:
Il 05/09/20 19:21, Marco Calistri ha scritto:
> (Top-posting reply)
>
> Thanks Mike, I will do it.
>
> Regards,
>
> Marco
>
>
>
Mike,
Nothing to do: same error related to rigctl, despite I've recompiled the
source:
Hamlib: rig_set_ptt: PTT RTS
set 05 19:47:15 linux-turion64 wsjtx[7054]: Hamlib: rig_set_ptt: PTT RTS
debug#1
set 05 19:47:15 linux-turion64 wsjtx[7054]: Hamlib: rig_set_ptt: PTT RTS
debug#2
--
73 de Marco, PY1ZRJ (former IK5BCU)
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
