Topics created by TomasL

@Phaedrux Turned on, or reset

@droftarts

I think mainly that N-channel MOSFETs are better for fast switching, so are more suitable for PWM applications such as the heaters and fans.

I use P-channel MOSFETs a lot, but the fact remains that they dissipate much more heat - up to a magnitude more than the N-types -, so cooling becomes a major problem.

Instead of a common ground, you can have a common +V

Yeah, that's what, on the continent, British cars were famous of - or feared … 😊

@o_lampe we continue to manufacture the Duet 2 mainly for our OEM customers, and they don't want any changes to the connectors because then they would need to change their wiring looms.

Flash memory is now full on the Duet 2 and RAM is getting tight too. In RRF 3.5 there are likely to be new features that are not available on Duet 2.

@phaedrux thanks, i revised my custom end gcode which is where those lines were coming from and seems to fix the issue.

{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600 ;END Move print head up{endif} G1 X5 Y{print_bed_max[1]*0.8} F{travel_speed*60} ;END present print {if max_layer_z < max_print_height-10}G1 Z{z_offset+min(max_layer_z+70, max_print_height-10)} F600 ;END Move print head further up{endif} {if max_layer_z < max_print_height*0.6}G1 Z{max_print_height*0.6} F600 ;END Move print head further up{endif} M140 S0 ; turn off heatbed M104 S0 ; turn off temperature ;M107 ; turn off fan M84 X Y E ; disable motors

Standard RepRap should be fine.

@tomasl For example configurations, see https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_cartesian#homing-z

Ian

@tecno Yes I read the documentation, then I was instructed on another forum that I need to do an M500 command, obviously that was not correct.

@tomasl said in Bed leveling problems:

@norder
Will do, thanks.

very gladly

Occasionally when updating the wifi server it will fail silently. Reflashing again using M997 S1 usually fixes it, as you've found. Sorry about that.

Glad to hear the rest of the update seems to have gone well and you're DWC is now back in sync. I suspect that what may have happened was the opposite of what I originally expected. The DWC files were updated, but your firmware was not, so there was a cryptic message for the heater since DWC wasn't getting the response it expected from the firmware.

You can check that you have 3.3 firmware and DWC now by looking at the Settings > General and Settings > Machine Specific tabs in DWC.

@tomasl

I had issues trying to set a static IP as well. I finally got it to work with some suggestions. The steps seems to be very picky. See this thread,

https://forum.duet3d.com/topic/22703/duet-3d-wifi-set-ip-address/7?_=1621469740585

Ok, will do.

@TomasL said in Multiple problems:

Now, I got it working so far.
It seems that the IR-probe stopped to work though.
Well a minor problem.

Please start a new thread if you need help with that.

Ha ha!

I've done things like that also.

When I really try, I can get a USB keyboard plugged into the HDMI connector on my laptop.