Posts made by p8blr

@dc42 How exactly do I modify the esteps/mm so that the plot crosses extrusion factor 1 at speed 0? I'm getting better results using a linear trendline, however, the issue I keep running into is this:

If I calibrate my esteps/mm at the slowest speed I use (1000mm/min for instance), then print some test prints at faster speeds, measure the widths, plot the results, my extrusion multiplier will always be off on the speed I calibrated at, i.e. if A = 0.0036, and I calibrated my multiplier to be 1 at 1000mm/min then my multiplier is now 1.0036 now at 1000mm/min.

@dc42 the steps/mm are correct. I have them set to the values specified by the extruder manufacturer.

Does this make more sense?

Book1.xlsx

• Print same part multiple times, only varying the print speed. (Two perimeter thick print, no infill)
• Measured the wall thickness several times, average them.
• Omit the 500mm/min speed because it is an outlier (may be a limitation of the pellet extruder)
• Theoretical bead width is 3.6mm, I take the nominal value (2*3.6mm) and divide it by the actual widths. This gives me an extrusion multiplier - I refer to it as the "corrective multiplier".
• Because I'm not using filament, my slicer has an arbitrary "filament diameter", I use the extrusion multiplier to recalculate a new filament diameter (Surface area * coefficient = surface area, solve for Diameter)
• I now create a new extrusion multiplier, based on the new extrusion multiplier at 1000mm/min being 1. This is calculated by taking the new nominal width, divided by the actual widths.
• I plot the extrusion multiplier vs the extrusion speed in mm/s (as specified in the M592 documentation) and apply a 2nd order polynomial trendline.

I end up with these coefficients:
M592 D2 A0.0047 B-0.00001 L1.29478

What is strange is that when I apply these, sometimes my extruder doesn't extrude at all.

Please let me know what you think. Thank you.

@dc42 I collected some data, but I'm not sure how to make an equation that fits the format. I can't set an intercept of 1. Was my mistake that I calibrated at my maximum speed?

I'm racking my brain trying to figure out how to make an equation that doesn't have a constant and I can't figure it out.

Marlin supports a constant:

@droftarts Can you explain or link me to an explanation of this equation: (1 + min(L, Av + Bv^2)) ?

I read through the forum posts linked in the M592 description but I still don't understand the theory behind that equation, let alone how to determine the A and B coefficents.

Thanks.

I've been testing a Dyze Pulsar and I've noticed that the print speed very much affects how much plastic exits the nozzle. I've done some testing by printing 3-inch cubes with the same profiles, but varying the print speed, weighed them. I came to the conclusion that as the speed increases, so should the extrusion multiplier. I've created fast/medium/slow printer profiles in Simplify3D V5 that work well. However, as I was trying to create a post-processor that would modify the extrusion distance based on the feed-rate, I wondered if this was a capability of the Duet?

@dc42 Interesting. Any idea on an estimated completion date on the feature request? Or maybe a workaround I could do instead? I want the user to be able to have a way out of a very long while loop.

Thanks.

@droftarts I updated to 3.5.3 and tested the code but no change, I then added a M400 like this below, and it still did not run the last few lines of code, line 11 & 12.

M98 P"soundNotifyShort.g"   ; beep
M42 P17 S1  ; set closing direction
G4 S1   ; wait
while sensors.gpIn[15].value == 1   ; while not fully closed yet
    M42 P16 S1  ; turn on motor
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M400
M42 P16 S0  ; turn off motor
M98 P"soundAlert.g" ; beep
M291 "Top cover is at max closed" S2

This code runs every line

M98 P"soundNotifyShort.g"   ; beep
G4 S1   ; wait
var myCounter1 = 5
while iterations <= 5
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M98 P"soundAlert.g"    ; beep
M291 P"end of code" S2

This code skips the lines after the while loop

M98 P"soundNotifyShort.g"   ; beep
M42 P17 S1  ; set closing direction
G4 S1   ; wait
while sensors.gpIn[15].value == 1   ; while not fully closed yet
    M42 P16 S1  ; turn on motor
    M98 P"promptUser.g" ; give user opportunity to cancel
    if global.userPrompt == 1
        break
    G4 S1
M42 P16 S0  ; turn off motor
M98 P"soundAlert.g" ; beep
M291 "Top cover is at max closed" S2

@jay_s_uk SBC mode, 3.5.3-rc.1. I'm afraid to update because that was an ordeal last time that bricked some of my expansion boards updating in sbc mode.

I have a bunch of code to automatically open/close a retractable cover on my printer and I have subsets of code that run different beeps to indicate motion and M291's to prompt the user. What I'm noticing is that it's not always running all of my code. I can't tell if line 10 isn't running b/c the motor is stopped with relay logic, lines 11 and 12 are definitely not running.

Problematic code

M98 P"soundNotifyShort.g"	; beep
M42 P17 S1	; set motor direction to closing
G4 S0.25	; short wait to let relay flip
while sensors.gpIn[15].value == 1	; while not fully closed yet
	M42 P16 S1	; turn on motor
	G4 S4		; wait
	M98 P"promptUser.g"	; give user opportunity to cancel
	if global.userPrompt == 1
		break ; user canceled
M42 P16 S0 	; turn off motor
M98 P"soundAlert.g"	; beep - note this is apparently not running b/c I don't hear it beep
M291 P"Top cover is at max closed" S2 ; this doesn't run either b/c I don't see the message box in DWC

soundNotifyShort.g

M42 P20 S1
G4 S.37
M42 P20 S0

promptUser.g

; Working within the limitation of the firmware, for there to be a non-exiting default option you must have a Cancel button (J1) and a message box
; of S4 or above, so the options are redundant if you only want a yes or no value, which I do. So the logic is reversed, no response sets input = 0
; creating a new global variable, and setting it to a non-zero value. So IF the user responds, the variable will change to 0

set global.userPrompt = 3
M291 P"Continue?" S4 T3 J1 K{"Yes", "No"} F0
set global.userPrompt = input

; global.userPrompt legend
; 0 is Yes
; 1 is No
; 3 is No response

soundAlert.g

M42 P19 S1
G4 S2.2
M42 P19 S0

@T3P3Tony Yep, that's what I ended up doing. I spoke with Teknic support and expressed interested in the HLFB wire potentially signaling errors rather than enabled status and they filed my feature request. For now this is my solution: https://forum.duet3d.com/post/346434

@droftarts I don't think I want to enable the servos on startup because then if the servos were ever disabled with a M18 for instance, that would trigger a driver-error because the HLFB wire would switch.

Question about the M957 being used for testing, would it cause the printer to pause if sent during a print?

Thanks

@p8blr From what I've discovered, the duet firmware assumes the state of the error pin on startup is "not an error", but the best you can configure the teknic motors to do is treat the HLFB wire as "enabled & not in shutdown" or "disabled or maybe in shutdown", and because the servos aren't enabled on startup, the duet's assumption will always be wrong. Until this is configurable by Duet or Teknic, this can't work.

Here's my workaround: I added another expansion board!!! I wired the servos with the "sinking" output as Teknic recommends.

in config.g

M950 J16 C"^121.io0.in"                   ; assign input for X HLFB+
M950 J17 C"^6.io0.in"                     ; assign input for Y1 HLFB+
M950 J18 C"^6.io1.in"                     ; assign input for Y2 HLFB+
M950 J19 C"^6.io2.in"                     ; assign input for Z1 HLFB+
M950 J20 C"^6.io3.in"                     ; assign input for Z2 HLFB+
M950 J21 C"^6.io4.in"                     ; assign input for Z3 HLFB+
M950 J22 C"^6.io5.in"                     ; assign input for Z4 HLFB+
M581 P16:17:18:19:20:21:22 T2 S0 R1       ; configure external trigger 2, active to inactive, when printing

trigger2.g

if sensors.gpIn[16].value == 0  ; if x servo is disabled or in shutdown
    M957 E"driver-error" D0 B121    ; raise driver error event, driver 0, CAN 121, P???

if sensors.gpIn[17].value == 0  ; if Y1 servo is disabled or in shutdown
    M957 E"driver-error" D0 B0    ; raise driver error event, driver 0, CAN 0, P???

if sensors.gpIn[18].value == 0  ; if Y2 servo is disabled or in shutdown
    M957 E"driver-error" D1 B0    ; raise driver error event, driver 1, CAN 0, P???

if sensors.gpIn[19].value == 0  ; if Z1 servo is disabled or in shutdown
    M957 E"driver-error" D2 B0    ; raise driver error event, driver 2, CAN 0, P???

if sensors.gpIn[20].value == 0  ; if Z2 servo is disabled or in shutdown
    M957 E"driver-error" D3 B0    ; raise driver error event, driver 3, CAN 0, P???

if sensors.gpIn[21].value == 0  ; if Z3 servo is disabled or in shutdown
    M957 E"driver-error" D4 B0    ; raise driver error event, driver 4, CAN 0, P???

if sensors.gpIn[22].value == 0  ; if Z4 servo is disabled or in shutdown
    M957 E"driver-error" D5 B0    ; raise driver error event, driver 5, CAN 0, P???

Any suggestions on improving the functionality? I've not created driver-error.g so the printer should just send a popup message in DWC and pause the print - which is essentially what I want when a servo goes into shutdown.

Also what does the P parameter do in M957? I was reading through the Events documentation and all it says is "Lower 16 bits of driver status word" and I have no idea what that means.

Thanks!

@T3P3Tony Because of this limitation, I don't think the HLFB (high level feedback) signal from Teknic servo motors can be used as an error signal to the duet. The way Teknic handles it, the HLFB pin will conduct (Active-High) when the servo is enabled and not in a shutdown state, but the servo will not be enabled on startup. Because of this, the current firmware will assume Active-Low on startup, and when the servo is enabled, it will trigger a driver-error event.

For Teknic servos (very popularly paired with Duet hardware) the error pin should only be observed when the printer is sending an enable signal and attempting to send move commands.

Are there any solutions in the meantime? I need a way to protect a large printer from potentially damaging itself.

I have some Teknic CPM-SDHP-3446P-ELN motors and a combination of Duet 6XDs and 1XDs and I'm trying to make the HLFB wire from the servo signal the duet to pause a print if the motors over-torque or lose steps.

How exactly would I set this up? It appears that the servo can be wired multiple ways.

Also, what is the name of the event trigger and how would that work? The HLFB conducts when the motor is enabled and not in a shutdown state, which may not necessarily mean that the motor is in an error state, it might just not be enabled yet so maybe I would code something like this?

config.g

; driver 0-5 error inputs are not configured in config.g
M950 J4 C"!^40.io0.in" ; create input pin number 4 on 1XD board at CAN address 40 for servo error
M581 P4 S0 T3 R1 ; invoke trigger 3 when an active-to-inactive edge is detected on input 4 and a file is being printed from SD card

driver0-error.g

if driver0 == "enabled"  ; not sure what variable to use here to see if axis was commanded to be enabled
   M25  ; pause print
   echo "Cannot move servo 0. Servo may be in a fault state"

trigger3.g

if driver6 == "enabled"  ; not sure what variable to use here to see if axis was commanded to be enabled
   M25  ; pause print
   echo "Cannot move servo 6. Servo may be in a fault state"

From the manual:

@dc42 Thanks, connecting the int pin fixed it.

For anyone else reading this thread in the future, you need 5 wires from a LIS3DH to a SAMMY C21.

GND - GND
V33 - V+
PA22 - SDA
PA23 - SCL
PA13 - INT

@droftarts

M955 P124.0

Returns: Accelerometer 124.0 type LIS3DH with orientation 12 samples at 1344Hz with 10-bit resolution

But when I record the motion profile I get:

Error: M956: Failed to start accelerometer data connection: INT1 error

I wired what @dc42 mentioned regarding the I2C mode, but the instructions aren't clear on [THIS](link url) page as to what interrupt pin I need to use.

Help please?

@chrishamm I've actually got it connected via ethernet to my router, however, my laptop is on wifi. Would that matter? I'm about 20ft from my router.

@Phaedrux I'm actually running it with a nvme drive on a pcie hat.