Welcome, Guest
Username: Password: Remember me

TOPIC: Can't read calinration - ERROR MESSAGE!

Can't read calinration - ERROR MESSAGE! 27 Mar 2021 16:29 #16

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 624
  • Thank you received: 294
A/V = Antivirus software?
73 Rick
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 27 Mar 2021 16:56 #17

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
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 27 Mar 2021 21:00 #18

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
I hope it stays fixed. MB1s suffer the same issue and they do not use ethernet cable.
Last Edit: 27 Mar 2021 21:12 by g0cgl.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 27 Mar 2021 21:18 #19

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 624
  • Thank you received: 294
Eric are they not connecting the Motherboard external NIC tot he radio boards via ethernet inside the rig?

Also SDR4ME thanks for the update- Packet loss or packet collisions are a nightmare and cause a lot of issues.

Bad switches and cheap switches- and crappy cables are around - I always make my own cables and use my cable tester to check crosstalk
73 Rick
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 28 Mar 2021 07:21 #20

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
It is hard wired, loss would be non-existent. Still, could be two different causes as MB1s get only one of the errors and not both.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 28 Mar 2021 12:38 #21

  • G3XLG
  • G3XLG's Avatar
  • OFFLINE
  • Posts: 156
  • Thank you received: 30
I turned off the Antivirus (a new part of Acronis which came on recently) - still no connection between the PC and the radio.
So, I decided to start again with the default IP address 192.168.16.200 but was unable to reset it using Device/Expert/New IP address presumably as no connection to radio?

Then decided to try the RST Reset button to get to the Default IP address. Pressed RST, got the flashing Red/Green light which changed to steady Green but still had not changed to the default IP Address.
So decided to do the Deep Reset using the LW and RST buttons together, got the flashing Red/Green which changed to a constantly flashing Yellow light,.not to the constant Green light

Any ideas guys for What Now? Will ask Roman tomorrow I suppose.
Ray G3XLG
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 28 Mar 2021 14:51 #22

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
I don't know, Roman will. This is the stated procedure:

a. Switch off the transceiver with the PWR button
b. Press and hold the L/W button on the rear panel of the transceiver (you will hear a light click),
switch on the transceiver with the PWR button. The LED will blink.
c. Release the L/W button
d. Open ESDR2 software and open Options-> Device menu, Expert tab and press Firmware
update.
e. After firmware update is finished, LED will turn to constant green light.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 28 Mar 2021 15:19 #23

  • G3XLG
  • G3XLG's Avatar
  • OFFLINE
  • Posts: 156
  • Thank you received: 30
I just tried that Erik.
Pressing the L/W button & then switching ON the radio brings the blinking Yellow light (as before).
Opening Options/Device/Expert & pressing "Firmware Update" brings the "Cannot connect to SunSDR2" message as before.
Thanks anyway, lets see if Roman has the answer?
Ray
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 28 Mar 2021 20:02 #24

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 624
  • Thank you received: 294
do you perhaps have another ethernet cable you can try?
And when you did the above- you did change your PC device IP address to the default address as well? hard code it into your IP address settings under Ipv4 - and restart the PC?
73 Rick
Last Edit: 28 Mar 2021 20:06 by N8SDR.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 06:55 #25

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
OK Ray, I am sorry. Please let us know the answer when you get it.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 07:00 #26

  • mir
  • mir's Avatar
  • OFFLINE
  • Posts: 51
  • Thank you received: 7
When the TRX is connected to PC and working short press the BT button, LED will change its color from yellow to green
73
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 11:41 #27

  • G3XLG
  • G3XLG's Avatar
  • OFFLINE
  • Posts: 156
  • Thank you received: 30
My thanks to Rick, Mir & Erik for your help
In my set up, I use the LAN sockets on the back of the router to provide a LAN cable from the Router to the PC and a separate cable from the router to the SDR. I tested these cables with a cable tester and they appear fine. I also use the PC for emails & the internet, which also work OK. I assume therefore the cable to the PC is OK. Just in case the other one to the SDR was faulty I changed it to another checked working cable..
A single click on the L/W button did indeed change the flashing yellow LED to green (thanks Mir)
I had not changed the IP address of the PC to the default value (Rick) so I did so and I now have the solid green LED and and the default address now appears as the SDR address in Options/Device BUT SDR Info has no info. Discover shows the default address Port 50001 and after clicking USE I expected the radio to work! I then clicked on the EESDR2 power button but I still get the "Can't connect to SunSDR2" message. So. I still don't know what is wrong.
Ray
Last Edit: 29 Mar 2021 11:43 by G3XLG. Reason: Typo
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 12:29 #28

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 624
  • Thank you received: 294
Ray

what happens if you click the Firmware button now as Erik mentioned above?

also is it possible on your router you may have a bad port- is another available in which you could plug in the SDR?
73 Rick
Last Edit: 29 Mar 2021 12:30 by N8SDR.
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 12:40 #29

  • G3XLG
  • G3XLG's Avatar
  • OFFLINE
  • Posts: 156
  • Thank you received: 30
Rick, I changed to another port on the router - made no difference.
With the solid green LED and the default address showing in EESDR2 I clicked the Firmware update button but got the same message "Can't connect to SDR".
I'm now beginning to wonder if there is a hardware fault in the SDR?
Meanwhile Roman has been in touch and said I should have my PC on sub-net 16 it was on 192.168.1.176 rather than 192.168.16,176. That also made no difference to connection between the SDR and the PC. I'm waiting now for his next suggestion - hopefully!
Ray
The administrator has disabled public write access.

Can't read calinration - ERROR MESSAGE! 29 Mar 2021 13:29 #30

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 1192
  • Thank you received: 474
A piece of probably unhelpful information: I didn't say so before but someone else has this trouble and contacted me last week. In his case it could not be ethernet cable related because he uses optical ethernet (two converters, one at router and one at SDR). He did not want to trouble Roman because of his unusual hardware. But essentially I saw that it was like Ray's configuration. I simplifed it to SDR to PC, did the procedure and it resumed working correctly. Then I followed my own advice I gave to the VK guy, to allow network access, and it is still working. So one happy camper.

So maybe take the router out of the equation and try again. If still failure, I would suspect SDR hardware fault as well unless other info transpires from EE.
The administrator has disabled public write access.
Time to create page: 0.120 seconds