Topics created by FL630

@fcwilt said in Z Probe - Mesh levelling and nozzle location?:

@fl630

There are a few things that change when configuring v3 firmware compared to v2.

For example, in v2 the pin names for things are specific like estop1.

In v3 the hardware has generic pin names like io3.in.

You use the command M950 to specify what pin you want to use by it's generic name and what you want to use it for.

For example M950 H1 C"out1" Q100 T1 creates heater 1 (the H1 parameter) using pin out1 (the C parameter). The Q parameter specifies the PWM frequency and the T1 parameter specifies which temperature sensor to monitor.

The link below should help:

A "how to" guide for configuring with v3

Aside from the actual changes you need to make to your configuration you need to upgrade to v3.3 (the most recent in two or three steps.

For example, I was starting from v2.05.1.

But for technical reasons you have to go from 2.05.1 to 3.0 and then from **3.**0 to 3.3

The link below should help:

A "how to" guide for updating firmware

Frederick

Thanks Frederick. I've just been reading those articles, prepping for the update whilst a print finished. I think what I might do is update the firmware then re-install the settings using the reprap configurator as it's easier for slightly clueless folk like me. From there I can jump into config.g and the others I've edited manually to adjust things as I have done for the current settings.

👍 👍

My guess is that it's caused by interference from another device. See https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors, especially the bit about trying a different WiFi channel.

@jay_s_uk said in Duet Web Control temp feedback and gcode freezing:

H0 is the bed.
H1 is the first hot end

My bad, a typo. Even with a 750w mains bed I think I'd struggle to get even half way to 215 degrees bed temp!

It seems to freeze up when I put in gcode through the gcode console. Quite easy to replicate.

New board arrived today @dc42, thanks to E3D's excellent service. Thank you for approving the replacement.

I've wired it all up as per the old board and the U3 chip is still in one piece. Can I ask what could cause the U3 to burn out so I don't replicate the same mistake? Could it have just been faulty or is it likely something I may have done? I'd really like to avoid another fried 5v rail!

That looks like a modified version of an old calibration test for Marlins linear advance. It draws a series of lines back and forth with varying amounts of pressure advance and you're supposed to find the line that gives the most even start and stop.

I haven't had much luck with it, as all the lines look basically the same, but I don't use much PA to begin with on a direct drive. For a bowden system it may be more apparent. There's also the issue that it's only a single first layer so it's likely to be squished down a bit which isn't a great real world test.

I think a better way to test would be to print a slightly more complex model with some height and varying the PA value every 10 layers or so, then you can get a better idea of the changes as the model progresses. You can either insert the PA command into the gcode file, or issue it manually from the gcode console.

If you have a PAnelDue, something like this can be very handy for live tuning. https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance

There's also this script for trying to find a good PA value.

https://forum.duet3d.com/topic/6698/pressure-advance-calibration