Posts made by Nappen

@jay_s_uk Thank u that did the trick. i feel abit foolish now haha

So i have had this working on this machine before so i know it did work.
When i push the probe it triggers under Status the probe goes from 0 - 1000
When i run G32 the machine homes and just keeps going. even if i push the probe it ignores it and just rams the hotend down in the bed.
and i cant for the life of me figure out why this is happening. and with new arms i need to do a delta calibration. only time i use the probe.

Config.g
M550 P"Anycubic Delta" ; set printer name
M665 R120 L286 B110 H280 ; 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

; Z-Probe
M558 P5 C"^zprobe.in" H10 F200 T2400 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z15.9 ; set Z probe trigger value, offset and trigger height
M557 R120 S20 ; define mesh grid

My Bed.g
; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Sep 03 2020 07:38:58 GMT+0200 (centraleuropeisk sommartid)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 12 peripheral and 3 halfway points, and perform 8-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y109.36 H0 Z-99999
G30 P1 X52.16 Y90.34 H0 Z-99999
G30 P2 X87.5 Y50.52 H0 Z-99999
G30 P3 X99.92 Y0 H0 Z-99999
G30 P4 X87.5 Y-50.52 H0 Z-99999
G30 P5 X52.16 Y-90.34 H0 Z-99999
G30 P6 X0 Y-109.36 H0 Z-99999
G30 P7 X-55 Y-95.26 H0 Z-99999
G30 P8 X-95.26 Y-55 H0 Z-99999
G30 P9 X-110 Y0 H0 Z-99999
G30 P10 X-95.26 Y55 H0 Z-99999
G30 P11 X-55 Y95.26 H0 Z-99999
G30 P12 X0 Y53.84 H0 Z-99999
G30 P13 X40.39 Y-23.32 H0 Z-99999
G30 P14 X-47.63 Y-27.5 H0 Z-99999
G30 P15 X0 Y0 H0 Z-99999 S8
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

@Phaedrux well i wanted to have them turn on automaticlly now i have to sitt and babysitt the first 2 layers just to wait untill layer 3 to kick the fans on.
that´s why i asked if it was possible to detect when the normal partcooling fan kicks on to also kick on the side fans.

now i have a macro that i start and stop the fans with buth i wanted it to be automaticcly

They are partcooling fans. that help cool bigger parts when i print fast so i have one on each side.
so i need to be able to shut them off when printing petg because they blow to much and make petg warp.
i tested changing pwm freq buth its prettty much the same the fans make weird noise no matter what i set.

Firmware i use is 3.2 b4 and i run duet wifi 1.03 with duex2

So i try´d to figure out a good way to solve this. but im stuck.
I Have a M106 fan that is pwm controlled and i have 2 bigger 80mm fans on the side with airducts aimed at the nozzleheight to get more cooling. they really dont like pwm and anything under 100% makes them scream digital noise.
Is there a simple way to make fans "see" that m106 is started and automaticlly turn on 2 fans on full?

@bearer said in esp32cam 5v power from expantionboard/duex 5:

the total 5v is what matters, but if the esp is the only additional 5v load its not a problem. there is just the one 5v source regardless of where you connect to on the duet (albeit there is a little difference in the length and width of the track, but for 300mA it doesn't matter).

what i can find by google
Turn off the flash lamp:180mA@5V; Turn on the flash lamp and turn on the brightness to the maximum:310mA@5V; Deep-sleep: Minimum power consumption can be achieved 6mA@5V; Moderm-sleep: Minimum up to 20mA@5V; Light-sleep: Minimum up to 6.7mA@5V

but i will remove the ledlamp as i dont need it so 180ma should be the load

so i ordered 2 esp32cam moduels just because they are able to output jpg stream to have a webcam on my printer to be able to look at them when im not in the room.
is it safe to run a esp32cam that draw maximum of 310ma 5v or is there another source on the duet that are more sutible?
1 of the printers will run a duet wifi 1.02 + duex 5
1 and one just runs a duet wifi 1.03

tried to find a suitable answer. but could not find any

@dc42 said in Panel due v2.0 stopt working bit works with usb:

@Nappen said in Panel due v2.0 stopt working bit works with usb:

o not at all neither look damaged but might be easy to just order them and swap them and se.
or is there any values that i can messure? i thr warrenty is already gone and i have some soilder skills. bust reslly bad at fault hunting.

Check L1 with a multimeter on the lowest resistance setting. It should have a very low resistance.

Check D2 using a multimeter on the diode setting.

BTW we are expecting to have new PanelDue firmware soon, to remove many of the limitations of the existing firmware. The new firmware will only work with RRF3 and it will probably be too large to run on version 1 and 2 PanelDue boards.

then i solve this board with scarapping it and getting a new thanks for the heads up

and i dont know if it helps but i tested it on a duet wifi 1.03 board

@dc42 said in Panel due v2.0 stopt working bit works with usb:

The V2.0 schematic is at https://github.com/dc42/PanelDue/blob/master/PCB/V2.0/schematic-2.0.png. UAB power feeds the power rail via D1, whereas power from the 4-pin connector goes via D2 and L1. So if it works on USB power, the fault must be with D2 or L1. Does either of those components look damaged?

The jumper should always be on 3.3v for common types of display. The version 3 PanelDue doesn't have the jumper, it's 3.3V unless you cut a trace and add a link.

no not at all neither look damaged but might be easy to just order them and swap them and se.

or is there any values that i can messure? i thr warrenty is already gone and i have some soilder skills. bust reslly bad at fault hunting.

@Phaedrux said in Panel due v2.0 stopt working bit works with usb:

Are you trying to connect via the ribbon cable or the 4 wire cable?

Have you tried connecting it to the duet while it's being powered by the usb? You might be able to test if it's working at all or if something more is fried.

Posting some close up photos of both sides of the PCB could help to see if something is burnt.

i connect it with the 4 wires.
and yes if i connect the 4 wires and use a usb cable for power it works no problem i can controll the printer from it.

did not even knew that it was possible to rum the screen of a ribbon cable might try it out. should the jumper be 3.3 or 5v when connecting it with a ribbon cable? so i dont fry anything else

so i have an old 4.3" display with a panel due v2.0
after missing the 5v jumper on the paneldue and connected it to a skr board with lcp-rrf it dies. probably a tiny puff off smoke came.
now the weird part if i connect a usb cable to the paneldue the screen works and can controll the printer but it cant get its own power? what could be the burnt component is it worth trying to repair or should i just get a new paneldue?

I was building a purge macro and found that it was possible to add jog buttons for xyz but not for extruders?

would be nice to have the possibility to run the extruder there as well.
so u could have say

G1 E50 f600
M291E P"message" R"message S3
G1 E-6.5 f600
M400
M292

so if u swap a filament and it did not fully clear out the old colour u could purge more in the message jog and then press ok to complete it.

So after a long time off running 1 extruder and 1 hotend. i decieded to connect another steppermotor on my duex 5 and use my Y-splitter.

buth something messes up.

This is my new config. i will post the old that works downunder.
The problem i get is that when i upload my new config. the motor just shake. vibrate does not move back or forward. buth i tryd to find the problem so i probably become blind. anyone that can see what i have done wrong this time?
It´s the same motors as in the rest of the build. if i test the "new" motor with moving the cable with my stock firmware it works. and its the same problem with tool 1 and tool 2

if it helps it´s a Duet Wifi 1.02 with a Duex 5 expantion board.
firmware is 1.21

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Feb 28 2018 08:15:50 GMT+0100 (Västeuropa, normaltid)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

M667 S1 ; Select CoreXY mode

; Network
M550 PHypercube ; Set machine name
M551 Preprap ; Set password
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S1 ; Enable Telnet

; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S0 ; Drive 4 goes backwards
M569 P5 S0 ; Drive 5 goes backwards
M569 P6 S0 ; Drive 6 goes backwards
M350 X32 Y32 Z16 E16:16 I0 ; Configure microstepping without interpolation
M92 X160 Y160 Z3200 E407.5:407.5 ; Set steps per mm pi3 134.5 bd87.9
M566 X600 Y600 Z12 E120:120 ; Set maximum instantaneous speed changes (mm/min) old xy 900
M203 X9000 Y9000 Z300 E1200:1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z100 E250:250 ; Set accelerations (mm/s^2)
M906 X900 Y900 Z1000 E1000:1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

M584 X0 Y1 Z2:3:4 E5:6 ; three Z motors connected to driver outputs 2, 3 and 4
M671 X330:-30:-30 Y150:255:45 S10 ; leadscrew position

; Axis Limits
M208 X5 Y5 Z0 S1 ; Set axis minima
M208 X300 Y300 Z450 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S1 ; Set active high endstops

; Filament Sensor
M591 D0 P1 C3 S1

; BLTouch - Heaters
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.

; Z-Probe
M558 P7 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P600 X20 Y0 Z1 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S20 ; Define mesh grid

; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S275 ; Set temperature limit for heater 1 to 275C

; 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 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; 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 saving after power loss is not enabled

; Custom settings are not configured

This is my old config that works with a single extruder.

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Feb 28 2018 08:15:50 GMT+0100 (Västeuropa, normaltid)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

M667 S1 ; Select CoreXY mode

; Network
M550 PHypercube ; Set machine name
M551 Preprap ; Set password
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S1 ; Enable Telnet

; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S0 ; Drive 4 goes backwards
M569 P5 S0 ; Drive 5 goes backwards
M569 P6 S0 ; Drive 5 goes backwards

M350 X32 Y32 Z16 E16 I0 ; Configure microstepping without interpolation
M92 X160 Y160 Z3200 E407.5 ; Set steps per mm pi3 134.5 bd87.9
M566 X600 Y600 Z12 E120 ; Set maximum instantaneous speed changes (mm/min) old xy 900
M203 X9000 Y9000 Z300 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z100 E250 ; Set accelerations (mm/s^2)
M906 X900 Y900 Z1000 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

M584 X0 Y1 Z2:3:4 E5 ; three Z motors connected to driver outputs 2, 3 and 4
M671 X330:-30:-30 Y150:255:45 S10 ; leadscrew position

; Axis Limits
M208 X5 Y5 Z0 S1 ; Set axis minima
M208 X300 Y300 Z450 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S1 ; Set active high endstops

; Filament Sensor
M591 D0 P1 C3 S1

; BLTouch - Heaters
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.

; Z-Probe
M558 P7 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P600 X20 Y0 Z1 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S20 ; Define mesh grid

; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S275 ; Set temperature limit for heater 1 to 275C

; 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 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; 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 saving after power loss is not enabled

; Custom settings are not configured

everytime the machine changes something i get this annoying message poping up. is it possible to disable?
and it always mention the older print in the
(I) Finished printing file 0:/gcodes/switch_mount.gcode, print time was 0h 49m
file o:/gcodes/3DBenchy.gcode selected for printing.
it´s popup now and then often when speed, fan or extruder settings are changed. so when i have verible settings on the fan that messange bombards my screen.

it´s my wifi board. and yes my plan was to power it from the expansion connector. not board. blame it on im a swed

so pin 8 for signal. 220uf capacitor shoult not be that hard:D then i go on to stage 2 and wire it up after a visit to the hobby store.
Thanks again dc

So i have started to make a simple toolchange that pretty much just going to move a plate with 2 bowden fittings so i can have 2 filaments with 1 hotend. or more later on.

i have seen people connecting
gnd and +5 v on pin 1-2 on expantion board.
and signal to pin 21.

is this correct?
and then in the config if i understand correct. i should add.
m307 H3 a-1 c-1 d-1

and then to controll the servo motion with
m280 p3 s10 T1?
is this correct?

so for example if
"tool 1 is at 10degree of the servo i put in
m280 p3 s10 T1

and when chaning to to tool 2 i add
m280 p3 s90 T1 (if the servo need to be 90degree for position 2?

i have your case that u uploaded from thingiverse. no connection between the frame and the screen.
the display worked it was just i started to se if i could avoid because it sucks that printing a 36h print and after 34h get a failed because the printer got a hickup o i started to remove unused stuff. to se if that was giving problems. and now without the screen connected. the printer has printed pretty much 24/7 no hickups. no freezing.
the reason i updated was that i tought it maybe was useful information for u. and maybe a firmware issue that makes a memory error or memory overload between as u said in the start it has happened on ethernet boards buth not on the wifi boards before.
and just by removing the display the problem is gone.
and it seams that the most of the duet users dont run the paneldue. so maybe it is that the error is a interface problem between duet and panelduo.
so it was more a heads up if u try to solve the problem.

I only run a 24v into the the duet so it´s getting it from the built in regulator

only the 4 wires that are connected as it said in the wire manual?