-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xLights Scanner crashing when trying to scan for Falcon F16V5 v1.03 #5106
Comments
Wha thappens if you hist Discover? Make sure you are on the latest 2024.20 version. |
I installed 2024.20 just now and get the same issue. |
Discover on the left side above FPP Connect on the Controllers tab |
When I do the discover, I get a crash inside xLights |
I now disconnect the ethernet cable going to the Falcon and do the same thing and get no crash at all. |
Can you update the firmware to .36. Logs show you are on .32
|
Updated firmware to 36, an |
When I use xScanner64, I can see that it recognizes the ip address in the list when it is initially populating. But, to me, when it starts trying to populate the names/description of each device, that is when it crashes. |
@keithsw1111 Adding Keith .. hoping he has some insight on the discovery process of the V5. |
Turn on AutoSize and FullxLights Control. |
Can you come see us in the zoom room? xlightszoom.com |
Stupid rookie move on my part. I have another device (one of my matrix's having the same ip address. Once i changed it to another ip address, I now have the visualize and upload output options available. |
I have assembled a new Falcon F16V5 v1.03 in an enclosure. I have powered it up and have both an wireless IP address as well as a LAN IP address displayed on the device. I can go in my navigator search bar and type the 10.0.0.86 and successfully reach the board. This is through he wired LAN port. I can make changes, view all the settings, etc for the Falcon.
The issue I have is when running the xLights Scanner to detect all things on the network, it crashes midway through the scan.
This happens with the Falcon still connected to the network with the same IP address as stated earlier (10.0.0.86). I can still reach this device through the browser still. I do get the debug report screen and will attach the zip file.
When I disconnect the Falcon from the network ( removed completely from the network, the xLights Scanner works as it should and detects all remaining devices on the network.
If I connect the Falcon back to the network, I again get the crash and debug report.
xScanner_dbgrpt-32764-20250109T180121.zip
xScanner_dbgrpt-24564-20250109T174952.zip
The text was updated successfully, but these errors were encountered: