inconsistant operation
-
You will need to be more specific about the G0/G1 error message. But my guess is that the rest of the message is "insufficient axes homed". If so, please follow the first rule up upgrading RepRapFirmware: always read the upgrade notes for the version you are upgrading to and any versions you skipped.
-
could an example of config.g for printer with 2.01 and dwc current version be published? The examples for config files are from 1.17-1.19 firmware. The firmware keeps advancing but all the other wiki data isn't following along the same or even close pace. Image the new comer just buying a duet first time comparing documentation to what wiki shows.
And these info I was able to find shows S2 placed in every non axes move during a homing command run. I have that covered. The probe command error is coming for the deploy retract macros not my homing files. It's not a config problem but something firmware based. I found many other bl touch users reporting the same behavior. If it's not firmware it's the interface. I can only believe that if the printer performs the homing start to finish 2 or 3 times correct, than another time "M280 P7 S90 bad command" error displays it's got to be a software issue. Otherwise it would always do it. This is the entire error message. "M280 P7 S90 bad command" and doesn't remain in log and not reported to m122 call. When it does happen probe enters blinking state, and needs reset via M280 P7 S160. This error is generated when M402 command from homeall.g is running retract.g macro.
-
I think there must be something wrong with your M280 P7 S90 line, such as a non-printing character in it somewhere, because the only times that the "bad command" error message is produce are when a line of GCode contains something other than whitespace or comments, and either doesn't start with letter G, M or T, or it does start with one of those letters but if it is G or M then it isn't immediately followed by a decimal digit.
Please try deleting and retyping that line. If that doesn't help, please upload your retractprobe.g file for me to look at and try out.
-
Um whats the deal with this java script error
I've power cycled dozens of times, restored factory setting, applied settling erased all gcode files from card and it keeps happening. I launch browser and and type M80 and blam there it is. error and disconnect. I have posted this before and Chrishamm responded to someone else saying he had a fix but I can find one.
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:
Version: 1.21.2-dc42
Message: TypeError: rememberedGCodes.indexOf is not a function
URL: http://192.168.1.50/js/dwc.js
Line: 1133:52
Error object: {} -
is there a change i don't see with mesh level.g I have probe and homing working with homeall.g. that tells me deploy/rectract g are good. But run mesh comp from dwc doesn't deploy probe. The m401 command isn't being executed even though its in the meshlevel.g. It just moves to starting position and heads down never deploying probe with m401. Home z and it does.
meshlevel.g
T0 ; Select first hot endG91 ; relitive moves
G1 Z5 F3000 ;lift Z 5mm
G1 X-295 y-302 F1500 S1 ;relative move to x,y -295mm neg dir stop at switch
G1 X5 Y5 F1000 ;relative back off switch 5mm pos dir
G1 X-295 Y-302 F360 S1 ;relative move x,y -302mm alliance neg stop at switch slowlymeshlevel.G90 ; Absolute coordinates
G1 X52 Y250 F3000 ; Go to first bed probe point and home the Z axisM557 X52:245 Y250:290 S20 ; Bed probe from X52 to 245 and Y50 to 302 in 60mm increments
M401 ; Lower BLTouch probe
G29 S2 ; Clears bed height map in RepRapFirmware
G29 S0; Kicks off the Z probing across the height map
M402 ; Retract BLTouch probeM374 ; Save calibration data. Default is sys/heightmap.csv
G1 X148.5 Y151 F3000 ; All done - move mid bed
-
Can you upload a zip file of your entire sys folder?
-
@sir-printsalot said in inconsistant operation:
Um whats the deal with this java script error
I've power cycled dozens of times, restored factory setting, applied settling erased all gcode files from card and it keeps happening. I launch browser and and type M80 and blam there it is. error and disconnect. I have posted this before and Chrishamm responded to someone else saying he had a fix but I can find one.
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:
Version: 1.21.2-dc42
Message: TypeError: rememberedGCodes.indexOf is not a function
URL: http://192.168.1.50/js/dwc.js
Line: 1133:52
Error object: {}Have you tried chrishamm's 1.22 release? I've added it to the 2.01 release now, it's at https://github.com/dc42/RepRapFirmware/releases/download/2.01/DuetWebControl-1.22.zip.
-
[0_1534207033527_sys.rar](Uploading 100%)
THE FILE YOU REQUESTED!
Right now I have a print running about an hour which is great. I had to run mesh level 4 times before I could get a height map though. I'm using 49 points and the first 1 run at it throw a bad command m280 p7 s10. and the other 2 probe didn't fully retract. the forth time it finished and created map. This was after down graded DWC to 1.21.1
I get java error about gcode every single command with both 1.21.2 and 1.22 adds low vin warning when I'm 24.7 vdc on my meter mounted next to psu. Warning say .4 vin and pause nothing because nothing is running because if i issue a command it with java disconnect me. Weird. no issues with 1.21.1 so far. -
-
I'll take a closer look in the morning but there are a few things I might suggest cleaning up.
-
@sir-printsalot said in inconsistant operation:
probe didn't fully retract. the forth time it finished and created map. This was after down graded DWC to 1.21.1I get java error about gcode every single command with both 1.21.2 and 1.22 adds low vin warning when I'm 24.7 vdc on my meter mounted next to psu.
If you tell me exactly what javascript error message you get with 1.22 then I'll ask chrishamm to look into it.
-
@Sir printsalot: Do an "Apply Settings" on the same device where you get the error.
-
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. -
I've asked Christian to take a look. Some other users have reported the same error message, but AFAIK they have all got past it.
-
Well I not smart enough to get past it. So with that shelved wait for Chrishamm I want to focus on 1 item at a time. I'm working with homez.g by itself. after x and y are homed I have machine physically placed with nozzle 5mm off bed which is 5.96 mm probe triggering height. My z coordinate reading is 0 for some reason. I run homez.g and m401 and g30 than m402 run. I have now raise z after in the macro. z raises back to starting position and display reads z0. z is actually back at 5 nozzle 5.96 triggering. where is the 5mm move up coming from and why does the g92 z0 get issued without an offset that includes this un written move. I'm learning more by separating macro and running them separately.
-
; homez.g
; called to home the Z axisthis is homez.g where the 5mm lift isn't commanded but happens and reflects z0 when physically at 5.96
G91 ;relative moves
G1 Z5 F200 S2 ;raise head 2mm to ensure it above trigger height
G90 ;back to absolute moves this might be wrong G91
G1 X148.5 Y151 F2000 ;put probe at bed center
G91 ; relative moves
M401 ;run deploy probe macro
G30 ; lower head, stop when probe triggered and set Z to trigger height
M402 ;run Retract probe macro
G90 ;back to absolute
G92 Z0this is homeall.g where z finishes out at 5.96 and physically there.
; homeX,Y.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sat Nov 25 2017 12:15:39 GMT-0500 (Eastern Standard Time); Relative positioning
G91
G1 Z5 F3000 S2 ;lift Z 5mm
G1 X-295 y-302 F1500 S1 ;relative move to x,y -295mm neg dir stop at switch
G1 X5 Y5 F1000 S2 ;relative back off switch 5mm pos dir
G1 X-295 Y-302 F360 S1 ;relative move x,y -295mm alliance neg stop at switch slowly
G90 ;absolute moves
G1 X148.5 Y151 F2000 S2 ; put probe center of bed
G91
M401
G30 ;lower probe set height
M402
G90i don't see anywhere in these macros a lift after completion and it didn't do it under 1.19.1 firmware and 1.15.1 dwc
-
sorry to keep adding but I wanted it documented. Ok so I left the machine at it's 5.96 height after homeall.g where display show 5.96 height. I than type in gcode field M401 and than G1 Z0 F2000 S1 and the results are.
M401 command probe deployed. G1 Z0 F2000 S1 displayed changed to Z0 no machine move physically happened. Same as sending a G92 Z0 command would. Some thing is definitely going on.I'm not using printer anymore until someone has time to help. I already has bent parts. I will patiently wait for someone willing to help, I'm just lost. Thank you
-
@sir-printsalot said in inconsistant operation:
M401 and than G1 Z0 F2000 S1 and the results are.
M401 command probe deployed. G1 Z0 F2000 S1 displayed changed to Z0 no machine move physically happened. Same as sending a G92 Z0 command would. Some thing is definitely going on.That is exactly what I would expect to happen. To home using a Z probe you use G30, not G1 S1 Zxxx. The G30 command will stop when the height of the nozzle above the bed is at the trigger height of the Z probe, which you have said is 5.96mm.
Homing an axis means establishing a known position for that axis. That position does not have to be zero. But if it makes you feel better, then after the G30 command followed by M402 to retract the probe, you can send G1 Z0 if you wish (note: no S1) to lower the nozzle to touch the bed.
-
@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.
