leadinglights
About
- Username
- leadinglights
- Joined
- Visits
- 38
- Last Active
- Roles
- Member
Comments
-
Thank you for your quick reply. The input to the RAMPS board is pin D11. One of the two sensors is selected by setting either RAMPS pin D4 for the touch probe, or by setting RAMPS pin D5 to select the underbed sensor. The outputs of the sensors are…
-
Thank you Repetier, G134 worked perfectly and stored the Z difference in EEPROM. I have put a video on YouTube which shows this, along with other parts of the calibration procedure. One thing that is not presently working, is that I haven't found …
-
I didn't realize that EXT_0_OFFSET should always be 0 although I probably did keep it at 0 Modifying my sensors so that the output could be shared with one common pin was just a matter of tri-stating the output of the un-selected sensor. The sequen…
-
I have previously manually selected the sensor controller by physically moving the pin onto D18. This allowed me to use G30 to get values to enter into EXT0_Z_OFFSET and EXT1_Z_OFFSET in the EEPROM before swapping to the other sensor for doing a m…
-
Thank you Repetier. If I modify my two Z sensor controllers so that the active sensor is selected by a spare pin on the RAMPS but that the output of both is wire OR'd to one pin (e.g., RAMPS D18) Is there any obvious reason that this would not work?…
-
Thank you Repetier, that now works better than I could have hoped. Adjusting the gain and bias through the EEPROM I was able to set up within minutes and it now is within 1 degree from 150 degrees to 250 degrees on both hotends. Mike
-
Thank you Repetier. I have now checked out the second hot-end/thermocouple/AD8495 plus a spare and I get a bit of a scatter from 4% low to 1% high on slope though somewhat more consistent on offset. This seems to be within the believable sum of erro…
-
Thanks Repetier, that looks like it was the cause of the problems.Should I change that in Configuration.h and in the configuration string and will it copy true? I have not been able to find ZHOME_HEAT_HEIGHT on any page of the firmware configuration…
-
After homing all from the Repetier Host, shown values are:- X=0, Y=0, Z=26 Note: Bed to the nozzle at Zmax is adjusted to 25mm ±0.1mm with glass plate of 1.9mm ±0.05mm on the bed so homed bed to nozzle is 23.1mm ±0.15mm On giving the G32 c…
-
I have been trying it again but no change. Configuration.h is at https://drive.google.com/file/d/1iKN22GlurufMdL4kiZgDOnJVBPNPMhKi/view?usp=sharing No changing of Z_PROBE_Z_OFFSET, Z_PROBE_BED_DISTANCE, Z_PROBE_SWITCHING_DISTANCE, Z_PROBE_REPETITI…
-
I will have to make a clean copy (and try it out) as the existing one is a mess -having fallen to changing anything that I thought might work. AFK for the next few hours but as soon as I am back. Mike
-
When I fit the printer mechanism and can return to a reasonable Z movement I will come back to Repetier firmware. I can only guess that having Z movement restricted to 26mm is causing all Z travel to be about 20mm. Temporarily changing to Marlin has…
-
Still not good. I have now fitted a new Arduino board, a new RAMPS board, pre-cleared the EEPROM, configured and programmed software 1.0.4dev. Zeros are in the expected direction, now set to home to Zmax. The result is that travel moves are still a…
-
I assume that clear the EEPROM is M502, M500, is this correct. This does not seem to have changed anything.I looked through the Configuration.H line by line but couldn't find anything unexpected.Something that is new, or not noticed before, is that …
-
Thanks MartinH I will do that first thing tomorrow. Mike
-
I was on 0.92.9 but tried 1.0.4dev, downloading the complete software. There was no difference in behaviour other than that my pins.h did not seem to be compatible and I lost panelacces to the printer. One possible clue is that homing each axis in…
-
I found a temporary work around. At the moment I am not trying to level the bed but simply get data from the Z probe conditioning circuit at the mesh points that will be used for actual bed leveling. I am now using a GCode file with a sequence like …
-
O.K., So the file seemed to be accepted but was not. I will try something different tomorrow.
-
I managed to attach the Configuration.H by renaming it to Configuration.txt Thanks for any help or clues where to look. Mike
-
I have tried that, along with many combinations of Z_PROBE_BED_DISTANCE, Z_PROBE_HEIGHT and even (in case) Z_PROBE_OFFSET. On one of my other printers, a Delta, everything just works as it should, while a Cartesian printer which I have now given to…
-
O.K.,I found it. My guess is that I left out something and the configurator did not present the Z_PROBE_DELAY for setting. Mike
-
Starting higher makes no difference as the software starts looking for the probe contact immediately at the end of the X or Y movement. The usual symptom is that the firmware reports that the Z probe was triggered before probing. I think what I am a…
-
Can a recovery time be added to the Z probe part of the firmware? The significance of this is that some Z probes such as piezo disk probes are triggered by the deceleration after an X or Y move and before the probe downward move. A short time, typic…
-
Or even a pointer to where in the code I could insert something like delay(100) to give a short delay before each Z down during Z probing.