Well I have spent around 12 hours trying to get the software to work with my printer and I'm at a loss, have tried different versions (2.1.1, 2.05a and 2.0.4PA), tried all of the 3 calibration methods, different settings, tried with an FSR, and a Z-probe, with different Z-probe Start Height, and different probing speeds, I have reset the eeprom and reset the height to the switch/fsr each time before starting, and the software continually tries to crash my hotend after a while, my most "successful" attempt was with the H.A.I. Calibration where the software goes through a few iterations, one of which was already getting pretty good with most of the height maps bellow 1mm error, and some at 0.0Xmm, however it then decided to change values drastically and as a result while moving from one point to the next it crashed the hot end into the glass..
Basic calibration is pretty much useless for me, because after 1 or 2 attempts after it homes again, it goes down and tries to go through the printer, the reason I believe is this "Z-Probe length set to: -39.735" which doesn't happen with the H.A.I. calibration which puts it at "Z-Probe length set to: -0.100000000000023" and then at "Z-Probe length set to: 0.199999999999989", although these values change slightly from test to test, the last test had these "values Z-Probe length set to: -0.15300000000002" and "Z-Probe length set to: 0.20700000000005" this last test was at a 1mm/s probe speed.
My printer tower are calibrated for a difference of less than 0.1º, and while I can't speak of the accuracy of the device used for this, I used a bahco squaring frame and it is aligned to the point that even putting pressure on the bed end doesn't move it, so if it's not at the < 0.1º is is likely close enough to not cause this sort of issues, I also reset the end stop screws which were measured with a digital caliper, and while I can't say they are 100% at the same height they are likely sub 0.20mm difference, and the software is suppose to compensate for the difference in screw height, so doubt this difference is causing the issue too.
The firmware being used is the one that is advised in the Rostock max v2, and ofc my printer is also a Rostock max v2, where the only hardware change is the hotend which is a E3D V6, connected using the seemecnc ez groove mount adapter and aluminium rods like the ones that come with the original hot end (but bigger).
When I was trying with the FSR, the FSR was placed directly on the hot end nozzle, through a plastic circular spacer and glued with hot glue, and the transition between the FSR and the connection to the rambo board was being done through an arduino with a voltage divider circuit to change sensitivity, adding to that I was also controlling how much sensitivity was triggering or not triggering the Z-min through a software on the arduino, tried several different sensitivities, and none of it seemed to make a difference, and ofc the hardware was in fact detecting the input, since it could go through several probings.
Since the software wasn't working I decided to switch the FSR for a microswitch (OMRON SS-5GL13-F), glued to the side of the E3D V6 hotend, the activation point is located at around X: -9.50 Y: -11.00, with the following configuration:
#define MIN_HARDWARE_ENDSTOP_Z true
#define FEATURE_Z_PROBE true
#define Z_PROBE_PIN 10
#define Z_PROBE_PULLUP true
#define Z_PROBE_ON_HIGH false
#define Z_PROBE_X_OFFSET -9.50
#define Z_PROBE_Y_OFFSET -11.00
// Waits for a signal to start. Valid signals are probe hit and ok button.
// This is needful if you have the probe trigger by hand.
#define Z_PROBE_WAIT_BEFORE_TEST false
/** Speed of z-axis in mm/s when probing */
#define Z_PROBE_SPEED 2
#define Z_PROBE_XY_SPEED 150
/** The height is the difference between activated probe position and nozzle height. */
#define Z_PROBE_HEIGHT 0.35
/** These scripts are run before resp. after the z-probe is done. Add here code to activate/deactivate probe if needed. */
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
Reporting H when being pressed and L when not, and ofc it is working since I can go through several iterations without running into any issues.
Here is the console and printer console log for the latest attempt (version 2.0.4ap H.A.I. with 1mm/s probe speed)
https://www.dropbox.com/s/mxzqqqruidkhy ... t.rtf?dl=0
and a screenshot of the software at the time of the crash
https://www.dropbox.com/s/svx5gxgewc9h4 ... 6.png?dl=0
as you can see from the log and even from the screenshot the last 2 probes are completely off, what happened was that the printer started making a pretty long arch from probing point to probing point, and in doing so the head (and probe) ended up crashing against the glass, and ofc by that point the printer started skipping steps due to forcing the head into the glass.
Anyway if you have any ideas of what I should do, or even suggestions on what I should test, it would be appreciated.
Thank you.
