Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Failed to read the device calibrations!

Failed to read the device calibrations! 15 Mar 2022 19:28 #1

  • torriens
  • torriens's Avatar
  • OFFLINE
  • Posts: 43
  • Thank you received: 1
Anybody knows this error dialog screen?
It pops up when starting expertsdr3
Where does it come from?
Attachments:
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 19:00 #2

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
Hallo I got same problem today as you have/had. Did you find any solution
sm6usu Svante
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 19:07 #3

  • torriens
  • torriens's Avatar
  • OFFLINE
  • Posts: 43
  • Thank you received: 1
No, not yet.
I got this message when updating to expertSDR3 latest version.
Till now I get no answers,..

I thought it could be a problem with my firmware 68.7 of the SUNSDR DX.
So I I am trying to update this.
Also no luck.
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 20:03 #4

  • W3FRG
  • W3FRG's Avatar
  • OFFLINE
  • Posts: 10
  • Thank you received: 3
I found that if I just turn the SDR2 Dx power on and only bring up the Start / Stop Gui for SDR3 V 12.1 SW and clk on the Firmware Manager, wheel in the lower right corner, it will ask for the FW update if needed.
Click on that and it should update.
GL Tom W3FRG
Last Edit: 17 Mar 2022 20:07 by W3FRG. Reason: update
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 20:23 #5

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
Ok I have the latest firmware 78.8 V3 0.12.1 and got same message . Before I get this message I tried to go from wifi to cable to my laptop. It worked for 1 our New stop and start then I get the fault message. Tried bt button on back and tranceiver flash green but will not start and give me the message Failed to read the device calibrations.. Help anybody
sm6usu Svante.
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 20:28 #6

  • torriens
  • torriens's Avatar
  • OFFLINE
  • Posts: 43
  • Thank you received: 1
Hmm, not working with me.
It does not come with a newer FW version.
Attachments:
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 20:45 #7

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
Hall again I just tried to reset with the rst to reset ip number and maybe more things but no luck Same message. the only different is that my tranceiver is update and had worked before .
svante sm6usu
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 17 Mar 2022 22:55 #8

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
:) Hallo again I have succed with that I can now start my tranceiver again. But the "fail to etc message" are still there when the tranciever window opens. But as soon I hit startbutton everything seems to work as nomal and failwindow dissapears. I have to look more tomorow. What I did was to go in to the ip number setup as I did when tranceveir was new. I put in the number and then hit ok started the tranceiver and it started. I have no antenna do to a storm but will put it up tomorrow again and see if everything is allright Had also sent a mail to the support. So we see what they say. Maybe something happen when I changed from wifi to cable connection with the IP numbers . Now it is time to go to bed
73 de sm6usu Svante
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 18 Mar 2022 16:24 #9

  • oz1ctz
  • oz1ctz's Avatar
  • OFFLINE
  • Posts: 17
  • Thank you received: 5
Hi Svante .
What happens if you press one of the tree buttons (see picture) . Default Read and Write . ?

I get calibration succesful . with all tree buttons ..

Maby if you press Default the correct data will be stored , and your fault go away ..

73 de Brian
sun1.jpg
The administrator has disabled public write access.

Failed to read the device calibrations! 18 Mar 2022 16:45 #10

  • torriens
  • torriens's Avatar
  • OFFLINE
  • Posts: 43
  • Thank you received: 1
YES!!

It did the job ;-)
Thank you brian.
The administrator has disabled public write access.

Failed to read the device calibrations! 18 Mar 2022 17:03 #11

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
Thank you I had contact with Roman today and he said exact the same.. Now I am back to my first problem with the tranceiver disconnct Today it worked 5 hours then disconnct and next stop was 30 minits after that. I am using a netcable today and no WiFi. Before FW 78.8 I did not had that problem it worked also with wifi all time. So testing is going on :unknown:
73 de sm6usu Svante
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 20 Mar 2022 12:33 #12

  • Svante
  • Svante's Avatar
  • OFFLINE
  • Posts: 48
  • Thank you received: 9
No disconnect in 24 hours :D Using WiFi and Log 4om last 8 hours. What I did? In windows controlpanel I take away V3 0.12.1 Then a new installation of V3 0.12.1 for the third time
After that I lower my powersupply from 14,0 volt to 12.8 volt . First running about 12 hours with no connection to wifi or netcable just the tranceiver no Log4om. This night or early morning 03.00 I start the wifi connection no problem and a couple of hours later I start Log4om I have also rise my voltage to 13,5 and I am happy with that. All is still working Also Stop and start all to see if it starts ok and it did.So far no problem . Maybe it is a limiter on the voltage? I dont know, but earlier I think the limit was 14.5 volt. Anyway I am really happy after several days struggle.
73 de sm6usu Svante
sm6usu
The administrator has disabled public write access.

Failed to read the device calibrations! 18 May 2022 00:26 #13

  • gotcha
  • gotcha's Avatar
I just discovered (today) that some third party software can cause this issue with both the sdr2 and sdr3 version of software. Don't know the technical particulars yet but do know when I uninstalled the latest software program I installed to my PC right before this started to happen to me, the problems went away completely when the software was disabled or uninstalled, either way.
This was completely reproducible 8 times in a row. I hate to say which software it was for fear of reprisals. I'll just say that it is one of the most popular remote desktop software out there. When uninstalled or disabled, the radio and expertsdr3 and expertsdr2 both worked just fine without any other intervention.
So you guys may want to investigate conflicts with ip addressing and ports and software code as a possibility of this problem. It was not a cable, router,or any other hardware issue in my case.
I hope this helps somebody.
Victor k4xtt
The administrator has disabled public write access.

Failed to read the device calibrations! 05 Aug 2023 13:20 #14

UPDATE: I pulled the power connector from the SDR2 Pro for a hard power reset, plugged it back in, then ran ExpertSDR2 (not 3) and upon opening it updated the firmware and now ExpertSDR2 is running normally. I'm going to wait a while before I try to install ExpertSDR3 again.

The ExpertSDR faq now has a section about this problem. It says the "Anydesk" program uses the ExpertSDR default UDP port of 5001 and causes a conflict. I don't have Anydesk installed and udp port 5001 is not in use except by ExpertSDR.

When trying to read or write the calibrations in ExpertSDR3 I get a "Failed to write calibrations" error. Get a "Failed to read calibrations" error too.
Last Edit: 05 Aug 2023 13:47 by robrob.
The administrator has disabled public write access.

Failed to read the device calibrations! 05 Aug 2023 13:38 #15

  • Tom W3FRG
  • Tom W3FRG's Avatar
  • NOW ONLINE
  • Posts: 51
  • Thank you received: 8
i recently posted this same anomaly.
I don't know the cause, but I ran "SFC" in the Command Prompt and it appears to have cleared up the issue.

Run the "Command Prompt" as Administrator.
This will appear on your screen:
C:\WINDOWS\system32>
Type in "sfc /scannow"
Leave a space after sfc.

Tom W3FRG
Attachments:
Last Edit: 05 Aug 2023 13:40 by Tom W3FRG. Reason: Add file
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.105 seconds