search

Pixelcontroller / f16v4_issues

F16V4 and F48V4 Issue Tracker
14 stars 0 forks source link

Firmware Upgrade Link Not Displaying #1

Closed Indigogyre closed 3 years ago

Indigogyre commented 3 years ago

Hello,

Upon booting the Falcon F16v4 controller I noticed that the link to upgrade the firmware was not available. The controller is connected to my every day network and received an IP without issue using DHCP. That did not seem to help so I decided to enter static network information and restarted the controller. This also did not seem to resolve the issue. The controller was then powered off completely and powered back up without any change. I connected to the controller from Chrome, Firefox and MS Edge Chromium with the same results.

I double checked and under settings the "Internet Access" option is turned on.

There is nothing within my network that would prevent the controller from connecting to the internet.

I've included screen shots of the various settings. ComputerBuild ComputerNetwork F16v4Banner F16v4Internet F16v4Network

Thank You, Dean

dpitts commented 3 years ago

HI

Not sure we have released new firmware yet.

Thank You,

David Pitts PixelController, LLC

From: Indigogyre @.> Sent: Monday, August 23, 2021 8:06 PM To: dpitts/f16v4_issues @.> Cc: Subscribed @.***> Subject: [dpitts/f16v4_issues] Firmware Upgrade Link Not Displaying (#1)

Hello,

Upon booting the Falcon F16v4 controller I noticed that the link to upgrade the firmware was not available. The controller is connected to my every day network and received an IP without issue using DHCP. That did not seem to help so I decided to enter static network information and restarted the controller. This also did not seem to resolve the issue. The controller was then powered off completely and powered back up without any change. I connected to the controller from Chrome, Firefox and MS Edge Chromium with the same results.

I double checked and under settings the "Internet Access" option is turned on.

There is nothing within my network that would prevent the controller from connecting to the internet.

I've included screen shots of the various settings. [Image removed by sender. ComputerBuild]https://user-images.githubusercontent.com/45136194/130544088-f5866393-9cb4-4b22-80eb-9d3c5b120a81.JPG [Image removed by sender. ComputerNetwork]https://user-images.githubusercontent.com/45136194/130544089-e803c1e9-ed39-43ad-b78b-ccb6cf092311.JPG [Image removed by sender. F16v4Banner]https://user-images.githubusercontent.com/45136194/130544091-417ae9f2-3e6a-43a5-86a8-197aa36dce41.JPG [Image removed by sender. F16v4Internet]https://user-images.githubusercontent.com/45136194/130544092-7db7dfa4-903b-41aa-b0f2-55edc5330ae7.JPG [Image removed by sender. F16v4Network]https://user-images.githubusercontent.com/45136194/130544093-da73804d-b6da-4eda-908e-1c8ca66f4929.JPG

Thank You, Dean

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v4_issues/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AARHOBFOSX6JJURWEYDF3WLT6L5AVANCNFSM5CV2JIQA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

keithsw1111 commented 3 years ago

It is released. He can download it from GitHub if necessary.

Sent from my iPhone

On 24 Aug 2021, at 12:40 pm, dpitts @.***> wrote:



HI

Not sure we have released new firmware yet.

Thank You,

David Pitts PixelController, LLC

From: Indigogyre @.> Sent: Monday, August 23, 2021 8:06 PM To: dpitts/f16v4_issues @.> Cc: Subscribed @.***> Subject: [dpitts/f16v4_issues] Firmware Upgrade Link Not Displaying (#1)

Hello,

Upon booting the Falcon F16v4 controller I noticed that the link to upgrade the firmware was not available. The controller is connected to my every day network and received an IP without issue using DHCP. That did not seem to help so I decided to enter static network information and restarted the controller. This also did not seem to resolve the issue. The controller was then powered off completely and powered back up without any change. I connected to the controller from Chrome, Firefox and MS Edge Chromium with the same results.

I double checked and under settings the "Internet Access" option is turned on.

There is nothing within my network that would prevent the controller from connecting to the internet.

I've included screen shots of the various settings. [Image removed by sender. ComputerBuild]https://user-images.githubusercontent.com/45136194/130544088-f5866393-9cb4-4b22-80eb-9d3c5b120a81.JPG [Image removed by sender. ComputerNetwork]https://user-images.githubusercontent.com/45136194/130544089-e803c1e9-ed39-43ad-b78b-ccb6cf092311.JPG [Image removed by sender. F16v4Banner]https://user-images.githubusercontent.com/45136194/130544091-417ae9f2-3e6a-43a5-86a8-197aa36dce41.JPG [Image removed by sender. F16v4Internet]https://user-images.githubusercontent.com/45136194/130544092-7db7dfa4-903b-41aa-b0f2-55edc5330ae7.JPG [Image removed by sender. F16v4Network]https://user-images.githubusercontent.com/45136194/130544093-da73804d-b6da-4eda-908e-1c8ca66f4929.JPG

Thank You, Dean

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v4_issues/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AARHOBFOSX6JJURWEYDF3WLT6L5AVANCNFSM5CV2JIQA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v4_issues/issues/1#issuecomment-904276110, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACOOXKDL35WFYO5NCQ6WR4LT6MBA7ANCNFSM5CV2JIQA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

keithsw1111 commented 3 years ago

Can you set your DNS to 8.8.8.8 to see if that makes a difference.

We can also turn on some logging:

  1. Place a SD card in the controller.
  2. On the settings page select Debug Mode SD Card.
  3. Set the Debug level to Debug
  4. Reboot the controller.
  5. Once booted go to the settings page and download the log
  6. Post the log here.

Once done you can disable the logging again.

Indigogyre commented 3 years ago

It will be about 6 hours before I can do any testing and get the log posted. Would you like me to capture a log with my current DNS setting also?

keithsw1111 commented 3 years ago

Either will be fine. I know 8.8.8.8 works for me but you can try both.

In the meantime you can download and install the firmware directly from the code page on github. Upgrading to build 3 will not impact any troubleshooting.

Indigogyre commented 3 years ago

Sorry it took so long to do the testing. Here is the debug.log file. debug.log

Would it also be possible to request some feature updates for the settings area? Maybe adding in a tools area so that basic network tools like ping, trace route and ns lookup would be available for troubleshooting?

keithsw1111 commented 3 years ago

So from the logs the DNS resolution is working:

000003599 380046c8 settings Resolving Update Server www.pixelcontroller.com. 000003621 380046c8 settings DNS www.pixelcontroller.com resolved to 50.62.138.205. 000003623 380046c8 settings Update Server www.pixelcontroller.com resolved to IP Address: 50.62.138.205. 000003623 380046c8 settings Connecting to Upgrade server. 000003681 380046c8 settings Connected to Upgrade Server.

At that point the log goes silent ... and it shouldnt ... something clearly was not right in the response ... but I am not sure what. I will need to enhance the logging to fix that.

There are a couple of other things concerning in the logs as well which I would also like to get to the bottom of.

For now if you want to reset your controller either via the OLED or by holding the select on boot that is likely to get you going again. I will include the additional logging in build 4. If your problems continue i will rush it out ... but if not i will likely hold it a few days to see if there is anything else worth including.

keithsw1111 commented 3 years ago

I am deliberately posting a separate response to the trouble shooting tools comment. It is a valid suggestion but not necessarily easy to do in a constrained hardware environment. Ping would definitely be nice. tracert too (as it is just ping with varying TTL values). NS lookup is a much bigger ask.

Indigogyre commented 3 years ago

So from the logs the DNS resolution is working:

000003599 380046c8 settings Resolving Update Server www.pixelcontroller.com. 000003621 380046c8 settings DNS www.pixelcontroller.com resolved to 50.62.138.205. 000003623 380046c8 settings Update Server www.pixelcontroller.com resolved to IP Address: 50.62.138.205. 000003623 380046c8 settings Connecting to Upgrade server. 000003681 380046c8 settings Connected to Upgrade Server.

At that point the log goes silent ... and it shouldnt ... something clearly was not right in the response ... but I am not sure what. I will need to enhance the logging to fix that.

There are a couple of other things concerning in the logs as well which I would also like to get to the bottom of.

For now if you want to reset your controller either via the OLED or by holding the select on boot that is likely to get you going again. I will include the additional logging in build 4. If your problems continue i will rush it out ... but if not i will likely hold it a few days to see if there is anything else worth including.

Hello Keith, There is no rush from my perspective.

Here is a twist for you. After doing the testing without any different results I decided to continue working with the controller to become familiar with it. It was configured in xLights which identified the controller without an issue and was able to setup some models. xLights configured the controller with ZCPP and it was able to blink some lights. After that, when I went to the interface screen the link for upgrading the firmware is now present.

I've changed the DNS address between the two with restarts and the link is still displaying properly now. I'm able to click the link and download the firmware update properly.

Let me know if you would like additional logs.

keithsw1111 commented 3 years ago

Well that sucks ... I was counting on the problem downloading the version.txt file as being something that would persist that we could test.

For now I will leave the ticket open. Feel free to repost logs after a reboot when build 4 comes out but from above I am guessing it is now ok.

Indigogyre commented 3 years ago

Thanks, I'll post the logs at that time.

Indigogyre commented 3 years ago

Hello Keith,

Here is my update.

  1. Manually upgraded from build 1 to build 3.
  2. Waited until build 4 was released.

The link for a new build is not showing up once more. Put the controller into debug mode like earlier post and captured the log.

I included the build 3 log and the build 4 log.

Thanks. Dean debug_build4.log debug_Build3.log

keithsw1111 commented 3 years ago

In this case it is deliberate ... I have not pushed out the link yet. What I can see from the log however is that it is retrieving the upgrade information for the prior version so I think it is working.

keithsw1111 commented 3 years ago

The version tag is now pushed but you likely wont see it as you upgraded manually ... so unless you downgrade to 3 it wont appear.

Either way I can see in the logs you have the upgrade info so I am going to close this as it is clearly working now and if someone else has the problem in future we now have additional logging to sort it out then.