Author Topic: Upload Output to F48 bootloop  (Read 664 times)

Offline chassy33

  • Newbie
  • *
  • Posts: 3
    • View Profile
Upload Output to F48 bootloop
« on: June 11, 2020, 03:28:43 PM »
Not sure if xLights bug or Falcon bug. Everything works great on falcon F48. I can change any settings I want and no problems. My issue starts when I use the "Upload output" option in xLights to upload all my models. It only uploads the first 16 ports out of 48. So none of my props past port 16 work. then If I make any changes on the "Port Configuration" page on the controller, it reboots controller and then gets stuck in endless boot loop until I factory reset it. If I manually add my port settings i can add all 48 and change anything. I am running SW 2.55 on F48 and I tried both 2020.22 and 2020.23 in xLights.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Upload Output to F48 bootloop
« Reply #1 on: June 11, 2020, 04:15:58 PM »
Share your config and we can try to reproduce it.

Offline chassy33

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Upload Output to F48 bootloop
« Reply #2 on: June 11, 2020, 06:11:32 PM »
What all information do you need?

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Upload Output to F48 bootloop
« Reply #3 on: June 11, 2020, 08:53:52 PM »
Tools package logs. And which controller.

Offline chassy33

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Upload Output to F48 bootloop
« Reply #4 on: June 12, 2020, 07:20:31 AM »
I am using an F48 controller with firmware load SW 2.55.  I tried using both 2020.22 and 2020.23 but got the same result with both. I attached my package log files. let me know if you need anything else from me.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Upload Output to F48 bootloop
« Reply #5 on: June 13, 2020, 03:48:04 AM »
This should be fixed in .24