Notifications
Clear all

possible bug in firmware  

  RSS
Maurice Heskett
(@maurice-heskett)
Active Member
possible bug in firmware

I'm experiencing a high rate of failure due to what I think is a bug.

 

The gcode for home_all, and the crash recovery rehome of just XY, gets a different X home, by 1 full step (or more, it is consistent) to the left on the build plate

when recovering from a crash. This results in a throwaway part, and I have a 13 gallon kitchen trash bag full of throw aways.

 

Can this be addressed in the RAMBo firmware? Please?

 

Take care & stay well

 

Gene

 

Posted : 02/08/2022 4:06 pm
JoanTabb
(@joantabb)
Moderator
RE: possible bug in firmware

Hi Gene. 

this may seem abstract. 

Have you tried lubing the rods? and checking for contaminants on the smooth rods?

Friction can cause inaccurate homing

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Posted : 02/08/2022 6:56 pm
fuchsr
(@fuchsr)
Famed Member
RE: possible bug in firmware

This is a user-to-user support forum, and the devs don't hang out here much (or at all). You probably want to go to Prusa's GitHub site and open a ticket there. 

Posted : 02/08/2022 7:13 pm
Maurice Heskett
(@maurice-heskett)
Active Member
Topic starter answered:
RE: possible bug in firmware

first and 2nd things I checked, its very smooth, no catches or drags anyplace.  Thanks Joan.

Posted : 02/08/2022 9:41 pm
Maurice Heskett
(@maurice-heskett)
Active Member
Topic starter answered:
RE: possible bug in firmware

Also, I can't log onto github, I've had a crash and had to start with a new install, and they won't let me in from my fixed address because I no longer have the username and password, no aliases but they recognize the only name I've used and won't let me re-register. I can't even post a help me login msg because you have to log in to send the msg.

Posted : 02/08/2022 9:50 pm
gudnimg
(@gudnimg)
New Member
RE: possible bug in firmware

Any chance you could write a few steps on how to reproduce this? I might be able to fix it for you. 

Posted : 13/09/2022 7:41 pm
Maurice Heskett
(@maurice-heskett)
Active Member
Topic starter answered:
RE: possible bug in firmware

no context. If you are referring to my inability to login to github, I assume its because my username (WOWELECTRONICS) is previously registered and with two spinning rust drive failures in short order last fall, I've absolutely no clue what my password might have been.  But because my address is non-volatile and associated with my email, I can't get in and they will not allow me to create a new account. If everything github knows about gheskett@shentel,net and WOWELCTRONICS was wiped clean from their system, I might stand a chance of creating a new account and joining the party. Until then its a lost cause.

Posted : 13/09/2022 9:33 pm
gudnimg
(@gudnimg)
New Member
RE: possible bug in firmware

The gcode for home_all, and the crash recovery rehome of just XY, gets a different X home, by 1 full step (or more, it is consistent) to the left on the build plate

when recovering from a crash.

No I’m not referring to Github but the original issue you posted here. What steps do I need to perform to recreate the issue?

Do you use Octoprint or SD card to print?

This issue on Github sounds similar https://github.com/prusa3d/Prusa-Firmware/issues/3460

Posted : 13/09/2022 9:40 pm
Maurice Heskett
(@maurice-heskett)
Active Member
Topic starter answered:
RE: possible bug in firmware

And its not possible to send a message to github w/o logging in. I've sent 5 or 6 passwd reset requests, all ignored. Typical for m$. And guess who owns github...

 

Thanks for checking Joan,I appreciate the effort.

Posted : 14/09/2022 9:38 pm
Share: