inconsistant operation
-
@sir-printsalot said in inconsistant operation:
java script error remember gcode is not a function error {} 1153
applies settings button does nothing launches this error.
restore factory setting launches this error.
every button and and text field launches this error.From my experience pressing "Apply Settings" will always restore the proper data type for the affected variable so I am surprised it is not working for you. Can you please try to clear the browser cache including cookies/storage for the printer and see if that fixes it (provided you are using DWC 1.22.1 of course).
-
that buttom is optioned out. When I hover mouse over it it show cycle with line through unable to toggle button icon. Non of any of the fixes are either working or available on my installation. I am experiencing behavior other aren't, or the same without the option to correct. I'm not sure if it's a windows thing.
As far as the triggered height from bed during probing, it's .96 mm. nozzle is offset higher .96mm I don't know where the additional 5mm is coming from. I have never written a lift of 5mm. after g30. The 5mm lift starting is avoidance of bed edge, because x moves 20 mm wider than bed on neg side. if nozzle was lower than bed nozzle will hit bed edge. But after nozzle is centered where it homes z z0 is .96mm above and my safe z travel height. I have never written to raise a second time. It does anyway. Look at my homez and my homeall. Homeall z is the same as homez a far as z homing goes. But homez raises the extra 5mm zeroing z there and homeall leaves z at .96 and writes the correct height. My question is why are the treated differently if the z portions are the same. My thing is after a homing run regardless of where machine goes, the readout needs to be the correct measured value from bed and it is 5mm higher than it actually is. Printing 5mm of air. I have to lower and g92 to correct it is using my Homez.g but not for my homeall.g and they are the same routine. makes no sense and is inconsistent comparatively.
-
What probe type are you actually using right now? P5, P7, P9? Perhaps it's returning to the dive height after a probe.
-
@sir-printsalot said in inconsistant operation:
java script error remember gcode is not a function error {} 1153
Can you try this?
Go to settings, List items, and delete all the entries in Default Gcodes, and hit apply.
-
probe is bl touch smart brand named probe pin. dive hieght is current position z neg 299 mm relative. so no static value to return to. Im away til sat vacation atm. get back to u soon. thank you for all your help. there is a solution.
