News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15527
Latest: Murfdog510
New This Month: 35
New This Week: 23
New Today: 1
Stats
Total Posts: 127424
Total Topics: 15642
Most Online Today: 111
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 31
Total: 35

F16V3 Unable to connect to network

Started by jem5136, October 03, 2022, 06:52:28 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jem5136

I have an F16V3 that I've used for a few year. A couple weeks ago I was manually making some changes to the string ports and the controller went unresponsive. I tried to reboot, which it appeared to connect- it gave the static IP I set up but I couldn't connect to it. I tried flipping it to DHCP, got an 0.0.0.0 for the IP. I tried a factory reset- nothing. Reflashed firmware 2.59- still nothing. The board will boot, and it will begin counting uptime but the IP remains at 0.0.0.0. I've tried multiple Cat5 cables, all the other Cat5s work on other controllers so I know they're good, but I get nothing from this controller.

Any ideas? I feel like I'm missing something obvious.

k6ccc

As far as the 0.0.0.0 address when you set it for DHCP, is there a DHCP server on the LAN that the F16V3 is connected to?  For example, if the F16v3 is directed connected to your laptop, there is no DHCP server active on the LAN.  Can't answer the rest of it.
Good luck.
Using LOR (mostly SuperStar) for all sequencing - using FPP only to drive P5 and P10 panels.
My show website:  http://newburghlights.org

Jim

jem5136

Yes, forgot to mention that, it's connected to a dedicated show router which has a DHCP server enabled. 

JonD

#3
Network ports do go bad sometimes, but it is not common.  Assuming you have tried using both ethernet ports and not just one side or the other?

I would find a laptop and assign both devices a static ip address within the same network range.  (don't use the same ip for both of course) Disable your laptop firewall if applicable.  Take a known working patch cord, plug one end directly into the laptop, and the other end directly into the controller.  Bypassing all other switches and networking cables.  Try to ping the controller from the laptop.  If that does not work, remove the cord from the controller, and place it in the other network port and try the same.  My next step would be to reflash the controller, but it sounds like you have already done that.  Might not hurt to try a different SD card and re-download the firmware image, but not sure it would make a difference.

jem5136

Quote from: JonD on October 03, 2022, 05:52:09 PMNetwork ports do go bad sometimes, but it is not common.  Assuming you have tried using both ethernet ports and not just one side or the other?

I would find a laptop and assign both devices a static ip address within the same network range.  (don't use the same ip for both of course) Disable your laptop firewall if applicable.  Take a known working patch cord, plug one end directly into the laptop, and the other end directly into the controller.  Bypassing all other switches and networking cables.  Try to ping the controller from the laptop.  If that does not work, remove the cord from the controller, and place it in the other network port and try the same.  My next step would be to reflash the controller, but it sounds like you have already done that.  Might not hurt to try a different SD card and re-download the firmware image, but not sure it would make a difference.

I have tried both ports in my troubleshooting- same reaction. 

I have tried to connect directly as you suggested and pinging the controller- no response. I did try downloading the firmware and using a new SD card- it reflashed without an issue but I get the same results. 

Also, not sure if this is helpful, but the LEDs on the Etho port both flash on and off as the same rate, about once a second, while one the network switch I get no lights (as if nothing's connected to the port). 

JonD

If you assigned both devices a static ip, used a store bought working patch cable, you should be able to connect to the Falcon.  If you are still unable, sounds the Falcon has some issues.

If you are comfortable with the cable and ip addresses you have assigned, I am not aware of anything else to try.

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod