Posts made by tippmann32503

Another thing I've noticed is that my paneldue doesn't respond with the latest readings immediately unless I press something on the screen (for example it is still showing active temp at 0 and current at 49.8 even though I've started a new print and the bed is at 81+). If I press any of the functions on the screen it will update.

A few months ago I rebuilt my BLV printer including neopixel status rings and had everything working as it should until I crashed my nozzle into my bed. I left it until this past week when I decided to get it back up and running. The repairs involved a new garolite board on the bed, replacement nozzle on my Hemera and replacement thermistor due to a broken wire. I then ran a new PID tune. Upon starting my printer back up, I seemed to have some sort of hotend fault (purple background color on the temp display on my paneldue - I only say some sort because the temp continued to hold and print as normal). I ran the PID tune again and haven't had a fault since.

That being said - the rings haven't operated as they should since I've started working on the printer again. The rings will turn on and cycle as they should upon startup but then immediately shut off as soon as the warning and error messages pop up on the paneldue (image shown below). In the past I was struggling with the rings being compatible with the paneldue but it was resolved after replacing/upgrading the panel to the paneldue 5i. I thought maybe that may have been a factor as well, but still wouldn't work when I left the panel unplugged. I also tried deleting my config-override.g file and rerunning the PID tune with M500 but to no avail.

Any ideas what may have changed? I'm thinking it had to do with the thermistor as everything else was simply a hardware change.

config.g file:

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Oct 09 2018 13:27:56 GMT+0300

; General preferences
M80 C"pson"				; Turns on the ATX power supply
G90                                                ; Send absolute coordinates...
M83                                                ; ...but relative extruder moves

M667 S1                                            ; Select CoreXY mode

; Network
M550 PBLV mgn Cube                                 ; Set machine name
M552 S1                                            ; Enable network
M552 S1 P"Skynet"				   ; SAV - Hidden Network
M586 P0 S1                                         ; Enable HTTP
M586 P1 S0                                         ; Disable FTP
M586 P2 S0                                         ; Disable Telnet
M575 P1 B57600 S0				   ; SAV - PanelDue connection

; Drives
M569 P0 S0                                         ; Drive 0 goes backwards blv: its was S1
M569 P1 S0                                         ; Drive 1 goes backwards blv: its was S1
M569 P3 S1                                         ; Drive 3 goes forwards
M569 P5 S0					   ; SAV - 8/3/23 - Added for Duex Triple Z
M569 P6 S0					   ; SAV - 8/3/23 - Added for Duex Triple Z
M569 P7 S0					   ; SAV - 8/3/23 - Added for Duex Triple Z


M584 X0 Y1 Z5:6:7 E3					; SAV - 3 Z motors connected to driver outputs 5, 6, and 7
M671 X-60:460:460 Y54:200:346 S20 			; SAV - sets homing locations

M350 X16 Y16 Z16 E16 I1                            ; Configure microstepping with interpolation
M92 X202.33 Y202.33 Z401.19 E341.06                	           ; Set steps per mm for Matrix 
M566 X600 Y600 Z24 E300                            ; Set maximum instantaneous speed changes (Jerk) (mm/min) 
M203 X20000 Y20000 Z600 E2000                      ; Set maximum speeds (mm/min) 
M201 X3000 Y3000 Z100 E5000			   				 ; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E900 I30                   ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Pressure advance
 M572 D0 S0.045					   ; Try here, go up/down as needed

; Axis Limits
M208 X-38 Y0 Z0 S1                                 ; Set axis minima - x-axis endstop is minimum
M208 X400 Y403 Z405 S0                              ; Set axis maxima - y-axis endstop is maximum

; Endstops
M574 X1 S1 P"xstop" 		; SAV - Adjusted for RRF3 on 8/3/23 - configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y2 S1 P"ystop"		; SAV - Adjusted for RRF3 on 8/3/23 - configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2          		; SAV - Adjusted for RRF3 on 8/3/23 - configure Z-probe endstop for low end on Z



; Filament sensor
M591 P7 C"e0stop" S1 D0 L6.2 R80:120 E40; filament monitor connected to E0 endstop

; Z-Probe
M574 Z1 S2                                         ; Set endstops controlled by probe
M307 H1 A372.3 C109.6 D4.6 B0			  		 ; Set PID for hotend values
M307 H0 A99.1 C453.2 D2.2 B0					  ; Set PID for heated bed values
M307 H3 A-1 C-1 D-1					; SAV - BLT Addition from Duet Wiki
M950 S0 C"duex.pwm5"					; SAV - Adjusted to Duex 8/3/23
M558 P9 C"^zprobe.in" H5 F1000 T10000			; SAV - Adjusted to Duex 8/3/23
G31 X62 Y-17 Z1.37 P25				; SAV - BLT Addition from Duet Wiki - Lower num = more space between noz and bed
M557 X30:370 Y30:370 S68			   	; Define mesh grid


; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4008 		; SAV - Adjusted to Duex 8/3/23 - sensor 0
M950 H0 C"bedheat" T0  					; SAV - Adjusted to Duex 8/3/23 - create bed heater and map sensor 0
M307 H0 B0 S1.00                             		; SAV - Adjusted to Duex 8/3/23 - disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                    		; SAV - Adjusted to Duex 8/3/23 - map heated bed to heater 0
M143 H0 S130                                      	; Set temperature limit for heater 0 to 130C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 	; SAV - Adjusted to Duex 8/3/23 - sensor 1
M950 H1 C"e0heat" T1 					; SAV - Adjusted to Duex 8/3/23 - create heater and map sensor 1
M143 H1 S290                                      	; Set temperature limit for heater 1 to 290C

; Fans
M950 F1 C"duex.fan3" 							   ; SAV - Added to Duex 8/3/23
M106 P1 C"Duex Fan" S1 H-1						   ; SAV - Added to Duex 8/3/23
M950 F2 C"duex.fan4" 							   ; SAV - Added to Duex 8/3/23
M106 P2 C"Axis Fans" S1 H-1						   ; SAV - Added to Duex 8/3/23
M950 F0 C"duex.fan5" Q500						   ; SAV - Added to Duex 8/3/23
M106 P0 C"Part Fan" S0 H-1					   	   ; SAV - Added to Duex 8/3/23


; 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

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

; Custom settings are not configured
M564 H0                                   	   ; Let the Jog buttons work blv: added to allow jog buttons

M501

@KenW Thanks. I think Ive found that mounting it to the side of the printer without a bowden tube was causing too many inconsistency issues. I stuck it right on the top of my matrix and it seems to be working consistently. It's just kind of bobble-heading right now though which Im not a huge fan of, I'll have to figure something out...

Hey Everyone,
I'm working on setting up my BTT sensor and while I'm getting readings from it utilizing "M591 P7 C"e0stop" S1 D0 L0.5 R90:110 E3" but my issue is it's triggering during the startup bed leveling process, sensing that no filament is being utilized, pausing the print, then when I resume it restarts the leveling process followed by the trigger, in an infinite loop. Is there a way to have it not initiate until the print has started? Is it just a matter of tweaking the E settings?

@droftarts Aside from M575 P1 B57600 S1? Any writeup on how to change the pin on the Duet?

@droftarts said in Paneldue not showing data/control:

@tippmann32503

Duet 2 Wifi to RRF 3.5.4

Do you mean 3.5 beta4?

I've since updated it to firmware version 3.5.0 (it's a V3.0).

Do you mean PanelDue Firmware 3.5.0-rc6?

Does the PanelDue work correctly if you disconnect the Fysetc board, and vice versa? What is the last firmware version where this combination worked correctly?

I have a Duet 3 Mini 5+ with PanelDue 5i connected by ribbon cable to PanelDue header, and Makerbase MKS Mini12864 V3.0 (basically a clone of the Fystec) connected to the Mini 5+ LCD headers, which both work in RRF 3.4.6 and 3.5beta4.

Ian

It might be a cheating way out, but is there a way to maybe send the signal through a different pin for the Fysetc and just change it in the Arduino sketch? I'd rather not but if it's the last option, imperfectly done is better than perfectly not...

@droftarts Sorry, had it backwards. 3.4.5. Yes, if I disconnect the Fysetc board it works exactly as it should The Fysetc board works as it should regardless of whether the Paneldue is plugged in. I have also tried connecting the Fysetc board to the 10 pin ribbon cable pins while the Paneldue is connected to the 4 pin connector and vice versa. This is the first time I've connected the Fysetc board and it was done after updating the Duet/Paneldue firmware, so there wasn't an original to work off of. I heard that the Duet 3 had some separate hoops to jump through but they got it working as well. The board you've noted definitely looks different than mine, not sure it makes a difference? This is the board.

Any ideas? For reference this is the sketch that's on the Neopixel board. https://github.com/mule1972/NeoPixelBLVmgn

@deckingman It's always the dumbest things, isn't it...was missing the jumper. That solved it, thanks!

Update: looks like the data is showing with the ribbon cable, but not with the 4 pin cable like I originally had it attached...

Update 2: I've got a Fysetc Neopixel board that connects to UTXDO (pin 10 on the ribbon cable for the paneldue). It turns out that with the older firmware I was able to have the 4 pin cable's UTXDO connected to the paneldue and the UTXDO on the ribbon cable connected to the Fysetc board and they'd both operate ok (I think), but I guess with the latest update they don't jive. Would you have any idea how to solve? Maybe change the output on the Neopixel board?

As part of my printer update I've updated my Duet 2 Wifi to RRF 3.5.4 and DWC 3.4.6. As part of those updates my Paneldue was no longer displaying correctly. I've since updated it to firmware version 3.5.0 (it's a V3.0). I had to go through USB and Bossa through the terminal on MAC if that makes any difference. It's currently only showing "connecting", no tools, bed, control, etc.

A few notes:
It is set to 57600 baud
I've got "M575 P1 B57600 S1" in my config.g
When the printer starts up it does run through the list of errors and wifi connections so that indicates to me that it is receiving info and not a cabling issue.

Any recommendations would be very helpful, thank you!

@Phaedrux I did try another header and changed the M950 in doing so, also unsuccessful.

@Maestro thanks for the help, but still no go. Here's what I was running for reference. I also tried S1 and adding Q500 to no avail.

; Fans
;M106 P0 S0 I0 F500 H-1                             ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 F500 H1 T35                          ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P2 S1 I0 F500 H1 T35                          ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
M950 F0 C"duex.fan5"				   ; SAV - Added to Duex 8/3/23
M106 P0 S255 H-1					   ; SAV - Added to Duex 8/3/23

I've been rebuilding my printer and part of it includes upgrading my Duet 2 Wifi to RRF 3.4.5 and a Duex5. I've tried adding some fans which were originally on the Duet to the Duex as always on, but haven't been able to get them to work. I've confirmed the fans still work by plugging them into the always on pins on the Duet, so I'm thinking it may be a config issue? Below is my fan section of config which I thought was correct as well (fans in question are the ones plugged into duex.fan5), but evidently something is off...

; Fans
M106 P0 S0 I0 F500 H-1                             ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T35                          ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T35                          ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
M950 F3 C"duex.fan5"				  
M106 P3 S1 H-1