Repetier Server very slow
HI all,
I am using Repetier Server on a Raspberry Pi 3B+ with a touchscreen and 2 printers connected to it, and it is unbearably slow the interface. When I click on any area of the screen it takes 4-5 seconds to receive the click. Is this normal?
I am using Repetier Server on a Raspberry Pi 3B+ with a touchscreen and 2 printers connected to it, and it is unbearably slow the interface. When I click on any area of the screen it takes 4-5 seconds to receive the click. Is this normal?
Comments
Wifi is not the best and if your wifi connection is slow and you have many data to transfer (webcam maybe even high res, show moves) that might slow down your browser. Also if you are printing it takes some seconds for changes like temperature/fan to take effect as they get send to printer in a queue and are executed when it's their turn, but the interface it self e.g. open menu or so should always be instant.
It is attached to the raspberry Pi 3B+ via the flat cable it comes with.
I am using an internal IP web address to access it. but again via PC is fine, but via the touchscreen is incredibly slow.
I have the same screen/pi combination and can scroll and navigate without bigger delays. Languages I use are german and english in case a translation makes a difference.
And if no process takes more then 20% cpu time in top the pi is not really busy and should react normally. If I click on one of the menu items the new screen is visible in felt 0.5 seconds.
You could try connecting it to a ethernet cable just to see if it depends on connection quality.
I am using Repetier Server Pro 0.93.1 on a Raspberry Pi 4B+ with a touchscreen and 1 printer (Rumba Board) connected to it. Printing starts normally. After about 30minutes the printer becomes verry slow. If I now click "Pause" after a few minutes it goes to nurmal. What could I do? Thanks for your help and Greetings
Also when it happens have a look at your console and see if you are getting communication errors with the slowdown.
A general slowdown can happen if the speed multiplier is changed, but that normally requires you to change it unless it is in the gcode you send.
One exception is when you have many very short moves in a row then firmware can not speed up to final speed. Similar can happen when a ok" was missed - this would reduce transfer speed until a timeout happens or firmware sends a ok with line number (which marlin normally does not do with default config). Then small moves can also lead to reduced buffer usage also preventing optimum speed. But longer moves would still be fast.