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: 15699
Latest: Nicole4Z
New This Month: 17
New This Week: 1
New Today: 1
Stats
Total Posts: 128634
Total Topics: 15830
Most Online Today: 44
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 5
Guests: 19
Total: 24

No network

Started by Steve_63, January 19, 2023, 10:58:47 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Steve_63

I have my controller in my garage so it is out of the weather and it has worked fine all year.  Yesterday I tried to connect to it to watch a Valentine sequence but couldn't connect to it.  When I went to the garage and looked at it I noticed that the eth0 IP was reset to 0.0.0.0 and the WiFi was reset to 10.58.0.1.  I have both set to manual IP set.  I did download and installed firmware v22 about a week ago, not sure if that is an issue.  Also, I noticed a large section of my lights on different ports are lit blue.

JonD

I would try resetting the controller and install the firmware again.  Many people skip the reset controller step and skip directly to the firmware update.  This can be problematic.  Even if you did reset the controller before the update, I would try it again.  Follow the directions exactly as it resolves a lot of issues.

Steve_63

Thank you for the information!  I will add that to my list of answers I'm keeping.  I contacted David Pitts at pixelcontroller and below is his feedback.  Apparently, I had firmware that was bad.  Once I reset my controller I was able to load an earlier firmware. 

I still have just one issue.  Each day my scheduled sequence should start each day but I have to reboot the Pi FPP because the either-net link gets broken from one day to the next.  Maybe I just need to do as you suggest and try the reboot again.

Here is my setup.
1. The Pi FPP is always powered up.
2. At 5pm my supplies and Falcon controller are powered up.
3. At 5:30pm the Scheduler starts the sequence.
4. At 10pm the Scheduler ends.
5. At 10:30pm the power supplies and Falcon are all powered down.

This worked flawlessly during Christmas but I've been having issues ever since I installed the bad firmware.

Thank you,
Steve

Hi
Please use build 21. 22 did have issues and we pulled it off Github a month ago so I am surprised you were able to download it.
Thank you,
David Pitts
david@pixelcontroller.com

tbone321

One thing that I would strongly suggest is NOT to update firmware unless you really need to.  As they say, "If it ain't broke, don't fix it".  Unless you are having a firmware related issue that is limiting or preventing you from using the device as needed, you really get no benefit from updating it but do get all of the risk of either bricking your device or going thru a whole lot of pain getting it working properly again.

JonD

Quote from: Steve_63 on January 30, 2023, 09:34:21 PMI still have just one issue.  Each day my scheduled sequence should start each day but I have to reboot the Pi FPP because the either-net link gets broken from one day to the next.  Maybe I just need to do as you suggest and try the reboot again.
If you're rebooting the Pi to resolve the issue, I would suspect the Pi is the issue not the controller.  Pi lockup and other issues are often caused by bad power supplies.  (Even if the power supply came directly from Raspberry)  Do you have another power supply you can try using for the Pi?

JonD

Quote from: tbone321 on January 30, 2023, 09:57:07 PMOne thing that I would strongly suggest is NOT to update firmware unless you really need to.  As they say, "If it ain't broke, don't fix it".  Unless you are having a firmware related issue that is limiting or preventing you from using the device as needed, you really get no benefit from updating it but do get all of the risk of either bricking your device or going thru a whole lot of pain getting it working properly again.
I don't upgrade every version if I am not having any issues, but don't like them to get too far behind either.  The V4 series has not been out that long, and there are already 22 versions of firmware.  I usually upgrade them once every couple of years to keep things current.  Problem is eventually there will be a feature or bug fix that you will want, and if you are upgrading from really old firmware you are more likely to run into issues upgrading.

Steve_63

Thank you for your feedback it is very useful to me.  I changed the DNS on my Pi to 8.8.8.8 before and switched it back to my home router IP last night and today the schedule started as usual (no need to reboot the Pi).  This goes along with your assessment that it is Pi related.

Support FPP

+- Recent Topics

Problem with one of my Remotes - syslog always starts with "soliciting.." by Jayl
March 28, 2023, 11:03:41 PM

F48v4-NS unable to connect to WiFi Hotspot by joeyblasko
March 28, 2023, 03:18:46 PM

F/S Arduino UNO R3 with extras by StickyWicket
March 28, 2023, 09:28:23 AM

DMX to pneumatic solenoid by deanathpc
March 27, 2023, 07:54:22 AM

Libre SBC with oled by mel4853
March 24, 2023, 04:04:06 PM

K8-Pi - Random Pixels on by cybercop23
March 24, 2023, 10:44:49 AM

Limitations on Video file size? by Jayl
March 23, 2023, 11:06:14 AM

FPP 7 Kubernetes Error by Jlwright325
March 22, 2023, 11:11:59 AM

FPP Install on Raspberry Pi Zero W by k6ccc
March 21, 2023, 05:53:50 PM

FPP install script on Ubuntu, no video by AlexanderMedia
March 21, 2023, 09:37:23 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod