That bed level looks spot on, nice work Yeah you've got to be careful when printing at the edges don't you. I cancelled one print with the head midway between two towers, and as it was homing, the bolt heads on the effector caught on the crossed wires that brace one face. Luckily I'd turned the current way down so the motors skipped and it didn't cause any damage. It's the first time I've doby nebbian - General
Thanks mate, it's been a LOOONG time coming, let me tell you. Mesh bed levelling FTW. After a good calibration, of course. File is available here:by nebbian - General
Trust me, it's not segments. You're also not running into any speed limits if you're at 1/32, even with 400 step motors. The limit for my machine is about 160 mm/s carriage speed, that's at ~640 steps/mm (1/64 ustepping, 400 step motors), and all three motors moving at once. Smoothie automatically limits the top speed based on that 100 khz frequency. Your machine, being a corexy, will haveby nebbian - General
My "Gosh" was aimed at the unsafe defaults! Totally agreed with you here.by nebbian - General
Yeah I guess it will do that on a Cartesian without the ability to go to negative coordinates! Gosh.by nebbian - General
you can add as much gcode as you like to the pause and resume functions, check the doc link. A really nice feature of smoothie is the ability to add custom menu entries that run custom gcode, not sure if rrf can do this.by nebbian - General
Yep. Pressing the kill button on the LCD pauses the print, turns the heaters off, moves the head up and away from the print, and it's up to you as to what you do next. Pressing the button again to resume, heats everything back up, and starts printing again where it stopped. It seems to work. It's a bit different to Repetier in that Repetier would keep the heaters going. Still seems usefulby nebbian - General
Yeah go figure. That'll teach me to believe the documentation. btw grid levelling works, at least it's good once the print is well inside the mesh. On the edges it's a bit flakey. My calibration at the moment is woeful, with all the bed taking off and putting back on, moving the printer, new firmware etc, it's all over the place. After doing the grid levelling routines the prints are nice anby nebbian - Controllers
QuoteDjDemonD Pause would be handy keep us posted. Tested working config is as follows: switch.pause.enable true # Enable this module switch.pause.input_pin 1.22!^ # Pin where pause button is connected switch.pause.output_on_command suspend # Suspend command switch.pause.output_off_command resume # Resumby nebbian - General
Sdavi, We have success! They uploaded some edits to the probe code, and now it seems to be working pretty reliably for me. Try the attached firmware. Somehow this seems oddly appropriate:by nebbian - Controllers
Quotehercek Edit: Based on this schematic: The resistor you removed should have been 10 kΩ which corresponds to OFF time 12 µs, fast decay time 3.8 µs, blanking time always constant at 1 µs. I just found that resistor on my bench (not easy, let me tell you!!) and measured it. Voila, 9.96k. Those graphs are interesting. I haven't tested this directly, but I had the feeling that 8825's wereby nebbian - Delta Machines
Quoteo_lampe That's why I don't want to deal with smoothiware: There is often this you_are_a_stupid_user subtone between the lines. Something I haven't seen on other 32bit firmware hubs. I'm rapidly coming to the same conclusion If only RRF supported normal LCD panels, and the Re-Arm.by nebbian - Controllers
Oooh just saw your edit. That's some fine detective work right there! What a wonderful test. I'll try it asap. Sounds to me like it could be a memory leak / out of bounds error.by nebbian - Controllers
Sdavi, Thanks for trying it out on the Azteeg X5 mini, that's a good data point. I'll try M501 next. It certainly sounds like a similar symptom. Regarding tower correction angles, I've looked through the code, and it seems to be implemented properly -- I can't see how they would hurt to specify them properly. Did you set them based on a calculator like this one?by nebbian - Controllers
Yeah I had to laugh as well. He certainly seems a bit bothered by it all. I don't know why he closed the issue straight away, I don't think that it's standard practice to do so on any of the other github repos that I've worked on. I carefully went through my config this morning, and saw that I had exactly one duplicated setting: currentcontrol_module_enable (as you pointed out). I'm not sureby nebbian - Controllers
Gosh. 3 hours after being submitted, the issue was closed because "This cannot be duplicated". Interesting, especially considering that you were able to duplicate it, and the person who closed my issue was aware of your problem as well. Not a good introduction to the Smoothie development process. *sigh* It would be great if you could post on the github issue, saying that you had the same prby nebbian - Controllers
I've submitted an issue for this:by nebbian - Controllers
Quoteo_lampe edit: The ROSC pin is already connected to the pad and grounded through the 010 resistor ( maybe not in full fast decay mode though ) O_lampe, you are a gentleman and a scholar. Many thanks for this info. Mine turned out to be the first variant. I've no idea how the firmware can measure the difference between 1 ohm and 0 ohms, but it sure seems to have made a difference. I usedby nebbian - Delta Machines
Hmm that config seems OK to me. The only difference with my config that might make a difference is the 'alpha_limit_enable' set to true on yours, mine doesn't have those lines (for alpha, beta and gamma). Try removing those lines (or set them to false). Also you can try this: turn the machine on, and jog in Z in +1mm increments. Do your carriages go up or down? If they go down for +Z movemeby nebbian - Delta Machines
DC42, is there any chance that you could try a cube at 0.161 layer height, 1/16 microstepping, no interpolation (if you're not sick of making cubes by now). Or if anyone else has a delta with 200 steps/mm, this would be a good test to do. The reason mine was making patterns at 0.202 was that full steps happen on my machine every 0.1mm in Z height (my steps/mm at 1/16 is 160). So 0.2mm layer heby nebbian - Delta Machines
I haven't changed these A4988 drivers to fast decay mode (hard to find info on how to modify my particular driver boards), but I did a similar test with SD6128's which are easier to modify. By default the SD6128's have much less of a problem with decay, but they still show a faint version of the same pattern (that doesn't change size with different microstepping). When I changed them to fast deby nebbian - Delta Machines
Quotesungod3k im not following the placebo is what exactly in your religous metaphor? Shielded cable. With a username like yours you should be familiar with religious rites!by nebbian - Controllers
Hercek wins 1000 internet points! Layer heights were 0.2, 0.202, and 0.1618 (multiple of golden ratio to spread the peaks). All prints were with A4988 drivers to accentuate the step issue. Btw, this has absolutely nothing to do with segments, and everything to do with stepper drivers that are in mixed decay mode.by nebbian - Delta Machines
Pop quiz: Which one setting was changed between these three cubes? Bonus points for guessing the actual setting values.by nebbian - Delta Machines
Also, if using the robotdigg carriages and 16 tooth pulleys, the teeth rub on the carriage as they go past. 20 tooth pulleys don't have this problem.by nebbian - Delta Machines
Quotemasterbinky Anyone have a good way to rule out the filament as a source of the issue? I find when I check my sainsmart dilaments, its diameter varies in an oscillating pattern. Two perpendicular measurements taken per point letting me approximate its cross section, which is roughly consistent but still leads me to believe it's truely an oval cross section making a corkscrew shape that I haveby nebbian - Delta Machines
Thanks for doing the test, but you really need to reflect light off the face to have any chance of seeing the tree ring pattern. Just looking at a surface in diffuse light won't tell us anything. Even matte filament won't show it, you need shiny filament. I don't think that the tree ring pattern has anything to do with segments either. I'm sure that it's to do with discontinuities in the stepby nebbian - Delta Machines
A shielded cable for what? The USB connection? I think all USB cables are shielded aren't they? I must admit that I didn't sacrifice a chicken, or say a prayer to the 3D printer gods before my experiments. The result seemed quite repeatable so I didn't see the need to invoke a placebo.by nebbian - Controllers
I had the same thing happen to me last night, with a compiled version of edge that I'd put some of my own slight changes in. Changing back to master (from a month or two ago) made it all start working again. I'm not sure what happens, it seems to just lock up completely, everything becomes unresponsive and the motors turn off. Try using the master branch. I hope this helps.by nebbian - Controllers
GroupB, I've worked hard to make the ripple more visible in my pictures, you need reflective filament, and just the right lighting, to see it. It's very hard to see with matte filament. Setting the decay rate on the SD6128's is really easy, there's a simple pair of pads that you jumper with some solder. I'd do it just to make the drivers quieter, if nothing else. I've done enough experimentsby nebbian - Delta Machines