Topics created by vwegert

@vwegert is that a positive babystep? If so, then you are correct about the change.
It won't affect anything in terms of using the smart effector

@vwegert said in LEDs with 5V fans?:

@fcwilt The conversion is done, there is no point in arguing about the fans any more (which I believe should have been made clear by my post). 12V fans would have been possible, but I would have had to add another voltage converter for all fans to my system.

I apologize for trying to be helpful - I won't in the future.

I also connected an accelerometer to my Duet 2 Wifi, and the first attempts with a so-so cable mostly worked with low speeds, but had dropouts when reading data. Try to add the Q parameter with a slower speed (less than 2MHz which is the default) or use a better cable. I finally used a USB3 cable and now I'm able to use it without a problem.

@vwegert I think a couple of things happened at the same time, which caused the problem:

You uploaded the 3.3 zip file under 3.2, so files get put in the 'sys' folder The update to 3.3 went okay for firmware and DWC The WiFi firmware failed to update (it happens, there's no error checking in the ESP firmware update process) Now on 3.3, you tried to update the WiFi firmware again, but the firmware folder hasn't been created (it only happens if you subsequently upload a firmware zip or bin file in 3.3), so the firmware can't find a relevant file.

You found one workaround, which is to create a firmware folder and add files. You can also (since RRF 3.3beta2) use the 'P' parameter in M997 to provide the absolute path and filename to use. See: https://duet3d.dozuki.com/Wiki/Gcode#Section_M997_Perform_in_application_firmware_update

Ian

The magnets seem to be nickel plated and the ballstuds are chrome plated. Easy to see where's more wear.
The tape solution seems the best workaround. (maybe punch a hole in the center of the tape to avoid contact to the magnet?)

@SIam said in first layer extrusion (?) issues:

@vwegert Have you tried to clean your print bed ? For me, it looks like that you have some fat or oil on the bed

I usually clean the print bed once every 5 prints or so. I just cleaned and de-greased it again, with very little effect.

Got it. I recently moved the printer to a new place - from one flat and level surface to another - and I didn't bother to re-level it. That came to bite me now - one of the corners (the front right) was considerably lower than the other ones, introducing a twist into the entire frame that was really hard to spot. Re-leveled the feet, now everything is back to normal (pun intended).

I also use the Path Workbench of FreeCAD together with a Duet CNC. Here I use the Marlin or the GRBL postprocessor, both work quite well. You might have to delete some G-commands from the file that the Duet does not know.

I have also looked into writing a postprocessor for the Reprapfimeware myself. What are the special features of the Reprapfirmware compared to Marlin or GRBL?

The postprocerssors of Freecad can be found here:
https://github.com/FreeCAD/FreeCAD/tree/master/src/Mod/Path/PathScripts/post
Take the one from Marlin and adapt it for the Reprapfirmware. With the wonderful gcode reference from:
https://duet3d.dozuki.com/Wiki/Gcode

@dc42 said in Delta: temporarily lift work envelope restriction:

M564 S0 should do what you want.

It does, thank you very much

@dc42 said in Store and recall WCS offsets?:

@Danal said in Store and recall WCS offsets?:

Note: This does not appear to be working (yet) in RRF3.

I presume you mean RRF3 on Duet 3 with attached RPi? It should be working in standalone mode and on Duet 2.

Good clarification. Yes, RRF3 on D3+Pi was the test environment where it puts in a comment but no actual G commands. I'm presuming from the comment that the rest of the code will come to that environment soon.

@vwegert without checking the datasheet i guess that pin defaults to high and the firmware enables an internal pull down. If you want to prevent it going high then try an external pull down resistor. 4K7-10K should do it.

(please test without Z probe in position to be flung)!

When Adrian Bowyer was developing the first firmware for the Duet, I tried to get him to put a bullseye similar to Pronterface's into RepRapFirmware, to make it easier for people transitioning from Pronterface! Never happened...

Ian

for the filament uses yes, the comments are used.

https://github.com/dc42/RepRapFirmware/blob/d9f051b6c658fa278b22535a8bd03d124bcf8fad/src/Storage/FileInfoParser.cpp#L651

@vwegert I know that problem. I have to lower the PWM frequency down to 10Hz to get it to run decently. Use

M106 P0 S0 F10 C"Part Cooling Fan"

in your config.g as @Phaedrux already mentioned.

P0 stands for the fan port 0 S0 says leave the fan off at startup of the machine F10 sets the PWM frequency in Hz C"name" assigns a name (optional)

Adjust these to your requirements.

@aidar Thanks - my Google sub-system might still be asleep...

Thank you for your response. It's a good idea.
It works. In config.g I wrote:
M581 T2 E0 S0;

and in
trigger2.g :
M80 ;
M581 T2 S-1;
M581 T3 E0 S0;

trigger3.g:
M81
M581 T3 S-1;
M581 T2 E0 S0;

There is one drawback to this solution.
When the M80 or M81 is executed in a different way, eg via Web or g-code printing, the button must be pressed twice.
Thank you for your help and I will be grateful for other suggestions.

@vwegert I kind or forgot but I actually made a video of my purge bucket in action. If it's any use, check it out here https://www.youtube.com/watch?v=zNNmZCXErYY&lc=z234cfh4dkylhh4ra04t1aokgl1ownrihxxz0fiwil5xrk0h00410

@vwegert said in Ideas for more realistic bed temperature control:

@dc42 Now I wish I had a FLIR to see how uniform the temperature really is on the surface and how far in I would have to go to get a realistic measurement... A shame that these things are so expensive...

I looked into buying one of those and from I have been able to deduce the precision of a FLIR is not that good. A spot measuring tool is much cheaper and far more precise. Do that's what I use now. It takes a lot more time to measure the whole bed though...

Nice! how does it fly?

I've been toying around with the idea of a CF/PETG hybrid drone frame.

If it's a blatant spam flood such as we had this morning, it's not necessary. If it's a subtle spam post tacked on to the end of an existing thread, then we may otherwise miss it, so please report it.