Welcome, Guest
Username: Password: Remember me
*****PLEASE, CHECK ALL PREVIOUS TOPICS, BEFORE CREATING A NEW ONE! DUPLICATED TOPICS WILL BE DELETED!*****

TOPIC: VAC problem windows 2004

VAC problem windows 2004 23 Jun 2020 17:58 #1

  • Miguel
  • Miguel's Avatar
  • OFFLINE
  • Posts: 7
  • Thank you received: 1
Hello guys!!
I have problems with new windows 2004. I am use vac 4.15 on mb1 version 3,after install new update window 2004 my vac not decode more, also tx with noise., so any help?? May be EI4KF can help.
Many thanks

PY5HOT MIKE
The administrator has disabled public write access.

VAC problem windows 2004 23 Jun 2020 18:08 #2

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 833
  • Thank you received: 329
Hello Mike - maybe EI4KF can help. He will try. I recommend, if still problems after reading below, that you contact me on Skype if necessary.

My Windows 10 'upgraded' 24 April to version 2004. Immediately, I found that in JTDX/WSJTx/MSHV/Digirite that there was no decoding of FT8 nor FT4 signals. There were representations of signals on the respective waterfalls but they were not clearly defined. I could ‘fiddle’ with VAC settings and get to an imperfect fix but then I found that my transmitted signal was unstable with distortion and nothing I did would improve it. I know from my experience of many support requests over the past 4 years that what works for one person does not necessarily work for someone else, even when they are using similar equipment and software. So what follows is my route through to solving the issue with a note about a variance that was required when I assisted somebody else with the same trouble. I therefore cannot guarantee success.

I tried reinstalling VAC 4.15, the most successful VAC version to date and one that I had used for the past 4 years. That did not change anything. So, I completely uninstalled it, removing all registry entries, and installed it afresh. Transmit seemed ok and I had decoding again but not for long. On a subsequent JTDX restart I was back to the original problem. Nevertheless, it might be worth trying a total uninstall/reinstall of 4.15, if this is your version, in case this works for you (use Revo Uninstaller and remove all registry entries). You will need to create and configure VAC lines again.

Then I completely uninstalled 4.15 and installed VAC version 4.62. This is the latest version but this version has a history of failure in our ham radio environment with regard to poor transmit quality. For me, trying other VAC versions resulted in the same issues as 4.15 and only 4.62 offered the solution.

With a lot of trial and error, the necessary settings in 4.62 are:

1 'MS per Int' needs to be reverted to the default of 7 on the RX line (Line 1 if you have followed the UMA). Any less and receive is compromised just like 4.15. This does not stop you from experimenting with a lower number, 5 or 3 which theoretically gives less latency, but in my case 7 was best.

2 Transmit can be made clean by a) setting both 'Capture Port' and 'Render Port' to WavePci and b) setting 'MS per Int' to 10. Again, you can experiment with the MS per Int figure but I found occasional transmit problems occurred until I set it to 10.

VACnew.png


Note the Cable MS figures: VAC 1 = 7 and VAC 2 =10.

NOTE: When solving this issue for someone else, only VAC version 4.60 would work. I have no idea why this was. Its best settings were the same as the those detailed above. So, you may need to experiment with both 4.62 and 4.60. Anan SDR users with the problem have found, as I did, that only 4.62 will resolve the issue. I tried 4.60 myself but for me it did not help.

If you need to acquire 4.60 or 4.62, you need only refer to the email link that was sent to you by Muzychencko and amend the version number part to 460 or 462.

If you are taking advantage of the dynamic range of our SDRs, and using the JTDX 32 bit sample size version, then ‘Format range BPS’ should be 8..32. If you are using the normal 16 bit sampling JTDX or WSJTx etc, then the 'Format range BPS' should be 8..24.

You will know that your TX is optimised by checking it in the SDR audio Monitor, where it should sound clean without artefacts, and in the ESDR2 Signal Analyser.

signal.png

For another TX and RX check on optimisation, refer to the VAC control panel and reset counters on Line 1 and Line2. Run the digital mode software in TX and RX for a while and then check the VAC control panel for any Oflows (overflows) or UFlows (underflows). There should not be any or maybe just a low number which is acceptable.
Last Edit: 23 Jun 2020 18:08 by g0cgl.
The administrator has disabled public write access.
The following user(s) said Thank You: S58WW, R3IIN, Fernando_py1fr

VAC problem windows 2004 24 Jun 2020 02:08 #3

  • Miguel
  • Miguel's Avatar
  • OFFLINE
  • Posts: 7
  • Thank you received: 1
Hello Erik

thank you for help, all okey work now.

best 73

PY5HOT Mike
The administrator has disabled public write access.

VAC problem windows 2004 24 Jun 2020 23:46 #4

  • DK3UD
  • DK3UD's Avatar
  • OFFLINE
  • Posts: 25
  • Thank you received: 8
Hi Erik,

I had similar problems with VAC after Windows 10 2004 Update. I am using a rather old version of VAC (4.14), which was working without
any problems on my MB1.

I was experimenting and trying a lot with the VAC parameters, and I found out, that "Ms per int" seems to be very critical. I tried different settings
and came to a value of "10" for RX and also TX settings. That was the best solution for me. Now it's working fine again!

Thanks for your interesting report on this issue!

73, Manfred
DK3UD
The administrator has disabled public write access.

VAC problem windows 2004 25 Jun 2020 05:23 #5

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 833
  • Thank you received: 329
Hello Manfred, long time no hear and I hope you are well. I am glad you have a solution. I have never tried VAC version 4.14 so that is an interesting observation. I am loathe to experiment more than I already have because once VAC is working in W10 2004 it is best to leave it alone. We have Ms per Int at 7 for RX which gives less latency than a higher value.

I have now been made privy to communication between Muzychenko and Microsoft over this issue. It is quite a long debate, the end result being that MS intend to keep the W10 2004 changes as they are. It all stems from driver installation issues whereby the identification of the driver to the OS is not clear. VB Cable has the same trouble.

Erik.
The administrator has disabled public write access.

VAC problem windows 2004 25 Jun 2020 07:07 #6

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 833
  • Thank you received: 329
Incidentally, this issue highlights a long held opinion of mine (since 2016 when I was starting the writing of the UMA) that we should not be completely dependent on 3rd party applications for critical functions such as VAC. It would be so much better if ESDR2 had its own proprietary VAC, akin to Digital Audio (e)Xchange that Flex developed for SmartSDR.
The administrator has disabled public write access.
The following user(s) said Thank You: Fernando_py1fr

VAC problem windows 2004 25 Jun 2020 07:17 #7

  • Rome
  • Rome's Avatar
  • NOW ONLINE
  • Quod Licet Jovi Non Licet Bovi
  • Posts: 694
  • Thank you received: 284
Hi, everyone.
That is why we created TCI.
JTDX developer plans to implement TCI, so you won't need VAC, I'm not aware of the terms, when it'll happen, but as far as I know it won't take long.
Роман, Roman
Expert Electronics
The administrator has disabled public write access.
The following user(s) said Thank You: Fernando_py1fr

VAC problem windows 2004 25 Jun 2020 07:43 #8

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 833
  • Thank you received: 329
Hello Roman. I have to say that we will need VAC. We need it for functions in ESDR2 such as Sound Card, Line Out, CW Skimmer. We need it for applications other than JTDX such as alternative FT8/FT4 programs, WSJTX for other modes, digital contest programs such as Digirite.

We need VAC; better would be an incorporated system or else we are at the mercy of constant upheaval as we have been in 2017 (VAC version 4.50) then 2018 (VAC versions 4.51 and 4.60) then 2019 (VAC version 4.61) and now in 2020 (VAC version 4.62, W10 2004, VB-Cable failure). TCI is genius, I hope it is implemented in JTDX, and it demonstrates your ability to evolve ESDR2 into a more complete package continuing with an EE proprietary VAC for your end users.
Last Edit: 25 Jun 2020 08:06 by g0cgl.
The administrator has disabled public write access.
The following user(s) said Thank You: Rome, Fernando_py1fr

VAC problem windows 2004 02 Jul 2020 06:55 #9

  • OK1NP
  • OK1NP's Avatar
  • OFFLINE
  • Posts: 10
I explored, that after lsat update I have exactly same problem like you guys (SunSDR2Pro). So my first test is set in 4.15 MS to 10 and at least it looks that for RX it helps, I have to test also TX.

Anyway thank you for help and manual, I will test it.

GL and best 73
Jan OK1NP
The administrator has disabled public write access.
Time to create page: 0.171 seconds