December 6, 2016 at 12:37 pm #22177
Today was released the RC8 version.
I’m interested in better graphic display performance (The ENSURE_SMOOTH_MOVES feature was very useful to smooth my laser raster engraving) and G38.2/3 support (Z probe)… but has other performance improvements also.December 6, 2016 at 12:38 pm #22178
Sweet! I’ll update our stuff asap!December 10, 2016 at 1:06 pm #22407
I updated and now (after flipping y) I start a gcode from SD (which I just cut 5 minutes before flashing) and the Z lifts then stops and machine halted is thrown up on the LCD. Does it have anything to do with the large change from 788 to 4535.44 on the z_axis mm/s? I doubt it and will try it again but something broke my particular setup lol.
NeilDecember 10, 2016 at 1:15 pm #22408
It means you are trying to move your z axis too fast. Check your gcode. It will allow a few moves that are too fast but if there are to many it stops the cut.December 10, 2016 at 1:16 pm #22410
Remember z axis is no more than about 8mm/s, useful range for cnc is about 4-5mm/s you shouldn’t be hitting that error. Check your cam settings and try again. Run a test cut first so you don’t waste material. I do it with every cut.December 10, 2016 at 1:34 pm #22411
May be new marlin has some bug with limiting high z speed…
Neil, check this postsDecember 10, 2016 at 1:47 pm #22412
It is not a bug it is intentional. Without it your chances of missing steps are very likely. When running a test cut you might not find out you missed steps, this is a clear indication.December 11, 2016 at 9:09 am #22475
weird thing is I just finished cutting the same gcode 5 minutes before the upgrade. I only have
I will run a different cut to see but.. I have attached the vbit profile I used. maybe 24mm/s on the xy is too much?
Attachments:December 11, 2016 at 9:28 am #22484
Make sure the “f” command is checked to run on every line. That 24/mms could carry over and be used on the Zaxsis and is likely your issue. The f box is mm/m, so mm/s*60December 11, 2016 at 12:41 pm #22494
Thanks for the info guys. I have updated my Estlcam settings to reflect your screenshot from the above post. I will throw one of the kids names on a scrap board to test! Thanks again. Keep up the excellent work Ryan!! Since switching to an e3dv6 clone hotend on my mp3dp the thing has been printing almost all day every day (PLA) I just switched out to a roll of PETG and so far so good. I purchased a laser module (100$ 2.8w – Leo) so I need another mpcnc just for the laser (duh). I was able to print all parts in petg on my monoprice mini but the c-xyz part is too large for the build plate so the good ol faithful mp3dp is printing the larger parts!
NeilDecember 19, 2016 at 8:39 am #22969
Marlin developers confirmed that there were changes in the way RC8 behave in jerk/acceleration implementation:
My configuration with 32 microstepping, 8mm threaded works great now with 7 mm/seg as max Z feedrate…. G0/G1 with high feedrate in Z don’t reset the arduino any more.December 27, 2016 at 9:32 pm #23604
Is it possible that you create a fork of marlin on github with your upgrades so we can easily track changes and propose MPCNC fix/addons against the base firmware ?
I have tried to take your changes and merge them either with the 1.1.0-RC8 tag or the RCBugFix branche or the RC branche, I have file conflicts.
Thanks 🙂December 27, 2016 at 9:43 pm #23605
Any change I have made to the firmware was commented with “//MPCNC” it is easily searched in arduino. I also have the firmware ready for download on the site you don’t need to make any changes yourself.
I wouldn’t mind making a fork, but I really don’t have the time to figure out that side of github right now. If you have a link to a quick and dirty tutorial I could try in the next few weeks. I understand forking it but not how to make my changes and how they are implemented when the original branch updates.January 4, 2017 at 10:33 am #24314
Reading through the news post on the front page, it’s not clear to me which pieces of software I need to upgrade. Do I need to flash my RAMPS board? Do I need the beta version of Estlcam? How can I tell if the problems fixed in the software are the same as the ones I’m currently experiencing?January 4, 2017 at 10:42 am #24316
I’ll read through it and see if I can clarify it.
If you are using estlcam, yes update it to at least .37.
if you are not using a laser, do not worry about the firmware.January 4, 2017 at 1:29 pm #24335
I have made a fork of Marlin to apply your changes : https://github.com/MaitreDede/Marlin/tree/MPCNC-RC7
I took the RC7 tag.
Then I applied your changes (each line with MPCNC) : from https://www.v1engineering.com/marlin-firmware/ the “Marlin RC7 MPCNC w/LCD” (I don’t know which threaded rod I have, so I took first)
Finally I updated to RC8.January 4, 2017 at 1:33 pm #24336
RC8 doesn’t work for us. We have to use the bugfix branch. I have the changes ready but I am going to test it a little longer before I put it up.
Thank you though.January 4, 2017 at 1:36 pm #24337
Ok, I will make a RCBugFix branch.
I am curious, what “doesn’t work” ? 🙂January 4, 2017 at 1:38 pm #24338
The LCD changes they made, you’ll see in the bugfix they took most of it out and implemented it in a different way.January 4, 2017 at 1:47 pm #24339
Took the previous branch I made (RC8) then merges the RCBugFix branch and tadaaa : https://github.com/MaitreDede/Marlin/tree/MPCNC-RCBugFixJanuary 4, 2017 at 5:27 pm #24352
Thanks Damien. I’ll try to test it on the weekend.January 4, 2017 at 5:49 pm #24354
I don’t think it merged right. You have 2 sets of movement settings in config, and missing a few thing in adv.
After you asked me to put it on github, I actually did. I am getting the same issues. I haven’t tried yours but mine will stop compiling.
I think it is trying to hold the settings from the rc and bugfix branches in the same file? I have no idea. I see the errors when it syncs but I am not sure what I am supposed to do to fix them? If I open it up in editor it had already made a mess of my file.January 4, 2017 at 6:18 pm #24357
You are right, I should have checked compilation before commiting.
I have removed the dupplicate movement section, and fixed sanity checks (DEFAULT_XYJERK is splitted to DEFAULT_XJERK and DEFAULT_YJERK).
I don’t see the missing things in adv. I will double check later.January 13, 2017 at 6:21 pm #24932
Just a heads up. I flashed a brand new mega worth the new fw. Before flashing i had updated my ug8lib to the newest version (although it looks like he moved future development to ug82). Doing so flagged an error compiling as the directory structure changed from /updates/ to /clib/. So in dogm_font_data_marlin i had to make to edits where u8g.h was being called. Then i was able to flash. Just throwing this out there on case someone else guys this snag.
NeilJanuary 15, 2017 at 12:00 pm #25019
I just flashed this.. and now my x y z on the LCD keeps chaning to ? and then back to the position. And when I got to prepare and move it in position and select set home offsets, the info screen says offsets applied but the x y z are still not at 0 and they are still flashing ?.
edit- by this I mean this https://github.com/MaitreDede/Marlin/tree/MPCNC-RCBugFix
Just tried to make a test cut (in the air), x was supposed to be moving at 30mms and it was moving at about 30mm a month.
You must be logged in to reply to this topic.