I have a Sunsdrpro2 running ok on this computer with SDR version 2

When I install version 3 and start I get a very strong pulsating wide signal going up to -20 dBm at 1/4 of a second rythm.....

other buttons seem ok and working but RX is getting crazy.


any ideas ????

Hmm I think I kind of get it. One apparently MUST also upgrade the firmware to run version 3

not clear from the manual....

dumb me...

PS: changing IP to do this is a pain in the ass for a radio that is located far away....

Ok I managed to get the update to the latest firmware version and went to V3 and all works on my network apart from the fact I have no audio, also not when I click on output to soundcard.

I am running on port 49999 if it matters.....

Any hints ???

Hi
By changing sampling (39Khz, ...) on the left-bottom corner of the software, and back to your own settings, you can fix temporaly the issue.
May be next time you will start the software, it could be OK or not...

Here I have such behavior on RX2 only, and no idea where it comes from (Firmware, software ?)

73 - P@t

I am playing now like 3 days with the remote and I can testify for sure there are serious issues wuth the audio interface to windows.

Line output usually works but whem I try to set my Windows mapper to bluetooth headset or whatever nothing works any more.

Only MME windows mapper in and out usually works but only after completely starting EESDR3. It looks like EESDR3 captures the state of audio at startup and anything changed in windows afterwards he cannot catch. And there is something weird going on the moment you try to use bluetooth. Then suddenly the whole selector box of audio devices becomes empty.

I wonder what interfaces EESDR supports apart from MME. On remotehams I use windows directsound with great success.

Pedro