If I run the calibration with Vers. 2.05A or 2.1.1PA the nozzle; crashed in the bed.
I also tested with the pull up resistor and open = H and closed = L but still the same. The software doesn't react on the switch state.

What did I wrong?
OK. I will try it with a higher Z offset. If itd doesn't work I will try the HTML version.Micael wrote:At this point it would seem like the z-probe option is not working very well (at least not for 2.05A) http://forum.seemecnc.com/viewtopic.php?p=78704#p78704 there have been quite a lot of reports of it crashing, including me I believe some people had success by significantly increasing z-probe height but not sure.
This assuming the probe doesn't crash right away in all calibration methods, if it does you can try increasing the z-probe height which should solve the problem (assuming it's crashing right away), if it doesn't then there is probably something wrong with your setup (unlikely).
Post by RollieRowland »
Yes, you are most likely having a similar issue. So if you would like to generate a height map then we could try and diagnose the issue.SirLinhart wrote:Our issue sounds similar to mhackney's. Regardless of calibration method we end up with 2 dips in 2 spots in the bed. Belts are evenly tight, skates are well locked in, rubber bands on the arms. We have an adjustable limit switch Z-probe that we set to match the position of the hotend to about .3mm. Have repositioned the bed multiple times, verified level by using a Starrett level. Multiple iterations though opendact from 2.0 to current on all modes. This has consumed a nauseating number of hours. I did pick up a set of tricklaser arms/effector/skates for a mex metal build, I can try them to see if it makes a difference, that will be our next step. If that fails then I'm not sure what to do besides an entire rebuild, and I'm not sure if Caspers frame can handle it.
If I still see failure, would generating a height map be useful to you Rollie? I could generate it with the Z-probe, just need to figure out how to use the G38 command and then determine a point set to check from.
Yes, it most likely isn't working. I never fully tested in those versions. I am currently fixing version 3.0s zProbe setting, for now if anyone is using it I recommend manually setting the zheight with the probe down and setting the zheight again afterwards.Micael wrote: At this point it would seem like the z-probe option is not working very well (at least not for 2.05A) viewtopic.php?p=78704#p78704 there have been quite a lot of reports of it crashing, including me I believe some people had success by significantly increasing z-probe height but not sure.
This assuming the probe doesn't crash right away in all calibration methods, if it does you can try increasing the z-probe height which should solve the problem (assuming it's crashing right away), if it doesn't then there is probably something wrong with your setup (unlikely).
If the software doesn't react at all when the state is changed then it is most definitely the settings in your firmware.D-G-C wrote: I changed the setting the Rostock software the the Z-probe is enable. The test with G31 shows open = L and close = H.
If I run the calibration with Vers. 2.05A or 2.1.1PA the nozzle; crashed in the bed.
I also tested with the pull up resistor and open = H and closed = L but still the same. The software doesn't react on the switch state.![]()
What did I wrong?
Code: Select all
#define FEATURE_Z_PROBE true
#define Z_PROBE_PIN 10
#define Z_PROBE_PULLUP true
#define Z_PROBE_ON_HIGH true
#define Z_PROBE_X_OFFSET 0
#define Z_PROBE_Y_OFFSET 0
#define Z_PROBE_WAIT_BEFORE_TEST false
#define Z_PROBE_SPEED 2
#define Z_PROBE_XY_SPEED 150
#define Z_PROBE_HEIGHT 39.91
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
Post by RollieRowland »
Correct, I left the default value for the rmax2. The value in my eeprom is currently set to zero.geneb wrote:If you're using FSRs under the bed, I think Z_PROBE_HEIGHT should be 0.
g.
If this is the Trick Laser kit, I would advise you to put it together without delay. The MAX METAL is far easier to assemble, and designed to be auto-aligning. MUCH less time to assemble, and a lot fewer ghosts to chase. My firmware's calibration system routinely finds tower radius offsets near zero, which is ideal.mhackney wrote:In the meantime, I did pick up one of the Max Metal kits that Eagle sold. I am thinking about building it up, calibrating it so I know it is good and then moving the effectors, arms and carriages from my V1 to this setup to test and vice versa. It should be an interesting test to see where the problem migrates.
Post by RollieRowland »
Yes, there is no calculation for travel time at the moment. This is planned however. For the iterative calibration, it is also unfinished.Paxy wrote:First of all, great job for version 3 of this great tool.
During this writing I am still trying to complete calibration process after heat-bed is changed.
With 3.0.0A calibration process (Basic calibration) took very long as it pause for 2 seconds after every move.
Is there any parameter that can be changed to make calibration faster. With 2.0.5 I had continuous movement during calibration and entire process finishes in about 30 minutes (H.A.I Calib).
Z probe to center, and Z probe to fist (close to the X axe) point is without delay, every other movement with 2 seconds delay.
P.S. Iterative Calibration button do not start any action (unlike 3.0.0PA)
Also there is some issue with Print console that not showing Z height when it is triged but later when this round end. (Perhaps this is reason for 2s delay issue).
What I mean here is that the height of the zprobe is not calculated by the program. Therefore the final z height will not be able to be printed on. All parameters except the z max length will be correct though.duvdev wrote: Hi
What do mean when you say
"The zprobe setting does not operate properly yet, so it requires that you manually set your z height with your probe in place prior to calibrating "
Do I have to place a paper on the bed and down the head until it grub the paper and the add the probe and see how much it is under the hot end?
It's probably your number format settings that you need to change, not your language. I've ran into this before since Europe and other places use a comma ',' as a decimal place, whereas Canada/US use a dot '.'kalliator wrote:Hi!
is it possible to implement language support in your tool RollieRowland? I tried to switch my OS to english but it does not work.
for Example: Diagonal Rod lenght is 418.000 and that comes out as 418000. so I have no chance to run that wonderfull tool.
Any Help would be greatly appreciated!
thanks,
Kalle
Thanks a lot! You absolutely made my dayJrjones wrote:It's probably your number format settings that you need to change, not your language. I've ran into this before since Europe and other places use a comma ',' as a decimal place, whereas Canada/US use a dot '.'kalliator wrote:Hi!
is it possible to implement language support in your tool RollieRowland? I tried to switch my OS to english but it does not work.
for Example: Diagonal Rod lenght is 418.000 and that comes out as 418000. so I have no chance to run that wonderfull tool.
Any Help would be greatly appreciated!
thanks,
Kalle
In Windows it's under Control Panel > Region and Language > Additional Settings > Numbers
Change the "Decimal Symbol" to '.' and the "Digit Grouping Symbol to "," and click apply. You can type them in the field if they aren't in the drop down list.
Yes, I used basic mode, as well as set the max iterations to 10, which apparently doesn't work.Micael wrote:Did you use the basic mode, because RollieRowland said on the last page that it was the only mode that was currently working (not sure if still true).
If you did I would advise making a mattercontrol macro to check for repeatability, I had that problem and went through several FSR systems and replaced arms and so on until I discovered that it was actually the e3d mount that was causing those issues.
Can't say with certainty since I don't have my printer connected to the computer at the moment, but either way the gist of it is that you want to emulate the movements the software is doing, and probe more or less in the same place the software is doing, and repeat that a couple of times while nothing down the values to see what's the difference between different readings on the same point, so for example:G28
G1 Z10 X0 Y0 F5000
G30
G1 Z10 X-110 Y-65 F5000
G30
G1 Z10 X0 Y0 F5000
G1 Z10 X110 Y65 F5000
G30
G1 Z10 X0 Y0 F5000
G1 Z10 X110 Y-65 F5000
G30
G1 Z10 X0 Y0 F5000
G1 Z10 X-110 Y65 F5000
G30
G1 Z10 X0 Y0 F5000
G1 Z10 X0 Y130 F5000
G30
G1 Z10 X0 Y0 F5000
G1 Z10 X0 Y-130 F5000
G30
Post by SirLinhart »
Return to “General Tips 'N Tricks”