Update from 0.93.1 to the latest version - any risks?
I am running the server on Linux Mint 19 for my printers and it never failed me. I see the new version is released. Is the update as simple as installing the package over the old one? Will it remember my printer settings, etc.? Or will I have to set up everything again? Is there any way to backup and reload the settings across these versions? Thanks.
Comments
Yes you update with autoupdater or just install the newer package. Configs are normally upgraded to new format adding new parameter but keeping the old one. As precaution make a copy of your printer xml config - also I never had this some users say that something changed. All other files are untouched but it might recompute timings for all gcode files.
Anyway, just download the latest version on our homepage and install the deb packe with
sudo dpkg -i failename.deb
and you get your update as well.
What could be the cause? In the older version I never got these and the only thing I did to the setup was just the upgrade with dpkg as suggested above. I have not touched any hardware, nothing.
Are always the same commands resend?
Does printer reset during connect?
I see you are using repetier firmware and due to line numbers these errors get detected on the fly without big delays. You might have gotten them previously as well. What is new that we now write:
Ignore due to resend: ok
but that is just for debugging and was previously just ignored. Important is that you do not have too much resends. But these are result of communication problems and outside servers responsibility. Different usb cable or baud rate can make them appear more often. Only thing where server might be responsible is when you have set input buffer too large. That would lead to errors due to loosing data before being read. In serial settings there is a wizard that tests different settings and error rate. But for quite a while the input size 127 should work well for repetier-firmware.
I will try the wizard - maybe I was getting these errors as you say, silently. It does not affect quality on easy prints, but may have some connection with an object I printed recently - too much curves and G-Code and therefore printer stops and blobs. I will also try the optimizations you suggest on this forum and get a better cable.
There was a time when arduino created 63 byte input buffers and when that causes no error compared to 127 I'd think this one is compiled with that. You can try M360 and if it is supported yous should see the buffer size in the answer. But in the end use what causes least errors. You can also try 80 byte so you use 63 byte in reality plus a reserve for emergency commands if supported. Just set 80 and try the active combination and see if errors are still 0.