Hello community:)
Thanks in advance to anybody reading this lengthy post!
It’s been a while since I haven’t been able to find the info that I need by searching other posts but I am having an issue and need advice/ideas. I have been prointing just fine for the last year+ since I put a new board in my Printrbot Jr. (Rev D) I just recently wiped my computer and did a clean install (OS X). I have reinstalled all necessary software to print. I am able to connect to my bot. I am able to manually move the extruder, via Repetier, over the entire print area AS LONG AS I ‘home all’ first. If I don’t ‘home all’ first, I can move only about half of the area on y axis. If i home all and then set up a print, evrything looks good, hot end heats up, extrudes manually but when I hit ‘Run’ it’s as if it disconnects except for that the hotend stays on and at temp. Even if I then ‘cancel job’, I am unable to move at all with Repetier and I can’t even turn off the heat. I am wondering if I should reflash the firmware but it seems like since it was fine before that It should still be fine, and that the issue is somewhere in my Repetier settings. Possibly? I have my dimensions set correctly as far as I can tell- I don’t remember if I used to have ‘receive cache size’ set to 63 or 127 before. It is currently at 63. Does this make a difference? I did get a ‘y stop hit’ message once or twice initially but I’m not seeing that any more even when It is stopping. Is there some place that I can detect and or change what is happening via M503 commands or anything like that? Is re-flash of firmware my best option? Why would it behave alright until I hit ‘Run’?
Any insight or ideas would be greatly appreciated! This community has always been an immense help to me even though I am usually just reading and not posting. Thanks in advance. I do hope that I’ve given sufficient detail:)
I ran into this on my printer. There is a setting that prevents the movements into negative x and y. When this is set you have to home all first. Then you can move normally. It prevents crashing into the endstops I suppose. I can’t remember where I turned it off and I’m not at home now but I’m sure it was a firmware setting. Hope it helps.
Hmmm, I wish that I knew where to look, lol. Thank you for reply- it’s certainly a start!
Is 0,0,0 where is was before on the print bed? You can probably check by looking at the gcode of your old prints, if you still have that gcode. To that end, you could also try printing a piece of gcode from before you wiped your computer. That is assuming you backed up something or printed from sd card or raspberry pi or something.
@NathanielStenzel , if i follow what you are asking, yes, all ‘x’, ‘y’ and ‘z’ home were 0,0 and 0 before. I clearly remember that without checking. when I do a M109, it seems to read the endstops correctly> says ‘open’ when open and 'triggered when triggered. Thanks for your input, it’s really appreciated:) I think you have helped me on the right path in the past as well.
@boog_nish so is 0,0,0 the center or a corner of the bed? I just want to make sure you really understood me. Was it that way before the computet wipe?
corner. Looking at printer it is the closest left corner
Did you try a gcode file from before the wipe? Is your slicer generating coordinates all in positive coordinates or does it generate coordinates centered at 0,0,0. The slicer needs to consider the bed center to be width/2,length/2 if 0,0,0 is in the corner.
Going to load one now and see. Sounds like a thing worth checking. Cool, thanks will try and then report
I hope the advice does the trick.
@NathanielStenzel . Oh man!! Loaded one of my good gcodes from before and it ran!!! Very excited for this progress although still not EXACTLY sure how to remedy. So I need to designate the bed center somewhere in my setting then, huh? Is that the fix?! So excited for a step in right direction!! Thank you thank you!
But in my ’ printer settings ’ the print center is set to half of bed size for both x and y. >?<
OK, so it is not the bed center coordinate. Compare the comments in the gcode from before to what you get now.
The slicer does not think it is talking to a different board than it was before, does it?
Hmmm, I am not sure about that… I don’t think so though, unless I flashed this board with the wrong firmware when I put it in… Over a year ago.
Did you back up your slicer’s setting? Are they in comments in the old gcode? Will slicing using the old slicer settings make OK results? Hmmm…the settings and the board/firmware type are about all that I can guess would be it.
@boog_nish you did print with the board, right?
Yes. Have been printing fine with this board for a year plus
I unfortunately did not back up my old settings. Dumb move on my part!
Although my x axis was reversed for that whole year plus… Otherwise printed fine- several hundred successful prints