Topics created by jckray

Very embarrassing, but it appears I had a typo in my IP address and even though I thought I had double-checked, I somehow missed it. Everything is working just fine. Can access DWC from my computer while it's using 5ghz even though the duet is using 2.4ghz.

Feeling pretty stupid lol 😐

@jckray I haven't tried myself, but documentation is here: https://duet3d.dozuki.com/Wiki/Duet_2_Maestro_12864_display_menu_system#Section_File_format_for_image_command

Ian

@phaedrux I forgot about start.g, thanks for reminding me! I will give that a go.

@phaedrux Will do, thanks!

@Phaedrux Yeah super strange!

@Phaedrux Thanks!

@Phaedrux Gotcha didn't know that existed. Just checked and I have zero hiccups on the current print I'm running, but there haven't been any issues with the current print thus far. I will make sure to check that next time there is an issue.

@jckray did you checked the SD socket to CONN_SD? Did it work?
what did you use? I have the same issue and will fix it in the same way but I don´t know which SD extender is the right one.

This will be possible when conditional GCode is implemented. The latest ReprapFirmware 3 beta includes the basis language support for conditional GCode. Now I need to implement the full object model and a few more commands.

Hi, did anybody actually get this working with daemon.g or other means?

PS - I just did some tests on the Duet WiFi on my bench:

1K resistor reads -2.7C to -3.0C. It should be 0.0C, so if my resistors are accurate then it is under-reading by almost 3C.

2K resistor reads 266.9 to 267.6C. It should be 266.3C, so if my resistor is accurate then it is over-reading by about 0.5C.

These are with zero L and H correction. I then tried the same resistors on a Duet Maestro:

1K gave -0.8 to -1.0C (under reading by 0.9C)
2K gave 270.3 to 270.7C (over reading by 4.2C)

The Maestro can measure PT1000 sensors more accurately. I think I may be able to improve on the error at low temperatures on the Duet WiFi.

@frank26080115
Okay, thanks.

I was mostly looking to see if anyone in the community had already done some work on the last two bullet points you mentioned.

You right pictures or redrawing is probably the best route at the moment.

You could connect a resistor in series with the fan.

@arhi said in Time Estimates Idea:

simulatedTime? Is this time calculated like pushing file trough the actual RRF system simulating how fast it would exec it or?

That's right. You can run a simulated print and it will do a faster than real time run through of the entire gcode file. Don't interact with the duet during the simulation. It's much faster than real time, but with really long multi-day prints it's still going to take a long time to simulate.

I've found that PrusaSlicer and Cura are already really accurate with their estimates when you're setting the acceleration and jerk values in the slicer. Cura also has a printer settings plugin that lets you set max feedrates etc. I find them to be within 20 minutes on a long print. Which is the same as the amount of time it might take to simulate it first.

@phaedrux have not tried 2.04 rc1 yet. I will test it

@dc42

Okay I got it to work. I was powering off the Duet after erasing and resetting the panel, which gives the white screen state. In this state, it does not seem to work.

What did work.

With the Duet powered on and plugged into the panel hold the erase button on the panel for a few seconds press the reset button on the panel DO NOT power cycle the Duet The panel will remain on, displaying as usual Bossa will now recognize the panel via it's serial port Upload the new panel firmware as usual via Bossa When complete, unplug the usb from the panel and power cycle the printer.

@phaedrux said in Power Loss Recovery and Power Supply Question:

I've seen it mentioned that you can add your own capacitor, so it is possible, but I'm not familiar enough with it to suggest what kind of capacitor or how to attach it.

That's right. Most PSUs have 3 sets of + and - output terminals. if one of those pairs is spare, the simplest way is to connect the capacitor to those spare terminals. A capacitance of 10000uF rated at 35V should help. be sure to get the + and - connections the right way round, or the capacitor will explode.

@jamesadoty said in [Solved] Calibrate Z-probe macro:

@jckray

I like your script though. It shows how powerful Reprap firmware really is.

Several times in the past I have read a request on the forum of the form "Can the Duet/RRF do X" and my impulse was to respond No, that would require a firmware change. But then I have thought of a way to do it using RRF features, in particular macros, additional axes and tool definitions. Cases in point:

Homing multiple axis motors using a separate endstop switch for each motor Doing mirror prints on an IDEX printer Extruding until an endstop switch is triggered Measuring Z probe repeatability