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

TOPIC: Getting going - help!

Getting going - help! 14 May 2019 18:21 #1

  • G8VR
  • G8VR's Avatar
  • OFFLINE
  • Posts: 3
I've started to get going today with this radio. The software recognises the radio in "Discover" and you can get "SDR Info", which gives SN, version, PCB revision and the PLL:Lock but when you go to start the transceiver in the software you hear a relay click in the radio, but the button on the radio stays solid orange and where the button in the software has gone red briefly it changes back to black - nothing. Any ideas gratefully rec'd! Thanks
The administrator has disabled public write access.

Getting going - help! 27 May 2019 07:51 #2

  • G8VR
  • G8VR's Avatar
  • OFFLINE
  • Posts: 3
Ok, I've resolved this now. Basically the firewall allows the software to check the radio, but not to start it, which foxed me. Once firewall privledges were corrected it started to work. It looks great, but on my i5 laptop with 8gb of memory it uses 50 of the CPU and when running it and JTDX together, it can top out at 100% and it's not good. I would have thought an i5 would run it easily - apprently not, well not on my laptop and there is next to nothing on it.
The administrator has disabled public write access.

Getting going - help! 27 May 2019 08:07 #3

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
If you are running a 64bit OS, ensure you also have the 64bit version of ESDR2.

If you are running a 32bit OS, change to 64 bit.

If you are running version 1.3.0 Beta 1, try 1.2.0 instead, either 32bit of 64bit as your OS dictates.

Also if you can increase RAM then go to 16GB.

My 64 bit i5 laptop will not run 1.3.0 Beta1 with ESDR2 for SUNSDR2Pro and JTDX - but will run 1.2.0 and JTDX. I did advise EE but apparently 1.3 has to be CPU intensive.

If you are on 64bit and 1.2.0 then there should not be an issue and the problem could be somewhere else like video hardware having inadequate RAM and using CPU RAM instead.

Erik.
The administrator has disabled public write access.

Getting going - help! 30 May 2019 16:32 #4

  • G8VR
  • G8VR's Avatar
  • OFFLINE
  • Posts: 3
Erik
This is really helpful - thank you and useful I suspect for others too.
It is 64bit with 1.3.0 Beta1, so I will change to 1.2.0 and see how we go.
73's Kerry G8VR
The administrator has disabled public write access.

Getting going - help! 31 May 2019 07:06 #5

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
OK Kerry - and please do let us know how you get on. If you have continuing problems, do not suffer in silence. Report it here or email Roman directly at EE. He is very helpful.

Erik EI4KF / G0CGL.
The administrator has disabled public write access.
Time to create page: 0.077 seconds