search

Pixelcontroller / f16v4_issues

F16V4 and F48V4 Issue Tracker
14 stars 0 forks source link

intermitted fault #21

Closed lesm2425 closed 2 years ago

lesm2425 commented 2 years ago

it started off with the controller freezing and having to reset it, on/off. this weekend it has started to have a sort of freezing every 4-8 seconds then continuing on. its a great controller but i have got the old fateful v3 and never had this problem. i am starting to think i should of staid with the v3.

dpitts commented 2 years ago

What build are you on, build 14?

lesm2425 commented 2 years ago

yes

------ Original Message ------ From: "dpitts" @.> To: "dpitts/f16v4_issues" @.> Cc: "lesm2425" @.>; "Author" @.> Sent: Monday, 13 Dec, 21 At 22:35 Subject: Re: [dpitts/f16v4_issues] intermitted fault (Issue #21)

What build are you on, build 14? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/21#issuecomment-992974991 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWPYTQZZGMFGSEEZKMJRJTUQZYM7ANCNFSM5J7KMFYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

lesm2425 commented 2 years ago

hi i am on build 14, i had problems sending video to you, i have posted it to you tube. replaced most of the ethernet cables and switch. 13 December 2021 - YouTube https://www.youtube.com/watch?v=NGlP7xurZiY

thanks les m

------ Original Message ------ From: "dpitts" @.> To: "dpitts/f16v4_issues" @.> Cc: "lesm2425" @.>; "Author" @.> Sent: Monday, 13 Dec, 21 At 22:35 Subject: Re: [dpitts/f16v4_issues] intermitted fault (Issue #21)

What build are you on, build 14? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/21#issuecomment-992974991 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWPYTQZZGMFGSEEZKMJRJTUQZYM7ANCNFSM5J7KMFYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

keithsw1111 commented 2 years ago

I cant tell from the video anything at all as I dont really know what it should have looked like.

A better approach to troubleshooting would be to capture logs. To do so.

  1. Install an SD card on the controller.
  2. On the settings page set the debug mode to SD Card and the level to debug and save it.
  3. Re-run the test getting it to hang.
  4. Download the log on the settings page.

This is actually not likely to give us everything we need which is where the more advanced debugging comes in.

  1. On the input page select one of the drop downs and choose "Dump Debug State" and save the page
  2. Reproduce the problem.
  3. While the problem is occurring be on the input page and hit the test button every 5 seconds during the hang.
  4. Again download the debug log.

If hung this latest test will prove whether it is actually hung or not and if it is why.

Given it recovers it does sound much more like a network issue but this troubleshooting will at least to some degree show if that is the case or not.

Another thing you could do is check to see if the packet counts increase on the status page while frozen. If they do then the controller is suspect ... if not then again network issues could be what is occurring.

lesm2425 commented 2 years ago

Hi Keith, Tonight when I get back from work we will check the packet counts when it's running. And install a sd card and do as you asked. I have got a small pi hat controller I only use on small display and I can try the same sequence on the parts of the display wear it was glitching. That way I no its not moisture problem ect. Regards  les murray Sent from my Galaxy -------- Original message --------From: Keith Westley @.> Date: 14/12/2021 04:52 (GMT+00:00) To: dpitts/f16v4_issues @.> Cc: lesm2425 @.>, Author @.> Subject: Re: [dpitts/f16v4_issues] intermitted fault (Issue #21) I cant tell from the video anything at all as I dont really know what it should have looked like. A better approach to troubleshooting would be to capture logs. To do so.

Install an SD card on the controller. On the settings page set the debug mode to SD Card and the level to debug and save it. Re-run the test getting it to hang. Download the log on the settings page.

This is actually not likely to give us everything we need which is where the more advanced debugging comes in.

On the input page select one of the drop downs and choose "Dump Debug State" and save the page Reproduce the problem. While the problem is occurring be on the input page and hit the test button every 5 seconds during the hang. Again download the debug log.

If hung this latest test will prove whether it is actually hung or not and if it is why. Given it recovers it does sound much more like a network issue but this troubleshooting will at least to some degree show if that is the case or not. Another thing you could do is check to see if the packet counts increase on the status page while frozen. If they do then the controller is suspect ... if not then again network issues could be what is occurring.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

lesm2425 commented 2 years ago

Hi Keith, I sorted the problem. I been a total dumb ass I had the setting completely wrong in fpp outputs it was in multicast not unicast. You live, learn and try to not panic.Sorry for all the trouble.Regards les murray Sent from my Galaxy -------- Original message --------From: Keith Westley @.> Date: 14/12/2021 04:52 (GMT+00:00) To: dpitts/f16v4_issues @.> Cc: lesm2425 @.>, Author @.> Subject: Re: [dpitts/f16v4_issues] intermitted fault (Issue #21) I cant tell from the video anything at all as I dont really know what it should have looked like. A better approach to troubleshooting would be to capture logs. To do so.

Install an SD card on the controller. On the settings page set the debug mode to SD Card and the level to debug and save it. Re-run the test getting it to hang. Download the log on the settings page.

This is actually not likely to give us everything we need which is where the more advanced debugging comes in.

On the input page select one of the drop downs and choose "Dump Debug State" and save the page Reproduce the problem. While the problem is occurring be on the input page and hit the test button every 5 seconds during the hang. Again download the debug log.

If hung this latest test will prove whether it is actually hung or not and if it is why. Given it recovers it does sound much more like a network issue but this troubleshooting will at least to some degree show if that is the case or not. Another thing you could do is check to see if the packet counts increase on the status page while frozen. If they do then the controller is suspect ... if not then again network issues could be what is occurring.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

keithsw1111 commented 2 years ago

All good.