CAT5 Ethernet failure after WiFi Install?

[K7ZS]

Hello

I recently installed the WiFi module in my early model 1258, which required the installation of the header.

The WiFi works, but now it will no longer work on the CAT5 Ethernet Interface?  I have set the IP Settings Eth-Type to AUTO, and IP-Interface to AUTO - PREFER ETHERNET.

I use a FIXED IP ADDRESS when here on the LAN (remote control station from other part of the house).  I get a steady PWR light, but no connectivity.

When I access the unit via USB interface, and it all looks right, except NETWORK NOT CONNECTED appears above the info.

What am I doing wrong, or is there a problem?

I am running firmware version 2.66

Thanks and 73

Kevin K7ZS

[dj0qn]

Kevin,

Not sure what your problem is, but try setting the RRC to use DHCP and see if
that works. Just a hunch.

73,
Mitch DJ0QN / K7DX

[K7ZS]

Hi Mitch

Thanks for the reply, but no joy.  I have tried this every which way possible, short of removing the WiFi unit entirely.

Under NO circumstances will the Control box connect via the wired Ethernet jack.  The cable is good, using it on another device right next to it.

Is there a hardware diagnostic to see if the on board ethernet has gone south? 

Both lights come on when the cable is plugged into the ethernet jack, but the front PWR light flashes infinitely.  Reconnect the WiFi antenna - BOOM, connects right away.  I don't see a way to DEFEAT the WiFi via software - am I missing it???

I am days away from a long, international trip, and I really need the wired connection for where I am going.

73 Kevin K7ZS


Any further thoughts much appreciated.

[Jan (Microbit)]

Kevin,

You could connect a serial terminal program(38400,N,8,1) to COM1 and log the printouts you get when booting up the RRC. You should get something like this:

==========================================
** 1258 Bootloader V1.9                 **
** Booting application                  **
==========================================
** Press capital x for xmodem apploader **
==========================================
Company   : Microbit
Product   : 1258
Version   : 5
HW        : 6
Software  : 2.69
Bootloader: 1.9
Compiler  : 4.6.2
Build     : Mar 13 2013 10:21:36
ROM/RAM   : 444944/56804
ethRAM    : 2944 (max 3kB!)
USBRAM    : 0
ResetSrc  : b [3]
Uptime    : 0
=========================
HW-device     = 0
CW-pot        = 1023
Debug level   = 0
Control panel = 0
Program mode  = 11 - Transparent, 2/4-wire
PID           = 4
Setup length  = 1224
=========================
codec = WM8985
silDetSet: 0 90
audio = BOTH_OPEN
duplex: New Audiocoding 108 (16 KHz)
phy = KSZ8041NL
phy = KSZ8041NL
eth, 10Mbit prefer mode, reneg. now!
eth link up (100FDX/MDI)
eth link lost
eth, 10Mbit prefer mode, success changing to 10Mbit!
eth link up (10FDX/MDI)
-------------------------
mac     : 00:1e:fd:01:86:9e
ip      : 192.168.136.79
netmask : 255.255.128.0
gateway : 192.168.128.1
dns     : 192.168.128.1
wifi    : module not present
-------------------------
Telnet: Listening on port 23
HTTP: Listening on port 80

the "phy = KSZ8041NL" and forward is when the RRC has found a LAN connection.

[K7ZS]

Looks like a hardware failure? I get both green lights on the ETHERNET adapter, and there is 'traffic' based on the left (innermost) LED flashing occasionally.

Here is my screen dump of the signon (antenna removed from WiFi to force ETHERNET)

==========================================
** 1285/1258 Bootloader V1.6            **
** Booting application                  **
==========================================
** Press capital x for xmodem apploader **
==========================================
Company   : Microbit
Product   : 1258
Version   : 4
HW        : 5
Software  : 2.66
Bootloader: <= 1.7
Compiler  : 4.6.2
Build     : Feb  5 2013 14:37:20
ROM/RAM   : 443952/56800
ethRAM    : 2944 (max 3kB!)
USBRAM    : 0
ResetSrc  : b [3]
Uptime    : 0
=========================
HW-device     = 0
CW-pot        = 1020
Debug level   = 0
Control panel = 1
Program mode  = 5 - TS480/TM-D710
PID           = 0
Setup length  = 1224
=========================
enable       : 1
speedWpm     : 0
iambic       : 2
paddleReverse: 0
weight       : 30
sideToneHz   : 700
sideToneDb   : 20
lfDelayMs    : 500
keyDelayMs   : 100
codec = WM8510
silDetSet: 0 90
audio = BOTH_OPEN
duplex: New Audiocoding 100 (8 KHz)
Wi-Fi not inited, normal init
Wi-Fi firmware 4.5.0
phy = KSZ8041NL
Ethernet link timeout, activating Wi-Fi
No matching Wi-Fi network

If I remove the WiFi module, might it work?

HELP!

73 Kevin K7ZS

[Jan (Microbit)]

You could also give removing the WiFi module a try just to see if it changes something.

[K7ZS]

Hello Jan

WiFi module Removed

ETHERNET CAME RIGHT UP.

So, they are MUTUALLY EXCLUSIVE??  That doesn't seem right?

Code snippet from boot log:

Wi-Fi not inited, normal init
phy = KSZ8041NL
eth link up (100FDX/MDI)
-------------------------
mac     : 00:1e:fd:01:80:2b
ip      : 192.168.0.227
netmask : 255.255.255.0
gateway : 192.168.0.10
dns     : 192.168.0.10
wifi    : module not present
-------------------------
Telnet: Listening on port 23
HTTP: Listening on port 80

[Jan (Microbit)]

Hardware isn't my "expertise", hehe, but when consulting with the others here we came to think that  when you "installed the header" something might have gone wrong? For ex. a short-circuit, which causes that strange behavior. Maybe you could examine the pcb and see if you can find something which looks suspicious?

[K7ZS]

Haven't use system for a while, but returning to the problem, here is all I can say.

Setting ETH TYPE to AUTO, ETHERNET PREFERRED will ALWAYS select the wireless, and if that is not available, system will not connect.  Turning the ETH TYPE to ETHERNET bypasses the wireless and will connect to the wired ethernet port.

SO

Contrary to the single reference in the documentation that AUTO will select ETHERNET if there is an available network connection on the ethernet port does NOT work here.

Otherwise, it works 100 percent as advertised.  I did remove the unit, nothing appears out of order in the way of solder bridges etc.

I have upgraded to latest firmware - no change.

Any further discoveries?

73 Kevin K7ZS

[K7ZS]

Spent some more time today on the issue of forcing the control unit to use the wired ethernet connecction with a WiFi module installed.

I finally found a way to set the firmware settings which will control whether or not Ethernet will be used if connected with the WiFi module installed.  (My last post inaccurately called the setting Eth-Type, but I was referring to the IP INTERFACE setting)

My findings:

1. If the IP INTERFACE option is set to ETHERNET, only a wired connection will be used even if wireless unit is installed
2. If the IP INTERFACE option is set to AUTO, and Eth-Type is set to AUTO, it will not use the ETHERNET interface if it is attached.  I have removed the antenna for this test, but it still 'sees' my wireless Access Point, but too weak to connect?  I cannot confirm that in the ABSENCE of a WiFi AP it will refuse to use the Ethernet interface.
3. If the IP-INTERFACE option is set to AUTO, and Eth-Type is set to AUTO-PREFER 10mbit, it WILL use the ETHERNET interface if it is attached, even in the presence of a WiFi AP.

So, at least I have found a way to use the wired interface without having to remove the WiFi module which was the only option I had before today.

Hope this helps someone else!

73 Kevin K7ZS

[Jan (Microbit)]

Thanks Kevin for your feedback! We will have a look here and see if there is something "funny" going on.

[Jan (Microbit)]

I have had a look at this now and here are my comments:

1/
There are only these two possible settings for 'IP-interface': 'Auto, prefer Ethernet' and 'Ethernet'.

2/
Using the settings 'IP-interface'='Auto, prefer Ethernet' and 'Eth-type'='Auto' works the same as 'Eth-type'='Auto, prefer 10Mbit' for me, that is if an Ethernet cable is connected the RRC will use Ethernet regardless of WiFi being installed and available.

So if that is not the case for you then something strange is going on.