search

dakboard / Hardware-OS

DAKboard Wall Display, CPU, and Raspberry Pi
25 stars 4 forks source link

Dakboard Screen Refresh #8

Closed DSO-side closed 3 years ago

DSO-side commented 3 years ago

I have two Dakboards. Each one is a screen connected to a Raspberry Pi with the Dakboard operating system loaded onto it so they boot directly into the Dakbaord screen. At times (Sometimes daily or more, sometimes once a week) I will pass the Dakboard and see a completely white screen with a "network couldn't be reached" error.

I think what must happen is the network connection is lost for a brief amount of time. If I click the raspberry pi off and back on immediately, it will boot right back up to the screen.

I'm hoping the dakboard software could be set to do that automatically. Ideally, a user could select a frequency, perhaps once an hour, perhaps once a day, to do a complete refresh of the system, so that if the screen info had been lost, it will then be refreshed automatically, without a physical turn of the raspberry pi switch.

Thank you! :)

maf1227 commented 3 years ago

I have the same issue. I did notice that if I change the DHCP timeout to a longer period it happened less frequently so I suspect it has something to do with the pi requesting a new IP address and getting the timeout when the IP release happens. I am not sure but try increasing your timeout to something like 7 days and see if it happens once a week. Not a solution but it seemed to help me have to unplug and plug back in less frequently.

DSO-side commented 3 years ago

Thanks so much for being in touch! :) And thank you for proposing a solution! ummm…. I have no idea how to do that though. lol

Is that something I could do even if I have the Raspberrypi set up with the Dakboard operating system? I know there is a way to enter terminal mode, even from the Dakboard operating system setup. Is that what I would have to do?

Thanks! :)

maf1227 commented 3 years ago

Check the DHCP settings on your router

cocarrig commented 3 years ago

Hi,

We are merging this issue into issue #23 . Please add any additional information you believe is necessary to issue #23.