new F48v4-NS problems with direct Ethernet connection

[BirdingPix]

I have just received my brand new F84V4-NS (blue; build 24) from Falcon, and I am having issues with it's Ethernet connection over direct wire to 10/100/1000 auto-sensing Ethernet switches.  I don't use WiFi on any of my Falcon or FPP devices... everything is direct wired over Ethernet. 

The new F48V4-NS simply won't connect over Ethernet wire UNLESS I plug it into a 10/100 Ethernet Switch.
My F16V3 and RaspberryPi (FPP) have always been connected without issues to my existing 10/100/1000 Ethernet Switch on my Light Show board.   I simply went to add my new F48V4 and it just sits there with its Ethernet connector blinking as follows: BOTH green and orange connector LEDs turn on steady for about 1 second and then both go off, and then in a little over another second, they both turn on steady again for about 1 second; this repeats with a cycle of a little over 2 seconds forever.

I have tried 4 different brands of 10/100/1000 ethernet switches and the F48V4 acts the same with all... same problem.  Once I connect the F48V4 to any 10/100 ethernet switch, it immediately connects as expected at 100 Mbps.

Is there some problem with the F48v4-NS ethernet port with regard to choosing its port speed when connected to a 10/100/1000 auto-speed detecting switch?? 

(The way I was able to disable the F48V4 factory-default WiFi =ON was to finally connect to it over 10/100 switch and log into into browser user interface and turn off WiFi.)

Any ideas?

Dave

[JonB256]

Check your cable? Gigabit expects all 8 wires to have good, correct conductivity. 100mb and 10mb only needs 4 wires (the Orange pair and Green pair).

[camguy52]

I have had similar issues with my new F48V4-NS.  I changed out my older TP-Link 5 port switch for a newer Netgear 5 port switch and the problem seemed to go away.

Hope this helps,

Doug

[tbone321]

That looks like a bug in the F48's firmware.  It appears to be negotiating for a gigabit connection but is not capable of communicating at that speed.  The older 10/100 switches can't go that high and stop the negotiation at 100 where it has no problem.

[BirdingPix]

Of course  have tried lots of 'known-good' Ethernet cables... and also 4 different brands of 10/100/1000 Ethernet Switches (Netgear, tp-link, Linksys, Ubiquiti).  The Falcon F16V3 (v2.59) connects every time to the Gigabit dumb switches, whereas the F48V4-NS (blue hardware v1.01) (build 24) has never connected and exhibits the above described problem. 

In the meantime, I have swapped out my previously used 10/100/1000 Ethernet switch for a old 10/100 switch and the F48V4 connects immediately.

So it sure seems like a firmware issue with the F48V4, which most likely can be fixed with a new firmware release. 


Dave

[JonD]

Most smart/managed switches have the ability to force certain ports to connect at slower speeds.  If your switch is somewhat intelligent, you might be able to configure it to only allow a 100mb connection on the port the NS was connect to as a workaround.  Does sound like a firmware or software fix may be needed to resolve the issue.

[k6ccc]

Most smart/managed switches have the ability to force certain ports to connect at slower speeds.  If your switch is somewhat intelligent, you might be able to configure it to only allow a 100mb connection on the port the NS was connect to as a workaround.  Does sound like a firmware or software fix may be needed to resolve the issue.

Unfortunately most dumb switches do not have that capability...