New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fimware gets stuck. #2
Comments
Can you confirm if you are using Monitor mode in Pronterface when printing? If so, try it with it off. |
ok so here what i could get: when gets stuck i get the line twice and then silence (reset?) when i start to print the first 2 command execute (goes up on z and retract with extruder then stuck) if i play with the jog it works but sometimes get reset randomly. sometimes issuing the welcome message. any tests i shuold make?! |
Does Sprinter work with you Pronterface? Do you have the most up-to-date Pronterface? What OS? |
yes it does, i do have latest pronterface, win7 os. oops sory for closeing then reopeing mistake... |
can you pastebin your configuration.h file? |
In your configuration.h you have: ... But in pins.h I do not see MOTHERBOARD == 21 and thus no pins defined. You should copy the section from https://github.com/kliment/Sprinter/blob/master/Sprinter/pins.h to your pins.h for MOTHERBOARD == 21 (starting on line 207 to 265) -Jay |
i did have that conifugred, i now can verfiy that the board resets!, i used m92 code to change steps per unit and after getting "stuck" and reconnecting the unit per axis goes back to default - that means it resets for sure. |
I have the same issue. What's interesting is that my first print with Marlin was wonderful (see http://forums.reprap.org/read.php?147,99606), but now everything I've tried to print since then dies on this issue. I've had to go back to Sprinter. |
Pointedstick, Can you give some more information? |
Mine hung the other day, but I blamed Pronterface since I have not had the issue with Repsnapper. FWIW, |
Erik: of course, now I'm unable to reproduce the bug. :p I have another one related to the printer stopping at the beginning of a print, but I still need to regress it more before I blame Marlin and open an Issue. |
So i have news, i put the firmware on sanguinlulu 1.2 and is working great, yet on sanguinolulu 1.3 i get the same affect as for the gen3+, stuck after 2 commands, and olso again if jog it too fast (lots of clicks) get stuck. i really want to debug this bug! its getting wierder every day, what shuold i test?! |
Hello, Did you tried the 0.9.10 version. Pushed it yesterday. I am on IRC almost every evening. (CET) You can PM me. Best regards, Erik van der Zalm ----- Original Message ----- So i have news, i put the firmware on sanguinlulu 1.2 and is working great, yet on sanguinolulu 1.3 i get the same affect as for the gen3+, stuck after 2 commands, and olso again if jog it too fast (lots of clicks) get stuck. i really want to debug this bug! its getting wierder every day, what shuold i test?! Reply to this email directly or view it on GitHub: |
just tried the 0.9.10 same results, il try cach you on the irc to debug this. |
after some debugging we found that its probely that some bootloaders take bore space and therefore require a smaller buffer, so if changed BUFFSIZE on marlin.pde to 4 everything is working great! so im closeing the issue, and if you have similar problem try this solution! |
Sweet! This fixed the issue for me as well! Nathaniel On Oct 19, 2011, at 11:16 AM, sefi wrote:
|
Ran into this issue today on 0.9.10L. BUFSIZE was set to 8 by default...trying 4 and will report back. |
So no change with v0.9.10L and a BUFSIZE of 4. I was using a baud rate of 250000. Same problem (if not quicker to occur) at 115200. No problems with Sprinter. |
im using gen3+ setup, with Marlin 0.9.7L and pronterface and sfact, and when ever i start a print it executes the first 2 commands then stops. then i have to disconnect and reconnect agian to get a response from the machine.
when telling the machine to move not in print, works nice, but sometimes get stuck also and have to reconnect. cant figure out what triggers it, but in print it happens every time.
i thought it might be a communaction problem so i took the speed down to 115200 - no effect.
The text was updated successfully, but these errors were encountered: