Posts made by Paddy

@jay_s_uk Many thanks Jay

I have done a clean install of all firmware on my Duet 2 WiFi. It running 3.5.0rc2.

I installed the external input shaping plugin but it wouldn't start. I can't remember the exact reason, something to do with a required webpack already claimed, or something like that. Using the web interface I removed the plugin but now when I try to install it, I get a message say invalid plugin manifest.

Can someone assist?

@OwenD said in Managed to mess up my config:

@Paddy
Update the wifi server
I seem to remember seeing that error during the upgrade (between uploading the three files - duet, DWC, Wifi)
The WiFi module firmware included here is version 2.1beta6.

Thanks. That sorted it. I had to erase my duet2 wifi as any wifi firmware newer than 1.27 wouldn't work. erasing everything and using bosso to get started got it sorted.

@Phaedrux I had tried that, but tried again anyway, unfortunately, it still gives the massage after it reconnects.

So, I'm up and running (sort of) but I have a lot of files in my system folder. The is a corexy with an bltouch and a duet3d accelerator.

Apart from config.g, bed.g, and my x, y, z, all homing files, what else do I need?

I'm wanting to get it to a 'clean' state. So I am trying to get it to 3.5.0 Release Candidate 2. However I am getting the following

Incompatible software versions
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.

In general it says Duet Web Control 3.5.0-rc.2

M122 returns

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.1 (2023-08-31 16:16:15) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S4-6J1F8-3SN6L-1VNZG
Used output buffers: 1 of 26 (18 max)
=== RTOS ===
Static ram: 23076
Dynamic ram: 76636 of which 12 recycled
Never used RAM 13420, free system stack 184 words
Tasks: NETWORK(2,nWait,15.5%,218) ACCEL(6,nWait,0.0%,348) HEAT(3,nWait,0.0%,329) Move(4,nWait,0.0%,364) MAIN(1,running,84.0%,743) IDLE(0,ready,0.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:03:19 ago, cause: reset button or watchdog
Last software reset at 2023-12-23 11:04, reason: User, Gcodes spinning, available RAM 13420, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 22.9, current 23.4, max 24.0
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-12-23 11:13:39
Cache data hit count 4294967295
Slowest loop: 6.59ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 15.09ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 1.27
MAC address cc:50:e3:4a:b8:38
Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 25760
WiFi IP address 192.168.2.124
Signal strength -60dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Grateful for any assistance.

@Phaedrux Many thanks. Changing the S to H in the homing files sorted it.

I went to add a new trigger height to config.g but couldn't see it (It must have been there but I've had a busy day)

I used the config tool and messed up my config - totally my fault. I used the config.bak to get config.g back but a number of files have been changed. The ones causing me issues just now are the home files. Trying to home x,y or z gives

My printer is a home made corexy with dual z axis and bltouch. It's a Duet2 wifi. Firmware is Duet Web Control 3.5.0-rc.1

Any help getting me back running would be most appreciated.

G28 Y
Error: in file macro line 6: G1: insufficient axes homed

My homimg files are;

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.4.0 on Fri Dec 22 2023 15:58:50 GMT+0000 (Greenwich Mean Time)
G91               ; relative positioning
G1 S2 Z5 F6000    ; lift Z relative to current position
G1 S1 X-205 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000       ; go back a few mm
G1 S1 X-205 F360  ; move slowly to X axis endstop once more (second pass)
G1 S2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.4.0 on Fri Dec 22 2023 15:58:50 GMT+0000 (Greenwich Mean Time)
G91               ; relative positioning
G1 S2 Z5 F6000    ; lift Z relative to current position
G1 S1 Y-205 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000       ; go back a few mm
G1 S1 Y-205 F360  ; move slowly to Y axis endstop once more (second pass)
G1 S2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.4.0 on Fri Dec 22 2023 15:58:50 GMT+0000 (Greenwich Mean Time)
G91              ; relative positioning
G1 S2 Z5 F6000   ; lift Z relative to current position
G1 S1 Z136 F1800 ; move Z up until the endstop is triggered
G92 Z131         ; set Z position to axis maximum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91             ; relative positioning
;G1 Z5 F100      ; lift Z relative to current position
;G90             ; absolute positioning

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.4.0 on Fri Dec 22 2023 15:58:50 GMT+0000 (Greenwich Mean Time)
G91                     ; relative positioning
G1 S2 Z5 F6000          ; lift Z relative to current position
G1 S1 X-205 Y-205 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-205             ; home X axis
G1 S1 Y-205             ; home Y axis
G1 X5 Y5 F6000          ; go back a few mm
G1 S1 X-205 F360        ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-205             ; then move slowly to Y axis endstop
G1 S1 Z136 F360         ; move Z up stopping at the endstop
G90                     ; absolute positioning
G92 Z131                ; set Z position to axis maximum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91                    ; relative positioning
;G1 Z5 F100             ; lift Z relative to current position
;G90                    ; absolute positioning

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.4 on Mon Dec 23 2019 16:28:56 GMT+0000 (Greenwich Mean Time)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Hypercube Elite"                                 ; set printer name

M669 K1                                            ; select CoreXY mode

M575 P1 S1 B57600								   ; Setup PanelDue

; Network
M552 S1                                            ; enable network
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Orbiter filament sensor
M950 J1 C"^connlcd.encb"; define logical input for filament auto load
M581 P1 T2 S0 R0 ;define trigger for filament auto load triggers trigger2.g
M950 J2 C"^connlcd.enca"; define logical input for filament unload
M581 P2 T3 S0 R0 ; define trigger for filament auto load triggers trigger3.g

; Accelerometer
M955 P0 C"spi.cs2+spi.cs1" I16 ; all wires connected to temp DB connector, no temperature daughterboard

; Drives
M569 P0 S1                                         ; physical drive 0 goes forwards
M569 P1 S1                                         ; physical drive 1 goes forwards
M569 P2 S0                                         ; physical drive 2 goes backwards
M569 P3 S0                                         ; physical drive 3 goes backwards
M569 P4 S0                                         ; physical drive 4 goes backwards
M584 X0 Y1 Z2:4 E3                                 ; set drive mapping
M671 X0:200 Y0:0 S1				   ; leadscrews at left (connected to Z) and right (connected to 
M350 X16 Y16 Z16:16 E16 I1                         ; configure microstepping with interpolation
M92 X80 Y80 Z3200:3200 E690		           ; set steps per mm
M566 X900.00 Y900.00 Z12.00:12.00 E300  		   ; set maximum instantaneous speed changes (mm/min) e was 40
M203 X9000.00 Y9000.00 Z180.00 E7200.00  	   ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z20.00:20.00 E3000          ; set accelerations (mm/s^2) e was 250
M906 X1000 Y1000 Z800:800 E1200 I10                ; set motor currents (mA) and motor idle factor in per cent
;M572 D0 S0.02                 ;pressure advance – to be calibrated
M207 S1.5 F7200 Z0.2     ;firmware retraction
M84 S30                                            ; Set idle timeout




;M350 X16 Y16 Z16:16 E16 I1                         ; configure microstepping with interpolation
;M92 X80 Y80 Z3200:3200 E685		           ; set steps per mm
;M566 X900.00 Y900.00 Z12.00:12.00 E300  		   ; set maximum instantaneous speed changes (mm/min) e was 40
;M203 X9000.00 Y9000.00 Z180.00 E3600.00  	   ; set maximum speeds (mm/min)
;M201 X4000.00 Y4000.00 Z20.00:20.00 E600          ; set accelerations (mm/s^2) e was 250
;M906 X1000 Y1000 Z800:800 E450 I30                 ; set motor currents (mA) and motor idle factor in per cent
;M84 S30     

; Axis Limits
M208 X0 Y0 Z0 S1                                   ; set axis minima
M208 X200 Y190 Z150 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                ; configure active-high endstop for low end on Y via pin ystop

; Filament Runout Sensor
;M591 D0 P2 C"e0_stop" S1  ; filament monitor connected to E0_stop
;M591 D0 P7 C"e0_stop" S0 E1216.9 L0.152 R3:65 A1

; Z-Probe
M950 S3 C"exp.heater3"                                  ; create servo pin 3 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000      ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-25.6 Y18.8 Z3.7                     ; set Z probe trigger value, offset and trigger height
M557 X30:170 Y30:170 P6:6                         ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138     ; 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
M143 H0 S130                                       ; set temperature limit for heater 0 to 130C
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the nozzle heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138      ; 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
M143 H1 S285                                       ; set temperature limit for heater 1 to 285C
M307 H1 B0 S1.00                                   ; disable bang-bang mode for the nozzle heater and set PWM limit

; Fans
M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 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
M572 D0 S0.1
; Custom settings are not defined
M501
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Hi,
I'm trying to get the orbiter sensor working on my corexy.
I have Dániel Bulyovcsity config but he is using the zstop pin but I am already using that. Daniel's instructions are
Wiring:
Blue: GND
Red: 3.3V
Green: Zstop
Yellow: Should be connected to a free Stop pin, I have used the Stop10(ENC_B) pin

//add in config.g file:

M591 D0 P1 C"!zstop" S1 ;set filament sensor switch for extruder 0
M950 J1 C"^connlcd.encb" ;define logical input for filament load/unload
M581 P1 T2 S0 R0 ;define trigger for filament auto load/unload macro to trigger2.g

I am using GIO pin 9 for yellow and in my config have
; Orbiter filament sensor
M591 D0 P1 C"exp.e3stop" S1
M950 J1 C"^connlcd.enca" ;define logical input for filament load/unload
M581 P1 T2 S0 R0 ;define trigger for filament auto load/unload macro to trigger2.g

Should this work the same?

@droftarts Thanks guys for the replies.

I did see that thread but didn't really grasp what was said.

The sensor has two buttons one solely used to unload. The other detects filament.

My thought is using it like a endstop. Assume its normally low, when filament is present it will be held high.

if it runs out while printing, it will go from high to low and trigger a 'runout' routine.

If goes from low to high while not printing (i've pushed filament in) it will trigger a 'load' routine.

If it goes from high to low and it isn't printing (I've pressed the unload button' it will do nothing.

Is this feasible?

@deckingman It's a momentary button that forms part of the Orbiter filament sensor.
I need it to perform two operations. Going from low to high, I need it to run a 'load filament' trigger. High to low, I need it to perform a 'run out' trigger.

In the 'run out' trigger I will need to check what state the printer is in, so that if it is triggered while the printer is not actually printing it exits the trigger without completing. Is that something that can be done?

@deckingman Brilliant - many thanks.

Hi,

I would like to prefix this post with the fact I don't know what I am talking about. So what I am about to ask could be nonsense.

So question.

is it possible to connect a button that would trigger a macro if its state changes from low to high and can trigger a different macro if the state changes from high to low?

Many thanks for your patience.

@oozeBot You are quite correct. I did look up the gcode dictionary but was too busy looking at the number to notice the letter had changed.

Many thanks!!!!

Hi,

I've just upgraded from 3.4.6 to 3.5.0rc-1 on my corexy. I've change M667 S1 to M669 S1 in config.g but the machine won't home.

Homing x only one stepper moves, and when homing y only the opposite stepper moves. This naturally causes the carriage to move diagonally and crash.

Could someone please point me in the right direction.

Many thanks

@Phaedrux Brilliant - that sorted it. I used the wifi server from 3.4.6.

Thanks again.

@Phaedrux thanks for the reply but unfortunately it's just the same.

Hi,

I upgraded my Duet2 WiFi from 3.4.6 to 3.5.0rc-1 and now can't connect over wifi.
The console shows the following;

TELNET is disabled
Warning: Heater 0 predicted maximum temperature at full power is 321oC
Warning: Heater 1 predicted maximum temperature at full power is 493oC
WiFi module is started
Error: WiFi module reported: Authentication failed
WiFi module is idle
Error: Wifi module reported: Timed out
WiFi module is idle
WiFi module is connected to access point Poljot
IP address 192.168.1.151

Although the text appears static the minutes and seconds that proceed each line is changing, so it's in a loop.

The files I uploaded were;
Duet2CombinedFirmware.bin
DuetWiFiModule_32S3.bin
DuetWiFiServer.bin
DuetWebControl-SD.zip

I know it's something I've done to cause this, but any help to recover would be appreciated

Many thanks.

@Phaedrux Many thanks

Am I right in thinking that the accelerometer is not intended to be mounted all the time?

If that is the case when should it be mounted? Does the input shaping need to be repeated?

I'm going to use it on my home built corexy is there a place I can get gcode for performing the input shaping?

Again, thanks in advance.

@jay_s_uk Thanks for taking the time to reply Jay.