Posts made by JonnyBrylcreem

Thanks for the info. I will swap my fans around when I get a chance

Good spot. That explains why I was controlling both fans! Thanks

I still don't get why I can only control the cooling fan, from the PanelDue, if the hotend fan is running though. It makes no difference from DWC.

I realise that under print conditions the HE fan will / should be running but it had me scratching my head until I realised it worked fine from DWC. I'd checked all my wiring and could see that the fan ran for a split second, when I powered the board on, so I was confident everything ought to work but it didn't appear to as far as the PanelDue was concerned.

Hi @aidar my fans are actually set up the other way around so the hotend is Fan 0, thermostatically controlled so it switches on at 45°C, and the part cooling is Fan 1.

Hi

I'm in the process of commissioning a new printer and have just noticed a weird cooling fan problem.

I am unable to control the cooling fan from the machines PanelDue unless the hotend fan is running. The PanelDue shows whatever speed you have set it to but it makes no change to the state of the fan. Changes to fan speed on the PanelDue do not appear to register with the DWC either. Apart from the fan all other commands from the PanelDue work correctly, as far as I can ascertain at present.

If the hotend fan is running then I can control the cooling fan from the PanelDue, but changes to the Fan speed, in the PanelDue Print tab, also appear to change the speed of the hotend fan as you can hear the pitch of the hotend fan whirr get noticeably louder. If you touch it gently the hotend fan feels to be spinning a lot faster too.

The cooling fan operates as I would expect from the DWC. I can operate the cooling fan with or without the hotend fan running and if the hotend fan is running then changes to the cooling fan speed in DWC do not impact on the speed of the hotend fan.

I am running Firmware version 3.1.1 and PanelDue Firmware 1.24 for a 7" integrated item.

config.g

I hope this makes sense. Any help you can give me in resolving this problem will be gratefully received.

Thanks

Jon

@Phaedrux I think you are probably right. I haven't had chance to test your theory yet, as I've been sidetracked trying to iron out all the other little issues, but it would make sense. As you say it won't stop me printing . I just couldn't figure it out and it bugged me.

So to clarify; after the probe triggers at 2.5mm off the bed the z axis then raises 5mm to end at 7.5mm above the bed

@droftarts thanks for getting back to me.
I'm fairly certain that the Z steps per mm are accurate. I measured the lift earlier and DWC inputs seem to translate to real world movements, as close as I can measure anyway.
The 7.5mm figure I was stating is a reading from the DWC which has me thinking it is a software issue rather than anything else.

Hi

This is driving me nuts and I've probably missed something stupid.
I've taken an Anycubic i3 Mega, gutted it and swapped the electronics for a Duet Wifi I had spare. Z and X axis homing is done by a Mini Differential IR board.

Everything appears to be working fine but whenever I run Homeall the nozzle lifts to 7.5mm above the bed at the end of the script. Trigger height is 2.5mm so something somewhere is causing the z axis to raise 5mm. I can't see what it is so if somebody can point out what I've missed it would be appreciated.

Config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 08 2020 14:00:34 GMT+0100 (British Summer Time)

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

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

; Drives
M569 P0 S1 ; physical drive 0 goes forwards X
M569 P1 S0 ; physical drive 1 goes backwards Y
M569 P2 S0 ; physical drive 2 goes backwards Z
M569 P3 S1 ; physical drive 3 goes forwards E0
M569 P4 S1 ; physical drive 4 goes forwards E1
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E413.79:420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y-25 Z0 S1 ; set axis minima
M208 X225 Y225 Z200 S0 ; set axis maxima

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

; Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
;M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X-20 Y-5 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:215 S20 ; 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 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed 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 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M143 H2 S280 ; set temperature limit for heater 2 to 280C
M307 H2 B0 S1.00 ; disable bang-bang mode for 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 S0 H-1 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 S"HE 0" 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
M563 P1 S"HE 1" D1 H2 F1 ; 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

; Custom settings are not defined

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Homeall.g

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 08 2020 14:00:34 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-230 Y-255 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-230 Y-255 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X25 Y0 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Thanks in advance

Jon

After updating Firmware to 1.21 and tweaking a few settings it now works fine. Thanks again

My bad, thanks a million

I'm in the process of swapping from a 0.8.5 board to Duet WiFi on my Ormerod 2.
As far as I can tell it should be a straight swap between the two boards and I've got everything working apart from I can't get the machine to home properly now.
The Y axis is fine as that's just a microswitch but I am having trouble with the X axis. It is using the standard Z probe that came with the machine and using that to home the x axis as well as the Z.
I see changes in the Z probe value when it gets close to an object so as far as I can tell it is working correctly but it doesn't want to trigger. When trying to home the X axis the head just wants to keep going and runs into the Z upright.

I'm using the standard files as supplied on the SD card and have swapped values that I was using on the 0.8.5 card (except I've probably missed something). Firmware version is 0.19 attached are my config and homeall files:

0_1527700605518_config.g

0_1527700626668_homeall.g

Thanks for the offer but I think I am going to pull my 0.8.5 board out my other printer, use a Duet WiFi (that I've never got around to using) in the Ormerod and then use the 0.8.5 in this delta

I can't figure out how to PM either!

Thanks for the sympathy....my own fault ,I should have been more careful.
I was rushing because that was the last hurdle to overcome before I got to try the thing out. I did exactly the same thing a few years back so I should have known better!

Many thanks........the problem has sort of resolved itself as I think I just destroyed the board.
I'm not 100% sure what happened but I must have shorted a couple of pins with the meter probe. Funny smell and the board no longer seems to be talking to anything

Thanks for the info, I will check it out.
I've just found this site which I think shows it https://emaker.io/documentation/fisher-build-instructions/electronics/

I am trying to wire a Duet 0.6 for use with a delta printer with a Smart Effector.
I have wired the part cooling fan to the FAN 0 and was planning on wiring the hotend fan to Pin 40 FAN V+ and Pin 39 FAN V-.
I don't see and power at these 2 pins. Do I need to configure these pins in any way, or am I just doing something stupid?
I guess I could always wire the fan straight to the PSU if it came to it but I don't really want to do that.
Any advice would be gratefully received

VICTORY IS MINE!

@dc42 @ayudtee @Phaedrux thanks for all your help.

@dc42 I had come to the conclusion it was a comms issue causing the reset as I had traced the fault to only occurring when the Ethernet port was connected to the network.

I've given the board a static IP address and that seems to have cured the problem. I'm afraid I was unable to look at the "last reset reason", the board just didn't want to report back.

I will give the new firmware a go at some point, first of all I want to finish putting the printer together and try to get it to print something!

Thanks again

Jon

I think the first problem that I need to address is that the board keeps resetting itself since I have flashed firmware 1.21 to it.

I previously thought it was just the fan dropping in and out but having tried to connect to Pronterface I can see that the board will initially connect and then after about 30 seconds it seems to disconnect. All the LED's go out on the board, the hotend fan shuts down and then everything powers up again. This process then just keeps cycling.

I get the following message on Pronterface:

I've tried re-flashing the board but I get exactly the same problem.

I don't think the board stays powered up for long enough before resetting to even try to connect to the router.

Any ideas please?

@ayudtee that was the format that I cut and pasted in, it made no difference. I wondered if it was because my router already had that MAC address in memory from my other printer so I tried changing the last "ED" to "00". Still didn't work.

I'm bound to have done something stupid, I just can't figure out what it is though.

Cheers for the help