Hello,

Another ‘phantom’ problem – hope its something simple to solve.

After a ‘fresh’ reboot of PC and ExpertSDR2 (latest version) – I am getting “Can’t Read Calibration” Error message

After dismissing the message – by pressing OK – The message repeats once again

On the second ‘dismiss’ by pressing OK button – the message “Can’t start SunSDR2DX! Pops up.

After dismissing this message and then pressing POWER button once again in ExpertSDR2 – the message “Can’t connect to SunSDR2DX!” pops up again.

I powered down the SunSDR2DX and rebooted.

I rebooted PC and restarted the EXperSDR2 program.

I checked that the network connections are OK and connected to same WORKING network.

Still same problem!

I even reinstalled the ExpertSDR2 software – still same problem.

Any suggestions??

If this is the error to which you refer:




you should ask Roman to help you.

Yes!

Sorry I should have posted screen shot - but you hit nail on head!

Except my message does not include the word 'user' - just simply "Can't read calibration"

I see 'others' also had similar problem

I dread to ask what caused this to happen.

Don't tell me we need to reinstall firmware??

Thank you as always for your quick and on the money response!

Cheers

ROMAN? any suggestions for how to 'fix' this problem?

OK, maybe it is a different error that you have but just to be sure, and not cause more problems, I would email Roman directly as he does not always follow this user forum.

OK will contact ROME to discuss the problem.

However, I think I solved it.

I did a SunSDR2DX 'reset' to the default address 192.168.16.200
I then started ExperSDR2.
During Start - it asked me if I wanted to reset default configuration settings / profile - then I responded YES
Here I presume - it wrote the calibration data - which must have been corrupted.
I then set my local net IP address in ExpertSDR2.
I rebooted the SunSDR2DX and started ExpertSDR2 with the new local IP address.
I then loaded my old TX profile.
I then set-up my shortcuts
I then set-up my 'features' - programs to launch (log4OM2)
I then set-up my CAT control
Bingo - ALL back to working state before the fault.

The REAL QUESTION is what caused the "Can't read calibration error" problem in the FIRST place!
So we can avoid this from happening again ;-)

Hope this is helpful to others who experience same problem - but PLEASE be careful what you are doing - so you do not destroy the SDR or 'brick-it' up!

My Thoughts -
Since from your message the cant read notice first appears before the can't connect to radio message
Mt first thought is local database issues - not SUNSDR hardware related - however I could be wrong

So is something amiss on your local PC that is causing data corruption- perhaps a bit of RF possibly getting into computer? It doesn't take much to corrupt data.

What is the system- ram- Hardware CPU- is it overclocked or running at base CPU speed? -

Hi Rick,

NO it appears NOT to be the PC - i've tried this from 2 different PC's and SAME results.

The PC's are not near the TX - no RF nearby.

ALSO - my 'fix' from yesterday - post #5 - appeared to resolve this issue

BUT no such luck!

This morning when I turned 'on' the SunSDR2DX - same problem

Back to square 1

I am guessing here - but I suspect some kind of HW failure - perhaps NNVRAM - where the internal configuration settings are kept?

It simply cannot hold charge and retain the memory contents?

I SINCERELY HOPE I AM TOTALLY WRONG!

But still looking for a solution.

Sending message to ROME as suggested now.

Cheers

Just to clarify once again - I have made some screen capture(s) - to show the error messages

Here is the ORDER of the error messages

1. Cant read calibration - this is the FIRST error message





when you dismiss this message - by clicking the OK button you then get the 2nd message

2. Cant read user calibration - message





when you dismiss this message - by clicking the OK button you then get the 3rd message

3. Cant start sunsdr2dx - message





when you dismiss this message - by clicking the OK button you then get the 4th message

4. Cant connect to sunsdr2dx - message







Hope the above screenshots - give a little more clarity to the problem at hand!

Thank you

Hello Everyone,

My apologies for not posting sooner – I’ve just been defocused with some other non-radio issues.

It appears that I have found my problem and have ‘fixed’ it!

So here is a detailed description of how my problem occurred and how I went about to fix it.

1. Out of nowhere I simply started to get the “can’t read calibration data” as per my original post

2. I tried everything as described in my earlier posts

3. In the end – doing a full reset and reconfiguration – only fixed the problem temporally.

4. I even wiped my PC and reinstalled windows – with new latest version of ExpertSDR2 – this did not fix the problem!

5. I then cam to the conclusion that it cannot be a software problem, and started to fault find any hardware issues.

6. The first thing was to check my network

7. I started to do a ping test to my SunSDR2DX IP to see if there were any issues or packet loss

8. BINGO! There was considerable packet loss. At times there was 100% packet loss and at other times 25% - bottom line there was issues with the IP connection.

9. I then checked the CAT6 cable – to make sure it was OK – I have a network cable tested – the cable was 100% OK

10. This made me think if the cable is OK – why am I getting packet loss?

11. I checked my network SWITCH – it was also performing OK

12. This time I decided to get a much shorter CAT6 Cable – only 2M to connect to the SunSDR2DX from the network SWITCH

13. BINGO! There were NO packet losses – the network was 100% or with connection to the SunSDR2DX

14. This made me think – why the problem with the other Cable?

15. The other cable was 10M long – although this is OK and within the network SWITCH specifications (i.e. the switch is able to drive this length of cable) it appears that there was a problem is sustaining a reliable IP (electrical) connection.

16. This observation after considering my earlier attempts to ‘fix’ this problem correlates to earlier findings.

17. When I reset the SunSDR2DX and it defaulted to its default IP od 192.168.16.200 – I used a 2M CAT6 cable to connect to PC directly from SunSDR2DX – so there was no problem at all with IP packet loss – and the system behaved OK. It was not until later when I reverted back to the 10M Cat6 cable and connected to the network SWITCH – the problems started again.

18. All of these problems – can’t read calibration data, cant connect to SunSDR2DX – relate to a BAD IP connection!

19. So, identifying the packet loss / BAD connection to SunSDR2DX totally correlates to the problems experienced.

20. I tried to think why – all of a sudden – all this happened to occur – NOW and the system worked fine for over 1 month – with SAME connections and hardware?

21. I could not find a logical answer – other than that the system must have been operating at the ‘limit’ of its specification threshold??

22. I am not sure what is the ‘maximum’ drive capability of the SunSDRDX2 Ethernet interface ‘chipset’ / hardware? But my guess is that my 10M Cat6 cable must have been at its ‘limits’.

23. Shortening the Cat6 Ethernet cable from the SunSDR2DX to 3M solved the problem for me!

24. I then did a ‘fresh’ reset – reconfigured everything (from backup profiles) – including assigning a NEW IP address and then in the OPTIONS menu - > expert section WRITE to the internal NVRAM in the SunSDR2DX to save my configuration data!

25. My SunSDR2DX has been working fine - without any issues since this reset and using a shorter Cat6 network cable! I don’t have any packet loss – all is working fine!


This was a very strange problem – and in my case TOTALLY related to a bad IP connection – due to long cable and insufficient drive to maintain reliable IP connection from SunSDR2 to the network SWITCH

Hope ALL of the above information is sufficient for everyone who experiences similar problem – to solve their issues.

First step I would do is make sure the IP connection has absolutely no packet loss!

If you do have packet loss – then you MUST fix this FIRST – try to shorten the Ethernet cable / check to see if cable is OK or damaged?

I’m sure if your IP connection is 100% - you will not experience this problem!

Note to Roman / Vasily

Can you please check to see what is the specification for the SunSDR2DX (and others) ethernet ‘chipset’ / hardware in terms of the maximum cable ‘drive’?
I feel that 10M cable appears to be at its limit?

Or there could be some degradation is the ‘drive’ over time – as everything worked for a long period of time – before problems with IP connections started.

Just an idea – if we have some guidelines – then we can make sure Radio(s) are operated within their electrical specifications for Ethernet cable lengths!

Thanks, and take Care & Be Safe