Topics created by Kolbi

@Kolbi said in Request 'Admin' account/password for DWC:

I would like to see the addition of an 'Admin' password for DWC.

Just like any other computer system, creating a separate admin account allows for the proper separation of duties and configuration/security. Of course I want end-users to use the device but they shouldn't be able to change the system files or macros unless it is warranted and approved, or they agree to take full responsibility.
Far too many times someone comes along who is smarter, and knows better, that just cannot keep their hands out of the 'cookie jar' and inadvertently causes damage – firsthand experience, both sides of the fence. And yes, I know that a person can simply remove the sd-card and make changes, but that is a bit different - in this case the person would have to take the time and effort to open the machine, break the tamper seal, and then own the potential problems to be faced with.

Cheers,
Kolbi

Hi,
same suggestion from my side: I´ve build a printer with/for students and I am sure on the long run that is a good way to go. For now the only workaround is that e.g. you can only allow them to use paneldue, but of course with the new nice plug-ins even though I haven´t visited the place for months (the local workshop stuff is now in charge for it) I am sure something like that needs to be done. Because I am not sure that even on the longrun paneldue will get the plug-ins that DWC is getting...

Verified sd-card / reformatted via tool from https://www.sdcard.org/downloads/formatter/
M39: SD card in slot 0: capacity 31.72Gb, free space 31.55Gb, speed 20.00MBytes/sec, cluster size 32kb

From ideaMaker settings I have changed minimum segment length from .01mm to .1mm, yielding no appreciable change in look_ahead underruns.

Sliced the same part in PrusaSlicer, yielding no to ~5 look_ahead underruns whereas ideaMaker yielding 50-60.

All the while, the part is coming out absolutely fine - no defects.

My conclusion can only be that look_ahead underruns are not critical. Simply a number representing the number of times that RRF has 'optimized' the gcode, amending unneeded deceleration-only moves, before the physical planning process.

@dc42, Please correct me if I am wrong.

Cheers,
Kolbi

@Nxt-1 Hehe, currently I have all the required hardware on-hand but my workload picked up and I haven't had the chance to mess around with it.
With that being said, the printer has been getting used often and the print quality has been fantastic, so I'm a little hesitant(scared) to modify it at the moment. I'll probably get it done during the upcoming holiday break, fingers crossed.

@dc42, I searched through the forum a bit more and discovered answers to most of my curiosities - apologies for wasting your time.

https://forum.duet3d.com/topic/10823/maximum-safe-pwm-fan-frequency

This was interesting:
https://forum.duet3d.com/topic/1000/can-t-get-fan-to-run-at-anything-but-full-speed/13:
Another option is to put a R-C filter in series with the fan so that the PWM gets smoothed out and you drive the fan with a variable voltage. Connect a resistor of between10 and about 200 ohms between the Duet fan output and the fan. Also connect a capacitor of at least 100uF in parallel with the motor.
I find it very hard to believe that the same motor works with RAMBO. The RAMBO board has a flyback diode in parallel with the fan output, but apart from that it has nothing else that would make a difference.
Standard Arduino PWM frequency is about 490Hz, but I don't know whether Marlin uses that or alters it.
This is a good read: https://www.allaboutcircuits.com/technical-articles/low-pass-filter-a-pwm-signal-into-an-analog-voltage/

If all else fails and fan does not like PWM out you can place a low-pass filter to smooth the pwm output into an analog signal-'ish', but what PWM freq to use and how does fPWM equate to fc? I'm reading that the highest possible PWM freq yields the best performance of the filter but how does the correspond to fc / or does it at all?
non-pwm_fan.png

So what I gather from all this – a high pwm frequency shouldn’t be detrimental to the controller board or the fan, in most cases it will have an effect on noise and speed limitations on either end of the spectrum. If it works, it works.

@fcwilt said in Faster / Better home-z possible?:

Hi again.

Just FYI did you know you can force the averaging of a fixed number of readings?

For example A5 S-1 will cause 5 readings to be taken and the average computed.

Frederick

Thanks Frederick - did not know that!

@bot Thanks bot!

@e4d Sorry, It's been a while and I don't have that on my latest laptop. I'll give a search on my home server when I get a chance to see if I may have backed it up.
But, give a look at the caribou github - variants from duet 2 and 3mini exist.
https://github.com/Caribou3d/CaribouCartesian/tree/master/STL/01_full-kits/Frame/Duet

Hope that helps!

Top post edited with BLUF.

Forgot to mention, if you are going to use the output for use in a code block within this forum, you'll need to do either of two things...
Replace

echo "\`\`\`g-code" >> /Users/me/Desktop/dump.md

with

echo "\`\`\`" >> /Users/me/Desktop/dump.md

-or-
Open the output file in a text editor, and do a search/replace; search for ```g-code and replace with ```

@Kolbi said in Random number generation with Meta Commands?:

@dc42 said in Random number generation with Meta Commands?:

It will be in the 3.02beta releases.

Nice! Is there a list of new expected features?

You can see what is already implemented or partly implemented at https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md.

@zapta I didn't think about that particular facet, but I do think it should all get thrown into a backup and restore function.
I typically work with industrial and military systems where this functionality is a hard requirement - granted; the duet2 is not either of these categories. Still, people do rely on them to get a job done, so it is warranted in my eyes.

@gnydick Thanks much, this is what I normally do.

Starting from software version 3.2 (currently still beta) you'll be able to browse the object model using a DWC plugin.

I think what you're looking for is move.extruders[0].filament.

@donstauffer I've added this or an equivalent facility to the firmware wishlist for consideration in RRF 3.4.

@dc42 Thanks so much!

@OwenD
That, and variables, will be very cool!

Granted, my coding skills are barely existent but I can usually make something useful - just not the most elegant. 🙂