--
Are you saying that Direwolf keys up SCU-17 and it's "FSK"
indicator lights up but Direwolf stays playing audio (AFSK modem
tones), the SCU-17's turns off the FSK light and then turns on the
PTT light?? If so, that does NOT sound right at all.? If you
would, please try Direwolf v1.6.?? I would expect Direwolf v1.7*
as very stable now but it's NOT released code and it's still
undergoing change.
--
Yes... I think, if I understand the question correctly.
Let me elaborate...
The SCU hase 3 LED indicator lights, FSK, PTT and Power...
Direwolf not running, FSK off, PTT off, Power on
Direwolf running, FSK on, PTT off, Power on
YAAC sends message, Direwolf triggers PTT then, FSK off, PTT on,
Power on
Direwolf drops PTT, FSK on, PTT off, Power on
Exit Direwolf application, FSK off, PTT off, Power on
--
The vew fellow HAMs who have had issue have been either using
unusual sound devices, using unusual isolation devices, etc.?
Direwolf can be made to work with any of them but you have to
determine what the right signal is for each of them.? In your
circumstance, the SCU-17 documentation is non-existent which makes
it extra hard.
--
The only documentation I know of for the SCU-17 is this...
But yea, they don't break things down all the way.
--
Of course the choice is yours but I can nearly guarantee you that
Direwolf will out perform *any* hardware TNC you buy.? TNCs like a
KPC3+ or PK96 can come close but most of the PIC/Arduino based
units will have significantly poor decode rates.
--
Oh, I agree for sure! The CPU in the machine is by far more
powerful than any TNC and would for sure have better error
correcting!
I'm just getting frustrated, I've spent many hours working on this
one issue and when I can open another app like FLDigi or WSJTX and
make it work perfecting the first time it only adds to the
frustration.
--
Well.. I hear the frustration here but Direwolf has recommend
hardware mentioned in the User Guide but you're not using that.?
You also were doing a lot of testing and you might have actually
missed the test that either "-DTR RTS" or "-DTR RTS"
was actually working for you (ignore whatever the LED lights are
as there is no FSK signal here in AFSK1200 packet).? FSK from an
SCU-17 perspective is used for things like "real" RTTY or CW on
HF radios.
--
You're
right, I very likely missed that with the FSK light on it wasn't
keying. I am by no means perfect or infallible so therefor I do
make mistake and I'll own.
For instance I didn't know there was recommended hardware. I
perused through the guide but I can't say I read it all. I read
some parts more than others.
As for FSK, no, I really had NO idea what is was used for. I can
say in the past week or so I've learned some things I didn't
know before
As for
rolling back to 1.6 it seems I've run into a issue compiling it.
I get the following.....
dwgpsd.c:64:2:
error: #error libgps API version might be incompatible.
?? 64 | #error libgps API version might be incompatible.
????? |? ^~~~~
make[2]: *** [src/CMakeFiles/decode_aprs.dir/build.make:141:
src/CMakeFiles/decode_aprs.dir/dwgpsd.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/patrick/direwolf/src/dwgpsd.c:64:2: error: #error libgps
API version might be incompatible.
?? 64 | #error libgps API version might be incompatible.
????? |? ^~~~~
[ 16%] Building C object src/CMakeFiles/direwolf.dir/cm108.c.o
make[2]: *** [src/CMakeFiles/direwolf.dir/build.make:843:
src/CMakeFiles/direwolf.dir/dwgpsd.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
[ 17%] Built target text2tt
[ 19%] Built target utm2ll
[ 27%] Built target gen_packets
make[1]: *** [CMakeFiles/Makefile2:633:
src/CMakeFiles/decode_aprs.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 29%] Built target ttcalc
make[1]: *** [CMakeFiles/Makefile2:579:
src/CMakeFiles/direwolf.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
If I
git checkout dev then it compiles just fine and starts out
with...
-- Dire
Wolf Version: 1.7.0-c9ffbd7
-- Build type set to: Release
CMake system: Linux
-- Target architecture: x86_64
-- Use SSE2 SIMD instructions
-- Use SSSE3 SIMD instructions
-- Use SSE 4.1 SIMD instructions
-- Use SSE 4.2 SIMD instructions
-- Use AVX SIMD instructions
-- Use AVX2 SIMD instructions
-- Looking for strlcpy
-- Looking for strlcpy - not found
-- Looking for strlcat
-- Looking for strlcat - not found
-- Could NOT find AVAHI (missing: AVAHI_COMMON_FOUND
AVAHI_CLIENT_FOUND)
-- Configuring done
-- Generating done
-- Build files have been written
(Continues Compiling Successfully)
I know
this message was very long, sorry about that, just trying to be
thorough.
