Over the last few weeks I have encountered this numerous times, nothing major how ever it is annoying...
It involves a number of sharp MX machines, the latest of which I am sitting next to right now, which is an MX-4111N.
Now here is the issue, when first brought to life the machine responds as normal, how ever after executing a few simulations, it starts to become unresponsive. Slowly at first but with in 30 seconds or so I have to wait 5 - 10 seconds for the machine to even acknowledge me entering a numerical digit.
Originally I thought, seeing as it only seemed to happen in the workshop, (which can get quite cold) that it could be the environment. But when on site a week ago working on a 2310U in an office block, where it was almost uncomfortably warm, I had the same issue.
I have so far figured out that rebooting the machines does nothing to fix the issue, but updating the firmware seems to put it back in its place, though I am not sure how long for.
Does any one know why this happens? Its interesting it is only in simulation, and the updating of firmware fix suggests it is a software issue, rather than hardware struggling to process commands.
Any thoughts would be appreciated, purely out of interest
It involves a number of sharp MX machines, the latest of which I am sitting next to right now, which is an MX-4111N.
Now here is the issue, when first brought to life the machine responds as normal, how ever after executing a few simulations, it starts to become unresponsive. Slowly at first but with in 30 seconds or so I have to wait 5 - 10 seconds for the machine to even acknowledge me entering a numerical digit.
Originally I thought, seeing as it only seemed to happen in the workshop, (which can get quite cold) that it could be the environment. But when on site a week ago working on a 2310U in an office block, where it was almost uncomfortably warm, I had the same issue.
I have so far figured out that rebooting the machines does nothing to fix the issue, but updating the firmware seems to put it back in its place, though I am not sure how long for.
Does any one know why this happens? Its interesting it is only in simulation, and the updating of firmware fix suggests it is a software issue, rather than hardware struggling to process commands.
Any thoughts would be appreciated, purely out of interest