Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. S1lencer
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 43
    • Best 4
    • Controversial 0
    • Groups 0

    S1lencer

    @S1lencer

    6
    Reputation
    4
    Profile views
    43
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    S1lencer Unfollow Follow

    Best posts made by S1lencer

    • RE: And here we go again G29 Bed Mesh leveling going bonkers

      @fcwilt said in And here we go again G29 Bed Mesh leveling going bonkers:

      So Z2 is at X-60.5 and Z4 is at X360.5?
      I had a friend who was having a similar problem and it turned out that he had the Z motors wired the opposite of what he thought and thus each leveling pass made it worse.
      It wouldn't hurt to double check your printer.
      In your M92 command you have Z1600.00:1600. While I doubt this is a problem the correct syntax would just be Z1600 or Z1600.00 if you prefer the trailing zeros.
      And just to make sure, Z1600 would be correct for 2mm (lead and pitch) lead screws - is that what you are using?

      Yes all of it is correct an i corrected the M92.
      Motors are correcly connected and i tried to plug them the other way around, that made things way worse as you and @Nurgelrot described.
      But these things did sadly not help.

      What did the trick was to reduce the Probingspeeds to this:

      M558 P1 R0.5 C"zprobe.in" H5 F600 T50000                                       ; set Z probe type to effector and the dive height + speeds
      
      

      and to give the steppers a little bit more juice upped the game hier from 1400 to 1600 and upped the drivespeed of the steppers to a max rate of 1600.

      Now i finaly have a Mesh Level wich i can trust:
      1e0f6287-25be-45e9-9356-587ee9fcdc29-image.png

      Thanks for all your thougts an the help.
      Will mark this thread as solved.

      Greetings
      Kai

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer
    • RE: Converting the Duet WiFi to use an external antenna

      Ok for the next time i will do that.
      Should be mentioned in the Wiki.

      posted in Duet Hardware and wiring
      S1lencerundefined
      S1lencer
    • RE: Motion Limit Switches

      Hi, had the same question at some point where i was using swithes instead of the stallguard homing.

      My approach was to use some kind of IR-Probe style switches witch would spit out an analog signal and would slow down the axis like in the z-Probing movement with davids IR-Probe but only for X and Y.

      Dont know i that is possible though.

      posted in Using Duet Controllers
      S1lencerundefined
      S1lencer
    • RE: Prusa new kitchen sink XL printer

      Besides the cycloidal geard extruder, the filament path looks like pain in the arse to fiddle the filament in šŸ˜‰ .
      An as an mechanical engineer i am not a huge fan of unsupported beams of aluminum hanging in mid air trying to hold up the linear rails and hole printheadassebly.
      But ohterwise i am curios to see what else prusa will bring to the table with this printer. Looks like an interesting design of the docking for the tools.

      posted in General Discussion
      S1lencerundefined
      S1lencer

    Latest posts made by S1lencer

    • RE: Precision Piezo on a Toolchanger with a Roto Board

      @dc42
      Hi, that did the Trick.
      Thanks fo the wise answer.

      posted in Third-party add-ons
      S1lencerundefined
      S1lencer
    • Precision Piezo on a Toolchanger with a Roto Board

      Hi,
      I am a little bit lost at the moment.
      I have a universal precision piezo Board mounted on the Head of an e3d-Style Toolchanger.
      The complete Toolchangehead (Stepper, Z-endstop = Precision-Piezo on Pin io0.in , and y-Endstop on Pin io1.in) is controlled over a roto Toolboard with CAN Address 24.

      My Problem lies now in the two "Z-Probes".
      First off, I would like to use the Precision-Piezo in digital mode on Pin io0.in. At the moment the Cables are connected as follows, ground -> io0.ground, V+ -> io0.+5v, and signal -> io0.in

      fo the Code in the config I added the following line:

      ; Z-Probe
      M558 K0 P1 R1.0 C"!24.io0.in" H7 F500 T10000                                     ; set Z probe type to effector and the dive height + speeds
      G31 K0 P500 X0 Y0 Z0                                                             ; set Z probe trigger value, offset and trigger height
      

      For the Scanning Z-Probe on the Roto Toolboard, i have the following added to the Config:

      ; Scanning Z probe
      M558 K1 P11 C"24.i2c.ldc1612" F36000 T36000          ; configure SZP as probe 1, type 11, on CAN address 120
      M308 A"SZP coil" S10 Y"thermistor" P"24.temp0"       ; thermistor on coil
      G31 K1 Z2 Y-10                                       ; define probe 1 offsets and trigger height
      M558.2 K1 S15 R101133                                ; set drive current and reading offset
      M557 X10:590 Y10:590 S10                           ; Define mesh grid for probe 1 (overwrites probe 0 mesh grid)
      

      My Questions now are how can i test if everything works correctly? I have at the moment the problem that my Precision-Piezo boart triggers correctly but where can i see if the signal goes through to the duet itself? The same goes for the Moment for the Y-endstop on pin io1.in + io1.+3,3v (simple Omron switch).
      Is there anywhere a dashboard, where I can see if the Signals will be picked up correctly by the duet?
      Fo Example, on my CNC-Mill software i have an simplified IO-Signal overview of all the inputs witch a light witch goes on when triggered.

      Greetings an thanks for the Help.

      posted in Third-party add-ons
      S1lencerundefined
      S1lencer
    • RE: Designing a PWM to Analog mini board for fans

      Hi, i have 6 preassembled boards left over from my last Batch.
      They are from Egons gerber Files and work like a charm.
      Feel fre to contact me about it.

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer
    • RE: Prusa new kitchen sink XL printer

      Besides the cycloidal geard extruder, the filament path looks like pain in the arse to fiddle the filament in šŸ˜‰ .
      An as an mechanical engineer i am not a huge fan of unsupported beams of aluminum hanging in mid air trying to hold up the linear rails and hole printheadassebly.
      But ohterwise i am curios to see what else prusa will bring to the table with this printer. Looks like an interesting design of the docking for the tools.

      posted in General Discussion
      S1lencerundefined
      S1lencer
    • RE: Toolboard V1.1 issue

      It is also possible that the switch suffers from the heat. The springs inside are mostly out of metal and the dimensions of these an thus also the springrate changes with temperature slightly. Is the reapeated reading under the same temperature the same?

      posted in Duet Hardware and wiring
      S1lencerundefined
      S1lencer
    • RE: Motion Limit Switches

      Hi, had the same question at some point where i was using swithes instead of the stallguard homing.

      My approach was to use some kind of IR-Probe style switches witch would spit out an analog signal and would slow down the axis like in the z-Probing movement with davids IR-Probe but only for X and Y.

      Dont know i that is possible though.

      posted in Using Duet Controllers
      S1lencerundefined
      S1lencer
    • RE: And here we go again G29 Bed Mesh leveling going bonkers

      @fcwilt said in And here we go again G29 Bed Mesh leveling going bonkers:

      So Z2 is at X-60.5 and Z4 is at X360.5?
      I had a friend who was having a similar problem and it turned out that he had the Z motors wired the opposite of what he thought and thus each leveling pass made it worse.
      It wouldn't hurt to double check your printer.
      In your M92 command you have Z1600.00:1600. While I doubt this is a problem the correct syntax would just be Z1600 or Z1600.00 if you prefer the trailing zeros.
      And just to make sure, Z1600 would be correct for 2mm (lead and pitch) lead screws - is that what you are using?

      Yes all of it is correct an i corrected the M92.
      Motors are correcly connected and i tried to plug them the other way around, that made things way worse as you and @Nurgelrot described.
      But these things did sadly not help.

      What did the trick was to reduce the Probingspeeds to this:

      M558 P1 R0.5 C"zprobe.in" H5 F600 T50000                                       ; set Z probe type to effector and the dive height + speeds
      
      

      and to give the steppers a little bit more juice upped the game hier from 1400 to 1600 and upped the drivespeed of the steppers to a max rate of 1600.

      Now i finaly have a Mesh Level wich i can trust:
      1e0f6287-25be-45e9-9356-587ee9fcdc29-image.png

      Thanks for all your thougts an the help.
      Will mark this thread as solved.

      Greetings
      Kai

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer
    • RE: And here we go again G29 Bed Mesh leveling going bonkers

      Hi to you both,

      @phaedrux said in And here we go again G29 Bed Mesh leveling going bonkers:

      Does your probe require deploying and retracting? If not, remove the M401 and M402 lines.

      no it doess not and is now removed.

      @phaedrux said in And here we go again G29 Bed Mesh leveling going bonkers:

      You should probably also add M561 to the start of your bed.g to clear any compensations, etc before starting.

      Ok is added

      @phaedrux said in And here we go again G29 Bed Mesh leveling going bonkers:

      What happens if you probe the same point over and over with G30 S-1? Does the reported trigger height increase as well?

      19.6.2021, 20:33:08	G30 S-1
      Stopped at height 0.181 mm
      19.6.2021, 20:33:06	M120 G91 G1 Z5 F6000 G90 M121
      Stopped at height 0.156 mm
      19.6.2021, 20:33:06	G30 S-1
      Stopped at height 0.156 mm
      19.6.2021, 20:33:04	G30 S-1
      Stopped at height 0.151 mm
      19.6.2021, 20:33:02	M120 G91 G1 Z5 F6000 G90 M121
      Stopped at height 0.106 mm
      19.6.2021, 20:33:02	G30 S-1
      Stopped at height 0.106 mm
      19.6.2021, 20:33:00	G30 S-1
      Stopped at height 0.094 mm
      19.6.2021, 20:32:57	G30 S-1
      Stopped at height 0.076 mm
      19.6.2021, 20:32:54	G30 S-1
      Stopped at height 0.031 mm
      19.6.2021, 20:32:50	G30 S-1
      Stopped at height -0.001 mm
      19.6.2021, 20:32:45	G30 S-1
      Stopped at height -0.024 mm
      19.6.2021, 20:32:41	G30 S-1
      Stopped at height -0.049 mm
      19.6.2021, 20:32:37	G30 S-1
      Stopped at height -0.074 mm
      
      

      Does the same as if meshbedleveling.

      @fcwilt said in And here we go again G29 Bed Mesh leveling going bonkers:

      Is Z16 the stepper driving the lead screw at X-60.5 and Z15 the stepper driving the lead screw at 360.5?

      Thanks for leading me to it, the microstepping of 15 was a typo.
      Corrected that and tried evrything again, but to no avail. Same problem persists.
      And yes first z-motor is at x-60,5 and y 150 end the second at X360.5 and y150.

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer
    • And here we go again G29 Bed Mesh leveling going bonkers

      Hi,
      on my second Printer i redid the wirering and tydied some things up.
      Flashed the new 3.3 Firmware on the Duet2Wifi and thougt it would be a good idear to redo the Bedleveling since a new heatbet alongside a new Heater and a springsteel plate war installed.

      Since then i think i must have do something wrong with the Leveling cause the Mesh process adds to evry probing step some tens of a millimeter.

      So the bed looks completly funky and starts at 0.034 and continusly climbs to 2.091mm and that simply cant be true.
      It seems if the probe ist constantly adding a specific Value after echt probing.
      10f5d67f-4fb2-4140-bccb-806643737533-image.png 8ea5ad44-ffb4-4b5e-951f-b97dd82e4c69-image.png

      Looks like some serpentine roads in the Alps šŸ˜‰

      But that is sadly not usable.
      Here are my config.g

      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jun 18 2021 23:45:09 GMT+0200 (MitteleuropƤische Sommerzeit)
      
      ; General preferences
      G90                                                                             ; send absolute coordinates...
      M83                                                                             ; ...but relative extruder moves
      M550 P"HeVo_Rail"                                                               ; set printer name
      M669 K1                                                                         ; select CoreXY mode
      
      ; Network
      M552 S1                                                                         ; enable network
      M586 P0 S1                                                                      ; enable HTTP
      M586 P1 S0                                                                      ; disable FTP
      M586 P2 S0                                                                      ; disable Telnet
      
      ; Drives
      M569 P0 S1                                                                      ; physical drive 0 goes forwards
      M569 P1 S1                                                                      ; physical drive 1 goes forwards
      M569 P2 S1                                                                      ; physical drive 2 goes forwards
      M569 P3 S1                                                                      ; physical drive 3 goes forwards
      M569 P4 S1                                                                      ; physical drive 4 goes forwards
      M584 X0 Y1 Z2:4 E3                                                              ; set drive mapping
      M350 X16 Y16 Z16:15 E16 I1                                                      ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z1600.00:1600 E5236.00                                        ; set steps per mm
      M566 X1200.00 Y1200.00 Z500:500 E40                                             ; set maximum instantaneous speed changes (mm/min)
      M203 X35100.00 Y35100.00 Z1200:1200 E6000.00                                    ; set maximum speeds (mm/min)
      M201 X3000.00 Y3000.00 Z400:400 E120.00                                         ; set accelerations (mm/s^2)
      M906 X1800 Y1800 Z1400:1400 E1200 I30                                           ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                                                         ; Set idle timeout
      
      ; Stall Detection
      M915 X Y S5 F0 H400 R4700													    ; X / Y Axes
      
      ; Axis Limits
      M208 X-3 Y-30 Z0 S1                                                             ; set axis minima
      M208 X300 Y300 Z300 S0                                                          ; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"xstop"                                                             ; configure active-high endstop for low end on X via pin xstop
      M574 Y2 S1 P"ystop"                                                             ; configure active-high endstop for high end on Y via pin ystop
      M574 Z1 S2                                                                      ; configure Z-probe endstop for low end on Z
      
      ; Z-Probe
      M558 P1 R0.5 C"zprobe.in" H5 F1800 T24000                                       ; set Z probe type to effector and the dive height + speeds
      G31 P200 X0 Y0 Z-0.12                                                           ; set Z probe trigger value, offset and trigger height
      M557 X5:295 Y5:295 S40                                                          ; define mesh grid
      
      ; Heaters
      ; Bed
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4559 C9.764201e-8                     ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0                                                           ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 B0 S1.00                                                                ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0                                                                         ; map heated bed to heater 0
      M143 H0 S90                                                                     ; set temperature limit for heater 0 to 90C
      
      ;Hotend
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8                          ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1                                                            ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 B0 S1.00                                                                ; disable bang-bang mode for heater  and set PWM limit
      M143 H1 S300                                                                    ; set temperature limit for heater 1 to 300C
      
      ; Fans
      M950 F0 C"fan0" Q25000                                                          ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H1 T45                                                               ; set fan 0 value. Thermostatic control is turned on
      
      M950 F1 C"!fan1" Q500                                                           ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H-1                                                                  ; set fan 1 value. Thermostatic control is turned off
      
      M950 F2 C"fan2" Q25000                                                          ; create fan 2 on pin fan2 and set its frequency
      M106 P2 S1 H1 T45                                                               ; set fan 2 value. Thermostatic control is turned on
      
      ; Tools
      M563 P0 S"T0" D0 H1 F0                                                          ; define tool 0
      G10 P0 X0 Y0 Z0                                                                 ; set tool 0 axis offsets
      G10 P0 R0 S0                                                                    ; set initial tool 0 active and standby temperatures to 0C
      
      ; Custom settings
      M671 X-60.5:360.5 Y150:150                                                      ; Z leadscrews are at (-15,220), (100,-20) and (215,220)0
      
      ; Miscellaneous
      M575 P1 S1 B57600                                                      	        ; enable support for PanelDue
      M501                                                                       	    ; load saved parameters from non-volatile memory
      M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"                              ; set voltage thresholds and actions to run on power loss
      T0                                                                              ; select first tool
      M376 H5                                                                         ; Set bed compensation Taper
      
      
      
      

      Here is my bed.g:

      ; bed.g
      ; called to perform automatic bed compensation via G32
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jun 18 2021 23:45:09 GMT+0200 (MitteleuropƤische Sommerzeit)
      G28                                                ; home
      M401                                               ; deploy Z probe (omit if using bltouch)
      
      ; Pass 1
      G30 P0 X2 Y150 Z-99999                             ; probe near a leadscrew, half way along Y axis
      G30 P1 X298 Y150 Z-99999 S2                        ; probe near a leadscrew and calibrate 2 motors
      
      ;Pass 2
      G30 P0 X2 Y150 Z-99999                             ; probe near a leadscrew, half way along Y axis
      G30 P1 X298 Y150 Z-99999 S2                        ; probe near a leadscrew and calibrate 2 motors
      
      ;Pass 3
      G30 P0 X2 Y150 Z-99999                             ; probe near a leadscrew, half way along Y axis
      G30 P1 X298 Y150 Z-99999 S2                        ; probe near a leadscrew and calibrate 2 motors
      
      ;Pass 4
      G30 P0 X2 Y150 Z-99999                             ; probe near a leadscrew, half way along Y axis
      G30 P1 X298 Y150 Z-99999 S2                        ; probe near a leadscrew and calibrate 2 motors
      
      G28 Z
      
      M402                                               ; retract probe (omit if using bltouch)
      
      
      

      here is my homeall.g:

      ; homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jun 18 2021 23:45:09 GMT+0200 (MitteleuropƤische Sommerzeit)
      G91                    ; relative positioning
      G1 H2 Z5 F30000        ; lift Z relative to current position
      G1 H1 X-308 Y335 F1800 ; move quickly to X or Y endstop and stop there (first pass)
      G1 H1 X-308            ; home X axis
      G1 H1 Y335             ; home Y axis
      G1 X5 Y-5 F30000       ; go back a few mm
      G1 H1 X-308 F360       ; move slowly to X axis endstop once more (second pass)
      G1 H1 Y335             ; then move slowly to Y axis endstop
      G90                    ; absolute positioning
      G1 X150 Y150 F30000    ; go to first bed probe point and home Z
      G30                    ; home Z by probing the bed
      
      

      an last but not least the homez.g:

      ; homez.g
      ; called to home the Z axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jun 18 2021 23:45:09 GMT+0200 (MitteleuropƤische Sommerzeit)
      G91 			     	; Relative mode
      G1 H2 Z5 F5000			; Lower the bed
      G90				        ; back to absolute positioning
      
      G1 X150 Y150 F50000		; Position the endstop above the bed centre
      
      G91 				    ; Relative mode
      
      G4 P1000				; wait 1000msec
      G30                     ; Probe the bed at the current XY position. 
                              ; When the probe is triggered, set the Z coordinate 
      						; to the probe trigger height.
      G90                     ; absolute positioning
      

      and the higmap:

      RepRapFirmware height map file v2 generated at 2021-06-19 11:38, min error 0.034, max error 2.205, mean 1.143, deviation 0.671
      xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
      5.00,295.00,5.00,295.00,-1.00,40.00,40.00,8,8
        0.034,  0.051,  0.062,  0.073,  0.112,  0.152,  0.171,  0.213
        0.532,  0.471,  0.465,  0.434,  0.424,  0.371,  0.311,  0.252
        0.592,  0.610,  0.653,  0.692,  0.753,  0.792,  0.831,  0.854
        1.132,  1.092,  1.032,  1.046,  1.045,  0.992,  0.985,  0.952
        1.167,  1.185,  1.206,  1.232,  1.314,  1.352,  1.413,  1.472
        1.593,  1.592,  1.572,  1.586,  1.575,  1.552,  1.532,  1.506
        1.632,  1.712,  1.753,  1.831,  1.889,  1.952,  2.012,  2.085
        2.205,  2.192,  2.172,  2.172,  2.152,  2.159,  2.132,  2.091
      

      I tried a lot in the past days, but i can't figure the hell out what i did wrong.
      Would be nice if someone of you could take a look at these files ant determen if i did something catastrophicly wrong :).

      By the way i use a Piezo Probe for probing the bed with the Nozzle of the printhead directly.
      Firmware 3.3 and Bed is mechanically OK in level

      Greetings from Germany
      Kai

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer
    • RE: Strange highmap problem

      @phaedrux said in Strange highmap problem:

      Your homez uses the z endstop to homez. The z min height is -6mm. There's your 6mm offset.

      You should use the probe to home z with a G30 before doing the mesh with G29 so that it has an accurate Z0 position that matches the probe offset.

      Thx fo the info will try that and report the results but it sounds plausible ;).

      Edit: Some 30min later, the Problem is solved, thank you very much.

      posted in Tuning and tweaking
      S1lencerundefined
      S1lencer