During print the LCD screen goes funky
Hi all.
I have been print fine for several weeks without much issues that I didn't create myself, but last night when I set to do a print the LCD screen went all funky.
It was going fine (I was in and out checking on it) when one time the LCD was showing all funky stuff (sorry didn't take a pic). It was printing fine and I was able to click the know and then go back to the info screen. The menu was fine and when I went back the main screen went back to normal.
I print from my PC and never had this happen. Not sure if its a fluke or what.
I'll be watching it tonight since I have work to do where the printer is.
Happen to anyone else?
Thanks
Re: During print the LCD screen goes funky
Yup, happens all the time, hence a firmware update which refreshes the screen more often: V2.2.1
If you don't have that version, then you can update to it. If you do have that version, then it will correct itself after a few minutes.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: During print the LCD screen goes funky
Wow peter. You are quick lol. (Get off the computer sometime lol)
I will update the firmware tonight.
Thank you very much. Glad it wasn't something majorly wrong or that my eye site is going more lol.
Re: During print the LCD screen goes funky
Scott
Computers are my business, so I never get a break...
Happy to help.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: During print the LCD screen goes funky
Fully understand. I sit in front of this thing for hours at work (drafting/designing architectural millwork) then go home and do more for my own business. Ahhh lol
Re: During print the LCD screen goes funky
Ok. I am trying to do the Firmware Update.
I have it in the root directory since it doesn't like spaces in directory folders.
Got the 175-RAMBo1-3a-en.hex in the same directory.
Try to run the updater. Hit update and I get this:
avrdude.exe: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude.exe: Device signature = 0x1e9801 avrdude.exe: reading input file "\Utilities\175-RAMBo1-3a-en.hex" avrdude.exe: error opening \Utilities\175-RAMBo1-3a-en.hex: No such file or directory avrdude.exe: input file \Utilities\175-RAMBo1-3a-en.hex auto detected as invalid format avrdude.exe: can't open input file \Utilities\175-RAMBo1-3a-en.hex: No such file or directory avrdude.exe: write to file '\Utilities\175-RAMBo1-3a-en.hex' failed avrdude.exe done. Thank you.
Totally confused.
Re: During print the LCD screen goes funky
Hi Scott
I have found that the best way to get the update loaded is to create a folder ("PR" - no spaces...) on the root of the C: drive, copy the contents of the uploader folder there, along with the hex files and run the uploader from that location.
You may also need to restart the program and/or printer a couple of times to get a reliable connection. Also connect the printer directly to the computer.
The message is rather strange - it seems to open and read the HEX file and then states that it doesn't exist - and I have seen it a few times myself.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: During print the LCD screen goes funky
Peter... Thanks. Will be trying again tonight. I'll move it to my c drive just in case.
I had the utilities folder on the root of the D drive but will create the folder and copy the files over and see after work today.
I'll be back if I have any more issues 🙂
Thanks again Peter!
Re: During print the LCD screen goes funky
Peter.. your method of creating the file in the root directory of C worked.
Very strange but it did it!
Thanks again.