Firmware Bin File Is Corrupted
Mystery crash? possible decadent board?
Woke up this morn to see this on the my new mini. Information technology was frozen in this state, I attempted everything, no joy... a 32+ hr impress destroyed. The file was over 220Kb. I am wondering if there is a limit to how big the file tin be? like say 199Kb? honestly IDK, hoping someone on here can shed some light. I have not attempted whatsoever consecutive prints afterwards his crash.
I practice have some boosted questions:
1. Why am I getting tonnes of zits when using my MacBookPro --> pronterface --> USB-A cable into the mini. When using the USB solo into the mini, the results is no more zits? What is up with that?
2. Has anyone modified the cooling fan outlet. seems to be too high[elevation]. Presently the air seems to be driven directly into the silicon sock I installed, resulting in stringing when using PLA?
Posted : 12/08/2020 three:19 pm
RE: Mystery crash? possible corrupt lath?
Looks like this problem: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/771
Can you upload your crash dump to that issue?
Edit: Seems like some other bug, so amend create a new outcome @ github.
This mail service was modified ii years ago by pab
Posted : 12/08/2020 3:31 pm
Topic starter answered:
RE: Mystery crash? possible corrupt board?
@pab
IDK what a crash dump is? or how to...
Posted : 12/08/2020 3:51 pm
RE: Mystery crash? possible corrupt lath?
Its a characteristic added with firmware 4.0.3:
Crash Dump feature
The advanced 32bit SoC running the Buddy board enables logging the system events. In the case of a arrangement crash, the information is written in the SPI flash. After the printer is restarted, users can download the Crash Dump file onto a USB bulldoze and provide it to the support squad/developers for debugging purposes.
To download the Crash Dump file, insert a USB bulldoze into the printer first and so head to "Settings -> Save Crash Dump".
Posted : 12/08/2020 3:53 pm
Topic starter answered:
RE: Mystery crash? possible corrupt board?
Ok, I have the bin file on the USB at present. But I tin not upload the >bin< file to github. I tried to open it with C++ besides, still no-get? How do I go a bin.file onto github for assessment then?
Posted : 12/08/2020 iv:19 pm
RE: Mystery crash? possible corrupt board?
Just nil the .bin file (if you are on a recent windows, only correct-click it and select "transport to" and "compressed (zipped) binder").
And then github will accept that file.
Posted : 12/08/2020 4:25 pm
Topic starter answered:
RE: Mystery crash? possible corrupt board?
G1 X157.713 Y107.263 E0.00530
G1 X157.733 Y107.444 E0.00324
G1 X157.706 Y107.721 E0.00495
G1 X157.558 Y107.993 E0.00552
G1 X157.371 Y108.117 E0.00401
M204 S1250
G1 X157.175 Y108.040 F9000.000
G1 E-1.40000 F4200.00000
G1 F7200.000
G1 X157.141 Y108.183 East-0.13235
G1 X156.916 Y108.117 Due east-0.12976
G1 X156.729 Y107.946 E-0.14045
G1 X156.688 Y107.856 E-0.05490
G1 X156.642 Y107.658 Due east-0.11254
G1 E-0.03000 F4200.00000
G1 Z121.300 F9000.000
G1 X158.600 Y105.035
G1 Z120.800
G1 E2.00000 F2400.00000
M204 S800
G1 F1500.000
Posted : 12/08/2020 4:28 pm
RE: Mystery crash? possible corrupt lath?
Quick question - why do ypu impress from Macbook through Pronterface? Why not from USB stick from MINI directly, or from deficated print server like Octoprint? You go zits considering your computer is not fast enough, it is not feeding data to USB port in time and printer skips parts of gcode. Information technology is not recommended to use whatsoever other than dedicated computer for printing, because whatsoever activity taking place that moment may disrupt existent-time stream of data to USB. Not to mention if your calculator decides it needs update and reboots in the middle of long print.... Besides, Pronterface is non actively adult anymore.
Print from USB stick directly, or if you insist on USB so get a Raspberty Pi and install Octoprint print server on it.
Posted : 12/08/2020 9:47 pm
Topic starter answered:
RE: Mystery crash? possible corrupt lath?
@crawlerin
Primarily because my printers are upstairs and my primary work station is downstairs. It is all near eliminating the trips upwardly and down stairs. If you demand to practise a quick slice you have the capacity to do that there on the spot. These laptops are indeed defended to merely the printer. They are old school MacBook Pros that are set to never sleep, dedicated to only pronterface to the printer. I am aware that the printer is reliant on the laptop, and aware that a causation of zits is due to the laptop not sending info @ a proper charge per unit. With pronterface yous yet have some manual controls [ minimal compared to the UI on the printer]. Pronterface was something that I seemed to be familiar with and worked well for me previously. Anyways... I have read somewhere, can not recall specifically, that 0.10 mm settings are decumbent to zits. <-- IDK? As of at present I have just seen zits on curves, nothing on any straight edges.
Posted : thirteen/08/2020 i:37 am
RE: Mystery crash? possible corrupt board?
@j-halter
I see. Well, that's one way to solve it ... though I still think Octoprint would be more than beneficial for such purposes, because information technology includes not simply press itself, just many useful plugins (webcam, spaghetti detective, exclude failed region,...). There seem to be unofficial Mac port of Octoprint, https://community.octoprint.org/t/setting-up-octoprint-on-macos/13425 you can requite information technology a attempt, if that does non work well, at that place's still RPi and official Octopi.
Yous get zits when printing curves considering of that exact reason of computer not keeping up sending data to printer. Direct motion is (basically) one control to X or Y and E motor, merely for printing curves Slicer calculates it as series of pocket-size X&Y then X&Y so 10&Y ... movements. Instead of i or 2 commands computer needs to send hundreds small-scale instructions to printer while extruder keeps extruding. Any modest stall causes filament to keep coming out while head stands still because motors look for their instructions.
Posted : 13/08/2020 nine:43 am
Source: https://forum.prusaprinters.org/forum/hardware-firmware-and-software-help/mystery-crash-possible-corrupt-board/
0 Response to "Firmware Bin File Is Corrupted"
Post a Comment