Posts made by brisma

Hi, I pushed a PR for the italian language

Try with Cura 4.5.0, the new official version 4.6.0 seems bugged.

Hi David,
I was wondering if it was possible to implement a confirmation dialog (maybe in the paneldue/dwc) now that we have some type of logic gcode.

I was thinking about a simple custom Confirm/Cancel dialog
For example, if filament runout, a confirmation dialog appear to assist the unload/load of the filament.

The best will be if the buttons can be customized to stop/continue the gcode or call macros.

Can be an idea?

M566 X480.00 Y480.00 Z30.00 E10000.00 ; Set maximum instantaneous speed changes (mm/min)

166mm/s of jerk on extruder? Try lowering to 600 (10mm/s)

M906 X1400.00 Y1400.00 Z900.00 E1428.00 I30

Why 1428 (that's useless) and not 1400 on extruder?

Are you on direct or bowden system? Can you try a print without PA?
Just comment this line:

; Pressure Advance
; M572 D0 S0.05 ; Enable pressure advance and set it. Marlin setup used a K of 0.03-0.05. HatchBox Wood K=0.03.

The size is correct... very strange

I've a custom HEVO, printed with PLA at 200/60°C at maximum 60mm/s with this config:

M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80 Y80 Z400 E860                              ; set steps per mm
M566 X600 Y600 Z120 E900                           ; set maximum instantaneous speed changes (mm/min)
M203 X15000 Y15000 Z600 E1800                      ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z240 E5000                        ; set accelerations (mm/s^2)
M906 X1300 Y1300 Z1300 E1300 I30                   ; set motor currents (mA) and motor idle factor in per cent

Edit:
DuetWifi with RRF 3.01RC9

Same problem to me with a custom HEVO on PrusaSlicer 2.2.0.
Now I'll retry with Cura 4.6...

@Leblond Certo, ma ripeto: sei su un forum inglese dove si parla inglese. Se non lo conosci e non hai voglia di impararlo almeno sforzati di usare il traduttore anziché scrivere in italiano.

Sorry for the OT.

@Leblond Mah guarda, sono italiano anch'io... eppure leggo e scrivo in inglese, basta avere la voglia ed il tempo di impararlo

In ogni caso, aggiorna prima a 3.0 usando questa guida:

https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

Ricorda che è un forum inglese.

A che versione vuoi aggiornare? Se sei su una 2.0x devi prima aggiorare a 3.0, poi aggiornare a 3.0.1.

@nickt try with sudo ls /dev/tty.*

@phaedrux
Thanks

Then, I will try changing my configuration with these new settings:

M566 X600 Y600 Z120 E900:900          ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z600 E18000:18000  ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z250 E6000:6000      ; Set accelerations (mm/s^2)

M572 D0:1 S0.20                                    ; Pressure advance

Correct?

Cartesian

Hi guys,
I built an Hypercube Evolution controlled by a Duet Wifi, it includes:

• 24V Power Supply
• Duet Wifi + PanelDue 5"
• Titan Extruder + E3D V6 Hotend (Bowden)
• 5 x Nema 17HS4401S stepper
• Raspberry Pi 3 + Camera
• 24V 5050 Led

Some photos of the printers:

Almost everything is working... but not the quality of the extrusion:

As you can see, there are some blob on the retraction point, tt seems that the retraction is too slow and produce these blob at the beginning and at the end of the loop.

I'm using Simplify3D and I use 5mm of retraction at 50mm/s. Coasting, Extra restart distance, Pressure Advance don't produce any change of the quality, the problems remains.

My Duet configuration is:

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Jun 19 2018 17:45:27 GMT+0200 (CEST)

; General preferences
G90                                ; Send absolute coordinates...
M83                                ; ...but relative extruder moves
M555 P2                            ; Set firmware compatibility to look like Marlin

M667 S1                            ; Select CoreXY mode

; Network
M550 PDuetWifi                     ; Set machine name
M552 S1                            ; Enable network
M587 S"Brisma-WiFi" P"Brisma-WiFi" ; Configure access point. You can delete this line once connected
M586 P0 S1                         ; Enable HTTP
M586 P1 S0                         ; Disable FTP
M586 P2 S0                         ; Disable Telnet

; Drives
M569 P0 S1 F7                         ; Drive 0 goes forwards
M569 P1 S1 F4                         ; Drive 1 goes forwards
M569 P2 S1 F1                         ; Drive 2 goes forwards
M569 P3 S0                            ; Drive 3 goes backwards
M569 P4 S0                            ; Drive 4 goes backwards
M350 X16 Y16 Z16 E16:16 I1            ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E430:418.5           ; Set steps per mm
M566 X600 Y600 Z12 E300:300           ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z600 E9000:9000    ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z250 E3000:3000      ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E1200:1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                               ; Set idle timeout

; Axis Limits
M208 X0 Y10 Z0 S1                  ; Set axis minima
M208 X300 Y300 Z350 S0             ; Set axis maxima

; Endstops
M574 X2 Y2 S1                      ; Set active high endstops

; Z-Probe
M574 Z1 S2                         ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1                ; Disable heater on PWM channel for BLTouch
M558 P9 H3 F300 T9000              ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X20 Y0 Z1.00               ; Set Z probe trigger value, offset and trigger height
M557 X20:280 Y20:280 S40           ; Define mesh grid

; Heaters
M307 H0 B0 S1.00                   ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B3950 R4700        ; Set thermistor + ADC parameters for heater 0
M143 H0 S110                       ; Set temperature limit for heater 0 to 110C
M305 P1 T100000 B3950 R4700        ; Set thermistor + ADC parameters for heater 1
M143 H1 S240                       ; Set temperature limit for heater 1 to 240C

; Fans
M106 P0 S0 I0 F500 H-1             ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0.45 I0 F25000 H-1        ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S0.10 I0 F500 H-1          ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1                      ; 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
M563 P1 D1 H1                      ; Define tool 1
G10 P1 X0 Y0 Z0                    ; Set tool 1 axis offsets
G10 P1 R0 S0                       ; Set initial tool 1 active and standby temperatures to 0C

; Automatic power saving
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Miscellaneous
M404 N1.75 D0.4	                                   ; Filament width and nozzle diameter
M376 H10                                           ; Set bed compensation to taper off over 10mm
M501                                               ; Load saved parameters from non-volatile memory
T0                                                 ; Select first tool
M572 D0:1 S0.10                                    ; Pressure advance

How can I optimize my configuration?

You need to reflash the firmware of the PanelDue, you've erased it

@boldnuts said in BLTouch Trigger not working:

Sounds like your pin probe needs adjusting, on the bltouch this is done via the small grub screw on the top to set the correct pin height.

But now is working correctly the trigger, are you sure I need to adjust the probe calibration?

After many tries I found something of interesting

When I power on the printer, I have to move the pin probe up (if it's down) and send a M280 P3 S160 I1 to "unlock" the sensor. After this, I can send all the commands to move the probe pin or to self-test (with the I1).

But if I power on the printer and the probe pin is down the command with S160 will not work and the sensor will start to blinking in error.

So, the simplest solution is to move the pin up before send any command, followed by the "unlock" command (M280 P3 S160 I1).

I modified all my homing config adding the unlock command before any commands, just to be sure that it's not locked in error before the homing.

Now, the question is: the command M280 P3 S160 I1 should not move the pin up automatically? Because it's not always working

@mloidl said in BLTouch Trigger not working:

A blink LED normally indicates an error.

Have you tried removing the I1 from the M280 command.
On my BL-Touch i had to add I1 because it was blinking without it. Maybe that's different for the 3DTouch.

Yes, I tried all these combinations:

• M280 P3 S10 I1
• M280 P3 S10
• M280 P3 S90 I1
• M280 P3 S90
• M280 P3 S160 I1
• M280 P3 S160

The result is always the same: blinking led.

@mloidl said in BLTouch Trigger not working:

Since you're not using an original BL-Touch i'm not sure if the start-up behavior is correct or not.
But what i've read is that the controlling the 3DTouch should be the same as for the BL-Touch.

Can you deploy/retract the probe when sending M280 P3 S10 I1 / M280 P3 S90 I1, directly?

Maybe you can try to not invert the Servo-Signal. Remove 'I1' from M280.

I tried sending the gcode manually, but immediately the led of the sensor started to blinking on and off without moving the probe and in DWC there was a constant 1000 as value of the trigger. It continued to blinking (and the trigger value remained 1000) until I restarted the printer power on/off.

After the restart the led was off with the probe down, on if the probe was up with a trigger value of 0 in DWC... until I resend the gcode

@mloidl said in BLTouch Trigger not working:

Hi,

When you power on your duet, is the BL-Touch doing a self test? Deploy/Retract several times.

If you have a newer BL-Touch you won't need the 220Ohm resistor any more.

You also don't have to call deployprobe.g and retractprobe.g manually, G30 will do this for you.

No, at power on the BLTouch seems "normal", no self test and no led powered. Only if I move the probe up and down manually the led blink.

I'm not using an original new BLTouch, but a 3DTouch (that was working correctly on the old i3).

If can be useful the result of M122 is the following:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08D4M-999N9-JD3S8-6J1FG-3S86R-13Q9N
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 28380
Dynamic ram: 96108 of which 16 recycled
Exception stack ram used: 508
Never used ram: 6060
Task NETWORK ready, free stack 396
Task HEAT blocked, free stack 1256
Task MAIN running, free stack 3560
=== Platform ===
Last reset 00:08:18 ago, cause: software
Last software reset at 2018-06-18 23:13, reason: User, spinning module GCodes, available RAM 6316 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 38.9, current 40.4, max 40.8
Supply voltage: min 23.9, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max 0/215
Driver 1: standstill, SG min/max 0/116
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2018-06-18 23:21:33
Slowest loop: 48.64ms; fastest: 0.07ms
=== Move ===
Hiccups: 55318, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 237, MaxWait: 2982539784ms, Underruns: 0, 0
Scheduled moves: 9, completed moves: 9
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 62.03ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 60:01:94:7e:eb:98
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15800
WiFi IP address 192.168.0.35
WiFi signal strength -50dBm, reconnections 0, sleep mode modem
Failed to request ESP stats
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===