Date   

Re: TUNING NOB PAINT

Matthew Phillips
 

Mine also has the problem.

A while back someone posted this:

41mm Silver Aluminum Knob | For Precision Instruments (lovemyswitches.com)

For the price I plan to buy this.

Matthew G6WPJ


Re: FDM-S3 dll for HDSDR

Paul
 

Hi Vianney,

Do you still estimate the extio.dll might be available by the end of this month?

Paul


Re: TUNING NOB PAINT

Pez T
 

I purchased an FDM-DUO that had paint scratches on the front of the knobs. My solution, was to remove the knobs and gently sand the front faces back to bare metal using fine Scotchbrite sanding pads. I am very happy with the result! :) 

 


Re: ELAD REMOTE 1.79 #linux #duo-art #wsjt-x

Pez T
 

Thanks Giovanni,

 

Yes I am aware of this, I already use Splashtop for this purpose, however I was asking more about the possibility of something like this (SW2 server/cleint, or a IP remote hardware interface) being on the future development roadmap? If not, that's OK, but I wanted to ask. 

 

Regards


Re: TUNING NOB PAINT

Simon
 

You could just paint it with a rattle can silver,( very light coat.) then a flash of rattle can laquar..see what it looks like and repaint it again when that wheres off next year...but even that will cost £20 from halfords or similar. Cost of new may be cheaper!

Simon g0zen


Re: TUNING NOB PAINT

Richard Meal
 

Thanks Simon - appreciate your thoughts.

Might reach out to Elad to see how much a replacement knob would be.

Richard  M0RGM 

On Sat, 14 May 2022, 10:38 Simon, <ohhellnotagain@...> wrote:
Hi

Whatever paint you use .(and yes 2 pack would be good, but then you need spray gun, compressor and min order is 1.2 l in uk.. abit over kill.)

But was getting at . BE very caretif removing old paint as any scratches in knob WILL show though new patand look crap.

I have considered asking Jeff my mate to knock up a solid ali one on his lathe for me..

Simon





Re: TUNING NOB PAINT

Simon
 

Hi

Whatever paint you use .(and yes 2 pack would be good, but then you need spray gun, compressor and min order is 1.2 l in uk.. abit over kill.)

But was getting at . BE very caretif removing old paint as any scratches in knob WILL show though new patand look crap.

I have considered asking Jeff my mate to knock up a solid ali one on his lathe for me..

Simon


Re: TUNING NOB PAINT

Wesley Knox
 

I would recommend an epoxy-based paint (possibly a two-part) if your government allows it. It will withstand wear much better than regular enamel or lacquer-based paints. 

Wes
KB6PR 


From: EladSDR@groups.io <EladSDR@groups.io> on behalf of Richard Meal <mw0rgm@...>
Sent: Friday, May 13, 2022 12:36:22 PM
To: EladSDR@groups.io <EladSDR@groups.io>
Subject: [EladSDR] TUNING NOB PAINT
 
All,

Would welcome your views.  The silver paint on the indentation of my tuning knob has largely worn away.  I'm considering repainting it, but before I do, has any one has success doing this and if so, what paint did you use?

Thanks,

Richard M0RGM 


TUNING NOB PAINT

Richard Meal
 

All,

Would welcome your views.  The silver paint on the indentation of my tuning knob has largely worn away.  I'm considering repainting it, but before I do, has any one has success doing this and if so, what paint did you use?

Thanks,

Richard M0RGM 


Re: ELAD REMOTE 1.79 #linux #duo-art #wsjt-x

Giovanni Franza
 

To remote control SW2 you can use TeamViewer, that let you control all the Windows PC running SW2.
As previously said, to use ELAD Remote, the hardware and software used to communicate is built into DUO ART.
Regards,

Giovanni HB9EIK IU2PKP


Re: ELAD REMOTE 1.79 #linux #duo-art #wsjt-x

Pez T
 
Edited

Hi Giovanni / ELAD,

 

Is there any likelihood of an IP remote solution to control the FDM-DUO or FDM-SW2, that doesn't require the ART? Either as a hardware based add-on box, or a software based (FDM-SW2 IP server/client) solution? 

 

Thanks in advance!


View SWR in FMD-SW2

Pez T
 

Hi all, 

Is it possible to view SWR in the FMD-SW2 software? 

I am operating my FDM-DUO with FDM-SW2 remotely (via Splashtop Enterprise) and I really need to be able to monitor VSWR. 

I was expecting (hoping) the S-Meter graph to display SWR when in TX, but maybe that is not a thing? 

Thanks in advance


Re: CAT time outs with multiple WSJT-X connections

Peter Sumner
 

Hello Mike,
well I am now 8 hours in with three instances of WSJT-X talking to the ELAD SW2 software, no time-out errors seen and I must say it is satisfying to see it all working as I had hoped it would.  Monitoring JT65, Q65 & FT8 currently Woo Hoo

I ended up extending the timeout value in the JSON file structure you gave me to be 750, then set the "Poll Interval" time for CAT in WSJT-X to be 10 seconds (default is 1 sec)

It goes to show that it can be done but it needs some secret sauce to make it all come together.

Conrad, you do not need FLRIG if you want to make it happen :-)

Thanks once again for all that chimed in and a special thanks to Mike for his insight into HAMLIB.

Regards,
Peter, vk5pj


On Thu, May 12, 2022 at 2:05 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Sounds like the ELAD can't service the requests fast enough.

Put this into a file called "hamlib_settings.json" and save it in each WSJT-X directory where WSJT-X.ini is stored.

Default timeout for the FT897 is 200ms to 500ms might work...may have to increase it some more if you still see timeouts.

{
     "config": {
            "timeout": "500"
     }
}


Mike W9MDB


On Wednesday, May 11, 2022, 11:29:22 PM CDT, Peter Sumner <vk8zlx@...> wrote:


Hi Mike
 my reference to the "cannot service the request" is based on the fact that I can do a successful CAT test in WSJT-X on each of the 3 instances but then at random intervals each of the WSJT-X instances display a HAMLIB time out error retrieving the data for VFO A (from memory).  I can select the retry each time this occurs and WSJT-X carries on then showing the round CAT status button as green until the next error.

Each WSJT-X is set to use the radio type FT-897, baud rate 4800 (4800 baud was selected for no special reason).  I cycled through a large selection of possible suggested radio types, including the FMDUO type and TS-480 but only the FT897 seemed to work for me when controlling the virtual Rx.  If there is a better option for the radio type I am open to suggestions.

I need to do some more tests with just one WSJT-X instance and measure the time between errors and then add a second then third to see if it might just be related to CPU loading,as I am asking the i5 PC to do quite a bit with the SW2 software and 3 instances of WSJT-X all chewing up resources.

thanks for your input

Regards,
Peter, vk5pj


On Thu, May 12, 2022 at 1:41 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
What do you mean "cannot service the requests for status in a timely manner".

Are you getting a timeout error?  What rig setting are you using for the ELAD?

Mike W9MDB




On Wednesday, May 11, 2022, 06:42:48 PM CDT, Peter Sumner <vk8zlx@...> wrote:


Hello Michael (W9MDB),
 The ports in use here are not splitters as I have seen others try to use when connecting logging programs, they are pairs of virtual com ports, much like you do for a virtual audio cable.  One end of the pair to WSJT-X and the other end of the virtual com cable to the Elad software, in all I have three pairs so each copy of WSJT-X has a dedicated link to a virtual port that is set for each sub receiver in the SW2 software.

in my case 

(Wsjt-X -R RX2) set to com4   <-->  com5 on vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to com6   <-->  com7 on vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to com8   <-->  com9 on vRX4 in the Elad SW2 software

This does work for short periods of time but HamLib does not seem to be happy as it would seem the SW2 software cannot service the requests for status in a timely manner.

If I understand your answer correctly, your suggesting multiple copies of FLRIG as an intermediary step to the SW2 software for each controlling WSJT-X instance would satisfy the requests from WSJT-X for timely status updates and still allow for CAT control of the virtual RX?   I have used FLRIG only once before so will have to take some time to catch up on its operations.

(Wsjt-X -R RX2) set to <--> FLGIG #1 <--> vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to <--> FLRIG #2 <--> vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to <--> FLRIG #3  <--> vRX4 in the Elad SW2 software

Thanks for the input

regards,
Peter, vk5pj


On Thu, May 12, 2022 at 2:14 AM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
I assume ya'll are using a serial splitter to try and hook up multiple COM ports to the ELAD, right?

That's never a good way to do this.

There are two solutions
#1 Use FLRig
#2 Use rigctld

I recommend #1 as the GUI interface for FLRig allows very good rig control.
You hook up FLRig to the ELAD and then all the WSJT-X instances can talk to FLRig -- just like OmniRig works but with better rig control.
The 2nd option is to run rigctld to talk to the ELAD and all the apps then talk to rigctld.  -- No rig control GUI though.

In either case above you can set up other software like N1MM, ACLog, etc on a virtual serial port pair and use "rigctlcom-wsjtx" to set up a TS-2000 emulator on the other serial port.
So...for example N1MM does not know how to talk to FLRig or rigctld.  Let's say we have a virtual serial pair COM10/11.
rigctlcom-wsjtx -m 4 -R COM10 -S 115200
If using rigctld
rigctlcom-wsjtx -m 2 -R COM10 -S 115200

N1MM then connects to COM11 as a TS-2000 at 115,200 baud.  
The only software I know of that will not work this way is HRD and I have plans for a new utility to allow that one too.

Mike W9MDB


Re: CAT time outs with multiple WSJT-X connections

Conrad, PA5Y
 

Aha it was due to the filename length.

 

This works. But indeed the timing is flaky.

 

C:\flrig-1.4.5\flrig.exe --config-dir C:\flrig-1.4.5\S3_1

C:\flrig-1.4.5\flrig.exe --config-dir C:\flrig-1.4.5\S3_2

C:\flrig-1.4.5\flrig.exe --config-dir C:\flrig-1.4.5\S3_3

 

 

 

 

-----Original Message-----
From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Neil Smith G4DBN via groups.io
Sent: 12 May 2022 18:59
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

C:\Users\"Conrad PA5Y"\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\"Conrad PA5Y"\Documents\flrig-1.4.5\S3_1

 

should work.  Windows uses the backslash for directory separators for ridiculous historical reasons

 

From the command line, you can usually use a caret as the escape character,

 

C:\Users\Conrad^ PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad^ PA5Y\Documents\flrig-1.4.5\S3_1

 

or in Powershell, obviously it had to be different again and they use a backtick `

 

C:\Users\Conrad` PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad` PA5Y\Documents\flrig-1.4.5\S3_1

 

Bit too late to say "Never use spaces in a Windows username or you'll end up with a home folder which causes unquoted spaces failures".

 

See also C:\Program Files\some stuff\qqq.exe  which would first try to execute c:\Program.exe

 

Stunning piece of nonsense from the 1980s

 

Neil

 

 

 

 

 


Re: CAT time outs with multiple WSJT-X connections

Neil Smith G4DBN
 

C:\Users\"Conrad PA5Y"\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\"Conrad PA5Y"\Documents\flrig-1.4.5\S3_1

should work.  Windows uses the backslash for directory separators for ridiculous historical reasons

From the command line, you can usually use a caret as the escape character,

C:\Users\Conrad^ PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad^ PA5Y\Documents\flrig-1.4.5\S3_1

or in Powershell, obviously it had to be different again and they use a backtick `

C:\Users\Conrad` PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad` PA5Y\Documents\flrig-1.4.5\S3_1

Bit too late to say "Never use spaces in a Windows username or you'll end up with a home folder which causes unquoted spaces failures".

See also C:\Program Files\some stuff\qqq.exe  which would first try to execute c:\Program.exe

Stunning piece of nonsense from the 1980s

Neil


Re: CAT time outs with multiple WSJT-X connections

Conrad, PA5Y
 

I cannot delete the quotes, or rather I can but they are immediately restored.

 

So given what you suggested I tried.

 

"C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\flrig.exe" –config-dir C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\S3_1

 

This is a copy paste from the target box

 

Flrig starts but with the following error

 

Pathlength limitations? I thought that was a thing of the past. Maybe because my username Conrad PA5Y has a white space?

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Michael Black via groups.io
Sent: 12 May 2022 18:30
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

You don't need any quotes.  With what you have there it's treating whole thing as the path to an executable which it is not...therefore "not valid".

At most you use quote around the path to the exectuable only.

 

Mike W9MDB

 

 

On Thursday, May 12, 2022, 11:26:10 AM CDT, Conrad, PA5Y <g0ruz@...> wrote:

 

 

Hello all

 

At work today, as a test,  I created 3 instances of Flrig without any issue.

 

This is an example of what was in the target box

 

C:\Users\nxf27317\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\nxf27317\Documents\flrig-1.4.5\S3_1

 

This works fine.

 

So now I go home and create this:

 

"C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\S3_1"

Always with the " " which I cannot delete, it was not there on my work PC.

 

I always get the following error. Can anyone tell me what is wrong? I have tried manually creating the folders as well, this was not necessary at work. Feels like a permissions issue.

 

73

 

Conrad PA5Y

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:54
To:
EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

I do not see any indication that the Xmlrpc Client is connected.

 

More tomorrow, time for zzzz

 

Conrad

 

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:37
To:
EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Ah I see, I will give that I try.

 

Conrad

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of PF1JM via groups.io
Sent: 11 May 2022 21:29
To:
EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Not only that, you also need to change the default Xmlrpc port in Fldigi for each VRX
Each transceiver, or in this case VRX, needs its own, unique port number.
So if you have the default port number 12345 on VRX1, you might want to assign 12346 to VRX2, and so on.
In wsjt-x in the Radio tab, you pick FLRig as rig, Network Server 127.0.0.1:12345 and so on.

Jeroen PF1JM


Re: CAT time outs with multiple WSJT-X connections

Michael Black
 

You don't need any quotes.  With what you have there it's treating whole thing as the path to an executable which it is not...therefore "not valid".
At most you use quote around the path to the exectuable only.

Mike W9MDB


On Thursday, May 12, 2022, 11:26:10 AM CDT, Conrad, PA5Y <g0ruz@...> wrote:


Hello all

 

At work today, as a test,  I created 3 instances of Flrig without any issue.

 

This is an example of what was in the target box

 

C:\Users\nxf27317\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\nxf27317\Documents\flrig-1.4.5\S3_1

 

This works fine.

 

So now I go home and create this:

 

"C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\S3_1"

Always with the " " which I cannot delete, it was not there on my work PC.

 

I always get the following error. Can anyone tell me what is wrong? I have tried manually creating the folders as well, this was not necessary at work. Feels like a permissions issue.

 

73

 

Conrad PA5Y

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:54
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

I do not see any indication that the Xmlrpc Client is connected.

 

More tomorrow, time for zzzz

 

Conrad

 

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:37
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Ah I see, I will give that I try.

 

Conrad

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of PF1JM via groups.io
Sent: 11 May 2022 21:29
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Not only that, you also need to change the default Xmlrpc port in Fldigi for each VRX
Each transceiver, or in this case VRX, needs its own, unique port number.
So if you have the default port number 12345 on VRX1, you might want to assign 12346 to VRX2, and so on.
In wsjt-x in the Radio tab, you pick FLRig as rig, Network Server 127.0.0.1:12345 and so on.

Jeroen PF1JM


Re: CAT time outs with multiple WSJT-X connections

Conrad, PA5Y
 

Hello all

 

At work today, as a test,  I created 3 instances of Flrig without any issue.

 

This is an example of what was in the target box

 

C:\Users\nxf27317\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\nxf27317\Documents\flrig-1.4.5\S3_1

 

This works fine.

 

So now I go home and create this:

 

"C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\flrig.exe --config dir C:\Users\Conrad PA5Y\Documents\flrig-1.4.5\S3_1"

Always with the " " which I cannot delete, it was not there on my work PC.

 

I always get the following error. Can anyone tell me what is wrong? I have tried manually creating the folders as well, this was not necessary at work. Feels like a permissions issue.

 

73

 

Conrad PA5Y

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:54
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

I do not see any indication that the Xmlrpc Client is connected.

 

More tomorrow, time for zzzz

 

Conrad

 

 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Conrad, PA5Y via groups.io
Sent: 11 May 2022 21:37
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Ah I see, I will give that I try.

 

Conrad

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of PF1JM via groups.io
Sent: 11 May 2022 21:29
To: EladSDR@groups.io
Subject: Re: [EladSDR] CAT time outs with multiple WSJT-X connections

 

Not only that, you also need to change the default Xmlrpc port in Fldigi for each VRX
Each transceiver, or in this case VRX, needs its own, unique port number.
So if you have the default port number 12345 on VRX1, you might want to assign 12346 to VRX2, and so on.
In wsjt-x in the Radio tab, you pick FLRig as rig, Network Server 127.0.0.1:12345 and so on.

Jeroen PF1JM


Re: CAT time outs with multiple WSJT-X connections

Michael Black
 

Sounds like the ELAD can't service the requests fast enough.

Put this into a file called "hamlib_settings.json" and save it in each WSJT-X directory where WSJT-X.ini is stored.

Default timeout for the FT897 is 200ms to 500ms might work...may have to increase it some more if you still see timeouts.

{
     "config": {
            "timeout": "500"
     }
}


Mike W9MDB


On Wednesday, May 11, 2022, 11:29:22 PM CDT, Peter Sumner <vk8zlx@...> wrote:


Hi Mike
 my reference to the "cannot service the request" is based on the fact that I can do a successful CAT test in WSJT-X on each of the 3 instances but then at random intervals each of the WSJT-X instances display a HAMLIB time out error retrieving the data for VFO A (from memory).  I can select the retry each time this occurs and WSJT-X carries on then showing the round CAT status button as green until the next error.

Each WSJT-X is set to use the radio type FT-897, baud rate 4800 (4800 baud was selected for no special reason).  I cycled through a large selection of possible suggested radio types, including the FMDUO type and TS-480 but only the FT897 seemed to work for me when controlling the virtual Rx.  If there is a better option for the radio type I am open to suggestions.

I need to do some more tests with just one WSJT-X instance and measure the time between errors and then add a second then third to see if it might just be related to CPU loading,as I am asking the i5 PC to do quite a bit with the SW2 software and 3 instances of WSJT-X all chewing up resources.

thanks for your input

Regards,
Peter, vk5pj


On Thu, May 12, 2022 at 1:41 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
What do you mean "cannot service the requests for status in a timely manner".

Are you getting a timeout error?  What rig setting are you using for the ELAD?

Mike W9MDB




On Wednesday, May 11, 2022, 06:42:48 PM CDT, Peter Sumner <vk8zlx@...> wrote:


Hello Michael (W9MDB),
 The ports in use here are not splitters as I have seen others try to use when connecting logging programs, they are pairs of virtual com ports, much like you do for a virtual audio cable.  One end of the pair to WSJT-X and the other end of the virtual com cable to the Elad software, in all I have three pairs so each copy of WSJT-X has a dedicated link to a virtual port that is set for each sub receiver in the SW2 software.

in my case 

(Wsjt-X -R RX2) set to com4   <-->  com5 on vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to com6   <-->  com7 on vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to com8   <-->  com9 on vRX4 in the Elad SW2 software

This does work for short periods of time but HamLib does not seem to be happy as it would seem the SW2 software cannot service the requests for status in a timely manner.

If I understand your answer correctly, your suggesting multiple copies of FLRIG as an intermediary step to the SW2 software for each controlling WSJT-X instance would satisfy the requests from WSJT-X for timely status updates and still allow for CAT control of the virtual RX?   I have used FLRIG only once before so will have to take some time to catch up on its operations.

(Wsjt-X -R RX2) set to <--> FLGIG #1 <--> vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to <--> FLRIG #2 <--> vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to <--> FLRIG #3  <--> vRX4 in the Elad SW2 software

Thanks for the input

regards,
Peter, vk5pj


On Thu, May 12, 2022 at 2:14 AM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
I assume ya'll are using a serial splitter to try and hook up multiple COM ports to the ELAD, right?

That's never a good way to do this.

There are two solutions
#1 Use FLRig
#2 Use rigctld

I recommend #1 as the GUI interface for FLRig allows very good rig control.
You hook up FLRig to the ELAD and then all the WSJT-X instances can talk to FLRig -- just like OmniRig works but with better rig control.
The 2nd option is to run rigctld to talk to the ELAD and all the apps then talk to rigctld.  -- No rig control GUI though.

In either case above you can set up other software like N1MM, ACLog, etc on a virtual serial port pair and use "rigctlcom-wsjtx" to set up a TS-2000 emulator on the other serial port.
So...for example N1MM does not know how to talk to FLRig or rigctld.  Let's say we have a virtual serial pair COM10/11.
rigctlcom-wsjtx -m 4 -R COM10 -S 115200
If using rigctld
rigctlcom-wsjtx -m 2 -R COM10 -S 115200

N1MM then connects to COM11 as a TS-2000 at 115,200 baud.  
The only software I know of that will not work this way is HRD and I have plans for a new utility to allow that one too.

Mike W9MDB


Re: CAT time outs with multiple WSJT-X connections

Peter Sumner
 

Hi Mike
 my reference to the "cannot service the request" is based on the fact that I can do a successful CAT test in WSJT-X on each of the 3 instances but then at random intervals each of the WSJT-X instances display a HAMLIB time out error retrieving the data for VFO A (from memory).  I can select the retry each time this occurs and WSJT-X carries on then showing the round CAT status button as green until the next error.

Each WSJT-X is set to use the radio type FT-897, baud rate 4800 (4800 baud was selected for no special reason).  I cycled through a large selection of possible suggested radio types, including the FMDUO type and TS-480 but only the FT897 seemed to work for me when controlling the virtual Rx.  If there is a better option for the radio type I am open to suggestions.

I need to do some more tests with just one WSJT-X instance and measure the time between errors and then add a second then third to see if it might just be related to CPU loading,as I am asking the i5 PC to do quite a bit with the SW2 software and 3 instances of WSJT-X all chewing up resources.

thanks for your input

Regards,
Peter, vk5pj


On Thu, May 12, 2022 at 1:41 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
What do you mean "cannot service the requests for status in a timely manner".

Are you getting a timeout error?  What rig setting are you using for the ELAD?

Mike W9MDB




On Wednesday, May 11, 2022, 06:42:48 PM CDT, Peter Sumner <vk8zlx@...> wrote:


Hello Michael (W9MDB),
 The ports in use here are not splitters as I have seen others try to use when connecting logging programs, they are pairs of virtual com ports, much like you do for a virtual audio cable.  One end of the pair to WSJT-X and the other end of the virtual com cable to the Elad software, in all I have three pairs so each copy of WSJT-X has a dedicated link to a virtual port that is set for each sub receiver in the SW2 software.

in my case 

(Wsjt-X -R RX2) set to com4   <-->  com5 on vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to com6   <-->  com7 on vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to com8   <-->  com9 on vRX4 in the Elad SW2 software

This does work for short periods of time but HamLib does not seem to be happy as it would seem the SW2 software cannot service the requests for status in a timely manner.

If I understand your answer correctly, your suggesting multiple copies of FLRIG as an intermediary step to the SW2 software for each controlling WSJT-X instance would satisfy the requests from WSJT-X for timely status updates and still allow for CAT control of the virtual RX?   I have used FLRIG only once before so will have to take some time to catch up on its operations.

(Wsjt-X -R RX2) set to <--> FLGIG #1 <--> vRX2 in the Elad SW2 software
(Wsjt-X -R RX3) set to <--> FLRIG #2 <--> vRX3 in the Elad SW2 software
(Wsjt-X -R RX4) set to <--> FLRIG #3  <--> vRX4 in the Elad SW2 software

Thanks for the input

regards,
Peter, vk5pj


On Thu, May 12, 2022 at 2:14 AM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
I assume ya'll are using a serial splitter to try and hook up multiple COM ports to the ELAD, right?

That's never a good way to do this.

There are two solutions
#1 Use FLRig
#2 Use rigctld

I recommend #1 as the GUI interface for FLRig allows very good rig control.
You hook up FLRig to the ELAD and then all the WSJT-X instances can talk to FLRig -- just like OmniRig works but with better rig control.
The 2nd option is to run rigctld to talk to the ELAD and all the apps then talk to rigctld.  -- No rig control GUI though.

In either case above you can set up other software like N1MM, ACLog, etc on a virtual serial port pair and use "rigctlcom-wsjtx" to set up a TS-2000 emulator on the other serial port.
So...for example N1MM does not know how to talk to FLRig or rigctld.  Let's say we have a virtual serial pair COM10/11.
rigctlcom-wsjtx -m 4 -R COM10 -S 115200
If using rigctld
rigctlcom-wsjtx -m 2 -R COM10 -S 115200

N1MM then connects to COM11 as a TS-2000 at 115,200 baud.  
The only software I know of that will not work this way is HRD and I have plans for a new utility to allow that one too.

Mike W9MDB

321 - 340 of 20616