Third-party add-ons

• 

  Precision Piezo troubles
  • Jbourns

  4
  0
  Votes
  4
  Posts
  131
  Views

  

  @s1lencer They are maybe 2 inches now, before they were about 300mm. Changing the length had zero effect. Its an original module V2, I have long since worn out the old pots and have replaced them with 25 turn pots. Adding 25 turn pots did nothing as well. For VR1 it wont go to 0.4Mohm. The only thing im able to measure is 175K to 2K ohm @whosrdaddy I did have it bed mounted but figured it was too noisy so its been moved to the print head. I also followed your suggestion on have a second piezo to cancel the noise, I dont see any changed. Tapping anywhere on the printer its picked up
• 

  Precision Piezo z probes guide for duet users reference
  • DjDemonD

  99
  0
  Votes
  99
  Posts
  7483
  Views

  

  I would check the calibration potentiometer. Adjust it as per the documentation. It is a good idea to make this adjustment, at the temperatures you would normally use when probing the bed. So if thats with heaters off, calibrate with heaters off and vice versa. Piezos do change sensitivity when heated or cooled, its a very sensitive instrument.
• 

  BLTouch P9 mode retracts the probe to late ?
  • Scachi

  4
  0
  Votes
  4
  Posts
  144
  Views

  

  Thank you for investigating this. I don't use the bltouch anymore so I can't give a fast feedback if you have found a fix. I can mount the bltouch again for testing it, but that may take a few days then.
• 

  Precision Piezo
  • Scachi

  1
  1
  Votes
  1
  Posts
  71
  Views

  No one has replied

• 

  BL Touch selftest gcode causes probe to cycle nonstop
  • feldfiber

  4
  0
  Votes
  4
  Posts
  109
  Views

  

  @vhoward @Scachi I have added line to the guide, see this post https://forum.duet3d.com/post/50206
• 

  Tuning the Precision Piezo to not trigger on every move
  • darookee

  10
  0
  Votes
  10
  Posts
  538
  Views

  

  Yes I think getting rid of springs can help. Play around with probing speeds too. Too slow and you don't get a trigger, too fast and you lose accuracy. Sorry for not picking up this one earlier I've been away travelling.
• 

  TL-Smoother Module - Improved Printing Quality?
  • SnowCrash

  6
  0
  Votes
  6
  Posts
  168
  Views

  

  I used them to eliminate a salmon skin texture on curved surfaces on a i3 cartesian with DRV8825 drivers. It was only the 4 diode version, but it helped enough.
• 

  Start Gcode for the Piezo Orion
  • pogo1213

  1
  1
  Votes
  1
  Posts
  98
  Views

  No one has replied

• 

  Xiaomi Dafang Camera
  • enggmaug

  1
  0
  Votes
  1
  Posts
  123
  Views

  No one has replied

• 

  New Product Release - Precision Piezo Orion
  • DjDemonD

  19
  0
  Votes
  19
  Posts
  1331
  Views

  

  Hello @pogo1213 . Is it the Orion groove mount STL you want? If so, I can provide that and also a modified version that I am currently using because the original did not fit well and was also too flexible. Orion groovemount original stl + my hacked version
• 

  BLT + DuetWiFi not triggering when Auto Delta Calibration
  • markost

  3
  0
  Votes
  3
  Posts
  127
  Views

  

  @dc42 Thanks!!! It seems that my caliper takes off measures above 140mm and I didn't noticed the first time (I mostly use it to take extremely small measuers). The homed height defined on M665 was higher by a couple of centimeters. Also the H parameter on M558 was too low, so all added up, the probe was expecting to trigger below the bed. I used a more analog method to take measures and it helped to solved the issue. My biggest mistake was to think that the probe will trigger at any height regardless of the other parameters, so I didn't think about checking the heights on those commands. Once you point me in the right direction I was able to quickly solve this issue. Thanks again!!! Marcos
• 

  Z-offset Issue(Probably Me)
  • Saadiqj

  8
  0
  Votes
  8
  Posts
  260
  Views

  

  @saadiqj I mean that where you use G1 S1 Z-370 to move the bed use G30 to call for a probe instead. https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe Here is my HomeAll.g for comparison. ; homeall.g ; called to home all axes ; ; BLTouch prep so we don't catch the probe pin on the edge of the bed ; M280 P3 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed M402 ; Retract probe just in case it's down ; Home XY for Z homing ; G91 ; relative positioning G1 Z5 F200 S2 ; Lower bed 5mm to ensure it is below the switch trigger height M913 X50 Y50 ; set X Y motors to 50% of their normal current for homing G1 S1 X-375 Y305 F4000 ; course home X or Y G1 S1 X-375 F4000 ; course home X G1 S1 Y305 F4000 ; course home Y G1 X2 Y-2 F1000 ; move away from the endstops G1 S1 X-10 F200 ; fine home X G1 S1 Y10 F200 ; fine home Y M913 X100 Y100 ; set X Y motors to 100% of their normal current ; Z homing section follows ; G90 ; absolute positioning G1 X190 Y90 F4000 ; Move x and Y axis over to bed center so probe is on top of bed ; Set lower speeds for homing M566 Z5 ; Set maximum instantaneous speed changes (mm/min) (Jerk) M203 Z350 ; Set maximum speeds (mm/min) M201 Z100 ; Set maximum accelerations (mm/s^2) ; Probe the bed ; M558 A1 F350 ; Set single probing at faster feed rate G30 ; Do a single probe to home our Z axis M558 A10 F100 ; Set tripple probing at slower feed rate G30 ; Probe again to get a more accurate position ; Set normal speeds again M566 Z60 ; Set maximum instantaneous speed changes (mm/min) (Jerk) M203 Z600 ; Set maximum speeds (mm/min) M201 Z600 ; Set maximum accelerations (mm/s^2) ; Move X and Y back Home ; G1 X0 Y270
• 

  Precision Piezo Orion - anyone got a working config?
  • Plecto

  4
  0
  Votes
  4
  Posts
  247
  Views

  

  I think I have found the reason why the probe wasn't working right, as I had the M558 and the G31 in the wrong order. RTFM! To specify which probe you are setting parameters for, send a M558 command to select the probe type before sending the G31 command, or use the T parameter. So, fingers crossed, it's working OK now.
• 

  CNCjs for Duet3D
  • Danal

  18
  0
  Votes
  18
  Posts
  529
  Views

  

  @dc42: Is there any reason why the Javascript code can't be run client side instead? In theory, it could all be client side. For example, Chilipeppr works this way*. In practice, that would be a huge change to CNCjs. As a "never before had a pull accepted", I feel it would be prudent to "go with the flow" for the moment, and add native Duet support to the way CNCjs is structured. After that, add a TCP/IP connection option. And… there is always the Windows, Mac, and Linux stand-alone versions. No server is needed at all. With those in play, I'll say that "all browser side" is somewhere between third priority and no real need to do it at all. . . Chilipeppr runs entirely in the browser, EXCEPT for a small program that provides the serial USB connection (browsers won't let Javascript control serial ports). Obviously, with a TCP/IP connection, this would be come moot.
• 

  IP Camera with Web Interface
  • GaRv3

  15
  0
  Votes
  15
  Posts
  688
  Views

  

  @AlexLin: for the interested this is the phone mount. I doesn't include the 3030 mount but that is easy to fix https://www.thingiverse.com/thing:2194278 Great! Thank you!
• 

  Precision Piezo z probe advice for custom hotend
  • fma

  15
  0
  Votes
  15
  Posts
  447
  Views

  

  Good! Thanks.
• 

  Temporary Effector FSR for Bed Levelling
  • TinkerBill

  3
  0
  Votes
  3
  Posts
  171
  Views

  

  hello I was playing with similar idea and have found that for FSR to be consistent you really have to slow down the speed. https://youtu.be/zBXN_6AAWp0
• 

  Reading data from Duet Wi-Fi
  • jaydevdave

  7
  0
  Votes
  7
  Posts
  599
  Views

  

  By default you need to send line numbers and checksums when sending data to the PanelDue port. This is to guard against character loss. You can turn off this requirement using the M575 command.
• 

  Plugins to the UI
  • MrBlom

  4
  0
  Votes
  4
  Posts
  524
  Views

  

  It may be worth adding an item in the DWC wishlist to request support for addons.