Hi Mike,
This approach with 3rd party SW would add more complexity to WSJT-X's QSO
logging and new callsign indication, seems like we will have to use JTAlert
logging instead of WSJT-X in multicast configuration.
73 Igor UA3DJY
>Пятница, 4 декабря 2015, 18:46 -05:00 от Michael Black :
>
>
On 05/12/2015 00:24, Laurie, VK3AMA wrote:
The only reason that JTAlert is not using multi-cast is due to
limitations of the current JTAlert Compiler/Language. One of many
reasons (not to mention lack of multi-threading and async
functionalities) that JTAlert is being rewritten.
Understood Laur
On 5/12/2015 11:01 AM, Bill Somerville wrote:
The requirement for multicast support is so that other applications that
wish to receive notifications from WSJT-X can coexist with each other.
In other words a well behaved WSJT-X UDP protocol server should use
multicast UDP to be a good citizen, not
On 04/12/2015 23:46, Michael Black wrote:
> But that won't be available until next year some time since it's a
> complete rewrite of JTAlert. The current version can't support
> multicast so right now one JTAlert is needed for each WSJT-X.
Hi Mike,
that's not correct. A single unicast UDP serve
I do believe that ability is under development for JTAlert where one
JTAlert can manage multiple WSJT-X instances.
But that won't be available until next year some time since it's a complete
rewrite of JTAlert. The current version can't support multicast so right
now one JTAlert is needed for each
On 12/04/15 17:26, Bill Somerville wrote:
That is the latest and greatest. But that is a different error message
from the last one.
It is the same as the one I initially reported though. I suppose my
previous attempt may have had the 'mode' selected by mistake.
Please make sure you have
On 04/12/2015 17:21, Steve Brown [wsjt] wrote:
>> testing. Do you get the top left field labelled "USB Device:" when you
>> >select the Peaberry v2 in WSJT-X "Settings->Radio"?
> Yes indeed I do. I can leave it blank or fill it in correctly, it
> doesn't make any difference. I still get the error '
Hi Bill,
On 12/04/15 12:59, Bill Somerville wrote:
> testing. Do you get the top left field labelled "USB Device:" when you
> select the Peaberry v2 in WSJT-X "Settings->Radio"?
Yes indeed I do. I can leave it blank or fill it in correctly, it
doesn't make any difference. I still get the error '
On 04/12/2015 11:55, Bill Somerville wrote:
> I select 'AE9RB Si570 Peaberry V2' I just get an alert 'Rig failure,
> >unsupported CAT type'.
Hi Steve,
back at r6144 in the development branch I put in changes to WSJT-X to
allow custom USB devices like the Peaberry to be used. It may be that
there
This is the best Group !!
I also had issue with rig split. But, after I used better hamlib from jtsdk, it
works perfectly. I recommend jtsdk - it is great. All problems I had
disappeared. It takes care of all dependencies.
Take care to set correct port speed, parity and stop bits in Settings.
Hi Tomek,
What a lively and helpful devgroup this is!
On 12/04/15 12:01, Tomasz Wawer wrote:
> I had this kind of issue. The reason was, that my bandwidth filter
> was set to 100Hz.
Interesting. I hadn't thought of that, but I used Quisk to set the bw to
2800 and retried, and there was no chang
Hi Bill,
On 12/04/15 11:55, Bill Somerville wrote:
> thought the device control was just the mixer oscillator via USB and
> assumed the only audio I/O was I/Q.
I think that's exactly what it is, DDS for the oscillator.
> Are you on Windows?
Nope, Linux here :)
73
Steve
CT7ANL / G1WMD
Hi
I had this kind of issue. The reason was, that my bandwidth filter was set to
100Hz. The CAT was somehow baffled. Also, sometimes there was a zombie rig
control process left from fldigi. Try to see:
ps -ef| grep rig
Also you can try
fuser -c /dev/ttyACM0
or whatever port you use for you
On 04/12/2015 11:47, Steve Brown [wsjt] wrote:
> I just quickly built r6203 but when
> I select 'AE9RB Si570 Peaberry V2' I just get an alert 'Rig failure,
> unsupported CAT type'. I expect I missed an option during the build so
> I'll take a detailed look later when I have more time.
Hi Steve,
Th
On 12/04/15 11:24, Bill Somerville wrote:
> welcome to the group!
Thanks!
> How are you delivering audio from your SDR to WSJT-X. I ask because most
> SDR implementations that deliver conventional audio streams also
> emulated a CAT serial port, usually with some sort of Kenwood emulation.
Th
On 04/12/2015 10:29, Steve Brown [wsjt] wrote:
> I'm having issues with the CAT control of my 'AE9RB Si570 Peaberry V2'
> where a 'Rig failure' message with the detail 'Hamlib error: Feature not
> available while getting current VFO mode' when I use the 'Test CAT'
> button which makes control impos
Hello all,
New member to the group here. If this is the wrong place please would
you point me in the right direction.
I'm having issues with the CAT control of my 'AE9RB Si570 Peaberry V2'
where a 'Rig failure' message with the detail 'Hamlib error: Feature not
available while getting current
17 matches
Mail list logo
