• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

DuetWiFiFirmware minor release 1.15c

Scheduled Pinned Locked Moved
Firmware installation
11
79
12.2k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    mhackney
    last edited by 19 Sept 2016, 19:19

    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!

    My 3D Printing blog: http://www.sublimelayers.com
    Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

    1 Reply Last reply Reply Quote 0
    • undefined
      mhackney
      last edited by 19 Sept 2016, 19:43

      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.

      My 3D Printing blog: http://www.sublimelayers.com
      Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

      1 Reply Last reply Reply Quote 0
      • undefined
        Toddimus
        last edited by 19 Sept 2016, 22:09

        @dc42:

        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.

        1 Reply Last reply Reply Quote 0
        • undefined
          mhackney
          last edited by 19 Sept 2016, 23:20

          That's interesting then because my JohnSL is hooked to the the E0 STOP and works perfectly fine with 1.15c firmware.

          My 3D Printing blog: http://www.sublimelayers.com
          Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

          1 Reply Last reply Reply Quote 0
          • undefined
            guywinslow
            last edited by 20 Sept 2016, 03:22

            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?

            1 Reply Last reply Reply Quote 0
            • undefined
              guywinslow
              last edited by 24 Sept 2016, 21:33

              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.

              1 Reply Last reply Reply Quote 0
              • undefined
                guywinslow
                last edited by 25 Sept 2016, 04:20

                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

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators
                  last edited by 25 Sept 2016, 08:21

                  @guywinslow:

                  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

                  That'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.

                  Duet WiFi hardware designer and firmware engineer
                  Please do not ask me for Duet support via PM or email, use the forum
                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    guywinslow
                    last edited by 25 Sept 2016, 18:53

                    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

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators
                      last edited by 25 Sept 2016, 19:42

                      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.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        guywinslow
                        last edited by 26 Sept 2016, 14:36

                        Ok, So the Coordinate System Calibration and the Limits need to be the same. Will this affect the Extruder and Y drive Extra movement i am seeing?

                        I have run test to see if it actually extrudes 100mm and the y drive actually moves 100mm when i send the G1 Command and that works fine. its just the articulated commands in a print. Almost like a timing error. Any ways the ramblings of and old man.

                        Config.g:
                        ; Configuration file for RepRap Ormerod
                        ; RepRapPro Ltd
                        ;
                        M111 S0 ; Debug on
                        M550 PTricolour Mendel WIFI
                        M551 Pgdww1620
                        M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xEA ; Set the MAC address
                        M552 S1 ; Enable WiFi

                        M555 P2 ; Set output to look like Marlin
                        M906 X800 Y1000 Z800 E800:800:800:800:800 ; Motor currents (mA)

                        M305 P0 R4700 T10000 B3988 ; set bed thermistor parameters
                        M307 H0 A128.4 C424.4 D2.4 B0
                        M307 H1 A762.7 C99.7 D5.5 B0

                        M574 X S1 ; Set endstop configuration
                        M574 Y2 S0 ; Set endstop configuration
                        M574 Z S1 ; Set endstop configuration
                        M569 P0 S0 ; Set X Axis Direction
                        M569 P1 S1 ; Set Y Axis Direction
                        M569 P2 S0 ; Set Z Axis Direction
                        M569 P3 S0 ; Set E0 Axis Direction
                        M569 P4 S0 ; Set E1 Axis Direction

                        M558 P1 X1 Y0 Z1 ; Set Z probe type
                        G21 ; Work in mm
                        M92 X100.25 Y100.25 Z4001.50 E420.00 ; Set axis steps per unit
                        M570 S180 ; Set heater timeout
                        ;
                        M563 P0 D0 H1 ; Create tool 0 = Color 1
                        M563 P1 D1 H1 ; Create tool 1 = Color 2
                        M563 P2 D2 H1 ; Create tool 2 = Color 3
                        M563 P3 D3 H1 ; Create tool 3 = Color 4
                        M563 P4 D4 H1 ; Create tool 4 = Temperature for this tool should be Set Low
                        G10 P0 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 0 operating and standby temperatures
                        G10 P1 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 1 operating and standby temperatures
                        G10 P2 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 2 operating and standby temperatures
                        G10 P3 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 3 operating and standby temperatures
                        G10 P4 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 4 operating and standby temperatures
                        G31 P500 Z0.65 ; Set the probe height and threshold PLA = 0.65, ABS = 0.75
                        T4
                        ;
                        M201 X800 Y800 Z15 E1000 ; acceleration tweaks for improved finish
                        M203 X15000 Y15000 Z150 E3600 ; speed tweaks for improved finish
                        ;
                        M208 X200 Y200 Z120 ; set axis max travel
                        M208 X0.0 Y0.0 Z0.0 S1 ; set axis minimum (adjust to make X=0 the edge of the bed)
                        M210 X200 Y200 Y170

                        I just realized i still had my M906 command setup for the Old Duet board and expansion board. as there is no expansion board hear and only two extruders i will modify and test. I will also remove the M210 command as well. Looks like its no longer supported

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          dc42 administrators
                          last edited by 26 Sept 2016, 15:12

                          I see that you have G92 X220.00 Y212.00 in your homing files, and M208 X200 Y200 Z120 in config.g. So your G92 command sets the X and Y position outside the declared printable area. This may account for the jumps you are seeing when homing. I suggest you remove the G92 commands in the homing files and use M208 X220 Y212 Z120 in config.g.

                          Also you have M574 X S1 in config.g. I presume it should be M574 X2 S1.

                          Is there a reason why your X endstop switch is NC/active high whereas your Y endstop switch is NO/active low, according to your M574 commands?

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            guywinslow
                            last edited by 28 Sept 2016, 14:56

                            X and Z are the infrared Sensor. I am getting sloppy in my coding. As the X and Y are the infrared Sensor i will comment it out and try

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              guywinslow
                              last edited by 28 Sept 2016, 14:57

                              Sorry X and Z are the infrared Sensor i will comment the M574 command out

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                guywinslow
                                last edited by 28 Sept 2016, 15:06

                                Ok, had to put X and Z back in:
                                M574 X0 S1 ; Set endstop configuration
                                M574 Y2 S0 ; Set endstop configuration
                                M574 Z0 S1 ; Set endstop configuration

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  guywinslow
                                  last edited by 28 Sept 2016, 15:28

                                  Ok, Ran another test print. issue still exists. its like the extruder continues to extrude wall the hot end is moving in word to print the next line. Same thing with my y end stop. the actual hardware stop is close to the point where the switch gets trigger. during the first seek to find the end the controller drives the y past the end just enough such that it hits the hardware before it lock hold the motor. And the next G1 command backs the y table off to do the fine adjustment. Any way and observation

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    dc42 administrators
                                    last edited by 28 Sept 2016, 16:22

                                    It sounds to me that your homing issue is because the endstop switch is not triggering before the physical stop. That would explain the pause. Can you adjust the position of the switch, so that it always triggered before the physical stop?

                                    You can post a video to YouTube and link to it from this forum.

                                    Duet WiFi hardware designer and firmware engineer
                                    Please do not ask me for Duet support via PM or email, use the forum
                                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      deckingman
                                      last edited by 28 Sept 2016, 17:18

                                      @guywinslow

                                      Hi. There are a couple of things I don't understand in your config.g. You've set axis directions (M569) for E0 and E1 therefore I'm assuming from that, that you have 2 extruders. Is that correct? Earlier on you've set the motor currents (M906) for 5 extruders but that won't matter if you are only using 2 of them. Later on you've set steps per mm (M92) for X,Y,Z and E, indicating that you only have one extruder. If you have 2 then you would normally have something like E420:420 instead of just E420. I'm not sure how the firmware would react if you only define steps/mm for one extruder but try to use two.

                                      Then you have defined 5 tools, each with their own extruder (D0 to D4) but sharing the same heater indicating that in fact you do have 5 extruders, in which case you ought to set steps/mm for all 5. Then for each of the 5 tools, you have an X offset of 20 which means that the nozzles are all 20mm off set in X but the Y and Z offsets are all the same. This would mean that you would have a single nozzle with 5 filament inputs but in that case, you wouldn't need to have an X offset. For tool definitions where there are multiple nozzles, usually one tool would have zero offsets and the others would be offset from that tool.

                                      Can you let us know how many extruders and how many hot ends (nozzles) you have and if the hot ends share the same heater? If you have multiple nozzles, what are the physical distances between them?

                                      Ian
                                      https://somei3deas.wordpress.com/
                                      https://www.youtube.com/@deckingman

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        guywinslow
                                        last edited by 29 Sept 2016, 02:30

                                        Sorry, this was original a copy from the old Duet. Specs:

                                        Extrudes: 2
                                        Hot ends: 1

                                        I indeed fead different Filaments into one hotend (2 feeds). the Tool head offset is do to the fact my x carage was supposed to use two hotends, but i only have on. and its easier to work on in the position its in.

                                        hear is a Cleaned up version, i will run a test print using:
                                        ; Configuration file for RepRap Ormerod
                                        ; RepRapPro Ltd
                                        ;
                                        M111 S0 ; Debug on
                                        M550 PTricolour Mendel WIFI
                                        M551 Pgdww1620
                                        M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xEA ; Set the MAC address
                                        M552 S1 ; Enable WiFi

                                        M555 P2 ; Set output to look like Marlin
                                        M906 X800 Y1000 Z800 E800:800 ; Motor currents (mA)

                                        M305 P0 R4700 T10000 B3988 ; set bed thermistor parameters
                                        M307 H0 A128.4 C424.4 D2.4 B0
                                        M307 H1 A762.7 C99.7 D5.5 B0

                                        M574 X0 S1 ; Set endstop configuration
                                        M574 Y2 S0 ; Set endstop configuration
                                        M574 Z0 S1 ; Set endstop configuration

                                        M569 P0 S0 ; Set X Axis Direction
                                        M569 P1 S1 ; Set Y Axis Direction
                                        M569 P2 S0 ; Set Z Axis Direction
                                        M569 P3 S0 ; Set E0 Axis Direction
                                        M569 P4 S0 ; Set E1 Axis Direction

                                        M558 P1 X1 Y0 Z1 ; Set Z probe type
                                        G21 ; Work in mm
                                        M92 X100.25 Y100.25 Z4001.50 E420.00:420.00 ; Set axis steps per unit
                                        M570 S180 ; Set heater timeout
                                        ;
                                        M563 P0 D0 H1 ; Create tool 0 = Color 1
                                        M563 P1 D1 H1 ; Create tool 1 = Color 2
                                        M563 P2 D2 H1 ; Create tool 2 = Color 3
                                        M563 P3 D3 H1 ; Create tool 3 = Color 4
                                        M563 P4 D4 H1 ; Create tool 4 = Temperature for this tool should be Set Low
                                        G10 P0 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 0 operating and standby temperatures
                                        G10 P1 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 1 operating and standby temperatures
                                        G10 P2 X20.0 Y0.0 Z0.0 S0 R0 ; Set tool 2 operating and standby temperatures
                                        G31 P500 Z0.65 ; Set the probe height and threshold PLA = 0.65, ABS = 0.75
                                        T4
                                        ;
                                        M201 X800 Y800 Z15 E1000:1000 ; acceleration tweaks for improved finish
                                        M203 X15000 Y15000 Z150 E3600:3600 ; speed tweaks for improved finish
                                        ;
                                        M208 X200 Y200 Z120 ; set axis max travel
                                        M208 X0.0 Y0.0 Z0.0 S1 ; set axis minimum (adjust to make X=0 the edge of the bed)

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          guywinslow
                                          last edited by 29 Sept 2016, 02:46

                                          Just ran test print with the last config i posted. Still have the extra Extrusion when the extruder starts the next shell line. note i am just printing one layer with this test prints, and in this case i am just printing two complete lines around the part. the passing it to look at the print.

                                          1 Reply Last reply Reply Quote 0
                                          39 out of 79
                                          • First post
                                            39/79
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA