You are not logged in.
Pages: 1
With halfstep and 5mm lead Screw i get a Real Hardware Resolution from 0.0125 mm which is cool for me printing with 0.025 layer. When i use dynamic lift and the Formula result is not a multiple of this real 0.0125 reproducable stepping resolution, the result per lift is wrong and get wronger on each lift about 0.0125mm because the stepper can hold on full and half steps. So on each 0.025 Layerheight there is a possibility from 50% to get the next Layerheight wrong by more then the half Layerheight.
So if get shahin right nanodlp handle this automaticaly internal and everything is ok.
Microstepping beyond 8x is gambling. You cant get better results then your stepper motor Hardware tolerance. Microstepping is usefull for smoother motion and not for tricking physics. Microstepping Resolution looks nice on printer specs. Stepper Motors handle Full and halfstep accuratly.
I'm using direct control with halfstep and 5mm Screw. My Initial question was about some kind of mathformula to round the result from your great Formula ( Btw. : thank you) to my hardware Resolution to avoid errors. I'm a Kind of Inverted MathNerd.
If i print a 160mm part with 20 micron layerheight i get 8000 layers resulting in totaly 16000 up and down movements. Worst case error accumulating according to your example by 0.001mm is then 16mm - 10%.
I might be totally wrong here too :-)
Is it possible to tie the dynamic lift result to the next multiple of the Z-Axis step resolution to avoid chaining stepping errors?
I changed the pigpiod timing from 10 back to default 5. I Think it Sounds better.
3 Volt out. Never use 5 Volt! When the switch is closed the signal then goes to your selected Pi input pin.
Cool Feature. Thank You. That will be helpful.
z calibration page get realtime data. As the movement still not completed and it does not have ajax information are not always correct.
My Z-Axis is really fast. The behaviour only affects the Buttons for upwards moving. Even for small movements. May trigger the Ajax with a small delay?
.
Do it has any other issue?
Don't no so far. I'm just in the middle of building my printer.
Actually I dont use any endstop. Accidentally i fried the chip of my optical endstop :-(
But both Buttons on the axis-callibration page try to use them, even when i disabled the endstop on the setup page. Therefore i made my own "set Zero" Button.
Any chance to probe for using endstop or not for the nanodlp Buttons?
Another Question: Do I have to adjust "Axis Direction" and "Movement Positioning" fields on setup page for direct movement and bottom up configuration?
Do I have to use all these [[WaitForDoneMessage]] [[Delay Seconds]] and [[GPIOWaitForLow]] stuff when using direct control with only a stepper driver and no ramps, arduino etc.?
And the last Question for today:
All Input boxes for length input use step="0.001". So it is not possible to match my resolution on Inputs where mm is used. The values loaded use the right number of digits, but i'm not able to submit them. Any chance to give the mm inputs more digits?
Go to setup page there are some settings available regarding Z-Axis.
Nope. Not for direct movement. They only show up when usb Shield is selected and Direct io is disabled.
found the problem.
button up do not reload the ajax for the platform information.
If i press then another button the values get messed up. If i reload the whole page before pressing the next button the correct values are set. It seems to be a ajax reload problem on the page for all up Buttons.
I use a own driver board with direct control. I thought there is no need for Gcode then.
1: move down with the down buttons on the calibration page to my desired bottom level.
2: press my own "set Zero" Button: executes:
[[PositionSet 0.0]] ;
[[PositionChange 0.0]] ;
Page show:
Current 0.000000 0
Log show:
Gcode Position change 0 to 0
Gcode Position set to 0
3: Press "10 mm up" Button
Z-Axis moves up 10mm but Page shows wrong value:
Current 0.000000 0
(expected value: Current: 10.000 800)
Log:
Pulsing Moving Up 800 pulses 10 mm
Pulsing Movement Finished Pulse 800 / 800 ; Height 0 / -800 ; Time 0.539836226
4. Press "10 mm down" Button:
Z-Axis moves down 10mm but Page show wrong value:
Current -10.000000 -800
( it should show Current: 0.000 -800)
Log:
Pulsing Moving Down 800 pulses 10 mm
Pulsing Movement Finished Pulse 800 / 800 ; Height -800 / 0 ; Time 0.540065577
If it is a general setup problem why is the axis moving correctly?
Motor and Movement and Direct GPIO settings are OK. No GCode used except for the Custom Button in Step 2
I just click on the buttons :-) Where do i have to select the mode on the calibration page?
All Buttons work correct in term of positioning the hardware.
down buttons movement is shown on page, up buttons not.
deleted because it was complete rubbish,
sorry
should start the day with coffee :-)
Take a close look on the different units in all nanodlp setup/profile pages. That helped me a lot.
Micron/Second, Millimeter, Pulse, Seconds and Microns are used.
Using more than 8 microsteps is mostly useless, because the achieved resolution is smaller then the steppermotor tolerance. You can't achieve predictable results.
Setup:
nanodlp Build #1364
direct gpio
No Endstop
Everything is fine so far. Z-Axis is moving pretty fast in the right direction and the right distance by pressing buttons. But all moving up Buttons did not actualize the Current Level in the Platform Information. This leads to incorrect Z-values. Down Buttons are OK.
Demo version on nanodlp.com:8080 does not show any help text. Js is looking in /help instead of /helps.
Hey Shahin,
first: Thank you for this great software!
Is it helpfull using a 64-Bit Version on Raspberry3 instead of the native32-Bit?
Pages: 1