DuetWiFiFirmware minor release 1.15c
-
I seem to remember reading something somewhere about the firmware finding the object height by reading the last G1 Z command in the gcode file. If you have a G1 Z at the end of your print to lift the head, that can screw it up. You can still lift the head but use G0 instead of G1 (does the same thing I think).
-
I seem to remember reading something somewhere about the firmware finding the object height by reading the last G1 Z command in the gcode file. If you have a G1 Z at the end of your print to lift the head, that can screw it up. You can still lift the head but use G0 instead of G1 (does the same thing I think).
Aha! Thank you, that is precisely the problem. I have a G1 Z100 in my ending script. I'll change that to G0 Z100.
-
A workaround for that is to put a comment starting with upper case E on the end of that G1 line. I'm not sure that using G0 instead of G1 will make any difference.
-
Found where I'd read that about G0 - it was here https://miscsolutions.wordpress.com/2014/06/11/five-tips-for-using-dc42-firmware-on-the-reprappro-ormerod/. No offence intended but if G0 doesn't work, maybe you should amend you blog David.
-
Using G0 fixed the problem. Many thanks for the help.
-
Those of you who are having Z probe trouble going from 1.15b to 1.15c, what probe type do you have set in M558, and how do you have the probe connected?
Any more thoughts on this issue?
I know you are quite busy, and hopefully have a life outside 3D printing, so I understand any delay.
-
Sorry I won't be able to look at this for several more days. I've already looked at the code changes in 1.15c and I didn't find anything to explain it.
If you wish, you could try connecting the fsr board to the Z probe connector instead of E0 and use probe type 5.
-
Just code my board in the mail 1 week ago. had to print a Case. Got wired and mounted today.
Improvements:
Stepper control vast improvement.
Temperature control wall much stabler, terns off when the gcode changes the temperature wall its printing.Working on reproducing it right now
-
OK, Cant reproduse
-
David or anyone, is the comment about M301 in config.g relevant if upgrading from 1.15-beta3 release?
-
Yes it is.
-
Thanks David. I'll upgrade now and know what to watch for.
-
Firmware update to 1.15c went smoothly but DWC does not seem to be updating even after a power reset. Unless HTML: 1.11b-dc42, JS: 1.11b-dc42 is correct for the 1.15c tagged binary on git?
-
Did you upload the DuetWebControl.bin file through the Settings page?
-
David, yes I did and it appeared to upload correctly with no returned errors.
-
As you are running DWC 1.11 at present, you need to run M997 S2 after uploading it. The web interface will disconnect and you will need to wait about 3 minutes before you can reconnect it. If you have a PanelDue running firmware 1.14 or later connected, you can see the firmware update progress on it.
-
Thanks David. I updated to the latest PanelDue firmware today too.
-
Got it, plus I had to flush browser cache. I forgot about the M997. I updated the WiFI server too so this machine is on the latest and greatest of everything. Thanks!
-
I should also add…
I had no problems with my FSRs and JohnSL connected to the E0 connector and I DO have G0 Z150 to terminate my bed.g file.
-
Sorry I won't be able to look at this for several more days. I've already looked at the code changes in 1.15c and I didn't find anything to explain it.
If you wish, you could try connecting the fsr board to the Z probe connector instead of E0 and use probe type 5.
I tried this and it worked! The signal line from the FSR board (Green wire) moved to "Z_PROBE_IN". Black to GND and Red to +3.3V.
It must have had something to do with the E0 endstop being used as the probe signal input.
I also tried firmware 1.15c with 18 bed probe points and that worked as well. So the only things I changed were going from E0 STOP to Z_PROBE_IN for the FSR probe board signal connection. This required changing the M558 parameter from P4 to P5.
For clarification, the G0 vs. G1 conversation that happened in the recent posts… I don't believe it has anything to do with the FSR probes not working. That was something to do with the reported object height on the DWC interface.
