bed leveling issues CR10 with new DuetWife
-
@dc42 said in bed leveling issues CR10 with new DuetWife:
After you home the printer, is X=0 Y=0 in the correct position (normally the front left corner of the bed)?
When you jog the axes, do they move by the right amount and in the correct direction?
You say "It seems to probe the bed in all kinds wrong positions", but is that when you run G32 to do leadscrew adjustment, or when you run G29 to do mesh bed probing?
The G31 line in your config.g file says that your BLTouch is offset from the nozzle by 50mm in the +Y direction. Is that correct?Yes X0 and Y0 are both correct with appropiate clearance for the nozzle
yes axes move the correct distance and direction when I move them using the GUI
I am not sure, I click on Auto Bed Compensation and it doesnt go to where i interpret from the config where it should go, like the Y axis goes off the table and the probe doesnt hit
yes the BLtouch is 50MM ahead of the nozzlethank you!
-
@imrj said in bed leveling issues CR10 with new DuetWife:
yes the BLtouch is 50MM ahead of the nozzle
In the +Y direction? That would be unusual in my experience, but not impossible.
If you home the printer and then send G30 P0 X100 Y100 Z-9999, what XY coordinates does it put the nozzle at to do the probing?
-
50 mm ahead of the nozzle looks like -50 to me, not +....or am i missing something here?
-
so i just adjusted the mechanical switch end points so I dont have to worry about any offsets, since now the endpoints hit while the nozzle and probe are as close to bottom/left as possible, this required I readjusted bed size to 270x270mm to make up for lost travel of offsets, but is all good now, i can live w that
the problem I have now is when doing mesh and bed stuff the Z axis is not rising and the probe hits right away giving me the error in the picture....whats going on here now?
-
bah....ignore last, step/mm way off for z-xis....will fix and update back
-
hallelujah, finally printed a 20mm calibration cube and is nearly perfect (using PETG).
..I will never complain about Marlin!!whats does 16x with interpolation mean? Is better to run native 256 with 0.9 step motors?
How do I hook up a PT100 with a generic MAX31865 board and hook up to where a daughter board goes? I dont see any documentation on this yet.
-
@imrj said in bed leveling issues CR10 with new DuetWife:
whats does 16x with interpolation mean? Is better to run native 256 with 0.9 step motors?
It means that the driver will take the 16 pulses and send 256 pulses to the motors to give smoother, quieter motion. It's probably the best way to operate since it gets you the benefits of high microstepping without hitting the CPU. You can try running with higher microstepping, but on fast travel moves or on axis with already high steps per mm values you may begin to hit the max step rate. If you're already running 0.9 degree steppers there's probably no point, IMO. The exception for this may be the extruder.
If you do decide to test it, you can check for missed steps or hiccups with M122 to get a diagnostics readout. Look for the movement section.
https://duet3d.dozuki.com/Wiki/Connecting_PT100_temperature_sensors
https://duet3d.dozuki.com/Wiki/PT100_temperature_sensor_daughter_board
-
@imrj said in bed leveling issues CR10 with new DuetWife:
How do I hook up a PT100 with a generic MAX31865 board and hook up to where a daughter board goes? I dont see any documentation on this yet.
You will need to look at the instructions for using a MAX31865 board with older Duets for general guidance, and adapt the connections to suit the daughter board connector. The connector pinout is marked on the underside of the Duet.
-
I did and it was a simple hookup to the MISO/MOSI/SCK, CS1 connectors....is picking up the sensor but temp is off by 10C and it wont rise above 25C....very odd.....same cabling and MAX unit and sensor work perfect when I hook up to Arduino...what gives?
-
any ideas?
-
Your board probably uses a different value reference resistor. The Duet daughter board uses 400 ohms, but some other boards use 430 ohms. You can tell the firmware the value using the R parameter of the M305 command.
