Z probe too high one side
I use a Pibot board with Repetier firmware.
I have in my start Gcdoe a G32 S0 command for probe.
It works on 3 points but when I print on the right side the nozzle is too high.
Z motors works for compensation but on the right side the nozzle goes too high.
I'm using a reflecting probe produced by Pibot.
Can you help me.
I tried to realize a mesh of point but it doesn't work. It only works with 3 points probe G32.
Can you help me?
I have in my start Gcdoe a G32 S0 command for probe.
It works on 3 points but when I print on the right side the nozzle is too high.
Z motors works for compensation but on the right side the nozzle goes too high.
I'm using a reflecting probe produced by Pibot.
Can you help me.
I tried to realize a mesh of point but it doesn't work. It only works with 3 points probe G32.
Can you help me?
Comments
I'm using this kit https://www.pibot.com/set-of-pibot-electronics-kits-for-3d-printer-2-0-d.html but the producer doesn't answer to questions. Bad situation:-(
At this link the configuration h and all of the firmware.
Can you help me to solve?
Thanks a lot.
https://drive.google.com/drive/folders/1zYWo3zz3kjyMgr0gdSABN-2nKQ-ZDY3_?usp=sharing
Extruder will only run if hot or if you allow cold extrusion using
M302 S1
It might also be that you need to invert enable signal for motor driver to get them work. Some need high some low. Just test if you can move them when you start firmware. At start motors are off so they should not block. If they block enable must be inverted.
I inverted the motor on configurator and now is ok.
Now I can move motor and I think I'll be able to test the printer.
Let's start again with autolevel.
I want to use a mesh of 9 points on the bed and I configured it in the configurator online.
When It starts with the first point the probe goes down but doesn't stop when triggers.
I have a blue led on the reflective z-probe that goes on but z axis continue to go down.
I tried to tes with M119 the status and i saw that it remains the same.
Always High with blue light on or off.
With other version of firmware it works.
Any idea?
Other question: Wich is the commend for autoleveling and 9 point probe? G29 or G32?
Thank you
It was a wrong assignation of the pin.
The problem is: how to have a 9 points grid on the bed before to print?
For example:
3 points on X with Y20
3 on X with Y 40
3on X with Y 60
I configured the bilinear one but it takes points always on the same Y value.
Probably is better if I wait before asking :-)
I did it from configurator and works.
Tonight I'll have some test on the correction bed level function.
after G32 S0 the nozzle goes down and scratch a little the plane and then goes to start printing on the left side.
At this point, the extruder is 2mm higher than the plane but when it goes on the right side is very attached to the plane.
So after configuring the new firmware I have the same problem but with an inverted side :-)
P.S.
The Z axis moves while X and Y moves. So I think printer reads some dates but no the correct one...
Any idea?
Thanks a lot guys. I hope I'll be able to use Repetier :-)
This is the start GCODE:
This is the Eprom configuration
What is the log from
Depending on setup this can cause illegal position and abort of G32. If you home x and y min I guess it should work with correct points.
What I wonder is when your printer is 900x1600 mm big, why do you not test rotation for full bed? You only measure a square 20-300x20-300 so rounding errors of that measurement count up. Also such big beds tend to deform when getting hot and move.
I configured the last version by online configurator but while I upload to the board, a the end of the process I have this message:
Tried to reinstall the old configuration and everything works again.
Any solution?
Does old firmware upload if you change any parameter making it differ? Question is if flash is write protected so uploading does not work and old just works because it is identical to already existing or if it writes and jus has a write failure.
Do mor euploads cause exactly the same error?
I eliminated some code that I added in pause command on start on the online configurator and now the upload is ok.
QUESTION 1
I sent G32 S0 and now I generated a mesh for the plane.
At this point, I execute the slicing but when printer starts goes to Z0 and not to Z-2.
So Zmotors compensate probably in the right way but extruder stays to Z0 position so +2 and prints in the air.
I saw also the GCODE of the slicing and it indicates the first layer to Z-2.
So the command is ok but is ignored.
QUESTION 2 - Z OFFSET
Where to set the parameter? In the slicer or in Eprom.
I hoped Repetier host and set the value in EPROM but nothing append. If I do the same in Slic3R from RHost, it works. Can you explain how to operate?
QUESTION 3 SD CARD
I saw there is no possibility to read SD card from the physical reader on the board.
This is the start GCODE
-----------------------------------------------------------------------------------------------------------------------------------------------
This the configuration files stored at this link
https://drive.google.com/drive/folders/1zYWo3zz3kjyMgr0gdSABN-2nKQ-ZDY3_?usp=sharing
Id like to use repetier :-)
>I sent G32 S0 and now I generated a mesh for the plane.
>At this point, I execute the slicing but when printer starts goes to Z0 and not to Z-2.
>So Zmotors compensate probably in the right way but extruder stays to Z0 position so +2 and prints in the air.
>I saw also the GCODE of the slicing and it indicates the first layer to Z-2.
>So the command is ok but is ignored.
z min is 0. You are not supposed to go below z min so moves to z-2 are forbidden. No one does that normally - only to compensate other errors.
Your slice code stopped before the first moves so can not see anything related to this. But all should have z 0 as start. So slicer starts with first layer height. If homing is too high so you need to go down 2mm that just means your z probe height is off by 2mm. With correct z probe height you end where you need to be.
>QUESTION 2 - Z OFFSET
>Where to set the parameter? In the slicer or in Eprom.
>I hoped Repetier host and set the value in EPROM but nothing append. If I do the same in Slic3R from RHost, it works. Can you explain how to operate?
z offsets are 0 in slicers and in firmware for first extruder as well. First extruder is reference for Z and extruder 2 and z probe are all relative to this.
>QUESTION 3 SD CARD
>I saw there is no possibility to read SD card from the physical reader on the board.
You have
"sdSupport": "0", resulting in
#define SDSUPPORT 0
must be 1 for sd card. Normally it gets activated by a controller. But it can also get deactivated by controller. In any case you need to activate it. As a test if sd support is gets compile din add in SDCard.cpp after
a error message
#error sd support active
If compilation breaks with that message you know it is activated now and you can remove the message. If SDSS was correct it should then work.
With the only one working version of the IDE (1.6.5) I can only upload the 0.92 version of Repetier.
Probably the only way to solve the problem is to set one by one the points of the mesh of the probing because after I execute the G32 S0 it always continues to print with wrong correction of the plane.
Any help to delete completely stored mesh or to set manually one by one the probing points?
>The biggest problem is that I'm not able to upload the new firmware because of Pibot board!! Impossible to flash the firmware with the latest version of the IDE. Doesn't recognize the board.
What board type do you need for pibot? Isn't it a regular Mega2560 based board - that should work on all IDE versions. If it is a 1280/1284 based sanguino clone you might need to install the sanguino board.
I'll solve this problem later... I hope.
I did a G32 S0 to have a new matrix with more points and them M500 to save in Eprom
This is the result:
14:59:22.523 : N15 M322*20
Then I try to start printing but it seems that it applies a different compensation for the Z axis and when it moves to the center it starts to scratch to the plane.
Is there a way to have a look at the matrix in the Eprom.
It seems it applies different coordinates.
This is my configuration h
I see the difference is 3.386 mm between highest and lowest position, that is quite bad leveled.
A even bigger problem is when you look into your measurements:
Start here for x constant and see how y changes. It should be eithe rincreasing or decreasing but you get
This does not look like a flat bed. At X166 it continues
...
With such deviations you can not expect good results.
Not the question is what is causing that. Is the bed really that bumpy, is the z probe unreliable or does it get disturbed? E.g. inductive probe gets disturbed when bed is heating. So in that case bed must be disabled to get proper measurements.
What you can expect is that the plane swings between +/- 0.4mm too close and too far away. I doubt that even with G33 you will be able to compensate that. Also this is just a guess from some values it shows clearly your problem. Guess it comes from the big bed size. Here you can get many effects and it is hard to find a plane bed that big. You might also get bending effects from the weight of bed and also the x/y axis depending on your system. Have at least seen systems where extruder was mid x lower from own weight.