DuetWiFiFirmware minor release 1.15c
-
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.
-
That's interesting then because my JohnSL is hooked to the the E0 STOP and works perfectly fine with 1.15c firmware.
-
Ok, figured out why my bed temperature keeps faulting. One of the Sch-row terminals is froze in the housing. Dos anyone now where i can find a Replacement for the bed power Terminals?
-
has anyone had any Extruder drive control issues, on my test print i am getting Blobs of plastic where it starts a new round in the outer shell.
-
OK, tried another Slicer, just on the chance something in the gcode. Issue manifest itself after a z movement. it can be seen when i try to home xy. The z moves up and the y go's to the stop and stops. then the y jumps in the direction it was moving. Looks like the same thing when i am running a print, except the z moves up and the selected tool (Extruder) jumps. giving me a blob of plastic. any ways hop this makes some sens and is helpful for any one with a Debugger.
Printer type: reprappro mendel
Fermware: 1.15C -
OK, tried another Slicer, just on the chance something in the gcode. Issue manifest itself after a z movement. it can be seen when i try to home xy. The z moves up and the y go's to the stop and stops. then the y jumps in the direction it was moving. Looks like the same thing when i am running a print, except the z moves up and the selected tool (Extruder) jumps. giving me a blob of plastic. any ways hop this makes some sens and is helpful for any one with a Debugger.
Printer type: reprappro mendel
Fermware: 1.15CThat's an odd symptom. Can you post a video?
Two notes:
- When you home all, if you are using the standard homing files on a Cartesian printer, then X and Y are homed together. Whichever one homes first will stop until the other is homed. So if Y homes before X, then Y will stop until X has homed.
- A common cause of an axis pausing for a moment when it should be reversing direction is a loose pulley.
-
No loose pulleys. Same hardware i was ruining with the Old Duet Controller. have tried to post pictures and movies before at your request. Only to have them blocked. Sorry. Hears my homeall.g file:
; Mendel home all file for use with dc42 Duet firmware
; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions
G91 ; Set to Relative Positioning
G1 Z4 F200 ; move hot end up by 5mm
;
G1 X240 Y240 F3000 S1 ; Home and set x and y axes
G92 X220.00 Y212.00 ; Initial homing done, now set fine Adjustments
G1 X-5 Y-5 F200 ; Back off end stops by 5mm
G1 X240 Y240 S1 ; Re-home X and Y at slower feed rate
G92 X220.00 Y212.00 ; Set top level Absolute Coordinates
;
; Adjust the XY coordinates in the following to place the IR sensor over a suitable spot
; If you are using a dc42 IR sensor then you can change the coordinates to be near the centre of the bed
G90 ; Set to Absolute Positioning
G1 X100 Y100 F6000
G30 -
My only comment on your homing files is that we don't normally use G92 in them any more. Instead we use M208 commands in config.g to tell the firmware what the bed limits are, which are also the positions assumed when endstop switches are triggered.
Please post your config.g file.
