Thank you for your prompt replies.
Well, I have changed over to the same subnet (192.168.1.0) but then EESDR2 does not see the rig, whatever IP I assign to my laptop and trying out two different ethernet-to-USB C adaptors. It does not discover it and it does obviously not connect to it.
SOLUTION: disconnect the WiFi.
- I did not know that I could not have several IPs, one for each NIC my computer has.
- As my WiFi connection connects me to this subnet which is controlled by my router, it seems that then it avoids connection via ethernet to avoid conflicts.
- Maybe another explanation I don't know about?
QUESTION: Is it possible to have a workaround and have direct connection with the same subnet as the WiFi connection and my home router?
I would like to test easily, without changing the rig's IP every time, with direct connection and router connection.
EMI problem:
YES, I have an EMI problem. If the ethernet cable is closer than 20 cm to the RF coax, then packets seem to get lost when send to the laptop, and CW sounds crappy (loosing dots and dashes). It is EMI, because it is power dependent. It only happens at full power (~100 W). I hear the proper transmission when plugging the headphones to the rig directly.
I am using the ethernet cable shipped with the rig, which I suppose is well shielded.
I have a bad grounding => have to work on this, but ground here is very bad and dry.
I will need to try some ferrites around the ethernet cables.
ANY suggestion will be very welcome.
Thank you fro your help and quick answers!