OK so I am new to the SunSDR2pro but very much not to SDr or WSJT or virtual comports etc.
Problem is after an indeterminate amount of time ESDR2 either stops replying to WSJT-x or closes the comport
A disable / enable cycle of the CAT port (RX1) at the ESDR2 Options/CAT page restores comms for a period (this period has no particular pattern or timing that I can see)
I am running 1.3.1 Update 5
I have tried various Data rates - No change in the behaviour
I have tried different Refresh rates at the WSJT-X end - no change in the behaviour
I have tried the Same WSJT-X set up with different SDR software - behaves normally
I have attached a screenshot of the Options/Cat page inc the Log during the fault condition
Can anyone give some guidence on this, I did check for similar posts but nothing directly comparable that I found.

Regards

Jim, GI1CET

It would help to know what virtual com port software is being employed and what settings are used within it. Also show the Radio tab settings of WSJTx including the PTT method.

Erik
Will provide those shortly but it should be noted that both WSJT-X and the Virtual comports work perfectly with all my other SDR software including SDR Console, PSDRmrx etc etc so I would be very surprised to find the issue there!

Find attached the requested settings pages, things to note are:
1. i do not normally use PTT Via CAT as I use separate external sequencer and this returns PTT to the driver radio last.
2.nothing else has been changed in the setup here, which is running on W7 64bit

I would try a shorter poll interval. Yours is 6 seconds and I would try it at 1 second and see if that makes a difference. If not, let us know.

Erik

Already done, in fact I started with my normal setting of 1 Second & 57.6K and on having problems reduced the rate to 9K6 and then increased the interval to see if it made any difference but no change.
If it helps my professional background is in Radio comms and spent a lot of time with SCADA systems running every Serial system under the sun so very familiar with this area, interestingly it has been running today for approx 1 hour without fail (it will probably keel over immediately after I post this of course) which is one of the longest periods without interruption.
I am currently running on 28MHz testing the ADC input with a 2M G4DDK Anglian transverter and switching to the VHF monitoring the same beacon to compare results (both RF inputs fed from a 3db hybrid coupler) and I must say it's holding its own very well.

I will switch it to VHf and let it run for a period now to see if that triggers anything and report results.

Regards

Jim, GI1CET

Hi Jim.
Here you have my settings . It works fine for me on win8 , never seen it fail.
I use split mode because WSJT-X control my dobbler frequency on 23cm eme .

and I use a seperat comport to PPT via RTS .

I am very happy with the preformance , I run main RX on one wsjt-x and RX2 on an other wsjt-x at the same time , RX 2 is tracking the EME beacon on 23cm , and main rx is making QSO es.

GL de OZ1CTZ Brian

Brian

Many thanks for that good to hear there is another EME station on using one

Interestingly I just put it to 57K6 and it failed almost immediately, put it back to 9K6 and it worked for a few min then failed, which Virtual serial port emulator are you using ?

Jim

Hi Jim.
here is a picture of the com port emulator.., you can just cancle the boxes in the beginning , then it works fine without registration .

. Yes I see your logo pointing to the moon ..FB . .

there has been many posts about the display/waterfall on our RIG ..
It is not that bad at all. !
If you set the screen to show 30 khz of the band , and the waterfall rate to the slowest , when using JT65 you can se alle the activity , very close to what you se in WSJT on just a
few Khz..

73 de Brian.

I would recommend following the setup in the UMA. It is tried and tested and does not fail.

Erik

Many thanks for the hint, I ran it overnight using the Eterlogic VSPE and it ran without complaint, Really weird that my Eltima VSP Emulation doesn't run it quite happily, as this is the first issue i have had with it in a long number of years both professionally and for amateur purposes, Fascinating really and when I have more time i must run some tests to see if I can pin down the exact cause but in the meantime it's working fine so thanks again, I have ordered up a licence so I can run it as a service for simplicity.

Brian (OZ1CTZ), I now have the Waterfall display running reasonably to my satisfaction displaying about 70 KHz and outputting via the Skimmer function to MAP65 for monitoring (although there is a significant oddity in level sent to MAP65 depending on whether I am on 28 or 144) with narrow output going to WSJT-X for QSO use both via appropriate VAC channels.

Again thanks to both for the assistance and I have no doubt I will have a further number of questions

Regards

Jim, GI1CET

You are welcome Jim. I agree with you, normally the VSP Emulation runs just fine. One of those mysteries.

Regards,
Erik.

Jim, until you mentioned running VSPE as a Windows Service I did not know that it could be. This is a recent innovation and I had not checked for updates for a long time. So I installed the latest version but now may I ask if you have managed to create the Service? I have followed the instructions and copied the required command into a CMD box with admin privilages but the Service does not create connectors and splitters on boot. In fact I am sure that the Service has not been created. I must be doing something wrong. Did you have success with it?

Erik.

Erik
It only works for registered / paid for copies, it wont work if you have the registration pop up occurring.

Mine runs fine and auto starts on boot up

Regards

Jim

Mine has been registered for years I will try again...

Erik.

You may have to go into service from windows and start the service, rather than from the command line, the install of the service works fine from the command line but I had to go into services and start the service and set it for autostart, the commandline seemed to time out, this was on W7 64bit

Jim