Posts made by cdoe

Hi guys,
I'm running RRF v3.5.4 on Voron 2.4 300 mm with duet 5 mini and SHTv3 toolboard. Xol toolhead with orbiter v2 extruder. Prusa Slicer is used to slice models.
I've noticed that printing staggers every 12 seconds or so - first thought was this was to let layer cool, but that was also visible on printing infill on large-ish prints as well.
SD card was changed and that had no effect (both old and new were able to produce 40mb/s reads and 10mb/s writes.
I've tried bumping up acceleration but that seems to have no effect as well. My bed compensation is tapered (over 6mm), however, pauses were also visible on layers higher than 6mm, suggesting that this is probably (don't take my word on it) not related to low acceleration for Z axis.
Attached are M122/M122 B124 outputs and my config along with gcode file.
Where/what can I look at next?
config.g.txt
M122B124.txt
M122.txt
v13_top_panel.gcode

I've set orbiter filament sensor v2 set up recently.
It has 2 outputs (FS for sensing if filament is present) and FTU (outputs if filament is tangled or filament unload button is pressed).
The set up is slightly more elaborate than just a sensor since both outputs have 2 functions and logic is not straightforward as well. FS output works as expected as in changing state when filament is present or runs out, FTU output only changes state if filament is already present.

I'm running FlySHT36v3 Max toolboard with 124 being board CAN address and connected FS to io1.in to FTU to io2.in inputs (taking 5v and ground from same 5 pin connector) and had to use triggers for things to work.
This is a section in config.g

; Filament Sensor
M950 J1 C"^124.io1.in"                       ; define logical input for filament auto load
M581 P1 T3 S1 R0                             ; define trigger for filament auto load triggers trigger3.g
M581 P1 T2 S0 R0                             ; define trigger for filament sensing triggers trigger2.g
M950 J2 C"^124.io2.in"                       ; define logical input for filament unload
M581 P2 T4 S1 R0                             ; define trigger for filament auto unload triggers trigger4.g

trigger2.g:

; trigger2.g
if state.status == "processing"
    M300 S2000 P100                                     ; play beep sound
    M291 P"Ran out of filament while printing" S0 T3    ; display message
    M25
elif state.status == "pausing" || state.status == "paused"
    M291 P"Retriggered filament sensor during pause" ; display message
else
    M300 S2000 P100                     ; play beep sound
    M291 P"Ran out of filament" S0 T3   ; display message

trigger3.g:

; trigger3.g
M98 P"0:/macros/filament-load"

trigger4.g:

; trigger4.g
if state.status = "processing"
    M300 S2000 P100                                                     ; play beep sound
    M291 P"Filament is stuck or filament unload button pressed" S0 T3   ; display message
    M25
else
    M98 P"0:/macros/filament-unload"

filament-load and filament-unload macros will need to be created and populated for this to work but that should be more or less straightforward and more printer-specific than general set up
Hope that helps

Thanks again, updating from duet board worked. Digitizer doesn't work though but that's a separate issue

Thanks I'll try that. Didn't realise it can be done while paneldue has no firmware at all...

I've been able to flash 3.4.1 with bossac. GUI version is windows/macos version only which i don't have, so it seems that my paneldue is now just a bunch of useless hardware

bossac says “flash command failed”

Hi,
I've tried re-flashing 3.5.0 rc 8 firmware over usb and followed process described in documentation.
PanelDue had 3.4.1 firmware previously. However, it was in storage and was stuck in calibration prompt - i.e. a dot on top of the screen was visible and there was a prompt to touch it, but that was not progressing as if touch was not detected.
Here are some outputs from bossac:

$ ./bossac --port=/dev/ttyACM0 -i
Atmel SMART device 0x289b09e0 found
Device       : ATSAM4S4
Chip ID      : 289b09e0
Version      : v1.13 RC2 Feb 20 2013 13:25:17
Address      : 4194304
Pages        : 512
Page Size    : 512 bytes
Total Size   : 256KB
Planes       : 1
Lock Regions : 16
Locked       : none
Security     : false
Boot Flash   : false

output when flashing with 3.5.0:

./bossac --port=/dev/ttyACM0 -e -w -v -b ~/Downloads/PanelDueFirmware-3.5.0-rc8-7.0i.bin 
Atmel SMART device 0x289b09e0 found
Erase flash
done in 0.001 seconds

Write 176720 bytes to flash (346 pages)
[                              ] 0% (0/346 pages)
Flash command failed

Similar output when trying with version 3.4.1:

./bossac --port=/dev/ttyACM0 -e -w -v -b ~/Downloads/PanelDueFirmware-3.4.1/PanelDueFirmware-3.4.1-7.0i.bin
Atmel SMART device 0x289b09e0 found
Erase flash
done in 0.001 seconds

Write 170916 bytes to flash (334 pages)
[                              ] 0% (0/334 pages)
Flash command failed

Are there any troubleshooting steps I could try to figure out why flashing no longer works and if hardware is in working condition?
There are no torn wires or connector strips on visual inspection

Only got my hands to it now. Sadly 140R resistor burned out so badly that there are no traces left to put replacement component. LEDs are fine though. Has anyone tried using silver tracing pen to re-draw traces? Will it work properly with moving part like effector?

Thank you.

Is there something similar to replacement parts for duet3d but for smart effector?
I'll need to replace LEDs (D1, D9 and D7) as I was switching from 24v to 12v and then back and forgot to remove 12v jumper for LEDs so they were working w/o extra resistor for some time.

When +12V is connected to centre pin of V_FAN voltage selection block - does it bypass mosfets? Also do I need to connect negative from buck converter to negative of duet wifi? Looks like negative from buck converter output is common on both sides so it's common with negative on PSU as well.

Thank you. That was it.

Hi,
I've built a large kossel based on dc42's design. After wiring everything and running G28 to home I've noticed that it never completes.
My config.g:

[[language]]
; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Dec 22 2017 18:14:30 GMT+0200 (EET)

; General preferences
M111 S0                                                                ; Debugging off
G21                                                                    ; Work in millimetres
G90                                                                    ; Send absolute coordinates...
M83                                                                    ; ...but relative extruder moves
M555 P1                                                                ; Set firmware compatibility to look like RepRapFirmare

;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
M665 R200 L180 B150 H720                                               ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0                                                          ; Put your endstop adjustments here, or let auto calibration find them
M208 Z0 S1                                                             ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1                                                       ; Set active high endstops
M558 P5 R0.4 X0 Y0 Z0 H5 F120 T6000                                    ; Set Z probe type to effector, the axes for which it is used and the dive height + speeds
G31 P100 X0 Y0 Z-0.1                                                   ; Set Z probe trigger value, offset and trigger height
M557 R150 S20                                                          ; Define mesh grid

; Drives
M569 P0 S0                                                             ; Drive 0 goes backward
M569 P1 S0                                                             ; Drive 1 goes backward
M569 P2 S0                                                             ; Drive 2 goes backward
M569 P3 S0                                                             ; Drive 3 goes backward
M350 X16 Y16 Z16 E16 I1                                                ; Configure microstepping with interpolation
M92 X200 Y200 Z200 E663                                                ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200                                           ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E1200                                        ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000                                           ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30                                        ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                                                                ; Set idle timeout

; Heaters
M305 P0 T100000 B3950 R4700 H0 L0                                      ; Set thermistor + ADC parameters for heater 0
M143 H0 S130                                                           ; Set temperature limit for heater 0 to 130C
M305 P1 T100000 B4388 R4700 H0 L0                                      ; Set thermistor + ADC parameters for heater 1
M143 H1 S280                                                           ; Set temperature limit for heater 1 to 280C

; 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

; Network
M550 Pdelta-dc42                                                       ; Set machine name
M552 S1                                                                ; Enable network
M586 P0 S1                                                             ; Enable HTTP
M586 P1 S0                                                             ; Disable FTP
M586 P2 S0                                                             ; Disable Telnet

; Fans
M106 P0 S1 I0 F500 H-1                                                 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45                                              ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1                                                 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Custom settings are not configured

```homedelta.g:

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Fri Dec 22 2017 18:14:30 GMT+0200 (EET)
G91 ; relative positioning
G1 S1 X725 Y725 Z725 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F1800 S2 ; go down a few mm
G1 S1 X10 Y10 Z10 F1000 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre

I've also noticed that M114 reports position as Nan: [c]X: nan Y: nan Z: nan E0: 0.0 E1: 0.0 E2: 0.0 E3: 0.0 E4: 0.0 E5: 0.0 E6: 0.0 E7: 0.0 E8: 0.0 Count 0 0 0 User nan nan 100.0[/c]
Endstop switches are NC type and they report state change properly both in DWC and when queried via M119
What else can I check to figure this one out?