4 ms·

Meh. That is true if you are selling thousands or more of an item, but for small companies, custom boards can be a nightmare. I worked for a company once that p

by fhood 8y ago

Meh. That is true if you are selling thousands or more of an item, but for small companies, custom boards can be a nightmare. I worked for a company once that put literally two full weeks of debugging into a problem caused by a flaky diode batch.

nottorp 8y ago
I'll raise you two full weeks of debugging and then the project got canceled because redesigning the board was needed and it was too expensive ;) I'm doing quite a few of low volume (mostly bussiness/industrial helpers) arm linux projects on Pis now. Some of them stay on Pis, if rebooting the board every 2 hours is feasible, some move to custom boards after the prototyping is done. Still, it's very nice to have an off the shelf documented board to start stuff on.
- HeyLaughingBoy 8y ago
  What issues have you seen that require a 2-hour reboot? Stability was one of my concerns with my last Pi project, so during development I basically never powered it off or rebooted (except to test power-up behavior) so I could see if I encountered any problems. No problems came up, but others' experiences are always good to learn from.
  - nottorp 8y ago
    Was it a project in a climate controlled area, like your home? Mine were in a factory, and after a while the stuff that they were supposed to connect to over USB simply vanished. A reboot (of just the Pi, not the other device) fixed it. So we just scheduled a reboot in 2 hours when the Pi started up.
    - HeyLaughingBoy 8y ago
      More or less: at home, but in a basement room with temperature swings. For the application it was fine: it was going to be used in a temp controlled environment anyway. My current project I'm thinking of using BeagleBone because I trust their temperature range specs. Is it possible your Pi was suspending USB as part of power management? I've had that problem with some other devices.
  - fhood 8y ago
    In my stuff we never did a two hour reboot, but we did do a daily one. Sometimes you just run into memory leaks some of which aren't even your fault.
    - nottorp 8y ago
      I don't know if they needed a two hour reboot, but the customer wanted to be sure. For sure they stopped seeing usb devices after less than 24 hours. It helped that they were just reading and transmitting some values every 10 minutes or so, the reboot didn't hinder that.

by fhood 8y ago

nottorp 8y ago

I'll raise you two full weeks of debugging and then the project got canceled because redesigning the board was needed and it was too expensive ;) I'm doing quite a few of low volume (mostly bussiness/industrial helpers) arm linux projects on Pis now. Some of them stay on Pis, if rebooting the board every 2 hours is feasible, some move to custom boards after the prototyping is done. Still, it's very nice to have an off the shelf documented board to start stuff on.

HeyLaughingBoy 8y ago
What issues have you seen that require a 2-hour reboot? Stability was one of my concerns with my last Pi project, so during development I basically never powered it off or rebooted (except to test power-up behavior) so I could see if I encountered any problems. No problems came up, but others' experiences are always good to learn from.
- nottorp 8y ago
  Was it a project in a climate controlled area, like your home? Mine were in a factory, and after a while the stuff that they were supposed to connect to over USB simply vanished. A reboot (of just the Pi, not the other device) fixed it. So we just scheduled a reboot in 2 hours when the Pi started up.
  - HeyLaughingBoy 8y ago
    More or less: at home, but in a basement room with temperature swings. For the application it was fine: it was going to be used in a temp controlled environment anyway. My current project I'm thinking of using BeagleBone because I trust their temperature range specs. Is it possible your Pi was suspending USB as part of power management? I've had that problem with some other devices.
- fhood 8y ago
  In my stuff we never did a two hour reboot, but we did do a daily one. Sometimes you just run into memory leaks some of which aren't even your fault.
  - nottorp 8y ago
    I don't know if they needed a two hour reboot, but the customer wanted to be sure. For sure they stopped seeing usb devices after less than 24 hours. It helped that they were just reading and transmitting some values every 10 minutes or so, the reboot didn't hinder that.