toggle quoted messageShow quoted text
OK, so you are seeing a 30 to 40 dB on the level meter, but no decodes and nothing in the waterfall? Quick check, does the level meter drop when you disconnect the antenna?
Any change if you move the level and gain sliders in JS8Call? Can you get any change by moving them?
-------- Original message --------
From: Bill / N1ASS <billn1ass@...>
Date: 01/09/2019 16:14 (GMT+00:00)
Subject: Re: [EladSDR] Set Up to use JS8Call with Elad Fdm Duo
On 8/31/2019 1:59 PM, Neil Smith G4DBN
OK, that is progress! Right, next let's look at receive.
I am assuming now that yhou are not running SW2, so this is
just for standalone use.No I am not.
In JS8Call, you should have something like this:It looks
Now check on the DUO to see if Menu 6 AUX VOL is set to around
10, and on the E1 knob, that AGC is set to OFF, AGC GAIN is set
to 2 or 3, SQL is OFF, AN is OFF, NR is OFF All is set as
you ar showning me
With those settings to start with, yhou should start seeing
some audio on the scal in JS8Call. You might need a little less
gain or a little more on the AGC and AUX, you'll need to adjust
things toi your antennas and band conditions.
It should look something like this on a section of the band
with no signals:
A level of 30 or 40 just on band noise is about right.Yes it
is in the range
Any luck with that? I wish,No Luck.
If you are using SW2 and want to use the AUX output then I
would recommend using Virtual Audio Cables, bujt that's a whole
different story/ No I am running it in stand alone.Bill
On 31/08/2019 17:12, Bill / N1ASS
On 8/31/2019 10:58 AM, Basile"Bill
"Actipis N1ASS wrote:
Got it to see com port 5,but no receive or
tx,I see the waterfall I hear signals on the speaker on of
the radio itself but I don't see them in the waterfall and
no output on the lp100a what so ever from the radio when I
try to send cq.
On 8/31/2019 9:33 AM, Neil Smith
OK, that means the COM port is not responding, or not
responding correctly. Are the settings identical to those
that worked OK in HRD? Do you have anything else running
that is trying to share the COM port? If you open Device
Manager, do you see the COM port with no errors? If you
disconnect the DUO, does that com port definitely
disappear and then return when you reconnect it?
This is with my DUO connected:
So Com3 on mine is definitely correct.
To test the port, I run ComTestSerial, which is a freee
utility from http://www.microridge.com/comtestserial.htm
then on the main page, I turn RTS off or on to check PTT
Green means PTT off, red means PTT on.
With PTT off, I then then type "FA;" into the Local
Commands box then click Send. I get back the FA response
from the DUO.
So that tells me Com3 is working to the DUO and it is
responding correctly to the serial port commands.
We need to be certain that you are able to communicate on
the CAT port before we can get the audio working.
Anyone else with any other ideas about what the problem
could be, or if there are simpler ways to check COM
ports? Please do chip in if you have any thoughts.
PS: Nerds can use a DOS command to change VFO frequency
or send any other CAT commands which don't need to see a
C:\Users\smithn>copy con COM3
1 file(s) copied.
where the ^Z is either F6 or an actual control-Z, not the
char '^' then the char 'Z', to set the VFO A frequency to
28000.123kHz without faffing about with programs, but that
only works if the system settings for COM3 are set to
38400, N, 8, 1. You'll get a series of PTT on/off events
as the handshake defaults to use RTS etc
On 31/08/2019 13:00, Bill /
this is what I am getting:
On 8/31/2019 7:47 AM, Neil
Smith G4DBN wrote:
Let's see if we can fix this one bit at a time.
First step, let's find out if CAT is working at all.
Using the same COM port that works as a TS-480 in
HRD, and with no other programs running that might be
locking the COM port, confirm that the WSJT-X or
JS8Call settings are the same as worked in HRD. Should
be 38400, 8 N 1 as usual.
Now I'm going to assume that you are using the latest
JS8Call or the latest WSJT-X (so you have the current
Hamlib setup, which is built-in to those).
Check that you have the radio type set in the program
settings to Elad FDM-DUO in the drop-down box (don't
use TS480, the Hamlibn for that is buggy, the DUO
library functions are new and work perfectly)
Check that you are set to PTT using RTS on the same
COM port which worked OK with HRD for CAT. The rest of
the settings shouldn't matter at this point, but set
them anyway to Fake It split and USB mode so you don't
have to go back and fiddle with the settings later.
Assuming that is OK, and the settings are all
correct, click the "Test CAT" button.
If that doesn't go green within a second or so, we
need to dig further into whether something is stopping
the COM port from working, so stop at this point and
report your findings.
If it does go green, then click the Test PTT and see
if the rig goes to TX. If it doesn't, then check the
DUO menu 54 and the PTT is set to IN+RTS, then retry.
If that still doesn't work, you have a different
issue around the RTS line, so change the PTT setting
to CAT and try again.
So, now you either have CAT and PTT working, or just
CAT or neither.
Can you test and report on whether those settings
work in JS8Call and/or WSJT-X?
Next step is to get receive and transmit audio
working, but let's go one step at once.
On 31/08/2019 12:24, Bill /
Thank you for the reply,I had some
time to try to make it work but it still doesn't
not.I did everything as you showed in the screen
shots.I know all usb ports are working,Hrd and
logbook works as ts-480 and cw idier works as
ft-897.What you think I should try next? Bill /
On 8/29/2019 3:07 PM,
Neil Smith G4DBN wrote:
Good advice from Charlie. Get FT8 working with
WSJT-X first as there are more users out there to
ask for help.
I had never tried JS8Call, so I checked my setup
with WSJT-X first, then downloaded and installed
JS8Call with all defaults.
Set up looks like this:
I have TXIN on the DUO menus set to AUTO and PTT
set to IN+RTS.
When I hit Test CAT, it worked and went green (my
default COM port is COM3, discovered the way
Charlie suggested). Then I hit Test PTT, the rig
went on to transmit and the button went red.
For the audio streams, I normally use Virtual
Audio Cable wiht SW2 on receive, but for this
test, I picked the FDM-DUO audio device on TX and
I set the DUO menus for AGC OFF, AGC GAIN 1 and
AUX VOL about 6 to get the level in JS8Call
somewhere in the 30-40dB region on band noise. I
also messed with the gain on the Windows audio
device for the DUO to drop the gain a bit
Seems to work fine.
Much simpler for me to use SW2 and Virtual Audio
cable as I have multiple receive programs
listening at the same time to the virtual device
and don't want to playh with JS8Call, but it looks
like it is just the same to configure with the DUO
On 29/08/2019 17:33,
Charles Ristorcelli wrote:
Bill, IMHO start trying a more common digital
The nuances of setting and using JS8call are best
handled after getting some experience.
I suggest try WSJT-X and look at FT8.
As for com post selection, I am not certain the
root of your problem.
I have one suggestion that solved the problem for
other DUO users.
You did not specify your operating system, but I
will assume it is Windows.
Make sure your DUO is powered off, and get the
System display under Control Panel opened.
Take careful note of the USB ports listed.
Now power on the DUO and you should hear three
audio "pings" as the DUO drivers get loaded. You
will see ELAD samplers, the ELAD audio card, and a
com port appear with each ping.
Note that comport number.
That is the com port to your DUO.
73 de NN3V